Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 9.846687316894531e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0007493495941162109s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.34181761741638184s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.6411993503570557s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.0005445480346679688s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.621246337890625e-05s
INFO | --- Analysis for 0080-3626 took 5.59399151802063s
Availability | SPARQL endpoint availability check for 土地利用图 took 9.942054748535156e-05s
Availability | VoID file availability check for 土地利用图 took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.2637064456939697s
Reputation | Calculation of the PageRank for 土地利用图 took 0.022349834442138672s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0013947486877441406s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 6.103515625e-05s
Believability | Calculation of trust value for 土地利用图 took 1.6689300537109375e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 2.6454660892486572s
Availability | SPARQL endpoint availability check for 113322 took 5.841255187988281e-05s
Availability | VoID file availability check for 113322 took 0.0007801055908203125s
Completeness | Calculation of interlinking completeness for 113322 took 0.292924165725708s
Reputation | Calculation of the PageRank for 113322 took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for 113322 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for 113322 took 4.076957702636719e-05s
Believability | Calculation of trust value for 113322 took 1.2874603271484375e-05s
INFO | --- Analysis for 11 took 7.562539577484131s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 8.940696716308594e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0002224445343017578s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.2881309986114502s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.022243976593017578s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.409385681152344e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.0728836059570312e-05s
INFO | --- Analysis for 12323 took 2.6073355674743652s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0745701789855957s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.00020360946655273438s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.26818418502807617s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020480871200561523s
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.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 9.107589721679688e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 5.9604644775390625e-06s
INFO | --- Analysis for 2000-us-census-rdf took 2.6088857650756836s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 2.3659844398498535s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.28316450119018555s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.02084493637084961s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.124641418457031e-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.8614795207977295s
Availability | SPARQL endpoint availability check for Open Data Web took 33.281919956207275s
Availability | VoID file availability check for Open Data Web took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.3082287311553955s
Reputation | Calculation of the PageRank for Open Data Web took 0.0205230712890625s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.361701965332031e-05s
Believability | Calculation of trust value for Open Data Web took 1.049041748046875e-05s
INFO | --- Analysis for _data.odw.tw took 43.88214468955994s
Availability | SPARQL endpoint availability check for 土地利用 took 4.363059997558594e-05s
Availability | VoID file availability check for 土地利用 took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.2966773509979248s
Reputation | Calculation of the PageRank for 土地利用 took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.075599670410156e-05s
Believability | Calculation of trust value for 土地利用 took 9.5367431640625e-06s
INFO | --- Analysis for _data1.odw.tw took 2.6594676971435547s
Availability | SPARQL endpoint availability check for 土地利用模型 took 8.702278137207031e-05s
Availability | VoID file availability check for 土地利用模型 took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.29924964904785156s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.021876096725463867s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.9325485229492188e-05s
Believability | Calculation of trust value for 土地利用模型 took 9.5367431640625e-06s
INFO | --- Analysis for _data2.odw.tw took 5.108903646469116s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.988380432128906e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.29413676261901855s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007245540618896484s
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.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 4.056140899658203s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 8.940696716308594e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.27443647384643555s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.0279159545898438e-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.225221633911133s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 0.00014495849609375s
Availability | VoID file availability check for ITS TEST DATASET took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.29933953285217285s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.021522998809814453s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.218650817871094e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 7.867813110351562e-06s
INFO | --- Analysis for A1 took 3.753599166870117s
Availability | SPARQL endpoint availability check for SummerOlympics took 2.1396632194519043s
Availability | VoID file availability check for SummerOlympics took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.30739378929138184s
Reputation | Calculation of the PageRank for SummerOlympics took 0.020462751388549805s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.413459777832031e-05s
Believability | Calculation of trust value for SummerOlympics took 1.1205673217773438e-05s
INFO | --- Analysis for abc took 8.846845149993896s
Availability | SPARQL endpoint availability check for Test_m took 9.679794311523438e-05s
Availability | VoID file availability check for Test_m took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Test_m took 0.28777408599853516s
Reputation | Calculation of the PageRank for Test_m took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for Test_m took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.075599670410156e-05s
Believability | Calculation of trust value for Test_m took 1.2159347534179688e-05s
INFO | --- Analysis for ABC took 2.790959596633911s
Availability | SPARQL endpoint availability check for my intro took 8.726119995117188e-05s
Availability | VoID file availability check for my intro took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for my intro took 0.32273054122924805s
Reputation | Calculation of the PageRank for my intro took 0.02087569236755371s
Interlinking | Calculation of Degree of Connection for my intro took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for my intro took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for my intro took 3.0994415283203125e-05s
Believability | Calculation of trust value for my intro took 1.1920928955078125e-05s
INFO | --- Analysis for abhay_intro took 2.7534780502319336s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.17289161682128906s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.31310367584228516s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.020368576049804688s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010085105895996094s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for abs-linked-data took 2.9302735328674316s
Availability | SPARQL endpoint availability check for AcadOnto took 9.036064147949219e-05s
Availability | VoID file availability check for AcadOnto took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.28455114364624023s
Reputation | Calculation of the PageRank for AcadOnto took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.0040740966796875e-05s
Believability | Calculation of trust value for AcadOnto took 9.775161743164062e-06s
INFO | --- Analysis for acadonto took 3.1019976139068604s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.182419061660767s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0008370876312255859s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.280275821685791s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.020607948303222656s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0009489059448242188s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.172325134277344e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for acorn-sat took 36.01651954650879s
Availability | SPARQL endpoint availability check for Addgene took 4.291534423828125e-05s
Availability | VoID file availability check for Addgene took 0.0007936954498291016s
Completeness | Calculation of interlinking completeness for Addgene took 0.26444005966186523s
Reputation | Calculation of the PageRank for Addgene took 0.020184040069580078s
Interlinking | Calculation of Degree of Connection for Addgene took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.2901763916015625e-05s
Believability | Calculation of trust value for Addgene took 1.1920928955078125e-05s
INFO | --- Analysis for addgene took 15.887689113616943s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 9.036064147949219e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.27733397483825684s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.250640869140625e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.1205673217773438e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 8.92151689529419s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.46642398834228516s
Availability | VoID file availability check for AEMET metereological dataset took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.3052558898925781s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.02229022979736328s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.504753112792969e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 1.1682510375976562e-05s
INFO | --- Analysis for aemet took 4.960655450820923s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.0392763614654541s
Availability | VoID file availability check for AgriNepalData took 0.00021767616271972656s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.27719712257385254s
Reputation | Calculation of the PageRank for AgriNepalData took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 6.747245788574219e-05s
Believability | Calculation of trust value for AgriNepalData took 1.1682510375976562e-05s
INFO | --- Analysis for agrinepaldata took 2.7888424396514893s
Availability | SPARQL endpoint availability check for AGRIS took 261.49437832832336s
Availability | VoID file availability check for AGRIS took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for AGRIS took 0.35375261306762695s
Reputation | Calculation of the PageRank for AGRIS took 0.020969867706298828s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for AGRIS took 9.846687316894531e-05s
Believability | Calculation of trust value for AGRIS took 1.049041748046875e-05s
INFO | --- Analysis for agris took 550.7105650901794s
Availability | SPARQL endpoint availability check for AGROVOC took 0.16978740692138672s
Availability | VoID file availability check for AGROVOC took 0.0005667209625244141s
Extra | Recovery of all triples for AGROVOC took 161.09510397911072s
Performance | Total latancy measurement for AGROVOC took 0.49195313453674316s
Amount of data | Number of triples check for AGROVOC took 184.05045294761658s
Interoperability | New terms check for AGROVOC took 2.987373113632202s
Versatility | Languages check for AGROVOC took 271.6249449253082s
Interpretability | Number of blank nodes check for AGROVOC took 300.07720613479614s
Interpretability | RDF structures check for AGROVOC took 0.12794113159179688s
Versatility | Serialization formats check for AGROVOC took 0.08850240707397461s
Availability | RDF dump link check for AGROVOC took 0.07954001426696777s
License | MR license check for AGROVOC took 0.10194778442382812s
License | HR license check for AGROVOC took 0.7728748321533203s
Amount of data | Number of property check for AGROVOC took 0.07769656181335449s
Understandability | Number of label check for AGROVOC took 128.66467833518982s
Understandability | URI regex check for AGROVOC took 0.17756152153015137s
Understandability | Vocabs check for AGROVOC took 0.10412359237670898s
Verifiability | Authors check for AGROVOC took 0.10002827644348145s
Verifiability | Publishers check for AGROVOC took 0.07551455497741699s
Performance | Throughput check for AGROVOC took 10.817049503326416s
Amount of data | Check the number of entities for AGROVOC took 0.00016641616821289062s
Verifiability | Contribs. check for AGROVOC took 0.0791327953338623s
Interlinking | sameAs chians check for AGROVOC took 0.08988523483276367s
Interlinking | skos check for AGROVOC took 2.5162370204925537s
Interlinking | skos check for AGROVOC took 0.22032880783081055s
Timeliness | dataset update frequency check for AGROVOC took 0.13017034530639648s
Currency | Creation date check for AGROVOC took 0.18845081329345703s
Currency | Modification date check for AGROVOC took 0.19627070426940918s
Rep.Conc. | URIs length for AGROVOC took 46.103376626968384s
Interoperability | New vocabularies check for AGROVOC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.08554315567016602s
Accuracy | Check Functional Property for AGROVOC took 0.08586549758911133s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.08496499061584473s
Accuracy | Check Empty annotation labels for AGROVOC took 16.673075199127197s
Accuracy | Check White space in annotation for AGROVOC took 2.9859819412231445s
Accuracy | Check Datatype consistency for AGROVOC took 4.486324310302734s
Consistency | Disjoint class check for AGROVOC took 0.0746300220489502s
Consistency | Check Misplaced properties for AGROVOC took 18.83996081352234s
Consistency | Check Ontology hijacking for AGROVOC took 51.21000003814697s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.5265483856201172s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 14.53746771812439s
Conciseness | Check Extensional conciseness for AGROVOC took 2.540436029434204s
Conciseness | Check Intensional conciseness for AGROVOC took 0.10562896728515625s
Security | Sign check for AGROVOC took 0.08596515655517578s
Availability | Check URIs Dereferenciability for AGROVOC took 2652.4140787124634s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.6606712341308594s
Reputation | Calculation of the PageRank for AGROVOC took 0.021381855010986328s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011301040649414062s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.6689300537109375e-06s
Believability | Calculation of trust value for AGROVOC took 1.0967254638671875e-05s
INFO | --- Analysis for agrovoc took 4374.7547788619995s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.2702667713165283s
Availability | VoID file availability check for Analytics India Magazine took 0.0007004737854003906s
Extra | Recovery of all triples for Analytics India Magazine took 3.119475841522217s
Performance | Total latancy measurement for Analytics India Magazine took 2.2705671787261963s
Amount of data | Number of triples check for Analytics India Magazine took 1.3643269538879395s
Versatility | Languages check for Analytics India Magazine took 1.3644425868988037s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.6159284114837646s
Interpretability | RDF structures check for Analytics India Magazine took 1.2764191627502441s
Versatility | Serialization formats check for Analytics India Magazine took 1.4834601879119873s
Availability | RDF dump link check for Analytics India Magazine took 1.3115763664245605s
License | MR license check for Analytics India Magazine took 1.3695929050445557s
License | HR license check for Analytics India Magazine took 1.3695671558380127s
Amount of data | Number of property check for Analytics India Magazine took 1.193159818649292s
Understandability | Number of label check for Analytics India Magazine took 1.3254921436309814s
Understandability | URI regex check for Analytics India Magazine took 2.8473942279815674s
Understandability | Vocabs check for Analytics India Magazine took 1.2662861347198486s
Verifiability | Authors check for Analytics India Magazine took 1.2763988971710205s
Verifiability | Publishers check for Analytics India Magazine took 1.5483014583587646s
Performance | Throughput check for Analytics India Magazine took 16.825656175613403s
Amount of data | Check the number of entities for Analytics India Magazine took 9.489059448242188e-05s
Verifiability | Contribs. check for Analytics India Magazine took 1.1102442741394043s
Interlinking | sameAs chians check for Analytics India Magazine took 1.4855988025665283s
Interlinking | skos check for Analytics India Magazine took 0.9794211387634277s
Interlinking | skos check for Analytics India Magazine took 0.13624930381774902s
Timeliness | dataset update frequency check for Analytics India Magazine took 0.947291374206543s
Currency | Creation date check for Analytics India Magazine took 2.5087227821350098s
Currency | Modification date check for Analytics India Magazine took 2.54785418510437s
Rep.Conc. | URIs length for Analytics India Magazine took 2.7065446376800537s
Interoperability | New vocabularies check for Analytics India Magazine took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 1.1249306201934814s
Consistency | Disjoint class check for Analytics India Magazine took 1.7979991436004639s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.033684492111206s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 2.8356711864471436s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.00014829635620117188s
Security | Sign check for Analytics India Magazine took 1.3312277793884277s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.3600192070007324s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.022640466690063477s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 2.956390380859375e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 1.1920928955078125e-06s
Believability | Calculation of trust value for Analytics India Magazine took 1.2636184692382812e-05s
INFO | --- Analysis for AIM took 101.58482646942139s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 8.749961853027344e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.29865407943725586s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020650386810302734s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 2.956390380859375e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.0728836059570312e-05s
INFO | --- Analysis for AISHE took 2.614788293838501s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for  equipment ontology took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.28464531898498535s
Reputation | Calculation of the PageRank for  equipment ontology took 0.021047115325927734s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 2.9087066650390625e-05s
Believability | Calculation of trust value for  equipment ontology took 1.2159347534179688e-05s
INFO | --- Analysis for akash took 2.580714464187622s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 263.02153611183167s
Availability | VoID file availability check for aliada-scanbit-net took 0.0008611679077148438s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.38015270233154297s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020878314971923828s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00011420249938964844s
Believability | Calculation of trust value for aliada-scanbit-net took 9.5367431640625e-06s
INFO | --- Analysis for aliada-scanbit-net took 1452.4557602405548s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.6552605628967285s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0007395744323730469s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 136.94157719612122s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.7081942558288574s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.5362262725830078s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.549638271331787s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.1028461456299s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.980708360671997s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8966188430786133s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.7815093994140625s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.7954750061035156s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.6526298522949219s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.6995384693145752s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 31.057732105255127s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5811564922332764s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.7981281280517578s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.2611439228057861s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.9570066928863525s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 1.3233425617218018s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.7139163017272949s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 12.308208703994751s
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.5321073532104492s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5691416263580322s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6449062824249268s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.620549201965332s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.6733748912811279s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.9611310958862305s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1341066360473633s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 54.008575677871704s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 1.6159772872924805s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5581622123718262s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6854772567749023s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6228005886077881s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 34.6694655418396s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.0356497764587402s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.5855512619018555s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.5948917865753174s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.486979246139526s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.7640221118927s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 32.482006549835205s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.3677456378936768s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.40634274482727s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.7205164432525635s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8393852710723877s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5420587062835693s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 12917.504420042038s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.6286683082580566s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.023923635482788086s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 8.20159912109375e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 1.8294086456298828s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.239776611328125e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 13742.198796749115s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.26137852668762207s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.2909541130065918s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.021447420120239258s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.7670135498046875e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.2636184692382812e-05s
INFO | --- Analysis for alpino-rdf took 3.7541353702545166s
Availability | SPARQL endpoint availability check for AAT-atawil took 8.869171142578125e-05s
Availability | VoID file availability check for AAT-atawil took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.312361478805542s
Reputation | Calculation of the PageRank for AAT-atawil took 0.020653486251831055s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.123283386230469e-05s
Believability | Calculation of trust value for AAT-atawil took 1.1682510375976562e-05s
INFO | --- Analysis for Altawil took 2.7038445472717285s
Availability | SPARQL endpoint availability check for Amer Nejma took 9.775161743164062e-05s
Availability | VoID file availability check for Amer Nejma took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.3128626346588135s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020680904388427734s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.1948089599609375e-05s
Believability | Calculation of trust value for Amer Nejma took 1.0728836059570312e-05s
INFO | --- Analysis for Amer_Nejma took 2.7378365993499756s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7466692924499512s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.3066709041595459s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.021200895309448242s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.512901306152344e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.1444091796875e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 4.018943786621094s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.9114227294921875e-05s
Availability | VoID file availability check for Anime Dataset took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.3129091262817383s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.0517578125e-05s
Believability | Calculation of trust value for Anime Dataset took 1.2874603271484375e-05s
INFO | --- Analysis for Anime took 3.989023447036743s
Availability | SPARQL endpoint availability check for ANNO took 0.00011396408081054688s
Availability | VoID file availability check for ANNO took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for ANNO took 0.2981727123260498s
Reputation | Calculation of the PageRank for ANNO took 0.020929574966430664s
Interlinking | Calculation of Degree of Connection for ANNO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.719329833984375e-05s
Believability | Calculation of trust value for ANNO took 1.049041748046875e-05s
INFO | --- Analysis for anno took 7.8971312046051025s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 8.893013000488281e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.3238375186920166s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.022168874740600586s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.724761962890625e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 1.0251998901367188e-05s
INFO | --- Analysis for AntiqueCarsCollection took 4.279870510101318s
Availability | SPARQL endpoint availability check for apache took 9.34600830078125e-05s
Availability | VoID file availability check for apache took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for apache took 0.37993788719177246s
Reputation | Calculation of the PageRank for apache took 0.021967649459838867s
Interlinking | Calculation of Degree of Connection for apache took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for apache took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for apache took 5.4836273193359375e-05s
Believability | Calculation of trust value for apache took 1.0251998901367188e-05s
INFO | --- Analysis for apache took 3.6322054862976074s
Availability | SPARQL endpoint availability check for Apertium RDF took 9.1552734375e-05s
Availability | VoID file availability check for Apertium RDF took 0.0007131099700927734s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.3138260841369629s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf took 5.9883222579956055s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.553794860839844e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.32894062995910645s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020422935485839844s
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.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.267692565917969e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 6.166943788528442s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.3016846179962158s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.0013580322265625e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 5.96541166305542s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 8.893013000488281e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0008068084716796875s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.3037736415863037s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.02091383934020996s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.0013580322265625e-05s
INFO | --- Analysis for apertium-rdf-en-es took 5.869857311248779s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 8.702278137207031e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.3435811996459961s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020908832550048828s
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.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 5.882395267486572s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.2778658866882324s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.267692565917969e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.9285569190979s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 9.131431579589844e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.2912318706512451s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.020937442779541016s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 5.766557693481445s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 0.0001468658447265625s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.28603553771972656s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.021000385284423828s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 5.79303503036499s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 8.845329284667969e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.28696179389953613s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.767492771148682s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.5299530029296875e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2953634262084961s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.1444091796875e-05s
INFO | --- Analysis for apertium-rdf-es-an took 6.016836404800415s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 8.7738037109375e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.31714320182800293s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.02034783363342285s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.870244979858398s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.3084099292755127s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020662546157836914s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.1444091796875e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 25.230743885040283s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.319683313369751s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 6.031990051269531e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 5.913783550262451s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 5.8650970458984375e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.2866401672363281s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.02053236961364746s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 5.87866735458374s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.286954402923584s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.020364761352539062s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 5.789404392242432s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 8.96453857421875e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0006430149078369141s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.29747891426086426s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02185797691345215s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 5.944829940795898s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 8.797645568847656e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.3155200481414795s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.021580934524536133s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 5.815221071243286s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 0.0001761913299560547s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.32448530197143555s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.021737098693847656s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.0728836059570312e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.926263093948364s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.2865869998931885s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020350933074951172s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 5.874446153640747s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.30469799041748047s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020957231521606445s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.99134373664856s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2745664119720459s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020627498626708984s
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.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.0531158447265625e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 5.816679239273071s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.2750527858734131s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.738075017929077s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 8.988380432128906e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0007333755493164062s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.29345154762268066s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.02118849754333496s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.744529724121094e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.587556600570679s
Availability | SPARQL endpoint availability check for AragoDBpedia - aragon open data took 0.6409554481506348s
Availability | VoID file availability check for AragoDBpedia - aragon open data took 0.00060272216796875s
Extra | Recovery of all triples for AragoDBpedia - aragon open data took 3.10915470123291s
Performance | Total latancy measurement for AragoDBpedia - aragon open data took 1.8937795162200928s
Amount of data | Number of triples check for AragoDBpedia - aragon open data took 0.8322756290435791s
Interoperability | New terms check for AragoDBpedia - aragon open data took 2.105109453201294s
Versatility | Languages check for AragoDBpedia - aragon open data took 60.50880432128906s
Interpretability | Number of blank nodes check for AragoDBpedia - aragon open data took 4.002132177352905s
Security | Check HTTPS for AragoDBpedia - aragon open data took 0.24741816520690918s
Interpretability | RDF structures check for AragoDBpedia - aragon open data took 0.8392105102539062s
Versatility | Serialization formats check for AragoDBpedia - aragon open data took 0.9240827560424805s
Availability | RDF dump link check for AragoDBpedia - aragon open data took 0.4001152515411377s
License | MR license check for AragoDBpedia - aragon open data took 0.7908632755279541s
License | HR license check for AragoDBpedia - aragon open data took 7.378593444824219s
Amount of data | Number of property check for AragoDBpedia - aragon open data took 0.37929487228393555s
Understandability | Number of label check for AragoDBpedia - aragon open data took 0.6683156490325928s
Understandability | URI regex check for AragoDBpedia - aragon open data took 1.0332977771759033s
Understandability | Vocabs check for AragoDBpedia - aragon open data took 0.49324798583984375s
Verifiability | Authors check for AragoDBpedia - aragon open data took 0.5541214942932129s
Verifiability | Publishers check for AragoDBpedia - aragon open data took 0.3819160461425781s
Performance | Throughput check for AragoDBpedia - aragon open data took 11.266321182250977s
Amount of data | Check the number of entities for AragoDBpedia - aragon open data took 8.344650268554688e-05s
Verifiability | Contribs. check for AragoDBpedia - aragon open data took 0.48090314865112305s
Interlinking | sameAs chians check for AragoDBpedia - aragon open data took 0.4506247043609619s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.5440225601196289s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.34888315200805664s
Timeliness | dataset update frequency check for AragoDBpedia - aragon open data took 0.43775439262390137s
Currency | Creation date check for AragoDBpedia - aragon open data took 1.2650952339172363s
Currency | Modification date check for AragoDBpedia - aragon open data took 0.4046659469604492s
Rep.Conc. | URIs length for AragoDBpedia - aragon open data took 6.8026509284973145s
Interoperability | New vocabularies check for AragoDBpedia - aragon open data took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for AragoDBpedia - aragon open data took 0.3999061584472656s
Accuracy | Check Functional Property for AragoDBpedia - aragon open data took 0.5473372936248779s
Accuracy | Check Inverse Functional Property for AragoDBpedia - aragon open data took 0.5256931781768799s
Accuracy | Check Empty annotation labels for AragoDBpedia - aragon open data took 1.4048736095428467s
Accuracy | Check White space in annotation for AragoDBpedia - aragon open data took 0.02992415428161621s
Accuracy | Check Datatype consistency for AragoDBpedia - aragon open data took 0.02769780158996582s
Consistency | Disjoint class check for AragoDBpedia - aragon open data took 0.38487672805786133s
Consistency | Check Misplaced properties for AragoDBpedia - aragon open data took 4.356780529022217s
Consistency | Misplaced classes for AragoDBpedia - aragon open data took 0.6729099750518799s
Consistency | Check Ontology hijacking for AragoDBpedia - aragon open data took 2.864083766937256s
Consistency | Check Invalid usage of undefined classes for AragoDBpedia - aragon open data took 1.3333990573883057s
Consistency | Check Invalid usage of undefined properties for AragoDBpedia - aragon open data took 5.108261823654175s
Conciseness | Check Extensional conciseness for AragoDBpedia - aragon open data took 0.0319364070892334s
Conciseness | Check Intensional conciseness for AragoDBpedia - aragon open data took 0.5581555366516113s
Security | Sign check for AragoDBpedia - aragon open data took 0.6601543426513672s
Availability | Check URIs Dereferenciability for AragoDBpedia - aragon open data took 3344.754675388336s
Completeness | Calculation of interlinking completeness for AragoDBpedia - aragon open data took 0.6436192989349365s
Reputation | Calculation of the PageRank for AragoDBpedia - aragon open data took 0.022825956344604492s
Interlinking | Calculation of Degree of Connection for AragoDBpedia - aragon open data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for AragoDBpedia - aragon open data took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for AragoDBpedia - aragon open data took 5.173683166503906e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBpedia - aragon open data took 2.1457672119140625e-06s
Believability | Calculation of trust value for AragoDBpedia - aragon open data took 9.5367431640625e-06s
INFO | --- Analysis for aragodbpedia took 3628.6078922748566s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.316558361053467s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0007483959197998047s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.29648375511169434s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.021409273147583008s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 4.887580871582031e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for archiveshub-linkeddata took 83.3123869895935s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.712000608444214s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.000579833984375s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.2937586307525635s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.528594970703125e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 7.3909759521484375e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 20.15846014022827s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.870978593826294s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.28560400009155273s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.647804260253906e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.2159347534179688e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 16.791606903076172s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.363059997558594e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.31241869926452637s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020544767379760742s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.870529174804688e-05s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.1444091796875e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 9.07279372215271s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.363059997558594e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.2881746292114258s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.02095508575439453s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010251998901367188s
Believability | Calculation of trust value for Arthroscopy community took 1.0967254638671875e-05s
INFO | --- Analysis for arthroscopy took 26.44869112968445s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.7847373485565186s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.00064849853515625s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 29.62860369682312s
Performance | Total latancy measurement for Wikidata entry for Art × Science International took 1.2954392433166504s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 65.15205430984497s
Interoperability | New terms check for Wikidata entry for Art × Science International took 2.25750732421875s
Versatility | Languages check for Wikidata entry for Art × Science International took 60.18433618545532s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 65.17278122901917s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.46092915534973145s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.18130183219909668s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.1822495460510254s
License | MR license check for Wikidata entry for Art × Science International took 0.6289842128753662s
License | HR license check for Wikidata entry for Art × Science International took 65.16939687728882s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.5477406978607178s
Understandability | Number of label check for Wikidata entry for Art × Science International took 65.16477179527283s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.4672377109527588s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.36470937728881836s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.19719910621643066s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.1866588592529297s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 7.224082946777344e-05s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.2481839656829834s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 54.77916884422302s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.30899739265441895s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.17035484313964844s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.21877574920654297s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.3583047389984131s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.5858263969421387s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 25.29838490486145s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.18985629081726074s
Accuracy | Check Empty annotation labels for Wikidata entry for Art × Science International took 16.91086506843567s
Accuracy | Check White space in annotation for Wikidata entry for Art × Science International took 2.6237380504608154s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.560985803604126s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.18182635307312012s
Consistency | Check Misplaced properties for Wikidata entry for Art × Science International took 16.97268295288086s
Consistency | Misplaced classes for Wikidata entry for Art × Science International took 8.97713565826416s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 30.577150583267212s
Consistency | Check Invalid usage of undefined classes for Wikidata entry for Art × Science International took 1.4428505897521973s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 10.872725486755371s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.805480718612671s
Conciseness | Check Intensional conciseness for Wikidata entry for Art × Science International took 1.5929458141326904s
Security | Sign check for Wikidata entry for Art × Science International took 0.21454358100891113s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 8.9352388381958s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.42540740966796875s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.020904064178466797s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 2.0265579223632812e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 1.9073486328125e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 1.2636184692382812e-05s
INFO | --- Analysis for artxscienceinternational-wikidata took 928.8113706111908s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.8514883518218994s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.2830476760864258s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.022228717803955078s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.368492126464844e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 14.30793309211731s
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.7077243328094482s
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.0006847381591796875s
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.292710542678833s
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.02092266082763672s
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.0013580322265625e-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.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 8.0108642578125e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 12.474462509155273s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.7022156715393066s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.2841813564300537s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0208284854888916s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.131431579589844e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 13.74186897277832s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.709123134613037s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.2819821834564209s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.02115154266357422s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.029273986816406e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.33514404296875e-05s
INFO | --- Analysis for ASCDC-CRB took 16.095993041992188s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.7133755683898926s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.32150912284851074s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.869171142578125e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 13.197370052337646s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.6959240436553955s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.29819202423095703s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.910064697265625e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.0251998901367188e-05s
INFO | --- Analysis for ASCDC-DQOT took 14.246038913726807s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.713979721069336s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.3089916706085205s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.021678924560546875s
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.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 9.107589721679688e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 14.425032615661621s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.5701956748962402s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.2838013172149658s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020589828491210938s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 7.772445678710938e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.2636184692382812e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 16.93039345741272s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.674818992614746s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.2794766426086426s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.0067901611328125e-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.0013580322265625e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 13.0803701877594s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.6528823375701904s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.32700300216674805s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.02277684211730957s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.245208740234375e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.33514404296875e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 13.179986953735352s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.5842297077178955s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.3070087432861328s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.022189617156982422s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.601478576660156e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.2159347534179688e-05s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 19.572284698486328s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.7185122966766357s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.315197229385376s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020546436309814453s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.486343383789062e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.775161743164062e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 12.514267683029175s
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.708167791366577s
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.0005967617034912109s
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.27433109283447266s
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.02053070068359375s
Interlinking | Calculation of Degree of Connection for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.867813110351562e-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.3113021850585938e-05s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 14.31182312965393s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 4.316845178604126s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.2953617572784424s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.3392181396484375e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC_-_DNB took 15.289738893508911s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 9.250640869140625e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.28678464889526367s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020984172821044922s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 7.271766662597656e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 9.775161743164062e-06s
INFO | --- Analysis for asit took 7.901897668838501s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.172325134277344e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.30242085456848145s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.02083277702331543s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.7670135498046875e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.0251998901367188e-05s
INFO | --- Analysis for asjp took 5.118265151977539s
Availability | SPARQL endpoint availability check for ASN:US took 2.632655143737793s
Availability | VoID file availability check for ASN:US took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for ASN:US took 0.2994384765625s
Reputation | Calculation of the PageRank for ASN:US took 0.0208284854888916s
Interlinking | Calculation of Degree of Connection for ASN:US took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ASN:US took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.651878356933594e-05s
Believability | Calculation of trust value for ASN:US took 8.344650268554688e-06s
INFO | --- Analysis for asn-us took 13.443665504455566s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 8.535385131835938e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.29000306129455566s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 2.9802322387695312e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 8.821487426757812e-06s
INFO | --- Analysis for aspire-mmu took 4.739445209503174s
Availability | SPARQL endpoint availability check for associations took 8.654594421386719e-05s
Availability | VoID file availability check for associations took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for associations took 0.34484386444091797s
Reputation | Calculation of the PageRank for associations took 0.02072596549987793s
Interlinking | Calculation of Degree of Connection for associations took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for associations took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for associations took 6.604194641113281e-05s
Believability | Calculation of trust value for associations took 9.775161743164062e-06s
INFO | --- Analysis for associations took 7.4521870613098145s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 8.440017700195312e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.28867053985595703s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.02072906494140625s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.845329284667969e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.0967254638671875e-05s
INFO | --- Analysis for athelia-rfid took 6.971004247665405s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.5916404724121094s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.30281496047973633s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 4.8160552978515625e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 9.5367431640625e-06s
INFO | --- Analysis for AugustiniConfessiones took 4.344696044921875s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.5077929496765137s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.2845454216003418s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.021130084991455078s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.107589721679688e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 9.775161743164062e-06s
INFO | --- Analysis for austrian_ski_racers took 3.9184072017669678s
Availability | SPARQL endpoint availability check for AVsOnto took 4.267692565917969e-05s
Availability | VoID file availability check for AVsOnto took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.30168867111206055s
Reputation | Calculation of the PageRank for AVsOnto took 0.0220491886138916s
Interlinking | Calculation of Degree of Connection for AVsOnto took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 2.8848648071289062e-05s
Believability | Calculation of trust value for AVsOnto took 1.0013580322265625e-05s
INFO | --- Analysis for AVsOnto took 3.4777045249938965s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.19675135612487793s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005214214324951172s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 164.70808005332947s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.4689826965332031s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1033601760864s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 255.6186020374298s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0331287384033s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0760591030121s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2442018985748291s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20149755477905273s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.22829675674438477s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10674118995666504s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 41.55801343917847s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1031422615051s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12404298782348633s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 144.15740704536438s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2836644649505615s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.18860554695129395s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11201858520507812s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24940729141235352s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.691888570785522s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.600120544433594e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13114714622497559s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0679075717926s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17436766624450684s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1347346305847168s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17293548583984375s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.22691798210144043s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.301588773727417s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 898.7714245319366s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17041587829589844s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.526366233825684s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.1658501625061035s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.719638347625732s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2541821002960205s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.17837405204773s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 21.15865182876587s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.433140754699707s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.50411105155945s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.7940685749053955s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16585779190063477s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.0721278190612793s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.7561419010162354s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021851062774658203s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.700920104980469e-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 9.059906005859375e-06s
INFO | --- Analysis for b3kat took 4292.756254911423s
Availability | SPARQL endpoint availability check for BabelNet took 0.5616941452026367s
Availability | VoID file availability check for BabelNet took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for BabelNet took 0.2927124500274658s
Reputation | Calculation of the PageRank for BabelNet took 0.020699739456176758s
Interlinking | Calculation of Degree of Connection for BabelNet took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BabelNet took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001633167266845703s
Believability | Calculation of trust value for BabelNet took 1.1682510375976562e-05s
INFO | --- Analysis for babelnet took 4.772499322891235s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 9.298324584960938e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.3003544807434082s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.021303892135620117s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.314018249511719e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.1205673217773438e-05s
INFO | --- Analysis for Bacevicius.lt took 2.6020262241363525s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.4219379425048828s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.30434298515319824s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.2438507080078125e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.049041748046875e-05s
INFO | --- Analysis for bag took 4.194584131240845s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 1.3879289627075195s
Availability | VoID file availability check for 红色经典歌曲 took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2783491611480713s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.021071434020996094s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.337860107421875e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.2636184692382812e-05s
INFO | --- Analysis for baixue took 4.1791887283325195s
Availability | SPARQL endpoint availability check for baixue composer took 4.5299530029296875e-05s
Availability | VoID file availability check for baixue composer took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for baixue composer took 0.3004751205444336s
Reputation | Calculation of the PageRank for baixue composer took 0.02101612091064453s
Interlinking | Calculation of Degree of Connection for baixue composer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for baixue composer took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.1948089599609375e-05s
Believability | Calculation of trust value for baixue composer took 1.1920928955078125e-05s
INFO | --- Analysis for baixue_composer took 3.172823190689087s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.363059997558594e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.31035494804382324s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020581960678100586s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.0994415283203125e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1682510375976562e-05s
INFO | --- Analysis for baixue_imagery took 3.1761817932128906s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 9.131431579589844e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.29065656661987305s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.86102294921875e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1205673217773438e-05s
INFO | --- Analysis for baixue_imagery1 took 4.305615425109863s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 8.96453857421875e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.29268836975097656s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.022310733795166016s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.076957702636719e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.1476006507873535s
Availability | SPARQL endpoint availability check for BBC Music took 0.4964289665222168s
Availability | VoID file availability check for BBC Music took 0.0004024505615234375s
Completeness | Calculation of interlinking completeness for BBC Music took 0.3006312847137451s
Reputation | Calculation of the PageRank for BBC Music took 0.02083730697631836s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00013065338134765625s
Believability | Calculation of trust value for BBC Music took 1.2636184692382812e-05s
INFO | --- Analysis for bbc-music took 3.752178907394409s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.24459218978881836s
Availability | VoID file availability check for BBC Programmes took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.32816123962402344s
Reputation | Calculation of the PageRank for BBC Programmes took 0.020682573318481445s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010323524475097656s
Believability | Calculation of trust value for BBC Programmes took 1.1920928955078125e-05s
INFO | --- Analysis for bbc-programmes took 10.977049589157104s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.26404500007629395s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.28505492210388184s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020554542541503906s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010275840759277344s
Believability | Calculation of trust value for BBC Wildlife Finder took 6.9141387939453125e-06s
INFO | --- Analysis for bbc-wildlife-finder took 9.613523244857788s
Availability | SPARQL endpoint availability check for BBOP took 4.410743713378906e-05s
Availability | VoID file availability check for BBOP took 0.0008013248443603516s
Completeness | Calculation of interlinking completeness for BBOP took 0.300922155380249s
Reputation | Calculation of the PageRank for BBOP took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for BBOP took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.9087066650390625e-05s
Believability | Calculation of trust value for BBOP took 1.1205673217773438e-05s
INFO | --- Analysis for bbop-selected took 20.739346504211426s
Availability | SPARQL endpoint availability check for Bdgp took 1.1440892219543457s
Availability | VoID file availability check for Bdgp took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Bdgp took 0.3090245723724365s
Reputation | Calculation of the PageRank for Bdgp took 0.021147966384887695s
Interlinking | Calculation of Degree of Connection for Bdgp took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bdgp took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bdgp took 1.1444091796875e-05s
INFO | --- Analysis for bdgp took 5.257562875747681s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.267692565917969e-05s
Availability | VoID file availability check for Bendev Junior took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.26887011528015137s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020685672760009766s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 2.86102294921875e-05s
Believability | Calculation of trust value for Bendev Junior took 1.1444091796875e-05s
INFO | --- Analysis for bendevoficial took 3.2843356132507324s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 10.869682550430298s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.001497507095336914s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.32106518745422363s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020972728729248047s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.176399230957031e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 8.58306884765625e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 22.7328839302063s
Availability | SPARQL endpoint availability check for berlios took 9.036064147949219e-05s
Availability | VoID file availability check for berlios took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for berlios took 0.27841782569885254s
Reputation | Calculation of the PageRank for berlios took 0.020318984985351562s
Interlinking | Calculation of Degree of Connection for berlios took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for berlios took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for berlios took 9.036064147949219e-05s
Believability | Calculation of trust value for berlios took 1.049041748046875e-05s
INFO | --- Analysis for berlios took 3.021519184112549s
Availability | SPARQL endpoint availability check for Between Our Worlds took 8.845329284667969e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.358903169631958s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020824432373046875s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0011241436004638672s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 8.845329284667969e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.1205673217773438e-05s
INFO | --- Analysis for betweenourworlds took 9.154870986938477s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.09834766387939453s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.2946920394897461s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.022144079208374023s
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.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.131431579589844e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for bfs-linked-data took 3.026445150375366s
Availability | SPARQL endpoint availability check for BibBase took 0.07780671119689941s
Availability | VoID file availability check for BibBase took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for BibBase took 0.3094015121459961s
Reputation | Calculation of the PageRank for BibBase took 0.020783424377441406s
Interlinking | Calculation of Degree of Connection for BibBase took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BibBase took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.512901306152344e-05s
Believability | Calculation of trust value for BibBase took 1.0013580322265625e-05s
INFO | --- Analysis for bibbase took 2.808227777481079s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 0.0001621246337890625s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.3188929557800293s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020919084548950195s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 9.942054748535156e-05s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.0251998901367188e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 10.395541429519653s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.315376281738281e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.2992255687713623s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.020830869674682617s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.775161743164062e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.0013580322265625e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 6.996161699295044s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.00010585784912109375s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.28592991828918457s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.743171691894531e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.049041748046875e-05s
INFO | --- Analysis for BibSonomy took 10.70566201210022s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 8.511543273925781e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.276395320892334s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020578622817993164s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 2.9802322387695312e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.049041748046875e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 5.874240159988403s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 0.00012302398681640625s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.3083012104034424s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.022240400314331055s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 2.9087066650390625e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.239776611328125e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.892256498336792s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.2719669342041016s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0005643367767333984s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 19.47104239463806s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.4964461326599121s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 44.394678592681885s
Interoperability | New terms check for Bio2RDF::Affymetrix took 44.980231285095215s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.11861276626587s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.1481618881225586s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.7384934425354004s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.1797044277191162s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 2.492063045501709s
License | MR license check for Bio2RDF::Affymetrix took 0.3670334815979004s
License | HR license check for Bio2RDF::Affymetrix took 60.096027851104736s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.14329838752746582s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.615978479385376s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.38840246200561523s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.1296541690826416s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.14062285423278809s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.13076281547546387s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.616073608398438s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 73.53831720352173s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.47237443923950195s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.2541787624359131s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.7522974014282227s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.19999337196350098s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.10516095161437988s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.2747495174407959s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.2252821922302246s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 111.34646201133728s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 17.33830761909485s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.2821347713470459s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.15247011184692383s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.11444568634033203s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 7.008139610290527s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8958561420440674s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.634598970413208s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.2798314094543457s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 64.88672590255737s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.2330069541931152s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.158902883529663s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.2525274753570557s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.3267822265625s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.6878311634063721s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.3206946849822998s
Security | Sign check for Bio2RDF::Affymetrix took 0.10786294937133789s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 11.414462566375732s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.32019710540771484s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020421504974365234s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.131431579589844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 14.923769474029541s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1034.7182433605194s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.5125091075897217s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0006716251373291016s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 18.521058320999146s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.1921849250793457s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 43.26415252685547s
Interoperability | New terms check for Bio2RDF::Biomodels took 42.87194538116455s
Versatility | Languages check for Bio2RDF::Biomodels took 60.23309063911438s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.26613497734069824s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.14505672454833984s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.9378519058227539s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.2864837646484375s
Availability | RDF dump link check for Bio2RDF::Biomodels took 2.4059083461761475s
License | MR license check for Bio2RDF::Biomodels took 0.4743626117706299s
License | HR license check for Bio2RDF::Biomodels took 60.261500120162964s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.27652406692504883s
Understandability | Number of label check for Bio2RDF::Biomodels took 9.825019121170044s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.6039121150970459s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.26366186141967773s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.26044344902038574s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.2405099868774414s
Performance | Throughput check for Bio2RDF::Biomodels took 11.188406705856323s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 70.98200750350952s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 1.4159808158874512s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.3747897148132324s
Interlinking | skos check for Bio2RDF::Biomodels took 0.9705243110656738s
Interlinking | skos check for Bio2RDF::Biomodels took 0.35326409339904785s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2568705081939697s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5109829902648926s
Currency | Modification date check for Bio2RDF::Biomodels took 0.4911527633666992s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 108.60635948181152s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 22.043656826019287s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.40868258476257324s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.26008105278015137s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.2906670570373535s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 6.652337074279785s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.892864465713501s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6380550861358643s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.4301629066467285s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.10767531394958s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.4063775539398193s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.701983690261841s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.3189632892608643s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.56231498718262s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.6938591003417969s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.44965100288391113s
Security | Sign check for Bio2RDF::Biomodels took 0.24501991271972656s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 9.924337148666382s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.4960010051727295s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.0210263729095459s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.0001163482666015625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 15.973270177841187s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1039.2111506462097s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.4679861068725586s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0006520748138427734s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 18.078476905822754s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2369067668914795s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 44.00729441642761s
Interoperability | New terms check for Bio2RDF::Bioportal took 42.056551456451416s
Versatility | Languages check for Bio2RDF::Bioportal took 60.25332164764404s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2678103446960449s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.1661372184753418s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.7318344116210938s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.32992053031921387s
Availability | RDF dump link check for Bio2RDF::Bioportal took 2.2818148136138916s
License | MR license check for Bio2RDF::Bioportal took 0.5069372653961182s
License | HR license check for Bio2RDF::Bioportal took 60.25476408004761s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.27370786666870117s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.378613233566284s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.5750784873962402s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.240980863571167s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.24527335166931152s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.27358078956604004s
Performance | Throughput check for Bio2RDF::Bioportal took 11.465264558792114s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 74.4605484008789s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.7019054889678955s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.36261892318725586s
Interlinking | skos check for Bio2RDF::Bioportal took 0.7488992214202881s
Interlinking | skos check for Bio2RDF::Bioportal took 0.34581899642944336s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.2598433494567871s
Currency | Creation date check for Bio2RDF::Bioportal took 0.49607038497924805s
Currency | Modification date check for Bio2RDF::Bioportal took 0.48968982696533203s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 108.08601522445679s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 27.286248922348022s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.4419107437133789s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.2794163227081299s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.2759382724761963s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 6.930333375930786s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8969335556030273s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6409673690795898s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.4002392292022705s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.56691336631775s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.4155521392822266s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.448535203933716s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.2549104690551758s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.569446086883545s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7000842094421387s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.43224215507507324s
Security | Sign check for Bio2RDF::Bioportal took 0.26593494415283203s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 11.23591423034668s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.43236804008483887s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.020932674407958984s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004200935363769531s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 178.13217449188232s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1220.9205906391144s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.14268064498901367s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.3300902843475342s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020694732666015625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.054473876953125e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-chembl took 16.793666124343872s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.48368000984191895s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0005543231964111328s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 18.670708894729614s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2250938415527344s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 44.582470417022705s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 41.37377381324768s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.25017547607422s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.2596781253814697s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.15551114082336426s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.4569859504699707s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.29763078689575195s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 2.3192903995513916s
License | MR license check for Bio2RDF::Clinicaltrials took 0.4603595733642578s
License | HR license check for Bio2RDF::Clinicaltrials took 60.24054455757141s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.24542236328125s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.510331153869629s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5949153900146484s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.2531461715698242s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2593684196472168s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.25797533988952637s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.257889032363892s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 74.93671894073486s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.5912063121795654s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.35578107833862305s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.9348621368408203s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.34305906295776367s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.25809288024902344s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.49243712425231934s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5253093242645264s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 110.67308068275452s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.4021122455596924s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.2738974094390869s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.28177857398986816s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 6.599008560180664s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.9079689979553223s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6562130451202393s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.4068899154663086s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.12543368339539s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.3835935592651367s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.118014097213745s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.2556049823760986s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.53065085411072s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7079129219055176s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.4224262237548828s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.2809281349182129s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 9.97782826423645s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.5088739395141602s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.026693344116210938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 6.341934204101562e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 16.172170162200928s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1025.5672707557678s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.497467041015625s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.00034117698669433594s
Extra | Recovery of all triples for Bio2RDF::Ctd took 18.43315839767456s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.1706113815307617s
Amount of data | Number of triples check for Bio2RDF::Ctd took 43.91268014907837s
Interoperability | New terms check for Bio2RDF::Ctd took 40.47762370109558s
Versatility | Languages check for Bio2RDF::Ctd took 60.24710702896118s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.2679908275604248s
Security | Check HTTPS for Bio2RDF::Ctd took 0.15600943565368652s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.8729145526885986s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.3206467628479004s
Availability | RDF dump link check for Bio2RDF::Ctd took 2.3648910522460938s
License | MR license check for Bio2RDF::Ctd took 0.45037031173706055s
License | HR license check for Bio2RDF::Ctd took 60.26905083656311s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.25386548042297363s
Understandability | Number of label check for Bio2RDF::Ctd took 10.021219491958618s
Understandability | URI regex check for Bio2RDF::Ctd took 0.561119556427002s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.2435154914855957s
Verifiability | Authors check for Bio2RDF::Ctd took 0.24011898040771484s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.25406813621520996s
Performance | Throughput check for Bio2RDF::Ctd took 11.648570537567139s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 73.43868947029114s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.6847541332244873s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.33638596534729004s
Interlinking | skos check for Bio2RDF::Ctd took 0.7185585498809814s
Interlinking | skos check for Bio2RDF::Ctd took 0.3532106876373291s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.23880457878112793s
Currency | Creation date check for Bio2RDF::Ctd took 0.482649564743042s
Currency | Modification date check for Bio2RDF::Ctd took 0.4737815856933594s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 110.56486535072327s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 17.62738347053528s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.44522833824157715s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.280914306640625s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.25324344635009766s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 6.814311742782593s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.894721508026123s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.635936975479126s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.39446187019348145s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.1283848285675s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.3699951171875s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 5.987703084945679s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.2980337142944336s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.543235540390015s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.6970241069793701s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.41339778900146484s
Security | Sign check for Bio2RDF::Ctd took 0.26969265937805176s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 11.208977699279785s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.3894481658935547s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.02080082893371582s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.580352783203125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 20.722774744033813s
Believability | Calculation of trust value for Bio2RDF::Ctd took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-ctd took 1049.731435060501s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 8.487701416015625e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.3334934711456299s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.021088123321533203s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 4.935264587402344e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-dataset took 2.9230728149414062s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.46553993225097656s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0005812644958496094s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 19.268769025802612s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.1996288299560547s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 44.20234513282776s
Interoperability | New terms check for Bio2RDF::Dbsnp took 43.46239924430847s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.253559589385986s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.2465229034423828s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.15626144409179688s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.7676470279693604s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.35097670555114746s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 2.4197824001312256s
License | MR license check for Bio2RDF::Dbsnp took 0.47210073471069336s
License | HR license check for Bio2RDF::Dbsnp took 60.256622314453125s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.24831128120422363s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.766200065612793s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5724537372589111s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.2500307559967041s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2481861114501953s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.25820040702819824s
Performance | Throughput check for Bio2RDF::Dbsnp took 10.850984811782837s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 74.12822031974792s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.5962846279144287s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.3798222541809082s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.8756251335144043s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.353740930557251s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.24614548683166504s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5182404518127441s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5014281272888184s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 110.84373784065247s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 27.9225115776062s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4340939521789551s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.28214526176452637s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.2746310234069824s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 6.786431074142456s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.9044857025146484s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6525037288665771s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.384782075881958s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 64.96416544914246s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.368300199508667s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.253536701202393s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.2903022766113281s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.52644944190979s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7040538787841797s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.4396698474884033s
Security | Sign check for Bio2RDF::Dbsnp took 0.26616334915161133s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 9.999376773834229s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.47269678115844727s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.02123880386352539s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 6.961822509765625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 15.209097146987915s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 1049.3631296157837s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.48685479164123535s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0007579326629638672s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 18.771262407302856s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.24387526512146s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 44.38402438163757s
Interoperability | New terms check for Bio2RDF::Drugbank took 41.480064392089844s
Versatility | Languages check for Bio2RDF::Drugbank took 60.25839066505432s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.2642946243286133s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.15514516830444336s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.6665728092193604s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3177297115325928s
Availability | RDF dump link check for Bio2RDF::Drugbank took 2.0862557888031006s
License | MR license check for Bio2RDF::Drugbank took 0.3882122039794922s
License | HR license check for Bio2RDF::Drugbank took 60.25672626495361s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.2540247440338135s
Understandability | Number of label check for Bio2RDF::Drugbank took 10.464410066604614s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5750503540039062s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.25695013999938965s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.24940705299377441s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.261066198348999s
Performance | Throughput check for Bio2RDF::Drugbank took 11.296140909194946s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 74.01519131660461s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.7262692451477051s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.37256407737731934s
Interlinking | skos check for Bio2RDF::Drugbank took 0.7681379318237305s
Interlinking | skos check for Bio2RDF::Drugbank took 0.3341495990753174s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.26270461082458496s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5170755386352539s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5246155261993408s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 108.27175307273865s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 14.401654481887817s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4521470069885254s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.28215837478637695s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.27239036560058594s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 6.654229402542114s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8938653469085693s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6536672115325928s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.38985753059387207s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 64.88842535018921s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.40000057220459s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 5.9253010749816895s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.2995703220367432s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.53337526321411s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.6950609683990479s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.44716405868530273s
Security | Sign check for Bio2RDF::Drugbank took 0.2874140739440918s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 10.516035795211792s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.5066256523132324s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.02096867561340332s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0006833076477050781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00010824203491210938s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 29.71352505683899s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-drugbank took 1046.6384422779083s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 1.2773466110229492s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006358623504638672s
Extra | Recovery of all triples for Bio2RDF::Genage took 19.18129587173462s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2136013507843018s
Amount of data | Number of triples check for Bio2RDF::Genage took 44.476722955703735s
Interoperability | New terms check for Bio2RDF::Genage took 44.03462290763855s
Versatility | Languages check for Bio2RDF::Genage took 60.244805574417114s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2705814838409424s
Security | Check HTTPS for Bio2RDF::Genage took 0.14457178115844727s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.4528343677520752s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.29693078994750977s
Availability | RDF dump link check for Bio2RDF::Genage took 2.411322593688965s
License | MR license check for Bio2RDF::Genage took 0.4635813236236572s
License | HR license check for Bio2RDF::Genage took 60.248697996139526s
Amount of data | Number of property check for Bio2RDF::Genage took 0.26615285873413086s
Understandability | Number of label check for Bio2RDF::Genage took 10.134474515914917s
Understandability | URI regex check for Bio2RDF::Genage took 0.612053632736206s
Understandability | Vocabs check for Bio2RDF::Genage took 0.2654454708099365s
Verifiability | Authors check for Bio2RDF::Genage took 0.2583308219909668s
Verifiability | Publishers check for Bio2RDF::Genage took 0.24530577659606934s
Performance | Throughput check for Bio2RDF::Genage took 11.524682521820068s
Amount of data | Check the number of entities for Bio2RDF::Genage took 75.18967175483704s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.7315232753753662s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.3558065891265869s
Interlinking | skos check for Bio2RDF::Genage took 0.7967307567596436s
Interlinking | skos check for Bio2RDF::Genage took 0.34490156173706055s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2588660717010498s
Currency | Creation date check for Bio2RDF::Genage took 0.5221138000488281s
Currency | Modification date check for Bio2RDF::Genage took 0.5025842189788818s
Rep.Conc. | URIs length for Bio2RDF::Genage took 110.07000994682312s
Interoperability | New vocabularies check for Bio2RDF::Genage took 25.819151878356934s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.42410969734191895s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.29811716079711914s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.2774834632873535s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 6.661599159240723s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8964769840240479s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6528332233428955s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.40729451179504395s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.46855759620667s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.386502504348755s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.19011926651001s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.313873052597046s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.544949769973755s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7074270248413086s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.43080568313598633s
Security | Sign check for Bio2RDF::Genage took 0.2536764144897461s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 10.106053352355957s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.532930850982666s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020888090133666992s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.270408630371094e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 23.4862277507782s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-genage took 1059.3886406421661s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.47565531730651855s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006558895111083984s
Extra | Recovery of all triples for Bio2RDF::Gendr took 18.83026695251465s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.237912893295288s
Amount of data | Number of triples check for Bio2RDF::Gendr took 43.429704427719116s
Interoperability | New terms check for Bio2RDF::Gendr took 39.87259554862976s
Versatility | Languages check for Bio2RDF::Gendr took 60.24337148666382s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.2677955627441406s
Security | Check HTTPS for Bio2RDF::Gendr took 0.15638470649719238s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.6799802780151367s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.30487871170043945s
Availability | RDF dump link check for Bio2RDF::Gendr took 2.2975032329559326s
License | MR license check for Bio2RDF::Gendr took 0.4464130401611328s
License | HR license check for Bio2RDF::Gendr took 60.26621389389038s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.26230621337890625s
Understandability | Number of label check for Bio2RDF::Gendr took 9.825220108032227s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5423028469085693s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.24285387992858887s
Verifiability | Authors check for Bio2RDF::Gendr took 0.25469303131103516s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2543325424194336s
Performance | Throughput check for Bio2RDF::Gendr took 11.098546028137207s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 71.91283893585205s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.7024998664855957s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.34864187240600586s
Interlinking | skos check for Bio2RDF::Gendr took 0.6795644760131836s
Interlinking | skos check for Bio2RDF::Gendr took 0.34701967239379883s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.25426435470581055s
Currency | Creation date check for Bio2RDF::Gendr took 0.5225732326507568s
Currency | Modification date check for Bio2RDF::Gendr took 0.5085020065307617s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 110.7818033695221s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 18.17545485496521s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.4164919853210449s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.24872159957885742s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2698338031768799s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.329563617706299s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8921835422515869s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.641446590423584s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.39196276664733887s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 64.90879559516907s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.375427722930908s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.441296815872192s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.2861900329589844s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.501973152160645s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.6961946487426758s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.4556887149810791s
Security | Sign check for Bio2RDF::Gendr took 0.2698330879211426s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 11.079694986343384s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.5899338722229004s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.021175622940063477s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 32.30493211746216s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-gendr took 1057.2375798225403s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.4891812801361084s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0005879402160644531s
Extra | Recovery of all triples for Bio2RDF::Goa took 19.401937007904053s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2762610912322998s
Amount of data | Number of triples check for Bio2RDF::Goa took 44.18768501281738s
Interoperability | New terms check for Bio2RDF::Goa took 41.17291045188904s
Versatility | Languages check for Bio2RDF::Goa took 60.26881241798401s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.267681360244751s
Security | Check HTTPS for Bio2RDF::Goa took 0.16580796241760254s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.5075218677520752s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.3350791931152344s
Availability | RDF dump link check for Bio2RDF::Goa took 2.4496734142303467s
License | MR license check for Bio2RDF::Goa took 0.4757978916168213s
License | HR license check for Bio2RDF::Goa took 60.257261753082275s
Amount of data | Number of property check for Bio2RDF::Goa took 0.2673971652984619s
Understandability | Number of label check for Bio2RDF::Goa took 9.723222255706787s
Understandability | URI regex check for Bio2RDF::Goa took 0.5553927421569824s
Understandability | Vocabs check for Bio2RDF::Goa took 0.27363038063049316s
Verifiability | Authors check for Bio2RDF::Goa took 0.26695775985717773s
Verifiability | Publishers check for Bio2RDF::Goa took 0.24404621124267578s
Performance | Throughput check for Bio2RDF::Goa took 11.283030986785889s
Amount of data | Check the number of entities for Bio2RDF::Goa took 73.39748430252075s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.5996365547180176s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.3393702507019043s
Interlinking | skos check for Bio2RDF::Goa took 0.9348232746124268s
Interlinking | skos check for Bio2RDF::Goa took 0.34884095191955566s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.2462158203125s
Currency | Creation date check for Bio2RDF::Goa took 0.5310730934143066s
Currency | Modification date check for Bio2RDF::Goa took 0.49333882331848145s
Rep.Conc. | URIs length for Bio2RDF::Goa took 108.55851936340332s
Interoperability | New vocabularies check for Bio2RDF::Goa took 24.60615825653076s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.44809985160827637s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2704958915710449s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.26088595390319824s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.392508268356323s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.894442081451416s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6438419818878174s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.39536499977111816s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 64.96626853942871s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.363138198852539s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 5.978284120559692s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.269716739654541s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.60214328765869s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7285284996032715s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.4013228416442871s
Security | Sign check for Bio2RDF::Goa took 0.27313923835754395s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 10.076396465301514s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.4768812656402588s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 5.817413330078125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 16.876077890396118s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-goa took 1049.8289859294891s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.4807922840118408s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0004138946533203125s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 19.949600219726562s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2265701293945312s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 43.877382040023804s
Interoperability | New terms check for Bio2RDF::Hgnc took 42.17936611175537s
Versatility | Languages check for Bio2RDF::Hgnc took 60.24427247047424s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2586019039154053s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.1543872356414795s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.8853676319122314s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.29206180572509766s
Availability | RDF dump link check for Bio2RDF::Hgnc took 2.423844575881958s
License | MR license check for Bio2RDF::Hgnc took 0.4771709442138672s
License | HR license check for Bio2RDF::Hgnc took 60.23959970474243s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.2557201385498047s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.651251792907715s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.568727970123291s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.23140239715576172s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.25301623344421387s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.2500479221343994s
Performance | Throughput check for Bio2RDF::Hgnc took 11.84661340713501s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 74.90485787391663s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.622107982635498s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.3613591194152832s
Interlinking | skos check for Bio2RDF::Hgnc took 0.6357779502868652s
Interlinking | skos check for Bio2RDF::Hgnc took 0.35012102127075195s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.23327422142028809s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5113990306854248s
Currency | Modification date check for Bio2RDF::Hgnc took 0.48354458808898926s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 109.87293601036072s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 19.768520832061768s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.4158132076263428s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.27322983741760254s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.26147031784057617s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 6.783484935760498s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8927712440490723s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6578052043914795s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.41058850288391113s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.23159837722778s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.361457109451294s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.634421348571777s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.2908143997192383s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.506516456604004s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7058429718017578s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.4627859592437744s
Security | Sign check for Bio2RDF::Hgnc took 0.2624518871307373s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 14.021547794342041s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.4817159175872803s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.021105527877807617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00014591217041015625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 20.652783632278442s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-hgnc took 1054.363464832306s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.5029222965240479s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0005691051483154297s
Extra | Recovery of all triples for Bio2RDF::Homologene took 18.193608045578003s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.253364086151123s
Amount of data | Number of triples check for Bio2RDF::Homologene took 43.448039054870605s
Interoperability | New terms check for Bio2RDF::Homologene took 41.33208394050598s
Versatility | Languages check for Bio2RDF::Homologene took 60.2493200302124s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.28199315071105957s
Security | Check HTTPS for Bio2RDF::Homologene took 0.15204381942749023s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.5322701930999756s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.3236348628997803s
Availability | RDF dump link check for Bio2RDF::Homologene took 2.066958427429199s
License | MR license check for Bio2RDF::Homologene took 0.6217098236083984s
License | HR license check for Bio2RDF::Homologene took 60.25043511390686s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.2540767192840576s
Understandability | Number of label check for Bio2RDF::Homologene took 9.219627141952515s
Understandability | URI regex check for Bio2RDF::Homologene took 0.6087284088134766s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.25344371795654297s
Verifiability | Authors check for Bio2RDF::Homologene took 0.27239155769348145s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.24097490310668945s
Performance | Throughput check for Bio2RDF::Homologene took 11.231608390808105s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 76.03346109390259s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.5747408866882324s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.35251927375793457s
Interlinking | skos check for Bio2RDF::Homologene took 0.7248237133026123s
Interlinking | skos check for Bio2RDF::Homologene took 0.3505122661590576s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.24640965461730957s
Currency | Creation date check for Bio2RDF::Homologene took 0.5279607772827148s
Currency | Modification date check for Bio2RDF::Homologene took 0.4880244731903076s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 108.99662399291992s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 14.606667041778564s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.39261817932128906s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.28660154342651367s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.24544668197631836s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 6.954139947891235s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8954095840454102s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6488029956817627s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.4273560047149658s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.11456251144409s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.405245065689087s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.984555006027222s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3112256526947021s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.542638301849365s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.741358757019043s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.4250001907348633s
Security | Sign check for Bio2RDF::Homologene took 0.2694835662841797s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 10.080549478530884s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.49061131477355957s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.02092576026916504s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.53131103515625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 22.011383056640625s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-homologene took 1036.5638134479523s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.4744534492492676s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0006988048553466797s
Extra | Recovery of all triples for Bio2RDF::Interpro took 19.92002272605896s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2441833019256592s
Amount of data | Number of triples check for Bio2RDF::Interpro took 44.44415473937988s
Interoperability | New terms check for Bio2RDF::Interpro took 41.658122301101685s
Versatility | Languages check for Bio2RDF::Interpro took 60.252233028411865s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.279285192489624s
Security | Check HTTPS for Bio2RDF::Interpro took 0.1565852165222168s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.4785590171813965s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.3111879825592041s
Availability | RDF dump link check for Bio2RDF::Interpro took 2.4648778438568115s
License | MR license check for Bio2RDF::Interpro took 0.4462006092071533s
License | HR license check for Bio2RDF::Interpro took 60.26828598976135s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2619156837463379s
Understandability | Number of label check for Bio2RDF::Interpro took 10.432183742523193s
Understandability | URI regex check for Bio2RDF::Interpro took 0.6001617908477783s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.23243427276611328s
Verifiability | Authors check for Bio2RDF::Interpro took 0.274660587310791s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.26556897163391113s
Performance | Throughput check for Bio2RDF::Interpro took 11.240006446838379s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 77.50316953659058s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.6184303760528564s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.3622732162475586s
Interlinking | skos check for Bio2RDF::Interpro took 0.8383467197418213s
Interlinking | skos check for Bio2RDF::Interpro took 0.35039210319519043s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.24395227432250977s
Currency | Creation date check for Bio2RDF::Interpro took 0.544710636138916s
Currency | Modification date check for Bio2RDF::Interpro took 0.5040488243103027s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 110.5593683719635s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 20.427067756652832s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.43035030364990234s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.25670671463012695s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2725841999053955s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 7.484086513519287s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8959527015686035s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6664009094238281s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.40610194206237793s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 66.00597953796387s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.423931360244751s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.597182750701904s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.29386568069458s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.545449018478394s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7378180027008057s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.41826391220092773s
Security | Sign check for Bio2RDF::Interpro took 0.2867469787597656s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 11.440528631210327s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.3453354835510254s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.02084660530090332s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010275840759277344s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 22.30874514579773s
Believability | Calculation of trust value for Bio2RDF::Interpro took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-interpro took 1057.5296602249146s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.1415097713470459s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.384890079498291s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.021060466766357422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.82012939453125e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-iproclass took 16.237730264663696s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.4723067283630371s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0006268024444580078s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 18.843071222305298s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2395572662353516s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 43.42806386947632s
Interoperability | New terms check for Bio2RDF::Irefindex took 41.51435375213623s
Versatility | Languages check for Bio2RDF::Irefindex took 60.25071406364441s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.24695158004760742s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.15583205223083496s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.6282732486724854s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.3279428482055664s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.4013783931732178s
License | MR license check for Bio2RDF::Irefindex took 0.48496413230895996s
License | HR license check for Bio2RDF::Irefindex took 60.249924421310425s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.2563507556915283s
Understandability | Number of label check for Bio2RDF::Irefindex took 9.660964012145996s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.591101884841919s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.27390289306640625s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.2516961097717285s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.247572660446167s
Performance | Throughput check for Bio2RDF::Irefindex took 11.541159629821777s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 74.73843693733215s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.6111559867858887s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.3581550121307373s
Interlinking | skos check for Bio2RDF::Irefindex took 0.7246596813201904s
Interlinking | skos check for Bio2RDF::Irefindex took 0.3724551200866699s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.2557086944580078s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5206563472747803s
Currency | Modification date check for Bio2RDF::Irefindex took 0.49126744270324707s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 109.9875226020813s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 21.434316635131836s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.3993561267852783s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2766757011413574s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.28922438621520996s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 6.936070919036865s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.9049198627471924s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6576547622680664s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.4170098304748535s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 64.92340850830078s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.3619637489318848s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.29356837272644s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.2938153743743896s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.52819609642029s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7004659175872803s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.42792510986328125s
Security | Sign check for Bio2RDF::Irefindex took 0.2662224769592285s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 9.773314476013184s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.521507740020752s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.02114081382751465s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 7.939338684082031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 22.44815468788147s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1042.316948890686s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.13946866989135742s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2880737781524658s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 4.124641418457031e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 9.313523769378662s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.4733402729034424s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0006968975067138672s
Extra | Recovery of all triples for Bio2RDF::Lsr took 19.589534997940063s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.253509759902954s
Amount of data | Number of triples check for Bio2RDF::Lsr took 44.20682191848755s
Interoperability | New terms check for Bio2RDF::Lsr took 42.83076071739197s
Versatility | Languages check for Bio2RDF::Lsr took 60.23477864265442s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.27572059631347656s
Security | Check HTTPS for Bio2RDF::Lsr took 0.15477657318115234s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.47793078422546387s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.32022619247436523s
Availability | RDF dump link check for Bio2RDF::Lsr took 2.4326698780059814s
License | MR license check for Bio2RDF::Lsr took 0.4737720489501953s
License | HR license check for Bio2RDF::Lsr took 60.24399471282959s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.2533266544342041s
Understandability | Number of label check for Bio2RDF::Lsr took 9.523446083068848s
Understandability | URI regex check for Bio2RDF::Lsr took 0.6115176677703857s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.24620890617370605s
Verifiability | Authors check for Bio2RDF::Lsr took 0.25005364418029785s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.2585170269012451s
Performance | Throughput check for Bio2RDF::Lsr took 11.50781536102295s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 72.43675494194031s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.7141079902648926s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.34076714515686035s
Interlinking | skos check for Bio2RDF::Lsr took 0.6881003379821777s
Interlinking | skos check for Bio2RDF::Lsr took 0.33664512634277344s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.264392614364624s
Currency | Creation date check for Bio2RDF::Lsr took 0.5382256507873535s
Currency | Modification date check for Bio2RDF::Lsr took 0.48665380477905273s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 111.20657730102539s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 31.535691261291504s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.4139578342437744s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.27311110496520996s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.28847479820251465s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 7.105071067810059s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.9022467136383057s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6585540771484375s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.4403223991394043s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.39203643798828s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.36795711517334s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 5.871577978134155s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.2561562061309814s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.50344920158386s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.6946015357971191s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.40923547744750977s
Security | Sign check for Bio2RDF::Lsr took 0.24840354919433594s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 10.257977724075317s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.46850156784057617s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02076578140258789s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 18.662919759750366s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-lsr took 1052.9862327575684s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.4762282371520996s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0006043910980224609s
Extra | Recovery of all triples for Bio2RDF::Mesh took 18.800992012023926s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2155568599700928s
Amount of data | Number of triples check for Bio2RDF::Mesh took 43.933016777038574s
Interoperability | New terms check for Bio2RDF::Mesh took 41.46471929550171s
Versatility | Languages check for Bio2RDF::Mesh took 60.233530044555664s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.25881505012512207s
Security | Check HTTPS for Bio2RDF::Mesh took 0.1556384563446045s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.6510756015777588s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.31116557121276855s
Availability | RDF dump link check for Bio2RDF::Mesh took 2.1833817958831787s
License | MR license check for Bio2RDF::Mesh took 0.5081861019134521s
License | HR license check for Bio2RDF::Mesh took 60.25194263458252s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.2534494400024414s
Understandability | Number of label check for Bio2RDF::Mesh took 10.330570936203003s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5695114135742188s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.24857735633850098s
Verifiability | Authors check for Bio2RDF::Mesh took 0.24183201789855957s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.270627498626709s
Performance | Throughput check for Bio2RDF::Mesh took 11.908206224441528s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 71.15165567398071s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.5967330932617188s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.3335428237915039s
Interlinking | skos check for Bio2RDF::Mesh took 0.8714413642883301s
Interlinking | skos check for Bio2RDF::Mesh took 0.5187318325042725s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.24480891227722168s
Currency | Creation date check for Bio2RDF::Mesh took 0.5007941722869873s
Currency | Modification date check for Bio2RDF::Mesh took 0.5114889144897461s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 109.20629000663757s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 13.623263120651245s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.4228527545928955s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2717149257659912s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.24417662620544434s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 6.702409744262695s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8909790515899658s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6281027793884277s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.3913748264312744s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 64.86488938331604s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.3376410007476807s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.437836408615112s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.2557225227355957s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.508610010147095s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.6832180023193359s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.46399378776550293s
Security | Sign check for Bio2RDF::Mesh took 0.2750508785247803s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 9.82357668876648s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.5351424217224121s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.02075505256652832s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 8.7738037109375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 18.4286687374115s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-mesh took 1032.0504744052887s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.48278355598449707s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0007727146148681641s
Extra | Recovery of all triples for Bio2RDF::Mgi took 18.77790880203247s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.230971097946167s
Amount of data | Number of triples check for Bio2RDF::Mgi took 43.43100881576538s
Interoperability | New terms check for Bio2RDF::Mgi took 44.168622970581055s
Versatility | Languages check for Bio2RDF::Mgi took 60.255597829818726s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.27321410179138184s
Security | Check HTTPS for Bio2RDF::Mgi took 0.16688203811645508s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.8384056091308594s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.29015231132507324s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.454922676086426s
License | MR license check for Bio2RDF::Mgi took 0.45713019371032715s
License | HR license check for Bio2RDF::Mgi took 60.23318600654602s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.25218725204467773s
Understandability | Number of label check for Bio2RDF::Mgi took 9.737268209457397s
Understandability | URI regex check for Bio2RDF::Mgi took 0.6129848957061768s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.2635972499847412s
Verifiability | Authors check for Bio2RDF::Mgi took 0.24912142753601074s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.2606387138366699s
Performance | Throughput check for Bio2RDF::Mgi took 12.048807144165039s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 73.17593836784363s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.735649824142456s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.34273219108581543s
Interlinking | skos check for Bio2RDF::Mgi took 0.9337954521179199s
Interlinking | skos check for Bio2RDF::Mgi took 0.3522968292236328s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.24380731582641602s
Currency | Creation date check for Bio2RDF::Mgi took 0.5331916809082031s
Currency | Modification date check for Bio2RDF::Mgi took 0.4820263385772705s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 108.32590556144714s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 25.031376838684082s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.3983280658721924s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.26826047897338867s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.28156065940856934s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 6.964557647705078s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8983585834503174s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6475234031677246s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.44188594818115234s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.26848649978638s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.4080846309661865s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.0669167041778564s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.32625412940979s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.53228688240051s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7183301448822021s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.4490935802459717s
Security | Sign check for Bio2RDF::Mgi took 0.2657754421234131s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 11.231937885284424s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.3367440700531006s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.989738464355469e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 20.614620685577393s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-mgi took 1051.4076266288757s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.48271751403808594s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0006666183471679688s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 17.89080810546875s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2608652114868164s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 43.81276869773865s
Interoperability | New terms check for Bio2RDF::Ncbigene took 41.59750747680664s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.256386041641235s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.2634999752044678s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.16667795181274414s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.9104087352752686s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.3123042583465576s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 2.2226200103759766s
License | MR license check for Bio2RDF::Ncbigene took 0.6207747459411621s
License | HR license check for Bio2RDF::Ncbigene took 60.25806379318237s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.2434384822845459s
Understandability | Number of label check for Bio2RDF::Ncbigene took 10.205629110336304s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.5627977848052979s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.2626652717590332s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.258181095123291s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.23192906379699707s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.38584852218628s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 74.50605010986328s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.6039552688598633s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.3797719478607178s
Interlinking | skos check for Bio2RDF::Ncbigene took 1.028630018234253s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.3541266918182373s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.23607945442199707s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.49461960792541504s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.49996423721313477s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 108.83955192565918s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 13.336279392242432s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.4257969856262207s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2812378406524658s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.2781860828399658s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 6.934929132461548s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8936383724212646s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6527636051177979s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.553260087966919s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.76235723495483s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.394066095352173s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.091772079467773s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.3032939434051514s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.54089093208313s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.708061695098877s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.44046807289123535s
Security | Sign check for Bio2RDF::Ncbigene took 0.2697310447692871s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 9.934877395629883s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.5151402950286865s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020906925201416016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00011801719665527344s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 15.417300462722778s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1038.2798471450806s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.47162437438964844s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.000667572021484375s
Extra | Recovery of all triples for Bio2RDF::Ndc took 19.25643014907837s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2194149494171143s
Amount of data | Number of triples check for Bio2RDF::Ndc took 43.46041297912598s
Interoperability | New terms check for Bio2RDF::Ndc took 41.853575706481934s
Versatility | Languages check for Bio2RDF::Ndc took 60.26378083229065s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.2643301486968994s
Security | Check HTTPS for Bio2RDF::Ndc took 0.14384865760803223s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.7899923324584961s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.30089330673217773s
Availability | RDF dump link check for Bio2RDF::Ndc took 2.1983389854431152s
License | MR license check for Bio2RDF::Ndc took 0.447277307510376s
License | HR license check for Bio2RDF::Ndc took 60.23733735084534s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.26673269271850586s
Understandability | Number of label check for Bio2RDF::Ndc took 10.323147535324097s
Understandability | URI regex check for Bio2RDF::Ndc took 0.606677770614624s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.24699878692626953s
Verifiability | Authors check for Bio2RDF::Ndc took 0.2595207691192627s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.2586815357208252s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 76.93765377998352s
Verifiability | Contribs. check for Bio2RDF::Ndc took 2.0550575256347656s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.3478660583496094s
Interlinking | skos check for Bio2RDF::Ndc took 0.7637248039245605s
Interlinking | skos check for Bio2RDF::Ndc took 0.34458160400390625s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.26363587379455566s
Currency | Creation date check for Bio2RDF::Ndc took 0.496351957321167s
Currency | Modification date check for Bio2RDF::Ndc took 0.5017111301422119s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 107.75350093841553s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 15.917088747024536s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.42864561080932617s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2659010887145996s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.27063417434692383s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 7.413264274597168s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8986589908599854s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.664104700088501s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.4058682918548584s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.28515768051147s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.400970697402954s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.532150506973267s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.2964606285095215s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.549347162246704s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7324914932250977s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.4460933208465576s
Security | Sign check for Bio2RDF::Ndc took 0.27121472358703613s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 10.385467290878296s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.5162527561187744s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.021145343780517578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.507469177246094e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 21.25492811203003s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-ndc took 1040.1871700286865s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.13480544090270996s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.3103480339050293s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.02122211456298828s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.552436828613281e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-nextprot took 3.658942699432373s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.4980282783508301s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0005705356597900391s
Extra | Recovery of all triples for Bio2RDF::Omim took 18.321143627166748s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.2735531330108643s
Amount of data | Number of triples check for Bio2RDF::Omim took 43.78440546989441s
Interoperability | New terms check for Bio2RDF::Omim took 42.70002102851868s
Versatility | Languages check for Bio2RDF::Omim took 60.25910496711731s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.25342750549316406s
Security | Check HTTPS for Bio2RDF::Omim took 0.1560497283935547s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.7995572090148926s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.34033989906311035s
Availability | RDF dump link check for Bio2RDF::Omim took 2.5498502254486084s
License | MR license check for Bio2RDF::Omim took 0.46889281272888184s
License | HR license check for Bio2RDF::Omim took 60.23660588264465s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2614288330078125s
Understandability | Number of label check for Bio2RDF::Omim took 9.763182640075684s
Understandability | URI regex check for Bio2RDF::Omim took 0.5550484657287598s
Understandability | Vocabs check for Bio2RDF::Omim took 0.24291181564331055s
Verifiability | Authors check for Bio2RDF::Omim took 0.2513883113861084s
Verifiability | Publishers check for Bio2RDF::Omim took 0.24684691429138184s
Performance | Throughput check for Bio2RDF::Omim took 11.657890796661377s
Amount of data | Check the number of entities for Bio2RDF::Omim took 75.04051494598389s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.7690873146057129s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.34266018867492676s
Interlinking | skos check for Bio2RDF::Omim took 0.7956821918487549s
Interlinking | skos check for Bio2RDF::Omim took 0.3976266384124756s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.23516249656677246s
Currency | Creation date check for Bio2RDF::Omim took 0.4978642463684082s
Currency | Modification date check for Bio2RDF::Omim took 0.5196948051452637s
Rep.Conc. | URIs length for Bio2RDF::Omim took 109.01681971549988s
Interoperability | New vocabularies check for Bio2RDF::Omim took 106.27543354034424s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4221351146697998s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.2785029411315918s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.264373779296875s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 7.018039703369141s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.903902530670166s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6464009284973145s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.39469408988952637s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.10987830162048s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.3774826526641846s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 5.999894618988037s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.2599999904632568s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.75287747383118s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7080111503601074s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.41858673095703125s
Security | Sign check for Bio2RDF::Omim took 0.27936220169067383s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 9.85427188873291s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.4880709648132324s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.0001308917999267578s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 31.3807692527771s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-omim took 1141.7461714744568s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 9.298324584960938e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.3005526065826416s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.02077651023864746s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.910064697265625e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 3.2262299060821533s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.46717023849487305s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0008780956268310547s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 18.26720142364502s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.241217851638794s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 44.38509821891785s
Interoperability | New terms check for Bio2RDF::Orphanet took 40.40836954116821s
Versatility | Languages check for Bio2RDF::Orphanet took 60.24033164978027s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.25026679039001465s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.15631747245788574s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.8212699890136719s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.28992795944213867s
Availability | RDF dump link check for Bio2RDF::Orphanet took 2.4025380611419678s
License | MR license check for Bio2RDF::Orphanet took 0.5421388149261475s
License | HR license check for Bio2RDF::Orphanet took 60.25450921058655s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.27423906326293945s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.386368751525879s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5808217525482178s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.27237462997436523s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.2511608600616455s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.2769010066986084s
Performance | Throughput check for Bio2RDF::Orphanet took 11.168575763702393s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 73.75059771537781s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.5603077411651611s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.4018974304199219s
Interlinking | skos check for Bio2RDF::Orphanet took 0.866253137588501s
Interlinking | skos check for Bio2RDF::Orphanet took 0.352475643157959s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.25564002990722656s
Currency | Creation date check for Bio2RDF::Orphanet took 0.49521780014038086s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5031347274780273s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 107.73694729804993s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 20.3849036693573s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.44367074966430664s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2957026958465576s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.28107476234436035s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 7.061546564102173s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.9030427932739258s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6664772033691406s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.515265703201294s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.14448165893555s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.3752920627593994s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.68172025680542s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.2739653587341309s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.54385590553284s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7066957950592041s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.45176124572753906s
Security | Sign check for Bio2RDF::Orphanet took 0.263016939163208s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 11.265931606292725s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.45246267318725586s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.020910263061523438s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 7.748603820800781e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 26.112325191497803s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1050.7448658943176s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.14077281951904297s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.2991766929626465s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.021789073944091797s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-pathwaycommons took 9.781095504760742s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.48579835891723633s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.00033593177795410156s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 19.183942079544067s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2444212436676025s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 44.00494384765625s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 42.168060064315796s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.23992705345154s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.2794532775878906s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.16884565353393555s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.38474202156066895s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.31682443618774414s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 2.428583860397339s
License | MR license check for Bio2RDF::Pharmgkb took 0.4717559814453125s
License | HR license check for Bio2RDF::Pharmgkb took 60.26086187362671s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.26428747177124023s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 9.905032873153687s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5648684501647949s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.2618393898010254s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.27021360397338867s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.25586915016174316s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.311270713806152s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 73.41920971870422s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.572437047958374s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.26387643814086914s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.820997953414917s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.3481001853942871s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.2525322437286377s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5225372314453125s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5221066474914551s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 107.96499609947205s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 23.253914833068848s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.4543948173522949s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.2694528102874756s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.23036718368530273s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 6.272356986999512s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.9042365550994873s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6638288497924805s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.49056553840637207s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 64.90125393867493s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.3723950386047363s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.254799127578735s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.297071933746338s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.537447929382324s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7138404846191406s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.4184131622314453s
Security | Sign check for Bio2RDF::Pharmgkb took 0.27190089225769043s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 9.867722511291504s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.4652385711669922s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.023546218872070312s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.605552673339844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 24.541049242019653s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 1051.0428619384766s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.4666287899017334s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.000659942626953125s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 18.439275979995728s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2268860340118408s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 44.56670165061951s
Interoperability | New terms check for Bio2RDF::Pubmed took 39.9567015171051s
Versatility | Languages check for Bio2RDF::Pubmed took 60.22860407829285s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.29466843605041504s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.14561915397644043s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.5439529418945312s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.31223177909851074s
Availability | RDF dump link check for Bio2RDF::Pubmed took 2.2705986499786377s
License | MR license check for Bio2RDF::Pubmed took 0.45840001106262207s
License | HR license check for Bio2RDF::Pubmed took 60.25227379798889s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.2501106262207031s
Understandability | Number of label check for Bio2RDF::Pubmed took 10.382631063461304s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5905237197875977s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.25017571449279785s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.2737267017364502s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.2445821762084961s
Performance | Throughput check for Bio2RDF::Pubmed took 11.145636796951294s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 72.83792161941528s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.553948163986206s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.3556063175201416s
Interlinking | skos check for Bio2RDF::Pubmed took 0.8516192436218262s
Interlinking | skos check for Bio2RDF::Pubmed took 0.349916934967041s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2451941967010498s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5013983249664307s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5155959129333496s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 108.50637340545654s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 14.939677953720093s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.4754459857940674s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.2723073959350586s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.2699117660522461s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 7.2755656242370605s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8927402496337891s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.649139404296875s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.37762975692749023s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.19534277915955s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.3535304069519043s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.292064428329468s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.2986366748809814s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.50039744377136s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.6868596076965332s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.3959014415740967s
Security | Sign check for Bio2RDF::Pubmed took 0.2745635509490967s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 10.255893468856812s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.5504977703094482s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.02196192741394043s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00014328956604003906s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 15.676252841949463s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.8358230590820312e-05s
INFO | --- Analysis for bio2rdf-pubmed took 1029.1272382736206s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.13687920570373535s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.26138758659362793s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.02082514762878418s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.605552673339844e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-sabiork took 9.258610248565674s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.47746777534484863s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0005872249603271484s
Extra | Recovery of all triples for Bio2RDF::Sgd took 18.9408860206604s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.241072177886963s
Amount of data | Number of triples check for Bio2RDF::Sgd took 43.385610818862915s
Interoperability | New terms check for Bio2RDF::Sgd took 41.18590307235718s
Versatility | Languages check for Bio2RDF::Sgd took 60.259472608566284s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.3143739700317383s
Security | Check HTTPS for Bio2RDF::Sgd took 0.15602660179138184s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.6085286140441895s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.2932250499725342s
Availability | RDF dump link check for Bio2RDF::Sgd took 2.099801540374756s
License | MR license check for Bio2RDF::Sgd took 0.4870436191558838s
License | HR license check for Bio2RDF::Sgd took 60.25608968734741s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.24712252616882324s
Understandability | Number of label check for Bio2RDF::Sgd took 10.456299543380737s
Understandability | URI regex check for Bio2RDF::Sgd took 0.5823047161102295s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.25426387786865234s
Verifiability | Authors check for Bio2RDF::Sgd took 0.2638537883758545s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.2750213146209717s
Performance | Throughput check for Bio2RDF::Sgd took 10.992236852645874s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 76.95219302177429s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.5464210510253906s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.3548893928527832s
Interlinking | skos check for Bio2RDF::Sgd took 0.8188915252685547s
Interlinking | skos check for Bio2RDF::Sgd took 0.3407328128814697s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2577240467071533s
Currency | Creation date check for Bio2RDF::Sgd took 0.48648881912231445s
Currency | Modification date check for Bio2RDF::Sgd took 0.5205118656158447s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 107.20865321159363s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 22.475223779678345s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.4527394771575928s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2623300552368164s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.2507960796356201s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 7.046091079711914s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.9034578800201416s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6612832546234131s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.39521265029907227s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 64.88500452041626s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.338744640350342s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.523422956466675s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.2644782066345215s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.517255783081055s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.6965248584747314s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.44618988037109375s
Security | Sign check for Bio2RDF::Sgd took 0.24638080596923828s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 9.963488578796387s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.5448312759399414s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020965099334716797s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010442733764648438s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 14.95527982711792s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-sgd took 1039.0469062328339s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 8.678436279296875e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.3279244899749756s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020853519439697266s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 4.124641418457031e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 3.1412758827209473s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.4613626003265381s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0006475448608398438s
Extra | Recovery of all triples for Bio2RDF::Sider took 18.535568952560425s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2460150718688965s
Amount of data | Number of triples check for Bio2RDF::Sider took 43.86944103240967s
Interoperability | New terms check for Bio2RDF::Sider took 40.46912670135498s
Versatility | Languages check for Bio2RDF::Sider took 60.253273487091064s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.28975462913513184s
Security | Check HTTPS for Bio2RDF::Sider took 0.14264154434204102s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.6019308567047119s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.32685232162475586s
Availability | RDF dump link check for Bio2RDF::Sider took 2.3792450428009033s
License | MR license check for Bio2RDF::Sider took 0.46874547004699707s
License | HR license check for Bio2RDF::Sider took 60.24821424484253s
Amount of data | Number of property check for Bio2RDF::Sider took 0.26631808280944824s
Understandability | Number of label check for Bio2RDF::Sider took 9.444963693618774s
Understandability | URI regex check for Bio2RDF::Sider took 0.6022593975067139s
Understandability | Vocabs check for Bio2RDF::Sider took 0.24927496910095215s
Verifiability | Authors check for Bio2RDF::Sider took 0.26091885566711426s
Verifiability | Publishers check for Bio2RDF::Sider took 0.2616744041442871s
Performance | Throughput check for Bio2RDF::Sider took 11.093398571014404s
Amount of data | Check the number of entities for Bio2RDF::Sider took 73.97604513168335s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.5795853137969971s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.39931511878967285s
Interlinking | skos check for Bio2RDF::Sider took 0.9424870014190674s
Interlinking | skos check for Bio2RDF::Sider took 0.35285234451293945s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.2651486396789551s
Currency | Creation date check for Bio2RDF::Sider took 0.5063860416412354s
Currency | Modification date check for Bio2RDF::Sider took 0.5066006183624268s
Rep.Conc. | URIs length for Bio2RDF::Sider took 107.62464737892151s
Interoperability | New vocabularies check for Bio2RDF::Sider took 68.54167127609253s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.4613494873046875s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.2741982936859131s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.27237915992736816s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 7.913945436477661s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8941531181335449s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6397559642791748s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.43570423126220703s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 64.82211971282959s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.421671152114868s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.472485780715942s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.3221871852874756s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.52661347389221s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7066032886505127s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.607806921005249s
Security | Sign check for Bio2RDF::Sider took 0.281414270401001s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 11.64537763595581s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.3185126781463623s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020867586135864258s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 12.863538265228271s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-sider took 1088.5586926937103s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.315376281738281e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.27960658073425293s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.021428346633911133s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.291534423828125e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-taxon took 2.8471896648406982s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.4582498073577881s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0005819797515869141s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 19.686875343322754s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2476279735565186s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 43.956154584884644s
Interoperability | New terms check for Bio2RDF::Taxonomy took 41.73105430603027s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.263813734054565s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2847788333892822s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.14291644096374512s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.816641092300415s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.3120119571685791s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 2.2943475246429443s
License | MR license check for Bio2RDF::Taxonomy took 0.5595347881317139s
License | HR license check for Bio2RDF::Taxonomy took 60.24055027961731s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.2454848289489746s
Understandability | Number of label check for Bio2RDF::Taxonomy took 9.824652671813965s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.6121892929077148s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.23940825462341309s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.2644054889678955s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.26560449600219727s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.338226795196533s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 72.14465236663818s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.5737178325653076s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.34551024436950684s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.7354967594146729s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.34819531440734863s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.27296948432922363s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5131337642669678s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.4824342727661133s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 107.84912705421448s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 14.936595916748047s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4282398223876953s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.27185511589050293s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.2752206325531006s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 6.911760568618774s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.9105536937713623s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6591634750366211s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.4187805652618408s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.04183101654053s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.3784942626953125s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.326214790344238s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.2974834442138672s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.5449013710022s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7130258083343506s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.4029712677001953s
Security | Sign check for Bio2RDF::Taxonomy took 0.2607753276824951s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 18.31224489212036s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.49167466163635254s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020823001861572266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 9.965896606445312e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 26.480883359909058s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 1051.9787182807922s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.1393423080444336s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.3620302677154541s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020954132080078125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.981590270996094e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 16.786978721618652s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.4654092788696289s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0005781650543212891s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 19.33647322654724s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.2392017841339111s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 44.012004137039185s
Interoperability | New terms check for Bio2RDF::Wormbase took 43.21079707145691s
Versatility | Languages check for Bio2RDF::Wormbase took 60.24606800079346s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.25496935844421387s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.15342235565185547s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.7058281898498535s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.28592658042907715s
Availability | RDF dump link check for Bio2RDF::Wormbase took 2.2926025390625s
License | MR license check for Bio2RDF::Wormbase took 0.48250412940979004s
License | HR license check for Bio2RDF::Wormbase took 60.24478054046631s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.26260852813720703s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.456758260726929s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.5863082408905029s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.2454216480255127s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.25928258895874023s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.24691224098205566s
Performance | Throughput check for Bio2RDF::Wormbase took 11.552786827087402s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 72.92728877067566s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 1.4201624393463135s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.3625307083129883s
Interlinking | skos check for Bio2RDF::Wormbase took 0.8563988208770752s
Interlinking | skos check for Bio2RDF::Wormbase took 0.34102535247802734s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.25138068199157715s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5087614059448242s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5103473663330078s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 107.34797358512878s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 18.271571159362793s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.4305455684661865s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.27392053604125977s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.28233814239501953s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 6.509474515914917s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8959217071533203s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6519801616668701s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.40408849716186523s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 64.8693585395813s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.393911123275757s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.349593877792358s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.2974953651428223s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.528298139572144s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7158915996551514s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.46466779708862305s
Security | Sign check for Bio2RDF::Wormbase took 0.27779412269592285s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 12.862076044082642s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.4615192413330078s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.02077007293701172s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.296966552734375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 19.940972328186035s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-wormbase took 1046.0400397777557s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 8.845329284667969e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.26889514923095703s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.1920928955078125e-05s
Believability | Calculation of trust value for Biografías y Vidas took 1.1205673217773438e-05s
INFO | --- Analysis for biografiasyvidas took 2.6528329849243164s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.2890336513519287s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.3005092144012451s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020629167556762695s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.225440979003906e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 8.344650268554688e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.0132436752319336s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 8.678436279296875e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0011281967163085938s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.317840576171875s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0009140968322753906s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.3392181396484375e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.1444091796875e-05s
INFO | --- Analysis for biolod-pdb took 7.422967910766602s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.4968879222869873s
Availability | VoID file availability check for BioModels RDF took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.41089630126953125s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020745515823364258s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0008947849273681641s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 4.6253204345703125e-05s
Believability | Calculation of trust value for BioModels RDF took 1.1444091796875e-05s
INFO | --- Analysis for biomodels-rdf took 4.011333703994751s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.3455886840820312s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.3274548053741455s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02098679542541504s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.24249267578125e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 9.5367431640625e-06s
INFO | --- Analysis for Biop took 6.466268062591553s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.131431579589844e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.28954052925109863s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02197861671447754s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0009608268737792969s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.100799560546875e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1682510375976562e-05s
INFO | --- Analysis for Bioportal took 2.8014094829559326s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 6.985664367675781e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0010480880737304688s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.29967617988586426s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020659923553466797s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006365776062011719s
Believability | Calculation of trust value for Amphibian gross anatomy took 7.62939453125e-06s
INFO | --- Analysis for bioportal-aao took 5.187891960144043s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.649162292480469e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.000850677490234375s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.3036613464355469s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.021100521087646484s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0003237724304199219s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-aba took 4.350514888763428s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2767982482910156s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0014810562133789062s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-acgt took 4.110203981399536s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.363059997558594e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.3061661720275879s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003275871276855469s
Believability | Calculation of trust value for Animal natural history and life history took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-adw took 4.235436201095581s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 5.1021575927734375e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.2782711982727051s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020873069763183594s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004630088806152344s
Believability | Calculation of trust value for Anatomical Entity Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-aeo took 4.335268974304199s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 0.00011086463928222656s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.30038976669311523s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.02099919319152832s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009605884552001953s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-aero took 4.540279865264893s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.1961669921875e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.3014669418334961s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.021626710891723633s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.00039958953857421875s
Believability | Calculation of trust value for AI/RHEUM took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-air took 4.357456207275391s
Availability | SPARQL endpoint availability check for Amino Acid took 8.726119995117188e-05s
Availability | VoID file availability check for Amino Acid took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.3301088809967041s
Reputation | Calculation of the PageRank for Amino Acid took 0.021720170974731445s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0010962486267089844s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.000331878662109375s
Believability | Calculation of trust value for Amino Acid took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-amino-acid took 4.480491638183594s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0007450580596923828s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.32639265060424805s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.021593332290649414s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.00030684471130371094s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-apo took 4.223021507263184s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 8.988380432128906e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0007271766662597656s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.3282930850982666s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.02068161964416504s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00025010108947753906s
Believability | Calculation of trust value for African Traditional Medicine took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-atmo took 4.278882741928101s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 9.465217590332031e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.28737354278564453s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.022521018981933594s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 8.845329284667969e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ato took 4.158068418502808s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.2842991352081299s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.02122807502746582s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013179779052734375s
Believability | Calculation of trust value for BioAssay Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-bao took 4.221448659896851s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 8.702278137207031e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.32619285583496094s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020930051803588867s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003714561462402344s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 4.30437707901001s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0003609657287597656s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.2789332866668701s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.000316619873046875s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-bcgo took 4.298193693161011s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0008597373962402344s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.28942179679870605s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.001397848129272461s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-bdo took 4.257965087890625s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0007965564727783203s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.2632789611816406s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.02077960968017578s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0009953975677490234s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005719661712646484s
Believability | Calculation of trust value for Basic Formal Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bfo took 4.302693605422974s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 8.940696716308594e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0007791519165039062s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.2871389389038086s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.021004438400268555s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007469654083251953s
Believability | Calculation of trust value for Bleeding History Phenotype took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-bho took 4.129462957382202s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 8.416175842285156e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.28646063804626465s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.02137923240661621s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004296302795410156s
Believability | Calculation of trust value for Bilateria anatomy took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-bila took 4.732547998428345s
Availability | SPARQL endpoint availability check for BIRNLex took 8.630752563476562e-05s
Availability | VoID file availability check for BIRNLex took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.2696564197540283s
Reputation | Calculation of the PageRank for BIRNLex took 0.020924806594848633s
Interlinking | Calculation of Degree of Connection for BIRNLex took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.001474618911743164s
Believability | Calculation of trust value for BIRNLex took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-birnlex took 4.209701061248779s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 0.00013065338134765625s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2821781635284424s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007131099700927734s
Believability | Calculation of trust value for Gene Regulation Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bootstrep took 4.157131671905518s
Availability | SPARQL endpoint availability check for BioPAX took 4.363059997558594e-05s
Availability | VoID file availability check for BioPAX took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for BioPAX took 0.28996753692626953s
Reputation | Calculation of the PageRank for BioPAX took 0.02045130729675293s
Interlinking | Calculation of Degree of Connection for BioPAX took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioPAX took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.489059448242188e-05s
Believability | Calculation of trust value for BioPAX took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bp took 4.274078845977783s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.3198111057281494s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.021050214767456055s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003364086151123047s
Believability | Calculation of trust value for Biomedical Resource Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bro_x1 took 4.256092309951782s
Availability | SPARQL endpoint availability check for Spatial Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.3087027072906494s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020835399627685547s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.0002105236053466797s
Believability | Calculation of trust value for Spatial Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-bspo took 4.660986661911011s
Availability | SPARQL endpoint availability check for BioTop took 9.250640869140625e-05s
Availability | VoID file availability check for BioTop took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for BioTop took 0.3172342777252197s
Reputation | Calculation of the PageRank for BioTop took 0.020600080490112305s
Interlinking | Calculation of Degree of Connection for BioTop took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BioTop took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006368160247802734s
Believability | Calculation of trust value for BioTop took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-bt took 4.547696590423584s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 7.224082946777344e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.308563232421875s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008740425109863281s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bto took 4.108865022659302s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 0.0001468658447265625s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3341860771179199s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.02103400230407715s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0017993450164794922s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-canco took 4.668099880218506s
Availability | SPARQL endpoint availability check for CAO took 8.249282836914062e-05s
Availability | VoID file availability check for CAO took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for CAO took 0.30019354820251465s
Reputation | Calculation of the PageRank for CAO took 0.021867752075195312s
Interlinking | Calculation of Degree of Connection for CAO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CAO took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0005786418914794922s
Believability | Calculation of trust value for CAO took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-cao took 4.231231451034546s
Availability | SPARQL endpoint availability check for CareLex took 8.630752563476562e-05s
Availability | VoID file availability check for CareLex took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for CareLex took 0.30002403259277344s
Reputation | Calculation of the PageRank for CareLex took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for CareLex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.221366882324219e-05s
Believability | Calculation of trust value for CareLex took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-carelex took 4.260837554931641s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.3054320812225342s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007777214050292969s
Believability | Calculation of trust value for Cell Cycle Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cco took 4.497952938079834s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.2999253273010254s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020910978317260742s
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.0019927024841308594s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00028514862060546875s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-cdao took 4.399027585983276s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 9.202957153320312e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.29970502853393555s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007739067077636719s
Believability | Calculation of trust value for Chemical entities of biological interest took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-chebi took 4.379497766494751s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 9.322166442871094e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.3368797302246094s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.02214980125427246s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002837181091308594s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 4.484752893447876s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 5.507469177246094e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.00040149688720703125s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.2806541919708252s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020307302474975586s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007340908050537109s
Believability | Calculation of trust value for Chemical Information Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cheminf took 4.413546085357666s
Availability | SPARQL endpoint availability check for Cell type took 8.58306884765625e-05s
Availability | VoID file availability check for Cell type took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for Cell type took 0.2739095687866211s
Reputation | Calculation of the PageRank for Cell type took 0.02197408676147461s
Interlinking | Calculation of Degree of Connection for Cell type took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cell type took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003757476806640625s
Believability | Calculation of trust value for Cell type took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cl took 4.395898103713989s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 0.00010919570922851562s
Availability | VoID file availability check for Cell Line Ontology took 0.0008475780487060547s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.30249977111816406s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.021638870239257812s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008013248443603516s
Believability | Calculation of trust value for Cell Line Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-clo took 4.263013601303101s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 0.00014829635620117188s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.2858161926269531s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.0208284854888916s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.0002014636993408203s
Believability | Calculation of trust value for Clinical Measurement Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cmo took 4.224079370498657s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0008442401885986328s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.28673410415649414s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0001971721649169922s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-cno took 4.200610876083374s
Availability | SPARQL endpoint availability check for Wheat trait took 8.916854858398438e-05s
Availability | VoID file availability check for Wheat trait took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.30298542976379395s
Reputation | Calculation of the PageRank for Wheat trait took 0.02174234390258789s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.459785461425781e-05s
Believability | Calculation of trust value for Wheat trait took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-co_wheat took 4.477341413497925s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 8.654594421386719e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.28939199447631836s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.021975040435791016s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003724098205566406s
Believability | Calculation of trust value for Cognitive Atlas took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cogat took 4.238245487213135s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.3139653205871582s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.02285170555114746s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007033348083496094s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-cogpo took 4.199400424957275s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.124641418457031e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.3202824592590332s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.02027273178100586s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00040912628173828125s
Believability | Calculation of trust value for Current Procedural Terminology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cpt took 4.5510475635528564s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.220008850097656e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.3800840377807617s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.023051977157592773s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.001739501953125s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-csp took 4.837621212005615s
Availability | SPARQL endpoint availability check for COSTART took 8.749961853027344e-05s
Availability | VoID file availability check for COSTART took 0.0007908344268798828s
Completeness | Calculation of interlinking completeness for COSTART took 0.3154470920562744s
Reputation | Calculation of the PageRank for COSTART took 0.021033048629760742s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0010259151458740234s
Believability | Calculation of trust value for COSTART took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cst took 4.502178192138672s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 8.845329284667969e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.3106534481048584s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0004990100860595703s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ctcae took 4.454740762710571s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.315376281738281e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.2892739772796631s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004401206970214844s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ctx took 4.546943187713623s
Availability | SPARQL endpoint availability check for Dendritic cell took 8.845329284667969e-05s
Availability | VoID file availability check for Dendritic cell took 0.00039076805114746094s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.27463316917419434s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020239830017089844s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0002918243408203125s
Believability | Calculation of trust value for Dendritic cell took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-dc_cl took 4.272119998931885s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 7.62939453125e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.2702012062072754s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.021139144897460938s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.893013000488281e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ddanat took 4.24901008605957s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.31582093238830566s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009253025054931641s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ddi took 4.207432508468628s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.28826260566711426s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020795583724975586s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.20159912109375e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-diagnosticont took 4.234450101852417s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 6.67572021484375e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.2921261787414551s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00016427040100097656s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 4.099919557571411s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Human disease ontology took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2981259822845459s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020926713943481445s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006160736083984375s
Believability | Calculation of trust value for Human disease ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-doid took 4.136076927185059s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0007252693176269531s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.2798488140106201s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.020290136337280273s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007696151733398438s
Believability | Calculation of trust value for Electrocardiography Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ecg took 4.270612716674805s
Availability | SPARQL endpoint availability check for Evidence codes took 8.487701416015625e-05s
Availability | VoID file availability check for Evidence codes took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2945828437805176s
Reputation | Calculation of the PageRank for Evidence codes took 0.02090620994567871s
Interlinking | Calculation of Degree of Connection for Evidence codes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 4.7206878662109375e-05s
Believability | Calculation of trust value for Evidence codes took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-eco took 4.401839017868042s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3349034786224365s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020561695098876953s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.001695394515991211s
Believability | Calculation of trust value for Experimental Factor Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-efo took 4.530885457992554s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.6253204345703125e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.29067277908325195s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.0221097469329834s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011436939239501953s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ehda took 4.468854904174805s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 9.799003601074219e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.3059804439544678s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007081031799316406s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ehdaa took 4.398085832595825s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 8.606910705566406e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0007569789886474609s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.31734132766723633s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.021552562713623047s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005533695220947266s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 4.218561172485352s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.3392181396484375e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.2885246276855469s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 2.8848648071289062e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-emap took 4.124767780303955s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Environment Ontology took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.2760586738586426s
Reputation | Calculation of the PageRank for Environment Ontology took 0.021143674850463867s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0008945465087890625s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0004706382751464844s
Believability | Calculation of trust value for Environment Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-envo took 4.48455548286438s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 0.00010132789611816406s
Availability | VoID file availability check for Plant environmental conditions took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.26488685607910156s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.02222132682800293s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0003097057342529297s
Believability | Calculation of trust value for Plant environmental conditions took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-eo took 4.208095550537109s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0007350444793701172s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.3021242618560791s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020470857620239258s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0011823177337646484s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-ep took 4.160248041152954s
Availability | SPARQL endpoint availability check for Epilepsy took 8.749961853027344e-05s
Availability | VoID file availability check for Epilepsy took 0.0007073879241943359s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.2842390537261963s
Reputation | Calculation of the PageRank for Epilepsy took 0.02069091796875s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00013637542724609375s
Believability | Calculation of trust value for Epilepsy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-epileponto took 4.071065187454224s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 9.012222290039062e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0004210472106933594s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.2791566848754883s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020415306091308594s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0010597705841064453s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0013468265533447266s
Believability | Calculation of trust value for eagle-i research resource ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-ero took 4.3668529987335205s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.3392181396484375e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.00067138671875s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.2764468193054199s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.02216339111328125s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011036396026611328s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ev took 4.126046895980835s
Availability | SPARQL endpoint availability check for ExO took 8.916854858398438e-05s
Availability | VoID file availability check for ExO took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for ExO took 0.3324012756347656s
Reputation | Calculation of the PageRank for ExO took 0.021080970764160156s
Interlinking | Calculation of Degree of Connection for ExO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for ExO took 0.0002589225769042969s
Believability | Calculation of trust value for ExO took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-exo took 4.316131591796875s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 8.96453857421875e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.2655622959136963s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.02082085609436035s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.0001087188720703125s
Believability | Calculation of trust value for Fungal gross anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-fao took 4.273560523986816s
Availability | SPARQL endpoint availability check for Biological imaging methods took 8.893013000488281e-05s
Availability | VoID file availability check for Biological imaging methods took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.2917954921722412s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020458698272705078s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00019311904907226562s
Believability | Calculation of trust value for Biological imaging methods took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-fbbi took 4.525332927703857s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 0.00011396408081054688s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.3129303455352783s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.021010160446166992s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.000640869140625s
Believability | Calculation of trust value for Drosophila gross anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-fbbt took 4.727126598358154s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 9.34600830078125e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0007510185241699219s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.30983662605285645s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02060413360595703s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.00041866302490234375s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-fbcv took 4.257113695144653s
Availability | SPARQL endpoint availability check for Drosophila development took 8.559226989746094e-05s
Availability | VoID file availability check for Drosophila development took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.3390071392059326s
Reputation | Calculation of the PageRank for Drosophila development took 0.021695613861083984s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.482269287109375e-05s
Believability | Calculation of trust value for Drosophila development took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-fbdv took 4.595900535583496s
Availability | SPARQL endpoint availability check for Fly taxonomy took 8.869171142578125e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0007123947143554688s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.28021788597106934s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.02041316032409668s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0004024505615234375s
Believability | Calculation of trust value for Fly taxonomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-fbsp took 4.546135663986206s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 9.942054748535156e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0007891654968261719s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.29730987548828125s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.02087569236755371s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00022292137145996094s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 4.304419994354248s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.28918933868408203s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.021900415420532227s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.00042629241943359375s
Believability | Calculation of trust value for Family Health History Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-fhho took 4.123602390289307s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.29894137382507324s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010194778442382812s
Believability | Calculation of trust value for Influenza Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-flu took 4.035919189453125s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 5.459785461425781e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.28901243209838867s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.413459777832031e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-fma took 4.368910789489746s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 9.679794311523438e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.29668354988098145s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.021363496780395508s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00013184547424316406s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-fypo took 4.147430658340454s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0007703304290771484s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.2698187828063965s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.021138906478881836s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.059906005859375e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-geospecies took 4.084576606750488s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.35833024978637695s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.02087092399597168s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016117095947265625s
Believability | Calculation of trust value for General Formal Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-gfo took 4.112533330917358s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 8.511543273925781e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.26387619972229004s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.021022558212280273s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.000614166259765625s
Believability | Calculation of trust value for General Formal Ontology: Biology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-gfo-bio took 4.237938404083252s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 8.606910705566406e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.30117368698120117s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020535707473754883s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008604526519775391s
Believability | Calculation of trust value for Gene Ontology Extension took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-go_x1 took 4.189081192016602s
Availability | SPARQL endpoint availability check for Gene Ontology took 0.00017023086547851562s
Availability | VoID file availability check for Gene Ontology took 0.0008041858673095703s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2988111972808838s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020778894424438477s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.000850677490234375s
Believability | Calculation of trust value for Gene Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-go_x2 took 4.115863800048828s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 9.751319885253906e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0007436275482177734s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.30028438568115234s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.020900726318359375s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 2.9087066650390625e-05s
Believability | Calculation of trust value for Cereal Plant Development took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-gro took 4.18134331703186s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 8.749961853027344e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.00036644935607910156s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.3056302070617676s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020787715911865234s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004458427429199219s
Believability | Calculation of trust value for Cereal plant gross anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-gro_x1 took 4.162963628768921s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.3029003143310547s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02104973793029785s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007450580596923828s
Believability | Calculation of trust value for Gene Regulation Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-gro_x2 took 4.180063962936401s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 0.00010704994201660156s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0007636547088623047s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2885003089904785s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02075958251953125s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005648136138916016s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hao took 4.244997978210449s
Availability | SPARQL endpoint availability check for HCPCS took 0.00010919570922851562s
Availability | VoID file availability check for HCPCS took 0.0007317066192626953s
Completeness | Calculation of interlinking completeness for HCPCS took 0.28323936462402344s
Reputation | Calculation of the PageRank for HCPCS took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002219676971435547s
Believability | Calculation of trust value for HCPCS took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hcpcs took 4.078686714172363s
Availability | SPARQL endpoint availability check for Health Level Seven took 8.821487426757812e-05s
Availability | VoID file availability check for Health Level Seven took 0.0007810592651367188s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.3027689456939697s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020668506622314453s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012676715850830078s
Believability | Calculation of trust value for Health Level Seven took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hl7 took 4.2863428592681885s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.2438507080078125e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2866809368133545s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.02100849151611328s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00034117698669433594s
Believability | Calculation of trust value for HEALTH_INDICATORS took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-hlth_indics took 4.294991970062256s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 8.749961853027344e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0007963180541992188s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.29331421852111816s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.020594358444213867s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.0279159545898438e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-hom took 4.2866575717926025s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.220008850097656e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0007002353668212891s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.28875279426574707s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020885229110717773s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.075599670410156e-05s
Believability | Calculation of trust value for HOM-HARVARD took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-hom_harvard took 4.128973960876465s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.2809586524963379s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006291866302490234s
Believability | Calculation of trust value for Human Phenotype Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-hp_x1 took 4.1019041538238525s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.2760148048400879s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.021679401397705078s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.001043558120727539s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hpio took 4.2245635986328125s
Availability | SPARQL endpoint availability check for HUGO took 4.506111145019531e-05s
Availability | VoID file availability check for HUGO took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for HUGO took 0.29643726348876953s
Reputation | Calculation of the PageRank for HUGO took 0.02044963836669922s
Interlinking | Calculation of Degree of Connection for HUGO took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for HUGO took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.700920104980469e-05s
Believability | Calculation of trust value for HUGO took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-hugo took 4.185956001281738s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0007233619689941406s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.4017946720123291s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020598173141479492s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006453990936279297s
Believability | Calculation of trust value for Information Artifact Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-iao took 4.283029556274414s
Availability | SPARQL endpoint availability check for ICD10 took 4.1484832763671875e-05s
Availability | VoID file availability check for ICD10 took 0.0003802776336669922s
Completeness | Calculation of interlinking completeness for ICD10 took 0.33684754371643066s
Reputation | Calculation of the PageRank for ICD10 took 0.02148890495300293s
Interlinking | Calculation of Degree of Connection for ICD10 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ICD10 took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0007953643798828125s
Believability | Calculation of trust value for ICD10 took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icd10 took 4.558373212814331s
Availability | SPARQL endpoint availability check for ICD10CM took 9.1552734375e-05s
Availability | VoID file availability check for ICD10CM took 0.0003857612609863281s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.3234853744506836s
Reputation | Calculation of the PageRank for ICD10CM took 0.020559310913085938s
Interlinking | Calculation of Degree of Connection for ICD10CM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006024837493896484s
Believability | Calculation of trust value for ICD10CM took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icd10cm took 4.0566723346710205s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.3392181396484375e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.28407979011535645s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.02034449577331543s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.000148773193359375s
Believability | Calculation of trust value for ICD-10-PCS took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-icd10pcs took 4.2730419635772705s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.9114227294921875e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.277768611907959s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006380081176757812s
Believability | Calculation of trust value for International Classification of Diseases took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-icd9cm took 4.023891925811768s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.100799560546875e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.3050675392150879s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.02057790756225586s
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.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004425048828125s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icf_x1 took 4.45440411567688s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 7.43865966796875e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.3045473098754883s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.00119781494140625s
Believability | Calculation of trust value for International Classification for Nursing Practice took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-icnp took 4.4188759326934814s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.220008850097656e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.2978177070617676s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004649162292480469s
Believability | Calculation of trust value for International Classification of Primary Care took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-icpc took 4.61424994468689s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 8.416175842285156e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.33454251289367676s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020536184310913086s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008387565612792969s
Believability | Calculation of trust value for ICPC-2 PLUS took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icpc2p took 4.4567811489105225s
Availability | SPARQL endpoint availability check for ICPS Network took 4.267692565917969e-05s
Availability | VoID file availability check for ICPS Network took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.27486681938171387s
Reputation | Calculation of the PageRank for ICPS Network took 0.020753860473632812s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.00090789794921875s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0002562999725341797s
Believability | Calculation of trust value for ICPS Network took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icps took 4.13774037361145s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.29787135124206543s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008218288421630859s
Believability | Calculation of trust value for Infectious Disease Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ido took 4.308768033981323s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2998623847961426s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011267662048339844s
Believability | Calculation of trust value for Brucellosis Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-idobru took 4.273912668228149s
Availability | SPARQL endpoint availability check for Malaria Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0007739067077636719s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.28774189949035645s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.022249460220336914s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0012650489807128906s
Believability | Calculation of trust value for Malaria Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-idomal took 4.129171133041382s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.3392181396484375e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.30745744705200195s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0002961158752441406s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-iev took 4.136372327804565s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.7206878662109375e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0003943443298339844s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.27937817573547363s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.0001621246337890625s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-imgt took 4.089906692504883s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.2438507080078125e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.2915949821472168s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005125999450683594s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-imr took 4.203275203704834s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0003859996795654297s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.2684812545776367s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.026747703552246094s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0008854866027832031s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0009629726409912109s
Believability | Calculation of trust value for Interaction Network Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ino took 4.2438130378723145s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.172325134277344e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.3111903667449951s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.020884990692138672s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.0517578125e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-invertebrata took 4.172125577926636s
Availability | SPARQL endpoint availability check for IxnO took 4.5299530029296875e-05s
Availability | VoID file availability check for IxnO took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for IxnO took 0.2864875793457031s
Reputation | Calculation of the PageRank for IxnO took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for IxnO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IxnO took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018906593322753906s
Believability | Calculation of trust value for IxnO took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ixno took 4.454647541046143s
Availability | SPARQL endpoint availability check for SysMO-JERM took 8.821487426757812e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.30256056785583496s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.000362396240234375s
Believability | Calculation of trust value for SysMO-JERM took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-jerm took 4.52877402305603s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 7.62939453125e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.29024791717529297s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020748615264892578s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 2.8133392333984375e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-kisao took 4.165905237197876s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.1961669921875e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0007555484771728516s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.272754430770874s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.02112436294555664s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00021767616271972656s
Believability | Calculation of trust value for Loggerhead nesting took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-lhn took 4.325053691864014s
Availability | SPARQL endpoint availability check for Lipid Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.27481818199157715s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00019931793212890625s
Believability | Calculation of trust value for Lipid Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-lipro took 4.125975131988525s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 0.00012159347534179688s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.3793160915374756s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020783424377441406s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018467903137207031s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-lnc took 4.828361988067627s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 8.797645568847656e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.3019833564758301s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.022101640701293945s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006377696990966797s
Believability | Calculation of trust value for Mouse adult gross anatomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ma took 4.001138210296631s
Availability | SPARQL endpoint availability check for Multiple alignment took 5.507469177246094e-05s
Availability | VoID file availability check for Multiple alignment took 0.000331878662109375s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.2761573791503906s
Reputation | Calculation of the PageRank for Multiple alignment took 0.02241349220275879s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0001976490020751953s
Believability | Calculation of trust value for Multiple alignment took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mao took 4.432010650634766s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 0.0001068115234375s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.3060269355773926s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.02076888084411621s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006852149963378906s
Believability | Calculation of trust value for Minimal anatomical terminology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mat took 5.511804819107056s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 8.821487426757812e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.31723880767822266s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.02077007293701172s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004189014434814453s
Believability | Calculation of trust value for Breast tissue cell lines took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mcbcc took 4.397184610366821s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.31493353843688965s
Reputation | Calculation of the PageRank for Cell line ontology took 0.021460294723510742s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007429122924804688s
Believability | Calculation of trust value for Cell line ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mccl took 4.254741191864014s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Cell line ontology took 0.0008363723754882812s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.31082868576049805s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020987987518310547s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014066696166992188s
Believability | Calculation of trust value for Cell line ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 4.109036922454834s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 9.584426879882812e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.292755126953125s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00023937225341796875s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mcv took 4.136240005493164s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 8.654594421386719e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.3255424499511719s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.02108287811279297s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.000171661376953125s
Believability | Calculation of trust value for Master Drug Data Base took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mddb took 4.241302967071533s
Availability | SPARQL endpoint availability check for MedDRA took 4.291534423828125e-05s
Availability | VoID file availability check for MedDRA took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for MedDRA took 0.33884620666503906s
Reputation | Calculation of the PageRank for MedDRA took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for MedDRA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011518001556396484s
Believability | Calculation of trust value for MedDRA took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mdr took 4.108234405517578s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 8.296966552734375e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0003917217254638672s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.27222299575805664s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008745193481445312s
Believability | Calculation of trust value for MedlinePlus Health Topics took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-medlineplus took 4.5131707191467285s
Availability | SPARQL endpoint availability check for MeGO took 8.392333984375e-05s
Availability | VoID file availability check for MeGO took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for MeGO took 0.27332615852355957s
Reputation | Calculation of the PageRank for MeGO took 0.020397186279296875s
Interlinking | Calculation of Degree of Connection for MeGO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MeGO took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.0001442432403564453s
Believability | Calculation of trust value for MeGO took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mego took 4.399462461471558s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 9.322166442871094e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.35742878913879395s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.022001028060913086s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.001795053482055664s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mesh-owl took 4.683469295501709s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.982948303222656e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.2862675189971924s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.0209348201751709s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006206035614013672s
Believability | Calculation of trust value for Mental Functioning Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mf took 4.194592237472534s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 8.368492126464844e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.28853678703308105s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020642995834350586s
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.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005841255187988281s
Believability | Calculation of trust value for Medaka fish anatomy and development took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mfo took 4.120832443237305s
Availability | SPARQL endpoint availability check for Emotion Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.31885647773742676s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020904541015625s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007290840148925781s
Believability | Calculation of trust value for Emotion Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mfoem took 4.129364252090454s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 8.940696716308594e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.42978572845458984s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010442733764648438s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mhc took 4.42736291885376s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 8.368492126464844e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.31220555305480957s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006558895111083984s
Believability | Calculation of trust value for Protein-protein interaction took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mi took 4.1396565437316895s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 8.440017700195312e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.000637054443359375s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2991006374359131s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007035732269287109s
Believability | Calculation of trust value for Mosquito insecticide resistance took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-miro took 4.090764760971069s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0007510185241699219s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.3059413433074951s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.02129673957824707s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001342296600341797s
Believability | Calculation of trust value for Measurement Method Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mmo took 4.4159533977508545s
Availability | SPARQL endpoint availability check for MGED Ontology took 9.012222290039062e-05s
Availability | VoID file availability check for MGED Ontology took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.2919137477874756s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020999908447265625s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0004096031188964844s
Believability | Calculation of trust value for MGED Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mo took 4.299257516860962s
Availability | SPARQL endpoint availability check for Protein modification took 8.273124694824219e-05s
Availability | VoID file availability check for Protein modification took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for Protein modification took 0.28032755851745605s
Reputation | Calculation of the PageRank for Protein modification took 0.02081918716430664s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00021958351135253906s
Believability | Calculation of trust value for Protein modification took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mod took 4.098371505737305s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 8.249282836914062e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.2747502326965332s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.02061605453491211s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006375312805175781s
Believability | Calculation of trust value for Mammalian phenotype took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mp took 4.318525075912476s
Availability | SPARQL endpoint availability check for Mouse pathology took 9.059906005859375e-05s
Availability | VoID file availability check for Mouse pathology took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.29091548919677734s
Reputation | Calculation of the PageRank for Mouse pathology took 0.021312713623046875s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004661083221435547s
Believability | Calculation of trust value for Mouse pathology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mpath took 4.376074314117432s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.506111145019531e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0007398128509521484s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.27675318717956543s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020798921585083008s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003521442413330078s
Believability | Calculation of trust value for Mass spectrometry took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ms took 4.256356239318848s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 8.344650268554688e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.37028050422668457s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.02107381820678711s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018661022186279297s
Believability | Calculation of trust value for Medical Subject Headings took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-msh took 4.624119758605957s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 8.440017700195312e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.30544328689575195s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.0210113525390625s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00017762184143066406s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-mthch took 4.041688919067383s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 5.364418029785156e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.3127896785736084s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.021155834197998047s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0008041858673095703s
Believability | Calculation of trust value for Natural Products Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-natpro took 4.552714109420776s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 8.392333984375e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.34086179733276367s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.021877288818359375s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008053779602050781s
Believability | Calculation of trust value for NCBI organismal classification took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 4.277607202529907s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 8.702278137207031e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0007343292236328125s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.3508419990539551s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020882129669189453s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.001922607421875s
Believability | Calculation of trust value for NCI Thesaurus took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ncit took 4.660225868225098s
Availability | SPARQL endpoint availability check for National Drug Data File took 9.918212890625e-05s
Availability | VoID file availability check for National Drug Data File took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.30372166633605957s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02145838737487793s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006377696990966797s
Believability | Calculation of trust value for National Drug Data File took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nddf took 4.111566781997681s
Availability | SPARQL endpoint availability check for National Drug File took 8.559226989746094e-05s
Availability | VoID file availability check for National Drug File took 0.0007462501525878906s
Completeness | Calculation of interlinking completeness for National Drug File took 0.30307793617248535s
Reputation | Calculation of the PageRank for National Drug File took 0.020932674407958984s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012001991271972656s
Believability | Calculation of trust value for National Drug File took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ndfrt took 4.189611434936523s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 0.00011920928955078125s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.2996537685394287s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.020979881286621094s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.001165628433227539s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 4.180525541305542s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.3005352020263672s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006451606750488281s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-neomark took 4.333975791931152s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.31667280197143555s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.02050471305847168s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.0001239776611328125s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-neomarkontology took 4.3866496086120605s
Availability | SPARQL endpoint availability check for NIFSTD took 8.654594421386719e-05s
Availability | VoID file availability check for NIFSTD took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.34558963775634766s
Reputation | Calculation of the PageRank for NIFSTD took 0.021088838577270508s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0018699169158935547s
Believability | Calculation of trust value for NIFSTD took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nif took 4.630941390991211s
Availability | SPARQL endpoint availability check for NIF Cell took 8.368492126464844e-05s
Availability | VoID file availability check for NIF Cell took 0.0011489391326904297s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.3002190589904785s
Reputation | Calculation of the PageRank for NIF Cell took 0.020778656005859375s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0012996196746826172s
Believability | Calculation of trust value for NIF Cell took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-nif_cell took 4.1390275955200195s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.220008850097656e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.2813732624053955s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014069080352783203s
Believability | Calculation of trust value for NIF Dysfunction took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 4.20817494392395s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0006740093231201172s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.2988169193267822s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005497932434082031s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-nigo took 4.419435024261475s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 8.249282836914062e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.2825484275817871s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005486011505126953s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-nmr took 4.4787867069244385s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.29534339904785156s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.02029895782470703s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00011134147644042969s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-nonrctontology took 4.328857421875s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.3387460708618164s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020679235458374023s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.001173257827758789s
Believability | Calculation of trust value for NanoParticle Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-npo took 4.3084330558776855s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 8.96453857421875e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.3172037601470947s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020694732666015625s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0008070468902587891s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-oae took 4.3115339279174805s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 8.511543273925781e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.27301716804504395s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.020531177520751953s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014450550079345703s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-obi took 4.324897289276123s
Availability | SPARQL endpoint availability check for OBOE took 8.440017700195312e-05s
Availability | VoID file availability check for OBOE took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for OBOE took 0.3050351142883301s
Reputation | Calculation of the PageRank for OBOE took 0.020905017852783203s
Interlinking | Calculation of Degree of Connection for OBOE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011301040649414062s
Believability | Calculation of trust value for OBOE took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-oboe took 4.358182191848755s
Availability | SPARQL endpoint availability check for OBOE SBC took 9.489059448242188e-05s
Availability | VoID file availability check for OBOE SBC took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.3020806312561035s
Reputation | Calculation of the PageRank for OBOE SBC took 0.02039957046508789s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007810592651367188s
Believability | Calculation of trust value for OBOE SBC took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 4.1514623165130615s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 8.916854858398438e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2661707401275635s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020745277404785156s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005717277526855469s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ocre took 4.388271808624268s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 8.726119995117188e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.2996668815612793s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.000823974609375s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-odgi took 4.604674816131592s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 5.14984130859375e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2731812000274658s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008769035339355469s
Believability | Calculation of trust value for Ontology for Genetic Interval took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ogi took 4.160135746002197s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.00037670135498046875s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.3225076198577881s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0002872943878173828s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ogmd took 4.1358959674835205s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.3007192611694336s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.020849227905273438s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.00064849853515625s
Believability | Calculation of trust value for Ontology for General Medical Science took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ogms took 4.070142984390259s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 8.535385131835938e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.27301669120788574s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.02026653289794922s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011093616485595703s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-omim took 4.4246320724487305s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.3033592700958252s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.00036263465881347656s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-omit took 4.172932386398315s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 8.487701416015625e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.2758183479309082s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.021224260330200195s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005795955657958984s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-omrse took 2.6663482189178467s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 8.344650268554688e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.3019130229949951s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020354509353637695s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007524490356445312s
Believability | Calculation of trust value for Ontology of Data Mining took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ontodm took 4.2524073123931885s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 8.678436279296875e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.001051187515258789s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.2684447765350342s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002315044403076172s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ontodt took 4.2685041427612305s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.38690185546875e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.28864407539367676s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020289182662963867s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006012916564941406s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ontoorpha took 4.211603164672852s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.0531158447265625e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.29485464096069336s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009067058563232422s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-opl took 4.004792213439941s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.1484832763671875e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0007195472717285156s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.275374174118042s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.021083593368530273s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008568763732910156s
Believability | Calculation of trust value for Phenotypic quality took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-pato took 4.43463397026062s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.315376281738281e-05s
Availability | VoID file availability check for Physician Data Query took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.28946971893310547s
Reputation | Calculation of the PageRank for Physician Data Query took 0.02169060707092285s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0007998943328857422s
Believability | Calculation of trust value for Physician Data Query took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pdq took 4.15720272064209s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.482269287109375e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.2875077724456787s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.021127700805664062s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007841587066650391s
Believability | Calculation of trust value for Pediatric Terminology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-pedterm took 4.102799892425537s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.3121345043182373s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020907163619995117s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.0001995563507080078s
Believability | Calculation of trust value for Parasite Experiment Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-peo took 4.263892412185669s
Availability | SPARQL endpoint availability check for PHARE took 8.58306884765625e-05s
Availability | VoID file availability check for PHARE took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for PHARE took 0.2862410545349121s
Reputation | Calculation of the PageRank for PHARE took 0.020839691162109375s
Interlinking | Calculation of Degree of Connection for PHARE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006275177001953125s
Believability | Calculation of trust value for PHARE took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-phare took 4.304718494415283s
Availability | SPARQL endpoint availability check for PKO_Re took 7.319450378417969e-05s
Availability | VoID file availability check for PKO_Re took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.2737877368927002s
Reputation | Calculation of the PageRank for PKO_Re took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for PKO_Re took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0001659393310546875s
Believability | Calculation of trust value for PKO_Re took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-pko took 4.169193983078003s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for PMA 2010 took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.3339102268218994s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0008883476257324219s
Believability | Calculation of trust value for PMA 2010 took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-pma took 4.299785852432251s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.57763671875e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.29729413986206055s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020798206329345703s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00016355514526367188s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-pmr took 4.274045467376709s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.410743713378906e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0007245540618896484s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.2983119487762451s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.021584510803222656s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0008661746978759766s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0004892349243164062s
Believability | Calculation of trust value for Plant Anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-po took 4.025328874588013s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 8.869171142578125e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2918210029602051s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.023343801498413086s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 7.581710815429688e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-po_x1 took 4.168402194976807s
Availability | SPARQL endpoint availability check for Plant Ontology took 5.602836608886719e-05s
Availability | VoID file availability check for Plant Ontology took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.3216581344604492s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020880460739135742s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004360675811767578s
Believability | Calculation of trust value for Plant Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-po_x2 took 5.099051237106323s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 8.797645568847656e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.2788987159729004s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020987510681152344s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006511211395263672s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pr took 4.186429262161255s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 8.654594421386719e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.3049304485321045s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.02097630500793457s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002605915069580078s
Believability | Calculation of trust value for Proteomics data and process provenance took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-propreo took 4.455239534378052s
Availability | SPARQL endpoint availability check for Pathway ontology took 8.535385131835938e-05s
Availability | VoID file availability check for Pathway ontology took 0.000720977783203125s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.28594326972961426s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.0001251697540283203s
Believability | Calculation of trust value for Pathway ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-pw took 4.136961221694946s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0008058547973632812s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.3070857524871826s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.022411346435546875s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 4.792213439941406e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-qibo took 4.296302318572998s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 8.654594421386719e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.33638429641723633s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020668983459472656s
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.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017566680908203125s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-rcd took 4.631639003753662s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.28745102882385254s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02219533920288086s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00013136863708496094s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-rctontology took 4.317807197570801s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 6.723403930664062e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.2809257507324219s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020445823669433594s
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.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.1552734375e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-repo took 4.500065326690674s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.2438507080078125e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.31195855140686035s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020787715911865234s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00020170211791992188s
Believability | Calculation of trust value for Physico-chemical process took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-rex took 4.493013858795166s
Availability | SPARQL endpoint availability check for RadLex took 8.821487426757812e-05s
Availability | VoID file availability check for RadLex took 0.0007381439208984375s
Completeness | Calculation of interlinking completeness for RadLex took 0.2788984775543213s
Reputation | Calculation of the PageRank for RadLex took 0.021066665649414062s
Interlinking | Calculation of Degree of Connection for RadLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015518665313720703s
Believability | Calculation of trust value for RadLex took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-rid took 4.142382860183716s
Availability | SPARQL endpoint availability check for RNA ontology took 4.291534423828125e-05s
Availability | VoID file availability check for RNA ontology took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.286513090133667s
Reputation | Calculation of the PageRank for RNA ontology took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005404949188232422s
Believability | Calculation of trust value for RNA ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-rnao took 4.4332356452941895s
Availability | SPARQL endpoint availability check for Role Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Role Ontology took 0.0007543563842773438s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.3148362636566162s
Reputation | Calculation of the PageRank for Role Ontology took 0.02268052101135254s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00020432472229003906s
Believability | Calculation of trust value for Role Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-roleo took 4.29058313369751s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.2861666679382324s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.02129673957824707s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0001766681671142578s
Believability | Calculation of trust value for Rat Strain Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-rs took 4.346661806106567s
Availability | SPARQL endpoint availability check for RxNORM took 8.702278137207031e-05s
Availability | VoID file availability check for RxNORM took 0.0007634162902832031s
Completeness | Calculation of interlinking completeness for RxNORM took 0.2894630432128906s
Reputation | Calculation of the PageRank for RxNORM took 0.02062702178955078s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006241798400878906s
Believability | Calculation of trust value for RxNORM took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-rxnorm took 4.58715558052063s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 8.559226989746094e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0008985996246337891s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.3122680187225342s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010128021240234375s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sao took 4.069754123687744s
Availability | SPARQL endpoint availability check for Systems Biology took 9.34600830078125e-05s
Availability | VoID file availability check for Systems Biology took 0.0007777214050292969s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.30459022521972656s
Reputation | Calculation of the PageRank for Systems Biology took 0.020482778549194336s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004978179931640625s
Believability | Calculation of trust value for Systems Biology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-sbo took 4.4581873416900635s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.2819395065307617s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00011491775512695312s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sbro took 4.130250930786133s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0003972053527832031s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.3028905391693115s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.021134138107299805s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.001329660415649414s
Believability | Calculation of trust value for Sleep Domain Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-sdo took 4.198864459991455s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 5.53131103515625e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.3179450035095215s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02063775062561035s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003349781036376953s
Believability | Calculation of trust value for Sample processing and separation techniques took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-sep took 4.31488037109375s
Availability | SPARQL endpoint availability check for Student Health Record took 8.893013000488281e-05s
Availability | VoID file availability check for Student Health Record took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.31427478790283203s
Reputation | Calculation of the PageRank for Student Health Record took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0005848407745361328s
Believability | Calculation of trust value for Student Health Record took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-shr took 4.288543939590454s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0012297630310058594s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.3185412883758545s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012183189392089844s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-sio took 5.394728660583496s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.4345855712890625e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0008389949798583984s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.2771313190460205s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020930051803588867s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0009915828704833984s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.0002658367156982422s
Believability | Calculation of trust value for Situation-Based Access Control took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sitbac took 5.345456600189209s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 9.298324584960938e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.31350111961364746s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.001886606216430664s
Believability | Calculation of trust value for SNOMED Clinical Terms took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-snomedct took 4.686614990234375s
Availability | SPARQL endpoint availability check for SNP-Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0008573532104492188s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.28011322021484375s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.022977352142333984s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006775856018066406s
Believability | Calculation of trust value for SNP-Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-snpo took 4.4486777782440186s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.38690185546875e-05s
Availability | VoID file availability check for Sequence types and features took 0.0007994174957275391s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.3063242435455322s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020735740661621094s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005810260772705078s
Believability | Calculation of trust value for Sequence types and features took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-so_x1 took 4.304152250289917s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 0.0001685619354248047s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0007882118225097656s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.37738585472106934s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.021454572677612305s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015566349029541016s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-sopharm took 4.709769248962402s
Availability | SPARQL endpoint availability check for SoyOntology took 4.267692565917969e-05s
Availability | VoID file availability check for SoyOntology took 0.0008461475372314453s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.32460784912109375s
Reputation | Calculation of the PageRank for SoyOntology took 0.02147984504699707s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001804828643798828s
Believability | Calculation of trust value for SoyOntology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-soy took 4.279033422470093s
Availability | SPARQL endpoint availability check for Spider Ontology took 0.00010800361633300781s
Availability | VoID file availability check for Spider Ontology took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.29416513442993164s
Reputation | Calculation of the PageRank for Spider Ontology took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00033736228942871094s
Believability | Calculation of trust value for Spider Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-spd took 4.413844108581543s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0007963180541992188s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.27582478523254395s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.02084207534790039s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00029778480529785156s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-spto took 4.2428131103515625s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.2845728397369385s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.02199387550354004s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.00044798851013183594s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-sso took 4.027984142303467s
Availability | SPARQL endpoint availability check for Software Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Software Ontology took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.3123326301574707s
Reputation | Calculation of the PageRank for Software Ontology took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00040459632873535156s
Believability | Calculation of trust value for Software Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-swo took 4.342881917953491s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.267692565917969e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.3307912349700928s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.02244114875793457s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00024080276489257812s
Believability | Calculation of trust value for Tick gross anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-tads took 4.246762275695801s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.32382726669311523s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0009081363677978516s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-tao took 4.468316316604614s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 9.679794311523438e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.29894590377807617s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.021006107330322266s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.821487426757812e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-taxrank took 4.494457721710205s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 8.487701416015625e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.3007543087005615s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.02164745330810547s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 9.202957153320312e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-teddy took 4.6382975578308105s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.28314852714538574s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020866870880126953s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008070468902587891s
Believability | Calculation of trust value for Time Event Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-teo took 4.299016237258911s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.0531158447265625e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.30449724197387695s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.021886825561523438s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0004000663757324219s
Believability | Calculation of trust value for Mosquito gross anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-tgma took 4.476971626281738s
Availability | SPARQL endpoint availability check for thesaurus took 8.726119995117188e-05s
Availability | VoID file availability check for thesaurus took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for thesaurus took 0.2899796962738037s
Reputation | Calculation of the PageRank for thesaurus took 0.0220339298248291s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.699562072753906e-05s
Believability | Calculation of trust value for thesaurus took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-thesaurus took 4.169866323471069s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0001266002655029297s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.2747354507446289s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.02162313461303711s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003428459167480469s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 4.132403612136841s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 0.00010728836059570312s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.324615478515625s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.021771669387817383s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008065700531005859s
Believability | Calculation of trust value for Translational Medicine Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-tmo took 4.080065965652466s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.29753565788269043s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.02077007293701172s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015926361083984375s
Believability | Calculation of trust value for Plant Trait Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-to took 4.3194239139556885s
Availability | SPARQL endpoint availability check for TOK_Ontology took 7.62939453125e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.2951483726501465s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020863771438598633s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00022149085998535156s
Believability | Calculation of trust value for TOK_Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-tok took 4.253911733627319s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 9.584426879882812e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.29775500297546387s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020783662796020508s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007119178771972656s
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 4.381865739822388s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.00040078163146972656s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.3073887825012207s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.022705554962158203s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010340213775634766s
Believability | Calculation of trust value for Uber anatomy ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-uberon took 4.370298385620117s
Availability | SPARQL endpoint availability check for Units Ontology took 0.00010514259338378906s
Availability | VoID file availability check for Units Ontology took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.2753105163574219s
Reputation | Calculation of the PageRank for Units Ontology took 0.020772933959960938s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00024318695068359375s
Believability | Calculation of trust value for Units Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-unitsontology took 4.201441049575806s
Availability | SPARQL endpoint availability check for Units of measurement took 8.845329284667969e-05s
Availability | VoID file availability check for Units of measurement took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.2878704071044922s
Reputation | Calculation of the PageRank for Units of measurement took 0.021152496337890625s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002853870391845703s
Believability | Calculation of trust value for Units of measurement took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-uo took 4.106431007385254s
Availability | SPARQL endpoint availability check for VANDF took 8.463859558105469e-05s
Availability | VoID file availability check for VANDF took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for VANDF took 0.3272695541381836s
Reputation | Calculation of the PageRank for VANDF took 0.02123427391052246s
Interlinking | Calculation of Degree of Connection for VANDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006961822509765625s
Believability | Calculation of trust value for VANDF took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-vandf took 4.088237285614014s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 9.942054748535156e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.29590702056884766s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.021486282348632812s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00042366981506347656s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-vao took 4.163487434387207s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 5.7220458984375e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.00032806396484375s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.2871437072753906s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.02197885513305664s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.000629425048828125s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-vhog took 4.098766803741455s
Availability | SPARQL endpoint availability check for VIVO took 4.363059997558594e-05s
Availability | VoID file availability check for VIVO took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for VIVO took 0.3054769039154053s
Reputation | Calculation of the PageRank for VIVO took 0.020589828491210938s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003654956817626953s
Believability | Calculation of trust value for VIVO took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-vivo took 4.20478630065918s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.3021280765533447s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.02095317840576172s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012378692626953125s
Believability | Calculation of trust value for Vaccine Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-vo took 4.311550617218018s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.33534836769104004s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.021001338958740234s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.0002105236053466797s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-vt took 4.363606214523315s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 9.846687316894531e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.28950953483581543s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.022370338439941406s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0004990100860595703s
Believability | Calculation of trust value for C. elegans gross anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-wbbt took 4.206378698348999s
Availability | SPARQL endpoint availability check for C. elegans development took 4.076957702636719e-05s
Availability | VoID file availability check for C. elegans development took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.278212308883667s
Reputation | Calculation of the PageRank for C. elegans development took 0.02165055274963379s
Interlinking | Calculation of Degree of Connection for C. elegans development took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for C. elegans development took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.4345855712890625e-05s
Believability | Calculation of trust value for C. elegans development took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-wbls took 4.08573317527771s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.172325134277344e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.273547887802124s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.7738037109375e-05s
Believability | Calculation of trust value for C. elegans phenotype took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-wbphenotype took 4.27259635925293s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 9.131431579589844e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.31682586669921875s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020824909210205078s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006177425384521484s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-who took 4.2337565422058105s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.5299530029296875e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.30066633224487305s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.02125716209411621s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006897449493408203s
Believability | Calculation of trust value for Xenopus anatomy and development took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-xao took 4.501856803894043s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.2890493869781494s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.021724939346313477s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.0002300739288330078s
Believability | Calculation of trust value for Experimental Conditions Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-xco took 4.0591795444488525s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 8.916854858398438e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.28844261169433594s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.02070140838623047s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00026154518127441406s
Believability | Calculation of trust value for Yeast phenotypes took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ypo took 4.055049896240234s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 8.797645568847656e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.29869580268859863s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020625829696655273s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007512569427490234s
Believability | Calculation of trust value for Zebrafish anatomy and development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-zfa took 4.263582468032837s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.291534423828125e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0013971328735351562s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.2937922477722168s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.2636184692382812e-05s
INFO | --- Analysis for Bioportal_link took 3.5169003009796143s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.4367692470550537s
Availability | VoID file availability check for BioSamples RDF took 0.0004153251647949219s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.286149263381958s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020802021026611328s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.3855438232421875e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.0967254638671875e-05s
INFO | --- Analysis for biosamples-rdf took 3.768329381942749s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.17240023612976074s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.00021195411682128906s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.2731900215148926s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.02095937728881836s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011587142944335938s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.1444091796875e-05s
INFO | --- Analysis for bis-linked-data took 2.8666388988494873s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.297971248626709s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.022063255310058594s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.267692565917969e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 9.5367431640625e-06s
INFO | --- Analysis for bll-thesaurus took 3.7610888481140137s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.3048186302185059s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.30309462547302246s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.021062374114990234s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.794929504394531e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.0251998901367188e-05s
INFO | --- Analysis for bluk-bnb took 14.385908842086792s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.3212442398071289s
Availability | VoID file availability check for Thesaurus BNCF took 0.0007431507110595703s
Extra | Recovery of all triples for Thesaurus BNCF took 44.30803728103638s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6582803726196289s
Amount of data | Number of triples check for Thesaurus BNCF took 0.8680553436279297s
Interoperability | New terms check for Thesaurus BNCF took 1.4429612159729004s
Versatility | Languages check for Thesaurus BNCF took 6.167198896408081s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.8890972137451172s
Security | Check HTTPS for Thesaurus BNCF took 0.09150171279907227s
Interpretability | RDF structures check for Thesaurus BNCF took 0.1316533088684082s
Versatility | Serialization formats check for Thesaurus BNCF took 0.12003111839294434s
Availability | RDF dump link check for Thesaurus BNCF took 0.12810754776000977s
License | MR license check for Thesaurus BNCF took 0.12031722068786621s
License | HR license check for Thesaurus BNCF took 0.20572853088378906s
Amount of data | Number of property check for Thesaurus BNCF took 0.11721563339233398s
Understandability | Number of label check for Thesaurus BNCF took 0.25411152839660645s
Understandability | URI regex check for Thesaurus BNCF took 0.2501678466796875s
Understandability | Vocabs check for Thesaurus BNCF took 0.12335515022277832s
Verifiability | Authors check for Thesaurus BNCF took 0.13203883171081543s
Verifiability | Publishers check for Thesaurus BNCF took 0.124481201171875s
Performance | Throughput check for Thesaurus BNCF took 10.975296974182129s
Amount of data | Check the number of entities for Thesaurus BNCF took 7.176399230957031e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.1215980052947998s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.12725472450256348s
Interlinking | skos check for Thesaurus BNCF took 0.17129921913146973s
Interlinking | skos check for Thesaurus BNCF took 0.1535029411315918s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.1279299259185791s
Currency | Creation date check for Thesaurus BNCF took 0.26174163818359375s
Currency | Modification date check for Thesaurus BNCF took 0.24890518188476562s
Rep.Conc. | URIs length for Thesaurus BNCF took 24.340070009231567s
Interoperability | New vocabularies check for Thesaurus BNCF took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.11781907081604004s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.15040969848632812s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.11883425712585449s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 11.354623079299927s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.49443745613098145s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.8054912090301514s
Consistency | Disjoint class check for Thesaurus BNCF took 0.12080645561218262s
Consistency | Check Misplaced properties for Thesaurus BNCF took 1.1465141773223877s
Consistency | Misplaced classes for Thesaurus BNCF took 6.638820171356201s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 7.06751012802124s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4811158180236816s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.2396795749664307s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.3529834747314453s
Security | Sign check for Thesaurus BNCF took 0.11727476119995117s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 23.534278631210327s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.33550572395324707s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.43865966796875e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 1.1682510375976562e-05s
INFO | --- Analysis for bncf-ns took 181.13132500648499s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5995311737060547s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006110668182373047s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.5171699523925781s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.0448405742645264s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.9143521785736084s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.007496356964111s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.256391525268555s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.641402006149292s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.30182576179504395s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38834261894226074s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.47168946266174316s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4131791591644287s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.29961180686950684s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.202128648757935s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3739292621612549s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.9780287742614746s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7108473777770996s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5630993843078613s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3597426414489746s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3887176513671875s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.040215492248535s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.00010991096496582031s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3732466697692871s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.39034557342529297s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35512423515319824s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.34168219566345215s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.45097804069519043s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7301552295684814s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35992932319641113s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.705156087875366s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3168158531188965s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3597538471221924s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3876516819000244s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8485057353973389s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03044748306274414s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02806997299194336s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35184645652770996s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.605468034744263s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4627804756164551s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.1877920627593994s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.528946876525879s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.847379922866821s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030057907104492188s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.42468786239624023s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.360548734664917s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.998478412628174s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3572530746459961s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02091240882873535s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.2438507080078125e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6689300537109375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1205673217773438e-05s
INFO | --- Analysis for bpr took 386.89761996269226s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 9.417533874511719e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.28368139266967773s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.021512508392333984s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.724761962890625e-05s
Believability | Calculation of trust value for Brazilian Politicians took 8.106231689453125e-06s
INFO | --- Analysis for brazilian-politicians took 2.6938276290893555s
Availability | SPARQL endpoint availability check for Bricklink took 3.3973400592803955s
Availability | VoID file availability check for Bricklink took 0.0007493495941162109s
Completeness | Calculation of interlinking completeness for Bricklink took 0.299724817276001s
Reputation | Calculation of the PageRank for Bricklink took 0.020900964736938477s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Bricklink took 7.104873657226562e-05s
Believability | Calculation of trust value for Bricklink took 1.0251998901367188e-05s
INFO | --- Analysis for bricklink took 210.41964387893677s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.089139223098755s
Availability | VoID file availability check for British Museum Collection took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.2824990749359131s
Reputation | Calculation of the PageRank for British Museum Collection took 0.021976709365844727s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.5762786865234375e-05s
Believability | Calculation of trust value for British Museum Collection took 1.0728836059570312e-05s
INFO | --- Analysis for british-museum-collection took 72.78107976913452s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.410743713378906e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.32345151901245117s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 3.6716461181640625e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.2874603271484375e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.7159605026245117s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.23909401893615723s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0005533695220947266s
Extra | Recovery of all triples for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 11.826715230941772s
Performance | Total latancy measurement for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.609093189239502s
Amount of data | Number of triples check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.9867064952850342s
Interoperability | New terms check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.8528046607971191s
Versatility | Languages check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.636529922485352s
Interpretability | Number of blank nodes check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.905522346496582s
Interpretability | RDF structures check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12326502799987793s
Versatility | Serialization formats check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12166571617126465s
Availability | RDF dump link check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11914420127868652s
License | MR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12067699432373047s
License | HR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 16.761223793029785s
Amount of data | Number of property check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11256837844848633s
Understandability | Number of label check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.18208861351013184s
Understandability | URI regex check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2315666675567627s
Understandability | Vocabs check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12077951431274414s
Verifiability | Authors check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11296963691711426s
Verifiability | Publishers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12101578712463379s
Performance | Throughput check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.782260417938232s
Amount of data | Check the number of entities for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.267692565917969e-05s
Verifiability | Contribs. check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1279613971710205s
Interlinking | sameAs chians check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11258053779602051s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12749028205871582s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1199948787689209s
Timeliness | dataset update frequency check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12004780769348145s
Currency | Creation date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2412886619567871s
Currency | Modification date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24895739555358887s
Rep.Conc. | URIs length for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.315616130828857s
Interoperability | New vocabularies check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13100266456604004s
Accuracy | Check Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12707161903381348s
Accuracy | Check Inverse Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11933493614196777s
Accuracy | Check Empty annotation labels for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.1449966430664062s
Accuracy | Check White space in annotation for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24721574783325195s
Accuracy | Check Datatype consistency for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.525432825088501s
Consistency | Disjoint class check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1137702465057373s
Consistency | Check Misplaced properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.0594582557678223s
Consistency | Check Ontology hijacking for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.290283918380737s
Consistency | Check Invalid usage of undefined classes for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2670366764068604s
Consistency | Check Invalid usage of undefined properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.6557223796844482s
Conciseness | Check Extensional conciseness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.6818299293518066s
Security | Sign check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11249804496765137s
Availability | Check URIs Dereferenciability for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3577.3269488811493s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.7682316303253174s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.021281719207763672s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.71661376953125e-05s
Interoperability | Check the re-using of existing vocabs for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.0728836059570312e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 3683.620050907135s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.23620343208312988s
Availability | VoID file availability check for business.data.gov.uk took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.27266430854797363s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 4.935264587402344e-05s
Believability | Calculation of trust value for business.data.gov.uk took 8.106231689453125e-06s
INFO | --- Analysis for business-data-gov-uk took 3.0876080989837646s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.5027260780334473s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0004975795745849609s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 2.2919561862945557s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.4859182834625244s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.38913917541503906s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.6318490505218506s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 43.19381284713745s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.2933199405670166s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.17394685745239258s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.3169412612915039s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.2981412410736084s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.30283284187316895s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.3125004768371582s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 19.548556327819824s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.34769749641418457s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.3366835117340088s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.604865312576294s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.3030095100402832s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.28804445266723633s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.2775545120239258s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.744953155517578s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 6.222724914550781e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.2905259132385254s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.27465224266052246s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3047060966491699s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.29328489303588867s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.2844502925872803s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.6055090427398682s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.5883867740631104s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 4.793186187744141s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.2973363399505615s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4343743324279785s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.42534542083740234s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.6908879280090332s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03446650505065918s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.027694225311279297s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.3150947093963623s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.4523541927337646s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.3668854236602783s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 3.6062769889831543s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2804450988769531s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.39251971244812s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03148365020751953s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.312957763671875s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.301863431930542s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1378.920161485672s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.38894057273864746s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.021877765655517578s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.1920928955078125e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.239776611328125e-05s
INFO | --- Analysis for BVMC took 1513.9921321868896s
Availability | SPARQL endpoint availability check for cablegate took 1.7653510570526123s
Availability | VoID file availability check for cablegate took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for cablegate took 0.2867114543914795s
Reputation | Calculation of the PageRank for cablegate took 0.020755290985107422s
Interlinking | Calculation of Degree of Connection for cablegate took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for cablegate took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.532669067382812e-05s
Believability | Calculation of trust value for cablegate took 1.2636184692382812e-05s
INFO | --- Analysis for cablegate took 16.864919662475586s
Availability | SPARQL endpoint availability check for Calames took 8.916854858398438e-05s
Availability | VoID file availability check for Calames took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for Calames took 0.2863152027130127s
Reputation | Calculation of the PageRank for Calames took 0.02247166633605957s
Interlinking | Calculation of Degree of Connection for Calames took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Calames took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Calames took 3.3855438232421875e-05s
Believability | Calculation of trust value for Calames took 1.1682510375976562e-05s
INFO | --- Analysis for calames took 4.4438629150390625s
Availability | SPARQL endpoint availability check for CaLiGraph took 10.583347797393799s
Availability | VoID file availability check for CaLiGraph took 0.000522613525390625s
Extra | Recovery of all triples for CaLiGraph took 11.565120697021484s
Performance | Total latancy measurement for CaLiGraph took 36.812254428863525s
Amount of data | Number of triples check for CaLiGraph took 36.08948826789856s
Interoperability | New terms check for CaLiGraph took 7.642174959182739s
Versatility | Languages check for CaLiGraph took 70.29792904853821s
Interpretability | Number of blank nodes check for CaLiGraph took 15.584075212478638s
Security | Check HTTPS for CaLiGraph took 10.74474549293518s
Interpretability | RDF structures check for CaLiGraph took 5.0273826122283936s
Versatility | Serialization formats check for CaLiGraph took 2.169984817504883s
Availability | RDF dump link check for CaLiGraph took 5.712777853012085s
License | MR license check for CaLiGraph took 4.5320518016815186s
License | HR license check for CaLiGraph took 67.15528321266174s
Amount of data | Number of property check for CaLiGraph took 11.05620002746582s
Understandability | Number of label check for CaLiGraph took 12.388681650161743s
Understandability | URI regex check for CaLiGraph took 12.255751132965088s
Understandability | Vocabs check for CaLiGraph took 4.288465976715088s
Verifiability | Authors check for CaLiGraph took 3.729231595993042s
Verifiability | Publishers check for CaLiGraph took 4.55697774887085s
Performance | Throughput check for CaLiGraph took 62.289681911468506s
Amount of data | Check the number of entities for CaLiGraph took 0.014487028121948242s
Verifiability | Contribs. check for CaLiGraph took 0.24706530570983887s
Interlinking | sameAs chians check for CaLiGraph took 0.6885125637054443s
Interlinking | skos check for CaLiGraph took 0.386260986328125s
Interlinking | skos check for CaLiGraph took 0.20321178436279297s
Timeliness | dataset update frequency check for CaLiGraph took 0.2954087257385254s
Currency | Creation date check for CaLiGraph took 0.5211267471313477s
Currency | Modification date check for CaLiGraph took 0.4517686367034912s
Rep.Conc. | URIs length for CaLiGraph took 60.99811291694641s
Interoperability | New vocabularies check for CaLiGraph took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.219649076461792s
Accuracy | Check Functional Property for CaLiGraph took 0.2790110111236572s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2769312858581543s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5742595195770264s
Accuracy | Check White space in annotation for CaLiGraph took 0.02620673179626465s
Accuracy | Check Datatype consistency for CaLiGraph took 0.049036502838134766s
Consistency | Disjoint class check for CaLiGraph took 0.22164058685302734s
Consistency | Check Misplaced properties for CaLiGraph took 60.8580002784729s
Consistency | Misplaced classes for CaLiGraph took 0.5011343955993652s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9418644905090332s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2477095127105713s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.44370675086975s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03272128105163574s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4226362705230713s
Security | Sign check for CaLiGraph took 0.4612247943878174s
Availability | Check URIs Dereferenciability for CaLiGraph took 9.936830997467041s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.49510812759399414s
Reputation | Calculation of the PageRank for CaLiGraph took 0.021425724029541016s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.600120544433594e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.6689300537109375e-06s
Believability | Calculation of trust value for CaLiGraph took 1.0967254638671875e-05s
INFO | --- Analysis for CaLiGraph took 1590.026447057724s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.2227325439453125s
Availability | VoID file availability check for CaLiGraph took 0.0006818771362304688s
Extra | Recovery of all triples for CaLiGraph took 1.1862375736236572s
Performance | Total latancy measurement for CaLiGraph took 1.0498020648956299s
Amount of data | Number of triples check for CaLiGraph took 13.585744380950928s
Interoperability | New terms check for CaLiGraph took 1.9205398559570312s
Versatility | Languages check for CaLiGraph took 60.26844358444214s
Interpretability | Number of blank nodes check for CaLiGraph took 0.22080731391906738s
Security | Check HTTPS for CaLiGraph took 0.11136436462402344s
Interpretability | RDF structures check for CaLiGraph took 0.22770285606384277s
Versatility | Serialization formats check for CaLiGraph took 0.24160194396972656s
Availability | RDF dump link check for CaLiGraph took 0.22103404998779297s
License | MR license check for CaLiGraph took 0.23483705520629883s
License | HR license check for CaLiGraph took 60.27690839767456s
Amount of data | Number of property check for CaLiGraph took 0.2294471263885498s
Understandability | Number of label check for CaLiGraph took 3.26233172416687s
Understandability | URI regex check for CaLiGraph took 0.5402181148529053s
Understandability | Vocabs check for CaLiGraph took 0.2337815761566162s
Verifiability | Authors check for CaLiGraph took 0.24699926376342773s
Verifiability | Publishers check for CaLiGraph took 0.23183465003967285s
Performance | Throughput check for CaLiGraph took 10.8433837890625s
Amount of data | Check the number of entities for CaLiGraph took 0.00996851921081543s
Verifiability | Contribs. check for CaLiGraph took 0.32913947105407715s
Interlinking | sameAs chians check for CaLiGraph took 0.6610546112060547s
Interlinking | skos check for CaLiGraph took 0.2397136688232422s
Interlinking | skos check for CaLiGraph took 0.23152756690979004s
Timeliness | dataset update frequency check for CaLiGraph took 0.2352464199066162s
Currency | Creation date check for CaLiGraph took 0.4832789897918701s
Currency | Modification date check for CaLiGraph took 0.4517195224761963s
Rep.Conc. | URIs length for CaLiGraph took 61.178269386291504s
Interoperability | New vocabularies check for CaLiGraph took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.22637033462524414s
Accuracy | Check Functional Property for CaLiGraph took 0.22579598426818848s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2404639720916748s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5067298412322998s
Accuracy | Check White space in annotation for CaLiGraph took 0.02597522735595703s
Accuracy | Check Datatype consistency for CaLiGraph took 0.04845476150512695s
Consistency | Disjoint class check for CaLiGraph took 0.23261094093322754s
Consistency | Check Misplaced properties for CaLiGraph took 60.833802700042725s
Consistency | Misplaced classes for CaLiGraph took 0.47978878021240234s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9367830753326416s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2454431056976318s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.51243567466736s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.029159069061279297s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.42800474166870117s
Security | Sign check for CaLiGraph took 0.24050092697143555s
Availability | Check URIs Dereferenciability for CaLiGraph took 10.260230541229248s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.5233211517333984s
Reputation | Calculation of the PageRank for CaLiGraph took 0.0209503173828125s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.367134094238281e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 2.1457672119140625e-06s
Believability | Calculation of trust value for CaLiGraph took 1.2636184692382812e-05s
INFO | --- Analysis for caligraph took 1372.38414144516s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.06348848342895508s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.27355051040649414s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.022409677505493164s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.218650817871094e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 9.775161743164062e-06s
INFO | --- Analysis for cap-italy-rdf took 2.7881276607513428s
Availability | SPARQL endpoint availability check for person took 4.100799560546875e-05s
Availability | VoID file availability check for person took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for person took 0.2867131233215332s
Reputation | Calculation of the PageRank for person took 0.020727872848510742s
Interlinking | Calculation of Degree of Connection for person took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for person took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for person took 2.956390380859375e-05s
Believability | Calculation of trust value for person took 1.4066696166992188e-05s
INFO | --- Analysis for card took 2.6836066246032715s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.172325134277344e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.29961729049682617s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.2636184692382812e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 3.2627689838409424s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.6309447288513184s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0005066394805908203s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 121.58580088615417s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 1.0091557502746582s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 9.10355281829834s
Interoperability | New terms check for Norway catch records dataset @PSNC took 14.096209049224854s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.1633207798004s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 2.220632553100586s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.2884361743927002s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 10.81957459449768s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.3375890254974365s
License | MR license check for Norway catch records dataset @PSNC took 0.7259232997894287s
License | HR license check for Norway catch records dataset @PSNC took 300.1805853843689s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.19545531272888184s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.8241732120513916s
Understandability | URI regex check for Norway catch records dataset @PSNC took 1.0989086627960205s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.591766357421875s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.19401931762695312s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.2573397159576416s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.210867643356323s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 7.43865966796875e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.2016127109527588s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.2037961483001709s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4922313690185547s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.41651153564453125s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 5.047124862670898s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.49212646484375s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.2485058307647705s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 152.46602416038513s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.18775081634521484s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.45734143257141113s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.4501650333404541s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 40.73783588409424s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.645942211151123s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.5596392154693604s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.18043971061706543s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 87.36148810386658s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.22127103805542s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 29.686731815338135s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.32778000831604s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 88.07857942581177s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.695634126663208s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.5601766109466553s
Security | Sign check for Norway catch records dataset @PSNC took 1.4366841316223145s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 10.641258716583252s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.4323272705078125s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.022135496139526367s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 6.604194641113281e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 0.00016427040100097656s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2281.3269720077515s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.131431579589844e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.3117983341217041s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.02120065689086914s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0001010894775390625s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.0251998901367188e-05s
INFO | --- Analysis for ce4r took 13.958825826644897s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7295217514038086s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005195140838623047s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.6735947132110596s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 1.1802277565002441s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.48708510398864746s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.817228078842163s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.16124105453491s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5146007537841797s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5825448036193848s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.42554140090942383s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.26325249671936035s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3938758373260498s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4626584053039551s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15831804275512695s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4555065631866455s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4848489761352539s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3284435272216797s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2630457878112793s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2036139965057373s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 12.038152933120728s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 6.747245788574219e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3575870990753174s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.252960205078125s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.9432964324951172s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20203185081481934s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16507387161254883s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.8745064735412598s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4852614402770996s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.120539665222168s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24588608741760254s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6621313095092773s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028043746948242188s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.028485536575317383s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.36664509773254395s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.3584504127502441s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.9001944065093994s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 2.2132837772369385s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.4669456481933594s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03072643280029297s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.21697354316711426s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17127418518066406s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 3884.5895686149597s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.7413277626037598s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.021973371505737305s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0008273124694824219s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 5.6743621826171875e-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.2159347534179688e-05s
INFO | --- Analysis for ceo took 4020.9746372699738s
Availability | SPARQL endpoint availability check for Chat Game corpus took 8.988380432128906e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.3545541763305664s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.02596879005432129s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.647804260253906e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.0013580322265625e-05s
INFO | --- Analysis for chat-game-corpus took 12.852303743362427s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 8.749961853027344e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0008034706115722656s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.31192898750305176s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020894527435302734s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 6.175041198730469e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.0728836059570312e-05s
INFO | --- Analysis for chem2bio2rdf took 134.0560986995697s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.5281732082366943s
Availability | VoID file availability check for ChEMBL RDF took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.29941821098327637s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.02172684669494629s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.8650970458984375e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.1205673217773438e-05s
INFO | --- Analysis for chembl-rdf took 3.901144504547119s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.0346043109893799s
Availability | VoID file availability check for chemdb  dataset took 0.00048804283142089844s
Extra | Recovery of all triples for chemdb  dataset took 4.920035123825073s
Performance | Total latancy measurement for chemdb  dataset took 2.47145676612854s
Amount of data | Number of triples check for chemdb  dataset took 0.540036678314209s
Interoperability | New terms check for chemdb  dataset took 3.478555917739868s
Versatility | Languages check for chemdb  dataset took 23.097434043884277s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5236637592315674s
Interpretability | RDF structures check for chemdb  dataset took 1.0398080348968506s
Versatility | Serialization formats check for chemdb  dataset took 0.8614745140075684s
Availability | RDF dump link check for chemdb  dataset took 0.6013405323028564s
License | MR license check for chemdb  dataset took 1.2197787761688232s
License | HR license check for chemdb  dataset took 3.2731568813323975s
Amount of data | Number of property check for chemdb  dataset took 0.5454666614532471s
Understandability | Number of label check for chemdb  dataset took 1.9291274547576904s
Understandability | URI regex check for chemdb  dataset took 1.2603683471679688s
Understandability | Vocabs check for chemdb  dataset took 0.5907950401306152s
Verifiability | Authors check for chemdb  dataset took 0.6776645183563232s
Verifiability | Publishers check for chemdb  dataset took 0.5888192653656006s
Performance | Throughput check for chemdb  dataset took 12.341003894805908s
Amount of data | Check the number of entities for chemdb  dataset took 4.363059997558594e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.5787756443023682s
Interlinking | sameAs chians check for chemdb  dataset took 0.6429357528686523s
Interlinking | skos check for chemdb  dataset took 0.9071779251098633s
Interlinking | skos check for chemdb  dataset took 0.48883891105651855s
Timeliness | dataset update frequency check for chemdb  dataset took 0.6524286270141602s
Currency | Creation date check for chemdb  dataset took 1.1070144176483154s
Currency | Modification date check for chemdb  dataset took 1.0398783683776855s
Rep.Conc. | URIs length for chemdb  dataset took 2.9055404663085938s
Interoperability | New vocabularies check for chemdb  dataset took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5213541984558105s
Accuracy | Check Functional Property for chemdb  dataset took 0.6117403507232666s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.5773830413818359s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.163881301879883s
Accuracy | Check White space in annotation for chemdb  dataset took 0.030405759811401367s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03334498405456543s
Consistency | Disjoint class check for chemdb  dataset took 0.5908830165863037s
Consistency | Check Misplaced properties for chemdb  dataset took 1.233875036239624s
Consistency | Misplaced classes for chemdb  dataset took 0.6206786632537842s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.3883769512176514s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.245119333267212s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 1.944282054901123s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.03165864944458008s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5349438190460205s
Security | Sign check for chemdb  dataset took 1.0603184700012207s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2507.596066713333s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.5170657634735107s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.021968603134155273s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.724761962890625e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb  dataset took 1.3113021850585938e-05s
INFO | --- Analysis for chemdb-basicInfo took 4759.385372638702s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5273017883300781s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0004477500915527344s
Extra | Recovery of all triples for chemdb estimated properties dataset took 4.942483425140381s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.519928455352783s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5617430210113525s
Interoperability | New terms check for chemdb estimated properties dataset took 3.37951397895813s
Versatility | Languages check for chemdb estimated properties dataset took 22.95400619506836s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5220599174499512s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5919594764709473s
Versatility | Serialization formats check for chemdb estimated properties dataset took 0.756007194519043s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.5715012550354004s
License | MR license check for chemdb estimated properties dataset took 1.068068027496338s
License | HR license check for chemdb estimated properties dataset took 3.2133638858795166s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5376851558685303s
Understandability | Number of label check for chemdb estimated properties dataset took 1.6082780361175537s
Understandability | URI regex check for chemdb estimated properties dataset took 1.1612958908081055s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.5584728717803955s
Verifiability | Authors check for chemdb estimated properties dataset took 0.6058754920959473s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.5482120513916016s
Performance | Throughput check for chemdb estimated properties dataset took 12.45785403251648s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 6.818771362304688e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.5532927513122559s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 0.6264762878417969s
Interlinking | skos check for chemdb estimated properties dataset took 0.7485442161560059s
Interlinking | skos check for chemdb estimated properties dataset took 0.5092782974243164s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 0.6013514995574951s
Currency | Creation date check for chemdb estimated properties dataset took 1.0607707500457764s
Currency | Modification date check for chemdb estimated properties dataset took 1.0064654350280762s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 2.962549924850464s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.48940086364746094s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.576723575592041s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.5484945774078369s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 2.2013087272644043s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.030277252197265625s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03254890441894531s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.5575883388519287s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.2256519794464111s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.6240429878234863s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 3.3434841632843018s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.2380921840667725s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 1.9367821216583252s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03211069107055664s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.518012523651123s
Security | Sign check for chemdb estimated properties dataset took 0.6849141120910645s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2508.4580950737s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.530526876449585s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.021323442459106445s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 5.269050598144531e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.049041748046875e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 4736.3537719249725s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5317273139953613s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0005342960357666016s
Extra | Recovery of all triples for chemdb phase transition dataset took 4.889806509017944s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.4648451805114746s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.558753252029419s
Interoperability | New terms check for chemdb phase transition dataset took 3.3537349700927734s
Versatility | Languages check for chemdb phase transition dataset took 22.60210680961609s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5355169773101807s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5230607986450195s
Versatility | Serialization formats check for chemdb phase transition dataset took 0.8327682018280029s
Availability | RDF dump link check for chemdb phase transition dataset took 0.6245560646057129s
License | MR license check for chemdb phase transition dataset took 1.4987008571624756s
License | HR license check for chemdb phase transition dataset took 3.39574933052063s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5307044982910156s
Understandability | Number of label check for chemdb phase transition dataset took 2.4609479904174805s
Understandability | URI regex check for chemdb phase transition dataset took 1.3546221256256104s
Understandability | Vocabs check for chemdb phase transition dataset took 0.6184673309326172s
Verifiability | Authors check for chemdb phase transition dataset took 0.7452003955841064s
Verifiability | Publishers check for chemdb phase transition dataset took 0.6032307147979736s
Performance | Throughput check for chemdb phase transition dataset took 11.9740571975708s
Amount of data | Check the number of entities for chemdb phase transition dataset took 8.678436279296875e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.6144351959228516s
Interlinking | sameAs chians check for chemdb phase transition dataset took 0.7481698989868164s
Interlinking | skos check for chemdb phase transition dataset took 0.9820623397827148s
Interlinking | skos check for chemdb phase transition dataset took 0.5005390644073486s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 0.7171707153320312s
Currency | Creation date check for chemdb phase transition dataset took 1.147305965423584s
Currency | Modification date check for chemdb phase transition dataset took 1.041529655456543s
Rep.Conc. | URIs length for chemdb phase transition dataset took 2.935377836227417s
Interoperability | New vocabularies check for chemdb phase transition dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.500532865524292s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.6227703094482422s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.5935156345367432s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 2.453519821166992s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.03046727180480957s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03285980224609375s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.5980997085571289s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2201733589172363s
Consistency | Misplaced classes for chemdb phase transition dataset took 1.609994888305664s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 3.4175491333007812s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.2365427017211914s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 1.9408955574035645s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.03200697898864746s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5238735675811768s
Security | Sign check for chemdb phase transition dataset took 1.0954945087432861s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2516.0234241485596s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.5500388145446777s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.021482229232788086s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 4.458427429199219e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.2159347534179688e-05s
INFO | --- Analysis for chemdb-phaseTransition took 4745.530154705048s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5276262760162354s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0005440711975097656s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 4.963183879852295s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.528355121612549s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5610561370849609s
Interoperability | New terms check for chemdb thermochemistry dataset took 3.4629838466644287s
Versatility | Languages check for chemdb thermochemistry dataset took 23.266862154006958s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5286595821380615s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5312163829803467s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 0.5797011852264404s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.4879026412963867s
License | MR license check for chemdb thermochemistry dataset took 0.5445833206176758s
License | HR license check for chemdb thermochemistry dataset took 3.117631673812866s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5229723453521729s
Understandability | Number of label check for chemdb thermochemistry dataset took 0.6046724319458008s
Understandability | URI regex check for chemdb thermochemistry dataset took 1.0072698593139648s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.5005154609680176s
Verifiability | Authors check for chemdb thermochemistry dataset took 0.5028202533721924s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.4986567497253418s
Performance | Throughput check for chemdb thermochemistry dataset took 12.967130661010742s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 7.104873657226562e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.4976842403411865s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 0.5325634479522705s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5613834857940674s
Interlinking | skos check for chemdb thermochemistry dataset took 0.490250825881958s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 0.4926304817199707s
Currency | Creation date check for chemdb thermochemistry dataset took 1.0325076580047607s
Currency | Modification date check for chemdb thermochemistry dataset took 1.029435157775879s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 2.906691074371338s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.49300527572631836s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.5268690586090088s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.48439717292785645s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 2.1994528770446777s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.029960155487060547s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.032845497131347656s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.5412125587463379s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2397170066833496s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6195213794708252s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 3.4250991344451904s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.241081714630127s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 2.0135438442230225s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.033974409103393555s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5393128395080566s
Security | Sign check for chemdb thermochemistry dataset took 0.49875617027282715s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2512.2014038562775s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.6206820011138916s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.02132415771484375s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.365776062011719e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 1.2874603271484375e-05s
INFO | --- Analysis for chemdb-thermochemistry took 4770.948002815247s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.267692565917969e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.3025777339935303s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.02089691162109375s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 2.9325485229492188e-05s
Believability | Calculation of trust value for ChemPedia RDF took 7.3909759521484375e-06s
INFO | --- Analysis for chempedia-rdf took 9.89838171005249s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.1961669921875e-05s
Availability | VoID file availability check for Chiman Maru took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.34255266189575195s
Reputation | Calculation of the PageRank for Chiman Maru took 0.02078533172607422s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 2.8371810913085938e-05s
Believability | Calculation of trust value for Chiman Maru took 1.239776611328125e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 2.8216943740844727s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.9193365573883s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.3799326419830322s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.02162957191467285s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.981590270996094e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.3113021850585938e-05s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 798.0488693714142s
Availability | SPARQL endpoint availability check for Chronicling America took 9.226799011230469e-05s
Availability | VoID file availability check for Chronicling America took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.3886606693267822s
Reputation | Calculation of the PageRank for Chronicling America took 0.02182793617248535s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0008709430694580078s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00011754035949707031s
Believability | Calculation of trust value for Chronicling America took 1.2159347534179688e-05s
INFO | --- Analysis for chronicling-america took 9.560011386871338s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.6959528923034668s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006515979766845703s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 80.62163043022156s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.9304051399230957s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 2.122112274169922s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.0172348022460938s
Versatility | Languages check for Cultural Heritage Thesaurus took 8.238210678100586s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 2.151820421218872s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3551502227783203s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.3177177906036377s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 7.007169961929321s
License | MR license check for Cultural Heritage Thesaurus took 0.534247636795044s
License | HR license check for Cultural Heritage Thesaurus took 0.8478150367736816s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.3198244571685791s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.6591281890869141s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.6774907112121582s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.3276066780090332s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.35138726234436035s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.3403916358947754s
Performance | Throughput check for Cultural Heritage Thesaurus took 12.110093593597412s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 7.700920104980469e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.36575794219970703s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.30512356758117676s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.39972591400146484s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.29860782623291016s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.2816307544708252s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6675655841827393s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.6340539455413818s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 30.477789402008057s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 1.0312187671661377s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.3007822036743164s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.3050832748413086s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.3270456790924072s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 6.477484703063965s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22096705436706543s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.37036943435668945s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 9.365663290023804s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.5083553791046143s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 8.092756509780884s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 4.483230113983154s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00014853477478027344s
Security | Sign check for Cultural Heritage Thesaurus took 0.3353407382965088s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 353.34207010269165s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.42902517318725586s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.08809471130371094s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0010030269622802734s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00012493133544921875s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.9292786121368408s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for cht took 572.6235613822937s
Availability | SPARQL endpoint availability check for ciard-ring took 8.916854858398438e-05s
Availability | VoID file availability check for ciard-ring took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.36927318572998047s
Reputation | Calculation of the PageRank for ciard-ring took 0.02122211456298828s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.57763671875e-05s
Believability | Calculation of trust value for ciard-ring took 6.67572021484375e-06s
INFO | --- Analysis for ciard-ring took 8.464635610580444s
Availability | SPARQL endpoint availability check for Cine Figure took 9.083747863769531e-05s
Availability | VoID file availability check for Cine Figure took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.33507633209228516s
Reputation | Calculation of the PageRank for Cine Figure took 0.020819664001464844s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.2438507080078125e-05s
Believability | Calculation of trust value for Cine Figure took 1.0967254638671875e-05s
INFO | --- Analysis for Cine_Figure took 2.9315133094787598s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 3.040489912033081s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.00037550926208496094s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.31906604766845703s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.02248549461364746s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007922649383544922s
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 7.152557373046875e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 19.506771326065063s
Availability | SPARQL endpoint availability check for CIPFA took 4.2438507080078125e-05s
Availability | VoID file availability check for CIPFA took 0.00033092498779296875s
Completeness | Calculation of interlinking completeness for CIPFA took 0.29093003273010254s
Reputation | Calculation of the PageRank for CIPFA took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.4809112548828125e-05s
Believability | Calculation of trust value for CIPFA took 5.0067901611328125e-06s
INFO | --- Analysis for cipfa took 2.9378790855407715s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.0528302192688s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.3540492057800293s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.021108150482177734s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00041937828063964844s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.0728836059570312e-05s
INFO | --- Analysis for ckan took 263.20768666267395s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.5412745475769043s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.32764458656311035s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020867109298706055s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for CLaSSES took 4.476812362670898s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.1961669921875e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.32370734214782715s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.021023988723754883s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.123283386230469e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.049041748046875e-05s
INFO | --- Analysis for classical_temples took 4.990842819213867s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.0152368545532227s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.3009464740753174s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020917415618896484s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.225440979003906e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 8.344650268554688e-06s
INFO | --- Analysis for clean-energy-data-reegle took 5.767244338989258s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.100799560546875e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.34819722175598145s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020896434783935547s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.843971252441406e-05s
Believability | Calculation of trust value for CLLD-afbo took 1.1682510375976562e-05s
INFO | --- Analysis for clld-afbo took 4.135687828063965s
Availability | SPARQL endpoint availability check for CLLD-APICS took 8.440017700195312e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.3293757438659668s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.021014690399169922s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.796287536621094e-05s
Believability | Calculation of trust value for CLLD-APICS took 1.1682510375976562e-05s
INFO | --- Analysis for clld-apics took 4.271459579467773s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.315376281738281e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.33484792709350586s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.021170616149902344s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 4.00543212890625e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 1.049041748046875e-05s
INFO | --- Analysis for clld-ewave took 5.024761199951172s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.2438507080078125e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.34641504287719727s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.72747802734375e-05s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 9.775161743164062e-06s
INFO | --- Analysis for clld-glottolog took 4.566122770309448s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 8.273124694824219e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.3478093147277832s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.021055221557617188s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.130073547363281e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.1444091796875e-05s
INFO | --- Analysis for clld-phoible took 4.230915784835815s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 8.368492126464844e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.3747434616088867s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.022106647491455078s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.653236389160156e-05s
Believability | Calculation of trust value for CLLD-SAILS took 1.0967254638671875e-05s
INFO | --- Analysis for clld-sails took 4.330077886581421s
Availability | SPARQL endpoint availability check for CLLD-WALS took 8.416175842285156e-05s
Availability | VoID file availability check for CLLD-WALS took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.3188474178314209s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.021043777465820312s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 7.939338684082031e-05s
Believability | Calculation of trust value for CLLD-WALS took 9.5367431640625e-06s
INFO | --- Analysis for clld-wals took 4.174666881561279s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 8.392333984375e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0003669261932373047s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.2957122325897217s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.022188901901245117s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.700920104980469e-05s
Believability | Calculation of trust value for CLLD-WOLD took 9.775161743164062e-06s
INFO | --- Analysis for clld-wold took 4.151325941085815s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.20025181770324707s
Availability | VoID file availability check for Cooperation Databank took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.29895758628845215s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.021460533142089844s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.7670135498046875e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.049041748046875e-05s
INFO | --- Analysis for CoDa took 3.0774946212768555s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 1.0965194702148438s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.32068300247192383s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.022059917449951172s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.337860107421875e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 1.0251998901367188e-05s
INFO | --- Analysis for coins-openuplabs took 4.103161811828613s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.397902488708496s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.32833099365234375s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.020682334899902344s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 0.00010800361633300781s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 7.152557373046875e-06s
INFO | --- Analysis for CoLChina_sp2000 took 7.719099760055542s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.05810260772705078s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.3283042907714844s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.022486448287963867s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.1961669921875e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.33514404296875e-05s
INFO | --- Analysis for colinda took 3.034571886062622s
Availability | SPARQL endpoint availability check for CN  2012 took 25.686288356781006s
Availability | VoID file availability check for CN  2012 took 0.0008499622344970703s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.42366766929626465s
Reputation | Calculation of the PageRank for CN  2012 took 0.021407127380371094s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.743171691894531e-05s
Believability | Calculation of trust value for CN  2012 took 8.106231689453125e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 125.34675478935242s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.4256093502044678s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.3100724220275879s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.020521879196166992s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for CompHistSem took 4.423553228378296s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 1.7946200370788574s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.29923462867736816s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.023149728775024414s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0008575916290283203s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 4.0531158447265625e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.33514404296875e-05s
INFO | --- Analysis for comsode-d3-2 took 8.322431802749634s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 8.7738037109375e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.311603307723999s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.082389831542969e-05s
Believability | Calculation of trust value for 2011 US Congress People took 9.059906005859375e-06s
INFO | --- Analysis for congresspeople took 3.501610279083252s
Availability | SPARQL endpoint availability check for MIMO took 0.2525196075439453s
Availability | VoID file availability check for MIMO took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for MIMO took 0.30585765838623047s
Reputation | Calculation of the PageRank for MIMO took 0.02201533317565918s
Interlinking | Calculation of Degree of Connection for MIMO took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.3113021850585938e-05s
Believability | Calculation of trust value for MIMO took 1.3113021850585938e-05s
INFO | --- Analysis for CONNECTED took 4.100085258483887s
Availability | SPARQL endpoint availability check for Copyright Free Music took 8.726119995117188e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.3105463981628418s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.025168895721435547s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.3855438232421875e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.2874603271484375e-05s
INFO | --- Analysis for Copyright_Free_Music took 3.9127745628356934s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 8.869171142578125e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0007190704345703125s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.3111696243286133s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.82012939453125e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.1444091796875e-05s
INFO | --- Analysis for copyrighttermbank took 34.53053617477417s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.574185609817505s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.3229103088378906s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.021150588989257812s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.933906555175781e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.1920928955078125e-05s
INFO | --- Analysis for core took 8.231411218643188s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.6122233867645264s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.00026988983154296875s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 100.96064066886902s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.9855363368988037s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 9.371986389160156s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.308268070220947s
Versatility | Languages check for Corine linked dataset @PSNC took 300.14992570877075s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 2.135364294052124s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.3141438961029053s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 6.6569435596466064s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.38408517837524414s
License | MR license check for Corine linked dataset @PSNC took 0.8561022281646729s
License | HR license check for Corine linked dataset @PSNC took 300.25529289245605s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.22519135475158691s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.946486711502075s
Understandability | URI regex check for Corine linked dataset @PSNC took 1.1074976921081543s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.5594644546508789s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.19112515449523926s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.2596433162689209s
Performance | Throughput check for Corine linked dataset @PSNC took 11.032158374786377s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 7.319450378417969e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.20070219039916992s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.21764349937438965s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4932093620300293s
Interlinking | skos check for Corine linked dataset @PSNC took 0.44400811195373535s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 8.47214651107788s
Currency | Creation date check for Corine linked dataset @PSNC took 0.4729127883911133s
Currency | Modification date check for Corine linked dataset @PSNC took 0.2413647174835205s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 156.0038685798645s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.2023465633392334s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.5131328105926514s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.5297496318817139s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 35.592812061309814s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.6346242427825928s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.574415683746338s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.20290040969848633s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 88.27764344215393s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.380080938339233s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 31.428051233291626s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.3309025764465332s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 88.29481625556946s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.7413809299468994s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.4547412395477295s
Security | Sign check for Corine linked dataset @PSNC took 1.7239151000976562s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 10.267568826675415s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.4811549186706543s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.021482229232788086s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.933906555175781e-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.0967254638671875e-05s
INFO | --- Analysis for Corine_linked_dataset took 2256.8761627674103s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 8.511543273925781e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.34494447708129883s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.02132868766784668s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 6.270408630371094e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.3828277587890625e-05s
INFO | --- Analysis for cornetto took 14.606120824813843s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.19678807258605957s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0004515647888183594s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 187.58974742889404s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.5988538265228271s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 113.1209499835968s
Interoperability | New terms check for Corporate Body Named Authority List  took 61.48721480369568s
Versatility | Languages check for Corporate Body Named Authority List  took 300.1166613101959s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 16.37820553779602s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.35907578468322754s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.8384664058685303s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 4.764544248580933s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.22018098831176758s
License | MR license check for Corporate Body Named Authority List  took 0.41978001594543457s
License | HR license check for Corporate Body Named Authority List  took 300.03334975242615s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.16977953910827637s
Understandability | Number of label check for Corporate Body Named Authority List  took 1.6876201629638672s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.39992856979370117s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.10090136528015137s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.23218894004821777s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.20181751251220703s
Performance | Throughput check for Corporate Body Named Authority List  took 10.707993030548096s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 8.0108642578125e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.16940617561340332s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 6.715356826782227s
Interlinking | skos check for Corporate Body Named Authority List  took 0.3520772457122803s
Interlinking | skos check for Corporate Body Named Authority List  took 0.28492236137390137s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.28592538833618164s
Currency | Creation date check for Corporate Body Named Authority List  took 0.4265425205230713s
Currency | Modification date check for Corporate Body Named Authority List  took 0.14876341819763184s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 436.45637679100037s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.17503714561462402s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.21161508560180664s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.16980934143066406s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 40.9451379776001s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.1816060543060303s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.597696542739868s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.14946842193603516s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.36038875579834s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.358124017715454s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 39.5162353515625s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.6360595226287842s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.4163763523102s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 2.995276927947998s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.4452831745147705s
Security | Sign check for Corporate Body Named Authority List  took 0.41721034049987793s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 11.452753782272339s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.7701809406280518s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.022894859313964844s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 5.1021575927734375e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.9073486328125e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.239776611328125e-05s
INFO | --- Analysis for corporate-body took 15083.535688877106s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.6015803813934326s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.3302145004272461s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.02102041244506836s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 4.4345855712890625e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 9.298324584960938e-06s
INFO | --- Analysis for CorpusFibonacci took 4.624247789382935s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.14060354232788086s
Availability | VoID file availability check for Country Name Authority List took 0.0005943775177001953s
Extra | Recovery of all triples for Country Name Authority List took 188.94212770462036s
Performance | Total latancy measurement for Country Name Authority List took 0.6243691444396973s
Amount of data | Number of triples check for Country Name Authority List took 70.04093313217163s
Interoperability | New terms check for Country Name Authority List took 61.09250497817993s
Versatility | Languages check for Country Name Authority List took 300.11774134635925s
Interpretability | Number of blank nodes check for Country Name Authority List took 17.076247453689575s
Security | Check HTTPS for Country Name Authority List took 0.34521055221557617s
Interpretability | RDF structures check for Country Name Authority List took 0.2730247974395752s
Versatility | Serialization formats check for Country Name Authority List took 4.495384216308594s
Availability | RDF dump link check for Country Name Authority List took 0.19270086288452148s
License | MR license check for Country Name Authority List took 0.48746228218078613s
License | HR license check for Country Name Authority List took 300.01942920684814s
Amount of data | Number of property check for Country Name Authority List took 0.17664003372192383s
Understandability | Number of label check for Country Name Authority List took 1.8132407665252686s
Understandability | URI regex check for Country Name Authority List took 0.36948347091674805s
Understandability | Vocabs check for Country Name Authority List took 0.09877538681030273s
Verifiability | Authors check for Country Name Authority List took 0.10100436210632324s
Verifiability | Publishers check for Country Name Authority List took 0.19335675239562988s
Performance | Throughput check for Country Name Authority List took 10.625337839126587s
Amount of data | Check the number of entities for Country Name Authority List took 0.00010848045349121094s
Verifiability | Contribs. check for Country Name Authority List took 0.21628761291503906s
Interlinking | sameAs chians check for Country Name Authority List took 9.50907564163208s
Interlinking | skos check for Country Name Authority List took 0.17390036582946777s
Interlinking | skos check for Country Name Authority List took 0.14003586769104004s
Timeliness | dataset update frequency check for Country Name Authority List took 0.5752830505371094s
Currency | Creation date check for Country Name Authority List took 0.6238677501678467s
Currency | Modification date check for Country Name Authority List took 0.2073822021484375s
Rep.Conc. | URIs length for Country Name Authority List took 421.04463171958923s
Interoperability | New vocabularies check for Country Name Authority List took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.17367863655090332s
Accuracy | Check Functional Property for Country Name Authority List took 0.24074649810791016s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.1681218147277832s
Accuracy | Check Empty annotation labels for Country Name Authority List took 40.805936098098755s
Accuracy | Check White space in annotation for Country Name Authority List took 3.0589818954467773s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.5997161865234375s
Consistency | Disjoint class check for Country Name Authority List took 0.12679076194763184s
Consistency | Check Misplaced properties for Country Name Authority List took 300.44424295425415s
Consistency | Misplaced classes for Country Name Authority List took 8.422534465789795s
Consistency | Check Ontology hijacking for Country Name Authority List took 37.35837364196777s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.7757747173309326s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.49283623695374s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.007580041885376s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.38402509689331055s
Security | Sign check for Country Name Authority List took 0.3975551128387451s
Availability | Check URIs Dereferenciability for Country Name Authority List took 11.303266763687134s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.7143893241882324s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.02108001708984375s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 5.650520324707031e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.430511474609375e-06s
Believability | Calculation of trust value for Country Name Authority List took 7.3909759521484375e-06s
INFO | --- Analysis for country-authority-list took 15305.295686006546s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.10060882568359375s
Availability | VoID file availability check for Courts thesaurus took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.3095061779022217s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.022607088088989258s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.461143493652344e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for courts-thesaurus took 3.0358030796051025s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 20.427584171295166s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.305988073348999s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.022092819213867188s
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.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 7.653236389160156e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for Covid-on-the-Web took 55.370689153671265s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.315184593200684s
Availability | VoID file availability check for CPA 2008 took 0.0007610321044921875s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.30156373977661133s
Reputation | Calculation of the PageRank for CPA 2008 took 0.0210111141204834s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0009441375732421875s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.8623809814453125e-05s
Believability | Calculation of trust value for CPA 2008 took 8.821487426757812e-06s
INFO | --- Analysis for cpa-2008 took 124.54343771934509s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.44122815132141113s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0005192756652832031s
Extra | Recovery of all triples for Cooperative Patent Classification took 23.666435718536377s
Performance | Total latancy measurement for Cooperative Patent Classification took 1.1702380180358887s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.19731044769287s
Versatility | Languages check for Cooperative Patent Classification took 100.16639375686646s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.32222771644592s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.3438138961791992s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.28151655197143555s
Availability | RDF dump link check for Cooperative Patent Classification took 0.2324216365814209s
License | MR license check for Cooperative Patent Classification took 0.2588052749633789s
License | HR license check for Cooperative Patent Classification took 90.23570394515991s
Amount of data | Number of property check for Cooperative Patent Classification took 0.1801609992980957s
Understandability | Number of label check for Cooperative Patent Classification took 90.30951476097107s
Understandability | URI regex check for Cooperative Patent Classification took 0.5848650932312012s
Understandability | Vocabs check for Cooperative Patent Classification took 0.2593822479248047s
Verifiability | Authors check for Cooperative Patent Classification took 0.3242201805114746s
Verifiability | Publishers check for Cooperative Patent Classification took 0.2676372528076172s
Performance | Throughput check for Cooperative Patent Classification took 11.17602801322937s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.462501525878906e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.22222185134887695s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.14968037605285645s
Interlinking | skos check for Cooperative Patent Classification took 0.19368410110473633s
Interlinking | skos check for Cooperative Patent Classification took 0.16246366500854492s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.16921782493591309s
Currency | Creation date check for Cooperative Patent Classification took 0.3971116542816162s
Currency | Modification date check for Cooperative Patent Classification took 0.3668212890625s
Rep.Conc. | URIs length for Cooperative Patent Classification took 131.92402935028076s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.22554349899291992s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 19.13259792327881s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.945667266845703s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.87985897064209s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.20884251594543457s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 100.47800183296204s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 22.86625337600708s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.6410598754882812s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 101.5573959350586s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.805598020553589s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.2880256175994873s
Security | Sign check for Cooperative Patent Classification took 0.20346784591674805s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 2.2384657859802246s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.5017645359039307s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.02107405662536621s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0006814002990722656s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 4.315376281738281e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 2.1457672119140625e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.3589859008789062e-05s
INFO | --- Analysis for CPC took 1190.2120487689972s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.26515483856201s
Availability | VoID file availability check for CPC 2008 took 0.00093841552734375s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.3121683597564697s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020867347717285156s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.267692565917969e-05s
Believability | Calculation of trust value for CPC 2008 took 1.0251998901367188e-05s
INFO | --- Analysis for cpc-2008 took 124.137202501297s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.905226469039917s
Availability | VoID file availability check for CPV  2003 took 0.0008847713470458984s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.3911855220794678s
Reputation | Calculation of the PageRank for CPV  2003 took 0.02142810821533203s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.220008850097656e-05s
Believability | Calculation of trust value for CPV  2003 took 9.059906005859375e-06s
INFO | --- Analysis for cpv-2003 took 114.49623918533325s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.66910672187805s
Availability | VoID file availability check for CPV 2008 took 0.0008077621459960938s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.27936530113220215s
Reputation | Calculation of the PageRank for CPV 2008 took 0.02111339569091797s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.8160552978515625e-05s
Believability | Calculation of trust value for CPV 2008 took 3.814697265625e-06s
INFO | --- Analysis for cpv-2008 took 124.24562311172485s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.617627620697s
Availability | VoID file availability check for crowdsourcing-fb took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.3110358715057373s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.021572589874267578s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.8160552978515625e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.0728836059570312e-05s
INFO | --- Analysis for crowdsourcing-fb took 535.6704139709473s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.740071535110474s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.39017605781555176s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.021300315856933594s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 5.1975250244140625e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 8.344650268554688e-06s
INFO | --- Analysis for ctic-public-dataset took 44.45030379295349s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 2.4322023391723633s
Availability | VoID file availability check for CulturaLinkedData took 0.0005018711090087891s
Extra | Recovery of all triples for CulturaLinkedData took 158.76897859573364s
Performance | Total latancy measurement for CulturaLinkedData took 2.862401008605957s
Amount of data | Number of triples check for CulturaLinkedData took 2.5450429916381836s
Interoperability | New terms check for CulturaLinkedData took 2.368570566177368s
Versatility | Languages check for CulturaLinkedData took 60.27946352958679s
Interpretability | Number of blank nodes check for CulturaLinkedData took 1.9793190956115723s
Interpretability | RDF structures check for CulturaLinkedData took 0.4660975933074951s
Versatility | Serialization formats check for CulturaLinkedData took 2.330705165863037s
Availability | RDF dump link check for CulturaLinkedData took 2.0042152404785156s
License | MR license check for CulturaLinkedData took 2.4910473823547363s
License | HR license check for CulturaLinkedData took 63.91654062271118s
Amount of data | Number of property check for CulturaLinkedData took 2.0272789001464844s
Understandability | Number of label check for CulturaLinkedData took 1.1187310218811035s
Understandability | URI regex check for CulturaLinkedData took 2.370250701904297s
Understandability | Vocabs check for CulturaLinkedData took 0.2576463222503662s
Verifiability | Authors check for CulturaLinkedData took 0.3240363597869873s
Verifiability | Publishers check for CulturaLinkedData took 0.25453948974609375s
Performance | Throughput check for CulturaLinkedData took 23.498305320739746s
Amount of data | Check the number of entities for CulturaLinkedData took 7.033348083496094e-05s
Verifiability | Contribs. check for CulturaLinkedData took 2.045109272003174s
Interlinking | sameAs chians check for CulturaLinkedData took 2.178372621536255s
Interlinking | skos check for CulturaLinkedData took 2.23970890045166s
Interlinking | skos check for CulturaLinkedData took 2.0136020183563232s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.28891706466674805s
Currency | Creation date check for CulturaLinkedData took 2.162069797515869s
Currency | Modification date check for CulturaLinkedData took 2.2726337909698486s
Rep.Conc. | URIs length for CulturaLinkedData took 56.95759558677673s
Interoperability | New vocabularies check for CulturaLinkedData took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 2.00884747505188s
Accuracy | Check Functional Property for CulturaLinkedData took 0.20244884490966797s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.1822974681854248s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 42.149680376052856s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6038737297058105s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.2744786739349365s
Consistency | Disjoint class check for CulturaLinkedData took 2.0617563724517822s
Consistency | Check Misplaced properties for CulturaLinkedData took 10.31702733039856s
Consistency | Misplaced classes for CulturaLinkedData took 4.186750650405884s
Consistency | Check Ontology hijacking for CulturaLinkedData took 51.95738768577576s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.2947978973388672s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 11.404291868209839s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.358186960220337s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.21668076515197754s
Security | Sign check for CulturaLinkedData took 1.0003435611724854s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 11.327513694763184s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.43497157096862793s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.021341800689697266s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.814697265625e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 1.9073486328125e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.1682510375976562e-05s
INFO | --- Analysis for culturalinkeddata took 659.9662864208221s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.25521373748779297s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.29889440536499023s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020661115646362305s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0006961822509765625s
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.417806386947632s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.10179924964904785s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007245540618896484s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.31163620948791504s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020357370376586914s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.3855438232421875e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 8.344650268554688e-06s
INFO | --- Analysis for cz-ares-rzp took 3.2234301567077637s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11694598197937012s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.337831974029541s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.3855438232421875e-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.435697555541992s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.10850667953491211s
Availability | VoID file availability check for Integrated pollution registry took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.34049534797668457s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.5762786865234375e-05s
Believability | Calculation of trust value for Integrated pollution registry took 8.58306884765625e-06s
INFO | --- Analysis for cz-cenia-pollution took 3.2724525928497314s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.1218404769897461s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0009174346923828125s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.2976093292236328s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.020205974578857422s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.4332275390625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 9.059906005859375e-06s
INFO | --- Analysis for cz-contracts took 3.1851091384887695s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.12259984016418457s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.3337574005126953s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.02075815200805664s
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.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.147125244140625e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ctia-bans took 5.915925025939941s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.10648083686828613s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0003616809844970703s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.32248783111572266s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.361701965332031e-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.291797637939453s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.10890388488769531s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.3079037666320801s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020696401596069336s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.5762786865234375e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 8.821487426757812e-06s
INFO | --- Analysis for cz-ctia-focus took 3.199350118637085s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.11628389358520508s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.3070392608642578s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020781755447387695s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.0531158447265625e-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.2855947017669678s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.11786746978759766s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.3126964569091797s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.314018249511719e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 9.059906005859375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 5.803640127182007s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.19031071662902832s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0007867813110351562s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.3370094299316406s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.021235227584838867s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.838539123535156e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 7.867813110351562e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 3.3662378787994385s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.11555099487304688s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.3531825542449951s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.02065730094909668s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.4809112548828125e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 7.62939453125e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 3.424543857574463s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.6899576187133789s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.31061744689941406s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.0208895206451416s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.029273986816406e-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 4.1147096157073975s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.3476424217224121s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.3430144786834717s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.021129846572875977s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.8281238079071045s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.381528377532959s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.32138848304748535s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.021713733673095703s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.100799560546875e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 7.867813110351562e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.710000514984131s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.36124396324157715s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.32631707191467285s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.02045154571533203s
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.000701904296875s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.7981395721435547s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.3643648624420166s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.31478452682495117s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.0223391056060791s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.029273986816406e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.730175733566284s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3796553611755371s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.29946422576904297s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020967960357666016s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.719329833984375e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 8.58306884765625e-06s
INFO | --- Analysis for cz-czso-regions took 3.5109543800354004s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3870811462402344s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.3423781394958496s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.0215911865234375s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.1484832763671875e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.8457295894622803s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.3799576759338379s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.32521677017211914s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.02086639404296875s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.00543212890625e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.7892370223999023s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.35619139671325684s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.30869460105895996s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.022761106491088867s
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.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.838539123535156e-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.7849278450012207s
Availability | SPARQL endpoint availability check for ATC groups took 0.10721087455749512s
Availability | VoID file availability check for ATC groups took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for ATC groups took 0.30932116508483887s
Reputation | Calculation of the PageRank for ATC groups took 0.02114248275756836s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.200241088867188e-05s
Believability | Calculation of trust value for ATC groups took 1.1205673217773438e-05s
INFO | --- Analysis for cz-eh-1-atc took 3.2723872661590576s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10776329040527344s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.34865236282348633s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.021183252334594727s
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.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.8623809814453125e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 9.298324584960938e-06s
INFO | --- Analysis for cz-fulfillments took 3.285855770111084s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.041162967681884766s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.00110626220703125s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.3049144744873047s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.02245306968688965s
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.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.792213439941406e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 7.867813110351562e-06s
INFO | --- Analysis for cz-ic took 3.639132261276245s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.12019228935241699s
Availability | VoID file availability check for List of Czech data boxes took 0.0007107257843017578s
Extra | Recovery of all triples for List of Czech data boxes took 156.5389051437378s
Performance | Total latancy measurement for List of Czech data boxes took 0.554478645324707s
Amount of data | Number of triples check for List of Czech data boxes took 9.3294358253479s
Interoperability | New terms check for List of Czech data boxes took 10.73850417137146s
Versatility | Languages check for List of Czech data boxes took 300.11078691482544s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.2930116653442383s
Interpretability | RDF structures check for List of Czech data boxes took 0.13974308967590332s
Versatility | Serialization formats check for List of Czech data boxes took 0.16992402076721191s
Availability | RDF dump link check for List of Czech data boxes took 16.663407564163208s
License | MR license check for List of Czech data boxes took 0.44256019592285156s
License | HR license check for List of Czech data boxes took 56.48389482498169s
Amount of data | Number of property check for List of Czech data boxes took 0.11212992668151855s
Understandability | Number of label check for List of Czech data boxes took 1.2929182052612305s
Understandability | URI regex check for List of Czech data boxes took 0.4239349365234375s
Understandability | Vocabs check for List of Czech data boxes took 0.12113213539123535s
Verifiability | Authors check for List of Czech data boxes took 0.12920808792114258s
Verifiability | Publishers check for List of Czech data boxes took 0.12166547775268555s
Performance | Throughput check for List of Czech data boxes took 10.710100412368774s
Amount of data | Check the number of entities for List of Czech data boxes took 3.0052058696746826s
Verifiability | Contribs. check for List of Czech data boxes took 0.12603139877319336s
Interlinking | sameAs chians check for List of Czech data boxes took 0.4077572822570801s
Interlinking | skos check for List of Czech data boxes took 0.1900007724761963s
Interlinking | skos check for List of Czech data boxes took 0.11686921119689941s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.23028302192687988s
Currency | Creation date check for List of Czech data boxes took 0.2857682704925537s
Currency | Modification date check for List of Czech data boxes took 0.1299896240234375s
Rep.Conc. | URIs length for List of Czech data boxes took 111.50854015350342s
Interoperability | New vocabularies check for List of Czech data boxes took 22.580069303512573s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.377744197845459s
Accuracy | Check Functional Property for List of Czech data boxes took 0.17548179626464844s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.16948485374450684s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 33.26011776924133s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.047696590423584s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.6116220951080322s
Consistency | Disjoint class check for List of Czech data boxes took 0.1325240135192871s
Consistency | Check Misplaced properties for List of Czech data boxes took 69.82851839065552s
Consistency | Misplaced classes for List of Czech data boxes took 7.60815954208374s
Consistency | Check Ontology hijacking for List of Czech data boxes took 32.47457790374756s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.3517017364501953s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 63.54938077926636s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.604858875274658s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.37682533264160156s
Security | Sign check for List of Czech data boxes took 0.18093013763427734s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 354.92372965812683s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.5789728164672852s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.021787405014038086s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 29.309123516082764s
Believability | Calculation of trust value for List of Czech data boxes took 1.0728836059570312e-05s
INFO | --- Analysis for cz-list-of-databoxes took 1643.7682645320892s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12116742134094238s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006132125854492188s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 147.47290539741516s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.615706205368042s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.131986618041992s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.836748123168945s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.17522263526917s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.128610610961914s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1182100772857666s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17186498641967773s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 15.756540060043335s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4774620532989502s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 54.962703227996826s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.131683349609375s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.6821472644805908s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2336900234222412s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1209113597869873s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1414659023284912s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1074056625366211s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.71204662322998s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.9698290824890137s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11694717407226562s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.27867984771728516s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12850379943847656s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11980295181274414s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12382030487060547s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.21956539154052734s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.14610862731933594s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 111.68725728988647s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 14.518147945404053s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.39856743812561035s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1304783821105957s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11106753349304199s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 35.169191122055054s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0385541915893555s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.5813727378845215s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11162328720092773s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 69.02056765556335s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.593229532241821s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 34.76708006858826s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4058237075805664s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 62.222636699676514s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6534583568573s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3696630001068115s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12589406967163086s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 353.26695013046265s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5804557800292969s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.021579742431640625s
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.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.435943603515625e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 14.975981950759888s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 8.821487426757812e-06s
INFO | --- Analysis for cz-nace took 1606.9429030418396s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.31844520568847656s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0005738735198974609s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.1 took 379.3019607067108s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.8356375694274902s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.3141660690307617s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.42822527885437s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.1 took 300.1611661911011s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.1 took 4.39368462562561s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.9825596809387207s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.1 took 6.496074914932251s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3781862258911133s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.8034708499908447s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.346897840499878s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.15626788139343262s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.7038745880126953s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.5204615592956543s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2353806495666504s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.49013519287109375s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3364741802215576s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.1 took 10.685288906097412s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.00014472007751464844s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2299351692199707s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.22314763069152832s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4576528072357178s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.15595293045043945s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.805210590362549s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.6774425506591797s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4138631820678711s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.1 took 97.36687517166138s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.1 took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.17614126205444336s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4023711681365967s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4331998825073242s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.1 took 79.79520916938782s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.385540723800659s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.5854270458221436s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.3280317783355713s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.204309463500977s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.441272258758545s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.1 took 78.79656791687012s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.7276241779327393s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 6.452692270278931s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.172555446624756s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.24215245246887207s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.8640868663787842s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.1 took 959.9970242977142s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.7417058944702148s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.02341938018798828s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.337860107421875e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.245208740234375e-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 32701.181685209274s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.23250389099121094s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.3085935115814209s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.022238731384277344s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.409385681152344e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 1.049041748046875e-05s
INFO | --- Analysis for cz-orders took 3.1855525970458984s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.19439029693603516s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0005674362182617188s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 146.93309593200684s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.5831882953643799s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 9.609876155853271s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 10.62391448020935s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.11108136177063s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.3085312843322754s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.1344742774963379s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.19495916366577148s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 15.079956293106079s
License | MR license check for Institutions of public power of the Czech Republic took 0.5309293270111084s
License | HR license check for Institutions of public power of the Czech Republic took 58.02338004112244s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.11337494850158691s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.4473044872283936s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.5235071182250977s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.1243140697479248s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.12885379791259766s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.11767888069152832s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.686179161071777s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.001192092895508s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.14902496337890625s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.4433579444885254s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.19639968872070312s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.10144519805908203s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.23043274879455566s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.24066519737243652s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.14097261428833008s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 113.18021535873413s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 109.1644184589386s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.39350461959838867s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.23316073417663574s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.10879635810852051s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 32.52897930145264s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.020479202270508s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.620124340057373s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.09975504875183105s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 68.24121356010437s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.553548812866211s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 32.50834083557129s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.2762315273284912s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 62.29697036743164s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.625241756439209s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.38406872749328613s
Security | Sign check for Institutions of public power of the Czech Republic took 0.1485452651977539s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 358.5831651687622s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.4151723384857178s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.023072004318237305s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.459785461425781e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 164.34161972999573s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-ovm took 1855.5461401939392s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.1069333553314209s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.30266594886779785s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.020952939987182617s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.695487976074219e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-ovm-agendas took 3.0562686920166016s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11226201057434082s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0006351470947265625s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 60.80317425727844s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.5454111099243164s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 55.23455595970154s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 36.42301607131958s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.17700386047363s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.210435152053833s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6241512298583984s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13071608543395996s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7446377277374268s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13111400604248047s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11426639556884766s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10494494438171387s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.9910640716552734s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.23953604698181152s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12237000465393066s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1286780834197998s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1131296157836914s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.490225315093994s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.00010776519775390625s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12848138809204102s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11411070823669434s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12434840202331543s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11256575584411621s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11558198928833008s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2148282527923584s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12523341178894043s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 242.71967244148254s
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.11059951782226562s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11786770820617676s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11838388442993164s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 13.73758339881897s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.144613265991211s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.605541706085205s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12897205352783203s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 185.09628295898438s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.337315320968628s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 18.505640745162964s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.317690134048462s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 186.6146001815796s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.8727145195007324s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.25003767013549805s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11848664283752441s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.276523351669312s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.4410696029663086s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.02163076400756836s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.175041198730469e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.62939453125e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.1457672119140625e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ruian took 1714.152892589569s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.744708776473999s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.29375720024108887s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.02083897590637207s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 8.440017700195312e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 4.0384604930877686s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.5059723854064941s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.2916855812072754s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.0218656063079834s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.773210048675537s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.46982312202453613s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.2946665287017822s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020513296127319336s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.0279159545898438e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 8.344650268554688e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 3.8399856090545654s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.11577725410461426s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.29676103591918945s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020754575729370117s
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.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.361701965332031e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 3.017132043838501s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.10747861862182617s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.30562472343444824s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.02268362045288086s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.337860107421875e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-sidc-drug-prices took 2.9596500396728516s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.11302900314331055s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.2696988582611084s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.02115774154663086s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0011966228485107422s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 4.4345855712890625e-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.214440107345581s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.11881566047668457s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0006000995635986328s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 148.89714980125427s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5383455753326416s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 9.501470565795898s
Interoperability | New terms check for Summary types of Czech institutions of public power took 10.92853569984436s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.1383533477783s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.3479549884796143s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.1171579360961914s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.21176624298095703s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 16.3800687789917s
License | MR license check for Summary types of Czech institutions of public power took 0.13064241409301758s
License | HR license check for Summary types of Czech institutions of public power took 56.29094433784485s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.11846566200256348s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.0367918014526367s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.24107670783996582s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.11799216270446777s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.1158895492553711s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.11629199981689453s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.791629791259766s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.0385191440582275s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.12249040603637695s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.3014230728149414s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.21884417533874512s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.11256957054138184s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.24279999732971191s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.2250080108642578s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.11905026435852051s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 113.03025841712952s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 88.86118412017822s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.35373449325561523s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.24015212059020996s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.12844038009643555s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 31.375108003616333s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.026618003845215s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.5588371753692627s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.11851716041564941s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 68.11402082443237s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.554739713668823s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 32.52096676826477s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.275515079498291s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 62.19958806037903s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.615673303604126s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.41525959968566895s
Security | Sign check for Summary types of Czech institutions of public power took 0.11590027809143066s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 354.28109860420227s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.5547676086425781s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.02207350730895996s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 120.54528164863586s
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 1784.7664334774017s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.1117711067199707s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.2825734615325928s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020792722702026367s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.409385681152344e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 9.775161743164062e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 3.0812501907348633s
Availability | SPARQL endpoint availability check for State funding providers took 0.10841965675354004s
Availability | VoID file availability check for State funding providers took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for State funding providers took 0.27602386474609375s
Reputation | Calculation of the PageRank for State funding providers took 0.023595094680786133s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.38690185546875e-05s
Believability | Calculation of trust value for State funding providers took 8.58306884765625e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 3.0313801765441895s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.11613273620605469s
Availability | VoID file availability check for Organizations active in R&D took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.3049488067626953s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 3.910064697265625e-05s
Believability | Calculation of trust value for Organizations active in R&D took 1.0728836059570312e-05s
INFO | --- Analysis for cz-vavai-organizations took 3.2319560050964355s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.1122896671295166s
Availability | VoID file availability check for R&D Programmes took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.3159606456756592s
Reputation | Calculation of the PageRank for R&D Programmes took 0.02064061164855957s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 3.981590270996094e-05s
Believability | Calculation of trust value for R&D Programmes took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-programmes took 3.0610196590423584s
Availability | SPARQL endpoint availability check for R&D Projects took 0.1117238998413086s
Availability | VoID file availability check for R&D Projects took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.3115725517272949s
Reputation | Calculation of the PageRank for R&D Projects took 0.020752429962158203s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.2438507080078125e-05s
Believability | Calculation of trust value for R&D Projects took 9.298324584960938e-06s
INFO | --- Analysis for cz-vavai-projects took 3.130673885345459s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.11138319969177246s
Availability | VoID file availability check for Institutional research plans took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.3052248954772949s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020781278610229492s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.220008850097656e-05s
Believability | Calculation of trust value for Institutional research plans took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-research-plans took 3.084076166152954s
Availability | SPARQL endpoint availability check for Results of R&D took 0.10661053657531738s
Availability | VoID file availability check for Results of R&D took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.2682223320007324s
Reputation | Calculation of the PageRank for Results of R&D took 0.02068161964416504s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.0531158447265625e-05s
Believability | Calculation of trust value for Results of R&D took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-results took 3.020533323287964s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.1114966869354248s
Availability | VoID file availability check for Tenders in R&D took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.25876379013061523s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 3.933906555175781e-05s
Believability | Calculation of trust value for Tenders in R&D took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.9134464263916016s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.649162292480469e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.00032520294189453125s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.26498985290527344s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020763874053955078s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.147125244140625e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 7.152557373046875e-06s
INFO | --- Analysis for czech_addresses took 3.68924880027771s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.6387319564819336s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.31396007537841797s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.021500349044799805s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.6716461181640625e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for DanteLatinLoanwords took 4.35990309715271s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.3897080421447754s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0007236003875732422s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 136.21400380134583s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 0.964379072189331s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 6.555592775344849s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.027380704879761s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.31628847122192s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.23644709587097168s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.13293957710266113s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.2866480350494385s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.2589564323425293s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.2187495231628418s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.21923184394836426s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.23463654518127s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.24283695220947266s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 1.517066478729248s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.50527024269104s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.2351830005645752s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.28747129440307617s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.2415764331817627s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.39548134803772s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.05718994140625e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.2510232925415039s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.6791083812713623s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.9445579051971436s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.23432064056396484s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.23084354400634766s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 2.2720255851745605s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 2.881091594696045s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 83.81170964241028s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.2324049472808838s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.27462124824523926s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.3237447738647461s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 42.15348172187805s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.2132680416107178s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.5744144916534424s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.22997355461120605s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 20.040072917938232s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.437273740768433s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 42.4810004234314s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.3508014678955078s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 21.083731412887573s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.7878806591033936s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.23903250694274902s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.2345876693725586s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 9.065973997116089s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.5744965076446533s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.02130746841430664s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014162063598632812s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.6689300537109375e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.2159347534179688e-05s
INFO | --- Analysis for data-bnf-fr took 832.9748408794403s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.3519289493560791s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.2964348793029785s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.02280426025390625s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 6.771087646484375e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 9.059906005859375e-06s
INFO | --- Analysis for data-cnr-it took 3.843574047088623s
Availability | SPARQL endpoint availability check for Data.gov took 1.6853821277618408s
Availability | VoID file availability check for Data.gov took 0.0007822513580322266s
Completeness | Calculation of interlinking completeness for Data.gov took 0.28955864906311035s
Reputation | Calculation of the PageRank for Data.gov took 0.021504878997802734s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.266334533691406e-05s
Believability | Calculation of trust value for Data.gov took 8.344650268554688e-06s
INFO | --- Analysis for data-gov took 19.509246826171875s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.08218765258789062s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.000415802001953125s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.2830643653869629s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.02102065086364746s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.890296936035156e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 8.106231689453125e-06s
INFO | --- Analysis for data-gov-ie took 2.8706815242767334s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.172325134277344e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.30496811866760254s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.021618127822875977s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.009506225585938e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 8.821487426757812e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.8019227981567383s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.991313695907593s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.2841196060180664s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02099323272705078s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.270408630371094e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 1.1205673217773438e-05s
INFO | --- Analysis for data-hnm-hu took 168.14174509048462s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.11606144905090332s
Availability | VoID file availability check for Climb Dataincubator took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.29350924491882324s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.02213144302368164s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.867813110351562e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.0013580322265625e-05s
INFO | --- Analysis for data-incubator-climb took 2.870145559310913s
Availability | SPARQL endpoint availability check for Discogs in RDF took 8.726119995117188e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0004010200500488281s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.2861309051513672s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.021067380905151367s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 0.00010180473327636719s
Believability | Calculation of trust value for Discogs in RDF took 1.2159347534179688e-05s
INFO | --- Analysis for data-incubator-discogs took 4.984332323074341s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.05685710906982422s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.29021358489990234s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.021828174591064453s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 6.008148193359375e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 5.245208740234375e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.520734071731567s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.06170964241027832s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0006985664367675781s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.3027317523956299s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.02082991600036621s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.630752563476562e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 1.0967254638671875e-05s
INFO | --- Analysis for data-incubator-moseley took 8.336209535598755s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.0520777702331543s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.2853715419769287s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.021579980850219727s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.702278137207031e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.3589859008789062e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 2.6982545852661133s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.5370373725891113s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.295745849609375s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.368492126464844e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 2.574920654296875e-05s
INFO | --- Analysis for data-incubator-nasa took 7.504324436187744s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.06018853187561035s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2822272777557373s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.021019458770751953s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.271766662597656e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.7415127754211426s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.0645604133605957s
Availability | VoID file availability check for Pokedex data in RDF took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.30004096031188965s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.021756649017333984s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.584426879882812e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.239776611328125e-05s
INFO | --- Analysis for data-incubator-pokedex took 3.5944674015045166s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.14530467987060547s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.27097582817077637s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.021802186965942383s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0009081363677978516s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 9.489059448242188e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.1205673217773438e-05s
INFO | --- Analysis for data-incubator-smcjournals took 2.946019411087036s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.5296468734741211s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006861686706542969s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 28.170394897460938s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.3329858779907227s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 16.985939979553223s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.5163695812225342s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.328475952148438s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.339243412017822s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.1556243896484375s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.3586108684539795s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.5434792041778564s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.3202812671661377s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.41686391830444336s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.344552993774414s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.6401567459106445s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 30.330116510391235s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 1.6336216926574707s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 1.1337285041809082s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.9527733325958252s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 4.014734983444214s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 24.49969506263733s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 7.152557373046875e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.3332843780517578s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.7891473770141602s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.40117955207824707s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.42884278297424316s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.34609007835388184s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.9805192947387695s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.8734073638916016s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 39.907963037490845s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.47159528732299805s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.40400218963623047s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.3424398899078369s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 28.962886571884155s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 2.956698417663574s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.132251977920532s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.8709874153137207s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 1.4655356407165527s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 7.9632298946380615s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 27.615424633026123s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.373033046722412s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.9298384189605713s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.823875904083252s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.5635702610015869s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.4290294647216797s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.12125730514526367s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.392488956451416s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.021401166915893555s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.29425048828125e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 1.9073486328125e-06s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 1.0013580322265625e-05s
INFO | --- Analysis for data-open-ac-uk took 696.2995648384094s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.7740838527679443s
Availability | VoID file availability check for Persée in RDF took 0.0006647109985351562s
Extra | Recovery of all triples for Persée in RDF took 1.2617383003234863s
Performance | Total latancy measurement for Persée in RDF took 0.6563787460327148s
Amount of data | Number of triples check for Persée in RDF took 6.619645595550537s
Interoperability | New terms check for Persée in RDF took 1.9451947212219238s
Versatility | Languages check for Persée in RDF took 121.78354573249817s
Interpretability | Number of blank nodes check for Persée in RDF took 0.43697476387023926s
Interpretability | RDF structures check for Persée in RDF took 0.9553406238555908s
Versatility | Serialization formats check for Persée in RDF took 1.1434526443481445s
Availability | RDF dump link check for Persée in RDF took 0.3179588317871094s
License | MR license check for Persée in RDF took 1.6774451732635498s
License | HR license check for Persée in RDF took 37.78500270843506s
Amount of data | Number of property check for Persée in RDF took 0.13481640815734863s
Understandability | Number of label check for Persée in RDF took 2.3754122257232666s
Understandability | URI regex check for Persée in RDF took 1.000819444656372s
Understandability | Vocabs check for Persée in RDF took 0.4835808277130127s
Verifiability | Authors check for Persée in RDF took 0.13775634765625s
Verifiability | Publishers check for Persée in RDF took 0.13003039360046387s
Performance | Throughput check for Persée in RDF took 10.856038570404053s
Amount of data | Check the number of entities for Persée in RDF took 6.842613220214844e-05s
Verifiability | Contribs. check for Persée in RDF took 0.13210272789001465s
Interlinking | sameAs chians check for Persée in RDF took 0.30953121185302734s
Interlinking | skos check for Persée in RDF took 0.7890183925628662s
Interlinking | skos check for Persée in RDF took 0.13011932373046875s
Timeliness | dataset update frequency check for Persée in RDF took 0.7563772201538086s
Currency | Creation date check for Persée in RDF took 0.6112499237060547s
Currency | Modification date check for Persée in RDF took 0.24086833000183105s
Rep.Conc. | URIs length for Persée in RDF took 3.7757792472839355s
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.13366937637329102s
Accuracy | Check Functional Property for Persée in RDF took 0.1623222827911377s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.1583566665649414s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.7425153255462646s
Accuracy | Check White space in annotation for Persée in RDF took 0.03879404067993164s
Accuracy | Check Datatype consistency for Persée in RDF took 0.031493186950683594s
Consistency | Disjoint class check for Persée in RDF took 0.33277082443237305s
Consistency | Check Misplaced properties for Persée in RDF took 2.6273107528686523s
Consistency | Misplaced classes for Persée in RDF took 0.22297263145446777s
Consistency | Check Ontology hijacking for Persée in RDF took 1.7400710582733154s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.227877140045166s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.7193894386291504s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.031012773513793945s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.14915800094604492s
Security | Sign check for Persée in RDF took 0.9186677932739258s
Availability | Check URIs Dereferenciability for Persée in RDF took 1456.3565764427185s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.5028977394104004s
Reputation | Calculation of the PageRank for Persée in RDF took 0.02276301383972168s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00016832351684570312s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Persée in RDF took 1.1682510375976562e-05s
INFO | --- Analysis for data-persee-fr took 1705.1139163970947s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 2.0261764526367188s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.30153536796569824s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011396408081054688s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.0251998901367188e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 10.004405975341797s
Availability | SPARQL endpoint availability check for Open Data Web took 23.08271360397339s
Availability | VoID file availability check for Open Data Web took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.2827129364013672s
Reputation | Calculation of the PageRank for Open Data Web took 0.02079486846923828s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.170967102050781e-05s
Believability | Calculation of trust value for Open Data Web took 1.1920928955078125e-05s
INFO | --- Analysis for data.odw.tw took 96.08307361602783s
Availability | SPARQL endpoint availability check for datahub took 4.172325134277344e-05s
Availability | VoID file availability check for datahub took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for datahub took 0.2990143299102783s
Reputation | Calculation of the PageRank for datahub took 0.020884275436401367s
Interlinking | Calculation of Degree of Connection for datahub took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for datahub took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for datahub took 4.553794860839844e-05s
Believability | Calculation of trust value for datahub took 1.1205673217773438e-05s
INFO | --- Analysis for datahub took 4.40136194229126s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 4.401644945144653s
Availability | VoID file availability check for Open Datasets in South Korea took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.299114465713501s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.0994415283203125e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 1.049041748046875e-05s
INFO | --- Analysis for datahub-kr-datamap took 12.872461080551147s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.36162352561950684s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3089125156402588s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.021445274353027344s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.176399230957031e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.1444091796875e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.630734205245972s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.416810750961304s
Availability | VoID file availability check for datos-artium-org took 0.0007460117340087891s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.30345678329467773s
Reputation | Calculation of the PageRank for datos-artium-org took 0.02090311050415039s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.0001251697540283203s
Believability | Calculation of trust value for datos-artium-org took 1.0967254638671875e-05s
INFO | --- Analysis for datos-artium-org took 165.26213026046753s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.856947660446167s
Availability | VoID file availability check for Datos.bcn.cl took 0.0006725788116455078s
Extra | Recovery of all triples for Datos.bcn.cl took 29.633780002593994s
Performance | Total latancy measurement for Datos.bcn.cl took 6.305278062820435s
Amount of data | Number of triples check for Datos.bcn.cl took 6.9709312915802s
Interoperability | New terms check for Datos.bcn.cl took 4.832008123397827s
Versatility | Languages check for Datos.bcn.cl took 301.0432198047638s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.2771494388580322s
Security | Check HTTPS for Datos.bcn.cl took 0.7428922653198242s
Interpretability | RDF structures check for Datos.bcn.cl took 1.4208011627197266s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2463109493255615s
Availability | RDF dump link check for Datos.bcn.cl took 1.3243155479431152s
License | MR license check for Datos.bcn.cl took 1.2088935375213623s
License | HR license check for Datos.bcn.cl took 36.681262731552124s
Amount of data | Number of property check for Datos.bcn.cl took 1.3360950946807861s
Understandability | Number of label check for Datos.bcn.cl took 1.661268949508667s
Understandability | URI regex check for Datos.bcn.cl took 2.5578975677490234s
Understandability | Vocabs check for Datos.bcn.cl took 1.3564507961273193s
Verifiability | Authors check for Datos.bcn.cl took 1.2589430809020996s
Verifiability | Publishers check for Datos.bcn.cl took 1.3623847961425781s
Performance | Throughput check for Datos.bcn.cl took 12.747262477874756s
Amount of data | Check the number of entities for Datos.bcn.cl took 7.05718994140625e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.306894302368164s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.3556790351867676s
Interlinking | skos check for Datos.bcn.cl took 1.5092802047729492s
Interlinking | skos check for Datos.bcn.cl took 1.3827171325683594s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.3441829681396484s
Currency | Creation date check for Datos.bcn.cl took 2.589503526687622s
Currency | Modification date check for Datos.bcn.cl took 1.2249743938446045s
Rep.Conc. | URIs length for Datos.bcn.cl took 19.237670421600342s
Interoperability | New vocabularies check for Datos.bcn.cl took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.431483507156372s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.2182831764221191s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.3104028701782227s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 14.442966222763062s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.3212432861328125s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.2632260322570801s
Consistency | Disjoint class check for Datos.bcn.cl took 1.4441802501678467s
Consistency | Check Misplaced properties for Datos.bcn.cl took 7.91200852394104s
Consistency | Misplaced classes for Datos.bcn.cl took 2.1955761909484863s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 10.532184839248657s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.2447614669799805s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 7.2733471393585205s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.29061412811279297s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.6404709815979004s
Security | Sign check for Datos.bcn.cl took 1.2376337051391602s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 8195.953630447388s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.757554054260254s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.022638320922851562s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 0.00037407875061035156s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0010068416595458984s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 9.250640869140625e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 2.1457672119140625e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 9.298324584960938e-06s
INFO | --- Analysis for datos-bcn-cl took 9028.390195846558s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.5627682209014893s
Availability | VoID file availability check for datos.bne.es took 0.0005474090576171875s
Extra | Recovery of all triples for datos.bne.es took 140.8436062335968s
Performance | Total latancy measurement for datos.bne.es took 4.95365834236145s
Amount of data | Number of triples check for datos.bne.es took 0.8571805953979492s
Interoperability | New terms check for datos.bne.es took 4.022371292114258s
Versatility | Languages check for datos.bne.es took 61.40096712112427s
Interpretability | Number of blank nodes check for datos.bne.es took 0.30599379539489746s
Security | Check HTTPS for datos.bne.es took 0.18047404289245605s
Interpretability | RDF structures check for datos.bne.es took 2.374924421310425s
Versatility | Serialization formats check for datos.bne.es took 2.3861632347106934s
Availability | RDF dump link check for datos.bne.es took 2.0897927284240723s
License | MR license check for datos.bne.es took 2.5110538005828857s
License | HR license check for datos.bne.es took 63.332226514816284s
Amount of data | Number of property check for datos.bne.es took 2.0268492698669434s
Understandability | Number of label check for datos.bne.es took 2.783499240875244s
Understandability | URI regex check for datos.bne.es took 2.556460380554199s
Understandability | Vocabs check for datos.bne.es took 0.3731420040130615s
Verifiability | Authors check for datos.bne.es took 2.210602045059204s
Verifiability | Publishers check for datos.bne.es took 0.35962533950805664s
Performance | Throughput check for datos.bne.es took 24.19004249572754s
Amount of data | Check the number of entities for datos.bne.es took 3.2901763916015625e-05s
Verifiability | Contribs. check for datos.bne.es took 0.3443121910095215s
Interlinking | sameAs chians check for datos.bne.es took 0.4061319828033447s
Interlinking | skos check for datos.bne.es took 0.5476698875427246s
Interlinking | skos check for datos.bne.es took 0.280214786529541s
Timeliness | dataset update frequency check for datos.bne.es took 2.290562152862549s
Currency | Creation date check for datos.bne.es took 0.6835911273956299s
Currency | Modification date check for datos.bne.es took 0.5812008380889893s
Rep.Conc. | URIs length for datos.bne.es took 52.73877000808716s
Interoperability | New vocabularies check for datos.bne.es took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 2.1336936950683594s
Accuracy | Check Functional Property for datos.bne.es took 2.073421001434326s
Accuracy | Check Inverse Functional Property for datos.bne.es took 0.3069798946380615s
Accuracy | Check Empty annotation labels for datos.bne.es took 46.49694895744324s
Accuracy | Check White space in annotation for datos.bne.es took 1.6095101833343506s
Accuracy | Check Datatype consistency for datos.bne.es took 1.2570908069610596s
Consistency | Disjoint class check for datos.bne.es took 0.3039205074310303s
Consistency | Check Misplaced properties for datos.bne.es took 10.882331132888794s
Consistency | Misplaced classes for datos.bne.es took 4.321291446685791s
Consistency | Check Ontology hijacking for datos.bne.es took 41.088204860687256s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.1626324653625488s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 9.571997880935669s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.3596620559692383s
Conciseness | Check Intensional conciseness for datos.bne.es took 0.31394410133361816s
Security | Sign check for datos.bne.es took 1.1690738201141357s
Availability | Check URIs Dereferenciability for datos.bne.es took 10.147370100021362s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.4774200916290283s
Reputation | Calculation of the PageRank for datos.bne.es took 0.02113652229309082s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00015997886657714844s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 1.6689300537109375e-06s
Believability | Calculation of trust value for datos.bne.es took 6.4373016357421875e-06s
INFO | --- Analysis for datos-bne-es took 652.2681519985199s
Availability | SPARQL endpoint availability check for dbacademic took 0.06454730033874512s
Availability | VoID file availability check for dbacademic took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for dbacademic took 0.31877636909484863s
Reputation | Calculation of the PageRank for dbacademic took 0.020237445831298828s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for dbacademic took 2.8371810913085938e-05s
Believability | Calculation of trust value for dbacademic took 4.291534423828125e-06s
INFO | --- Analysis for dbacademic took 2.811563014984131s
Availability | SPARQL endpoint availability check for DBkWik took 266.3164246082306s
Availability | VoID file availability check for DBkWik took 0.0006444454193115234s
Extra | Recovery of all triples for DBkWik took 1.3876304626464844s
Performance | Total latancy measurement for DBkWik took 0.43753552436828613s
Amount of data | Number of triples check for DBkWik took 5.198738098144531s
Interoperability | New terms check for DBkWik took 1.9059276580810547s
Versatility | Languages check for DBkWik took 61.0003867149353s
Interpretability | Number of blank nodes check for DBkWik took 0.1154794692993164s
Interpretability | RDF structures check for DBkWik took 0.20464324951171875s
Versatility | Serialization formats check for DBkWik took 0.27529048919677734s
Availability | RDF dump link check for DBkWik took 2.5066545009613037s
License | MR license check for DBkWik took 0.4664344787597656s
License | HR license check for DBkWik took 60.66919755935669s
Amount of data | Number of property check for DBkWik took 0.1293349266052246s
Understandability | Number of label check for DBkWik took 2.4627342224121094s
Understandability | URI regex check for DBkWik took 0.4952049255371094s
Understandability | Vocabs check for DBkWik took 0.1894683837890625s
Verifiability | Authors check for DBkWik took 0.15433549880981445s
Verifiability | Publishers check for DBkWik took 0.1364128589630127s
Performance | Throughput check for DBkWik took 10.642221212387085s
Amount of data | Check the number of entities for DBkWik took 0.00011396408081054688s
Verifiability | Contribs. check for DBkWik took 0.11535334587097168s
Interlinking | sameAs chians check for DBkWik took 0.2997324466705322s
Interlinking | skos check for DBkWik took 0.3296933174133301s
Interlinking | skos check for DBkWik took 0.09025907516479492s
Timeliness | dataset update frequency check for DBkWik took 0.15022492408752441s
Currency | Creation date check for DBkWik took 0.3523123264312744s
Currency | Modification date check for DBkWik took 0.21274137496948242s
Rep.Conc. | URIs length for DBkWik took 11.16473650932312s
Interoperability | New vocabularies check for DBkWik took 19.372035264968872s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.9267055988311768s
Accuracy | Check Functional Property for DBkWik took 0.39994168281555176s
Accuracy | Check Inverse Functional Property for DBkWik took 0.19603586196899414s
Accuracy | Check Empty annotation labels for DBkWik took 0.9251470565795898s
Accuracy | Check White space in annotation for DBkWik took 0.023161649703979492s
Accuracy | Check Datatype consistency for DBkWik took 0.03680014610290527s
Consistency | Disjoint class check for DBkWik took 0.1334061622619629s
Consistency | Check Misplaced properties for DBkWik took 11.671380996704102s
Consistency | Misplaced classes for DBkWik took 20.613946676254272s
Consistency | Check Ontology hijacking for DBkWik took 1.6434378623962402s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.1271045207977295s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.60080599784851s
Conciseness | Check Extensional conciseness for DBkWik took 0.03261160850524902s
Conciseness | Check Intensional conciseness for DBkWik took 0.6798741817474365s
Security | Sign check for DBkWik took 0.31910085678100586s
Availability | Check URIs Dereferenciability for DBkWik took 12.43215274810791s
Completeness | Calculation of interlinking completeness for DBkWik took 0.32897210121154785s
Reputation | Calculation of the PageRank for DBkWik took 0.021212339401245117s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.343292236328125e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 14.641257762908936s
Believability | Calculation of trust value for DBkWik took 1.2159347534179688e-05s
INFO | --- Analysis for dbkwik took 1690.8353486061096s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 9.083747863769531e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.2906787395477295s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.021391868591308594s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0009381771087646484s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.0001251697540283203s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 6.078030347824097s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.49140095710754395s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0003113746643066406s
Extra | Recovery of all triples for dblp Knowledge Graph took 8.059622764587402s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.8131856918334961s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.1564171314239502s
Interoperability | New terms check for dblp Knowledge Graph took 1.6555840969085693s
Versatility | Languages check for dblp Knowledge Graph took 0.18504953384399414s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 3.6540720462799072s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.15700221061706543s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.20193195343017578s
Availability | RDF dump link check for dblp Knowledge Graph took 0.14885902404785156s
License | MR license check for dblp Knowledge Graph took 0.18294906616210938s
License | HR license check for dblp Knowledge Graph took 30.141119956970215s
Amount of data | Number of property check for dblp Knowledge Graph took 0.1471569538116455s
Understandability | Number of label check for dblp Knowledge Graph took 0.4808955192565918s
Understandability | URI regex check for dblp Knowledge Graph took 0.28109025955200195s
Understandability | Vocabs check for dblp Knowledge Graph took 0.16492128372192383s
Verifiability | Authors check for dblp Knowledge Graph took 0.18454384803771973s
Verifiability | Publishers check for dblp Knowledge Graph took 0.15734648704528809s
Performance | Throughput check for dblp Knowledge Graph took 11.02336573600769s
Amount of data | Check the number of entities for dblp Knowledge Graph took 7.677078247070312e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.16170573234558105s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.22085905075073242s
Interlinking | skos check for dblp Knowledge Graph took 0.16121935844421387s
Interlinking | skos check for dblp Knowledge Graph took 0.16405582427978516s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.16800475120544434s
Currency | Creation date check for dblp Knowledge Graph took 0.28621482849121094s
Currency | Modification date check for dblp Knowledge Graph took 0.3315162658691406s
Rep.Conc. | URIs length for dblp Knowledge Graph took 15.032462120056152s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.15493416786193848s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.12737035751342773s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.17052865028381348s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 7.111221551895142s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.0907742977142334s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.020990371704102s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.14859962463378906s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.28933072090148926s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 5.7565741539001465s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 16795.79051375389s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 3.723015069961548s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.699833631515503s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.19235539436340332s
Security | Sign check for dblp Knowledge Graph took 0.13297772407531738s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 2.7279436588287354s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.8335037231445312s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.021043062210083008s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.4781951904296875e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 1.6689300537109375e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 7.152557373046875e-06s
INFO | --- Analysis for dblp-kg took 16956.66243839264s
Availability | SPARQL endpoint availability check for DBnary took 0.33100008964538574s
Availability | VoID file availability check for DBnary took 0.0002949237823486328s
Extra | Recovery of all triples for DBnary took 1.280635118484497s
Performance | Total latancy measurement for DBnary took 0.425462007522583s
Amount of data | Number of triples check for DBnary took 1.216803789138794s
Interoperability | New terms check for DBnary took 3.4675889015197754s
Versatility | Languages check for DBnary took 62.56929397583008s
Interpretability | Number of blank nodes check for DBnary took 0.9130682945251465s
Security | Check HTTPS for DBnary took 0.15548491477966309s
Interpretability | RDF structures check for DBnary took 0.39884185791015625s
Versatility | Serialization formats check for DBnary took 0.3618049621582031s
Availability | RDF dump link check for DBnary took 0.07632303237915039s
License | MR license check for DBnary took 0.1473984718322754s
License | HR license check for DBnary took 62.05213379859924s
Amount of data | Number of property check for DBnary took 0.12018108367919922s
Understandability | Number of label check for DBnary took 0.5735034942626953s
Understandability | URI regex check for DBnary took 0.15639805793762207s
Understandability | Vocabs check for DBnary took 0.1669330596923828s
Verifiability | Authors check for DBnary took 0.08014178276062012s
Verifiability | Publishers check for DBnary took 0.06202435493469238s
Performance | Throughput check for DBnary took 10.544208765029907s
Amount of data | Check the number of entities for DBnary took 6.794929504394531e-05s
Verifiability | Contribs. check for DBnary took 0.07784223556518555s
Interlinking | sameAs chians check for DBnary took 0.10843157768249512s
Interlinking | skos check for DBnary took 0.2271251678466797s
Interlinking | skos check for DBnary took 0.07919859886169434s
Timeliness | dataset update frequency check for DBnary took 0.1315009593963623s
Currency | Creation date check for DBnary took 0.1647036075592041s
Currency | Modification date check for DBnary took 0.17987871170043945s
Rep.Conc. | URIs length for DBnary took 11.126582860946655s
Interoperability | New vocabularies check for DBnary took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for DBnary took 0.15235686302185059s
Accuracy | Check Functional Property for DBnary took 0.17194223403930664s
Accuracy | Check Inverse Functional Property for DBnary took 0.12099361419677734s
Accuracy | Check Empty annotation labels for DBnary took 0.6547183990478516s
Accuracy | Check White space in annotation for DBnary took 0.030711889266967773s
Accuracy | Check Datatype consistency for DBnary took 0.027487993240356445s
Consistency | Disjoint class check for DBnary took 0.09414887428283691s
Consistency | Check Misplaced properties for DBnary took 8.73511290550232s
Consistency | Misplaced classes for DBnary took 0.25957608222961426s
Consistency | Check Ontology hijacking for DBnary took 1.6369273662567139s
Consistency | Check Invalid usage of undefined classes for DBnary took 1.2731139659881592s
Consistency | Check Invalid usage of undefined properties for DBnary took 9.828328609466553s
Conciseness | Check Extensional conciseness for DBnary took 0.036092519760131836s
Conciseness | Check Intensional conciseness for DBnary took 0.17171239852905273s
Security | Sign check for DBnary took 0.12163996696472168s
Availability | Check URIs Dereferenciability for DBnary took 11.467469453811646s
Completeness | Calculation of interlinking completeness for DBnary took 0.2996349334716797s
Reputation | Calculation of the PageRank for DBnary took 0.021012306213378906s
Interlinking | Calculation of Degree of Connection for DBnary took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for DBnary took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for DBnary took 5.507469177246094e-05s
Interoperability | Check the re-using of existing vocabs for DBnary took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBnary took 1.4066696166992188e-05s
INFO | --- Analysis for dbnary took 288.9723837375641s
Availability | SPARQL endpoint availability check for DBpedia took 0.9494309425354004s
Availability | VoID file availability check for DBpedia took 0.0006406307220458984s
Extra | Recovery of all triples for DBpedia took 2.9154114723205566s
Performance | Total latancy measurement for DBpedia took 2.7340362071990967s
Amount of data | Number of triples check for DBpedia took 2.7621939182281494s
Interoperability | New terms check for DBpedia took 5.1142637729644775s
Versatility | Languages check for DBpedia took 32.082956075668335s
Interpretability | Number of blank nodes check for DBpedia took 0.5833714008331299s
Security | Check HTTPS for DBpedia took 0.3710768222808838s
Interpretability | RDF structures check for DBpedia took 0.8068981170654297s
Versatility | Serialization formats check for DBpedia took 0.6810827255249023s
Availability | RDF dump link check for DBpedia took 0.552480936050415s
License | MR license check for DBpedia took 1.3011510372161865s
License | HR license check for DBpedia took 31.78821873664856s
Amount of data | Number of property check for DBpedia took 0.6061954498291016s
Understandability | Number of label check for DBpedia took 4.469947099685669s
Understandability | URI regex check for DBpedia took 1.164708137512207s
Understandability | Vocabs check for DBpedia took 0.6245739459991455s
Verifiability | Authors check for DBpedia took 0.6448409557342529s
Verifiability | Publishers check for DBpedia took 0.613983154296875s
Performance | Throughput check for DBpedia took 11.085079908370972s
Amount of data | Check the number of entities for DBpedia took 7.05718994140625e-05s
Verifiability | Contribs. check for DBpedia took 0.5731847286224365s
Interlinking | sameAs chians check for DBpedia took 2.4026362895965576s
Interlinking | skos check for DBpedia took 0.8885247707366943s
Interlinking | skos check for DBpedia took 0.5727078914642334s
Timeliness | dataset update frequency check for DBpedia took 0.6864902973175049s
Currency | Creation date check for DBpedia took 1.1937921047210693s
Currency | Modification date check for DBpedia took 1.1871838569641113s
Rep.Conc. | URIs length for DBpedia took 34.68049430847168s
Interoperability | New vocabularies check for DBpedia took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.5913064479827881s
Accuracy | Check Functional Property for DBpedia took 0.5786857604980469s
Accuracy | Check Inverse Functional Property for DBpedia took 0.5630853176116943s
Accuracy | Check Empty annotation labels for DBpedia took 2.5638070106506348s
Accuracy | Check White space in annotation for DBpedia took 0.0298306941986084s
Accuracy | Check Datatype consistency for DBpedia took 0.027265548706054688s
Consistency | Disjoint class check for DBpedia took 0.5402734279632568s
Consistency | Check Misplaced properties for DBpedia took 33.29751253128052s
Consistency | Misplaced classes for DBpedia took 1.5455560684204102s
Consistency | Check Ontology hijacking for DBpedia took 3.514866828918457s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.117691993713379s
Consistency | Check Invalid usage of undefined properties for DBpedia took 2.622799873352051s
Conciseness | Check Extensional conciseness for DBpedia took 0.03254246711730957s
Conciseness | Check Intensional conciseness for DBpedia took 1.951634168624878s
Security | Sign check for DBpedia took 0.6026623249053955s
Availability | Check URIs Dereferenciability for DBpedia took 3946.6939539909363s
Completeness | Calculation of interlinking completeness for DBpedia took 0.6996364593505859s
Reputation | Calculation of the PageRank for DBpedia took 0.021523475646972656s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008983612060546875s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia took 1.0251998901367188e-05s
INFO | --- Analysis for dbpedia took 6452.083929538727s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.2438507080078125e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.29077577590942383s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.021596908569335938s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 5.888938903808594e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.580352783203125e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.0967254638671875e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 7.60301947593689s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.167673826217651s
Availability | VoID file availability check for DBpedia Commons took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.3106503486633301s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.437301635742188e-05s
Believability | Calculation of trust value for DBpedia Commons took 1.3113021850585938e-05s
INFO | --- Analysis for dbpedia-commons took 16.536946773529053s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 0.8308126926422119s
Availability | VoID file availability check for DBpedia in Greek took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.3139641284942627s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.022264480590820312s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.001010894775390625s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00021338462829589844s
Believability | Calculation of trust value for DBpedia in Greek took 9.059906005859375e-06s
INFO | --- Analysis for dbpedia-el took 7.184621810913086s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.5393986701965332s
Availability | VoID file availability check for DBpedia in Spanish took 0.0005781650543212891s
Extra | Recovery of all triples for DBpedia in Spanish took 2.9701709747314453s
Performance | Total latancy measurement for DBpedia in Spanish took 1.4386508464813232s
Amount of data | Number of triples check for DBpedia in Spanish took 0.8593037128448486s
Interoperability | New terms check for DBpedia in Spanish took 2.6566901206970215s
Versatility | Languages check for DBpedia in Spanish took 61.011780977249146s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.40066957473754883s
Security | Check HTTPS for DBpedia in Spanish took 0.13851284980773926s
Interpretability | RDF structures check for DBpedia in Spanish took 1.7604985237121582s
Versatility | Serialization formats check for DBpedia in Spanish took 0.7762162685394287s
Availability | RDF dump link check for DBpedia in Spanish took 0.4879138469696045s
License | MR license check for DBpedia in Spanish took 1.0939948558807373s
License | HR license check for DBpedia in Spanish took 62.1092894077301s
Amount of data | Number of property check for DBpedia in Spanish took 0.3723299503326416s
Understandability | Number of label check for DBpedia in Spanish took 2.2352302074432373s
Understandability | URI regex check for DBpedia in Spanish took 0.9593226909637451s
Understandability | Vocabs check for DBpedia in Spanish took 0.5365583896636963s
Verifiability | Authors check for DBpedia in Spanish took 0.35039520263671875s
Verifiability | Publishers check for DBpedia in Spanish took 0.3202488422393799s
Performance | Throughput check for DBpedia in Spanish took 11.566124439239502s
Amount of data | Check the number of entities for DBpedia in Spanish took 0.00010919570922851562s
Verifiability | Contribs. check for DBpedia in Spanish took 0.4810333251953125s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.5833520889282227s
Interlinking | skos check for DBpedia in Spanish took 0.8443000316619873s
Interlinking | skos check for DBpedia in Spanish took 0.2677631378173828s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.558286190032959s
Currency | Creation date check for DBpedia in Spanish took 0.726499080657959s
Currency | Modification date check for DBpedia in Spanish took 0.6587624549865723s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.495075464248657s
Interoperability | New vocabularies check for DBpedia in Spanish took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.350832462310791s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.5657055377960205s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.5824978351593018s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.175063133239746s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.030963897705078125s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.03220844268798828s
Consistency | Disjoint class check for DBpedia in Spanish took 0.33008313179016113s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.08256983757019s
Consistency | Misplaced classes for DBpedia in Spanish took 1.0732834339141846s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.465999126434326s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.1180200576782227s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 6.693522214889526s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.031155109405517578s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.6288063526153564s
Security | Sign check for DBpedia in Spanish took 0.40932726860046387s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 3.1369094848632812s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.3351433277130127s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.0215756893157959s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00011515617370605469s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 1.0013580322265625e-05s
INFO | --- Analysis for dbpedia-es took 1219.0805597305298s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.302506923675537s
Availability | VoID file availability check for DBpedia in Basque took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.3496565818786621s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.02123403549194336s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.7670135498046875e-05s
Believability | Calculation of trust value for DBpedia in Basque took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-eu took 7.2944159507751465s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.1770479679107666s
Availability | VoID file availability check for DBpedia in French took 0.0005018711090087891s
Extra | Recovery of all triples for DBpedia in French took 102.55598044395447s
Performance | Total latancy measurement for DBpedia in French took 0.45339322090148926s
Amount of data | Number of triples check for DBpedia in French took 13.141808271408081s
Interoperability | New terms check for DBpedia in French took 16.073442220687866s
Versatility | Languages check for DBpedia in French took 300.0812110900879s
Interpretability | Number of blank nodes check for DBpedia in French took 0.6066112518310547s
Security | Check HTTPS for DBpedia in French took 0.19775700569152832s
Interpretability | RDF structures check for DBpedia in French took 0.513451337814331s
Versatility | Serialization formats check for DBpedia in French took 0.5203573703765869s
Availability | RDF dump link check for DBpedia in French took 7.154534101486206s
License | MR license check for DBpedia in French took 2.1541619300842285s
License | HR license check for DBpedia in French took 300.06496572494507s
Amount of data | Number of property check for DBpedia in French took 0.5765411853790283s
Understandability | Number of label check for DBpedia in French took 2.2293882369995117s
Understandability | URI regex check for DBpedia in French took 0.30254578590393066s
Understandability | Vocabs check for DBpedia in French took 0.16030097007751465s
Verifiability | Authors check for DBpedia in French took 0.48985743522644043s
Verifiability | Publishers check for DBpedia in French took 0.15160274505615234s
Performance | Throughput check for DBpedia in French took 10.419632196426392s
Amount of data | Check the number of entities for DBpedia in French took 2.079474449157715s
Verifiability | Contribs. check for DBpedia in French took 0.16387701034545898s
Interlinking | sameAs chians check for DBpedia in French took 0.6546058654785156s
Interlinking | skos check for DBpedia in French took 0.23521113395690918s
Interlinking | skos check for DBpedia in French took 0.09441971778869629s
Timeliness | dataset update frequency check for DBpedia in French took 0.42663049697875977s
Currency | Creation date check for DBpedia in French took 0.40624403953552246s
Currency | Modification date check for DBpedia in French took 0.19658517837524414s
Rep.Conc. | URIs length for DBpedia in French took 184.77481079101562s
Interoperability | New vocabularies check for DBpedia in French took 7.226217746734619s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.11672329902648926s
Accuracy | Check Functional Property for DBpedia in French took 0.16715002059936523s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.12051129341125488s
Accuracy | Check Empty annotation labels for DBpedia in French took 24.935149908065796s
Accuracy | Check White space in annotation for DBpedia in French took 3.064753532409668s
Accuracy | Check Datatype consistency for DBpedia in French took 2.648435115814209s
Consistency | Disjoint class check for DBpedia in French took 0.2978360652923584s
Consistency | Check Misplaced properties for DBpedia in French took 7.014316082000732s
Consistency | Misplaced classes for DBpedia in French took 9.736270904541016s
Consistency | Check Ontology hijacking for DBpedia in French took 37.00408601760864s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.242729663848877s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 7.413601636886597s
Conciseness | Check Extensional conciseness for DBpedia in French took 2.9600024223327637s
Conciseness | Check Intensional conciseness for DBpedia in French took 3.681943416595459s
Security | Sign check for DBpedia in French took 0.16699600219726562s
Availability | Check URIs Dereferenciability for DBpedia in French took 11.91906189918518s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.7134413719177246s
Reputation | Calculation of the PageRank for DBpedia in French took 0.020748138427734375s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 9.560585021972656e-05s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 6.653266906738281s
Believability | Calculation of trust value for DBpedia in French took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia-fr took 1786.4245760440826s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.8954100608825684s
Availability | VoID file availability check for DBpedia in Japanese took 4.0997889041900635s
Extra | Recovery of all triples for DBpedia in Japanese took 5.583798885345459s
Performance | Total latancy measurement for DBpedia in Japanese took 6.676931142807007s
Amount of data | Number of triples check for DBpedia in Japanese took 29.57404589653015s
Interoperability | New terms check for DBpedia in Japanese took 17.79673147201538s
Versatility | Languages check for DBpedia in Japanese took 1.3471777439117432s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3230931758880615s
Security | Check HTTPS for DBpedia in Japanese took 0.7999982833862305s
Interpretability | RDF structures check for DBpedia in Japanese took 1.394277572631836s
Versatility | Serialization formats check for DBpedia in Japanese took 1.3564527034759521s
Availability | RDF dump link check for DBpedia in Japanese took 1.3298401832580566s
License | MR license check for DBpedia in Japanese took 1.3438336849212646s
License | HR license check for DBpedia in Japanese took 61.32704973220825s
Amount of data | Number of property check for DBpedia in Japanese took 1.3343756198883057s
Understandability | Number of label check for DBpedia in Japanese took 1.325716495513916s
Understandability | URI regex check for DBpedia in Japanese took 2.6275413036346436s
Understandability | Vocabs check for DBpedia in Japanese took 1.3433356285095215s
Verifiability | Authors check for DBpedia in Japanese took 1.3161497116088867s
Verifiability | Publishers check for DBpedia in Japanese took 1.3230936527252197s
Performance | Throughput check for DBpedia in Japanese took 13.318958044052124s
Amount of data | Check the number of entities for DBpedia in Japanese took 6.961822509765625e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3169529438018799s
Interlinking | sameAs chians check for DBpedia in Japanese took 1.3326435089111328s
Interlinking | skos check for DBpedia in Japanese took 1.331019401550293s
Interlinking | skos check for DBpedia in Japanese took 1.3318777084350586s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.333143949508667s
Currency | Creation date check for DBpedia in Japanese took 2.713141679763794s
Currency | Modification date check for DBpedia in Japanese took 2.68001651763916s
Rep.Conc. | URIs length for DBpedia in Japanese took 110.98204803466797s
Interoperability | New vocabularies check for DBpedia in Japanese took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.341670274734497s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.3430614471435547s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.361687421798706s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 3.343848466873169s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.025526046752929688s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.027826786041259766s
Consistency | Disjoint class check for DBpedia in Japanese took 1.521630048751831s
Consistency | Check Misplaced properties for DBpedia in Japanese took 94.2053472995758s
Consistency | Misplaced classes for DBpedia in Japanese took 3.0289719104766846s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.134336948394775s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.2134380340576172s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 93.98380374908447s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.03300809860229492s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 3.325901508331299s
Security | Sign check for DBpedia in Japanese took 1.3672480583190918s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 8.750505924224854s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.39644908905029297s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.021611452102661133s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010275840759277344s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 9.5367431640625e-07s
Believability | Calculation of trust value for DBpedia in Japanese took 5.245208740234375e-06s
INFO | --- Analysis for dbpedia-ja took 960.776202917099s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.315376281738281e-05s
Availability | VoID file availability check for dbpedia lite took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.2749507427215576s
Reputation | Calculation of the PageRank for dbpedia lite took 0.022625446319580078s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00010919570922851562s
Believability | Calculation of trust value for dbpedia lite took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-lite took 5.559784412384033s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.2436840534210205s
Availability | VoID file availability check for DBpedia in Dutch took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.29986071586608887s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.021111726760864258s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.0001761913299560547s
Believability | Calculation of trust value for DBpedia in Dutch took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-nl took 3.4553956985473633s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 15.353251218795776s
Availability | VoID file availability check for DBpedia in Portuguese took 0.000457763671875s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.4214320182800293s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.021060466766357422s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.320808410644531e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia-pt took 31.270703554153442s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 0.00010633468627929688s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.29042959213256836s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.02113056182861328s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 7.104873657226562e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.049041748046875e-05s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 13.865587949752808s
Availability | SPARQL endpoint availability check for DBTropes took 4.124641418457031e-05s
Availability | VoID file availability check for DBTropes took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for DBTropes took 0.29767346382141113s
Reputation | Calculation of the PageRank for DBTropes took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.202957153320312e-05s
Believability | Calculation of trust value for DBTropes took 1.0251998901367188e-05s
INFO | --- Analysis for dbtropes took 3.660517692565918s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 8.368492126464844e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.3171541690826416s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.0218660831451416s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.602836608886719e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 1.0251998901367188e-05s
INFO | --- Analysis for dbtune-artists-last-fm took 3.209947347640991s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.1961669921875e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.28794360160827637s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.02093195915222168s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.552436828613281e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.0251998901367188e-05s
INFO | --- Analysis for dbtune-audioscrobbler took 2.9133567810058594s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.5978875160217285s
Availability | VoID file availability check for DBTune.org/classical took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.28615665435791016s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.021854400634765625s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.510185241699219e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.049041748046875e-05s
INFO | --- Analysis for dbtune-classical took 9.128202438354492s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.848927974700928s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0004017353057861328s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.2942516803741455s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.030048370361328125s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0010673999786376953s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 8.296966552734375e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 6.9141387939453125e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 11.680949926376343s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 5.585644721984863s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.31712818145751953s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.02076888084411621s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 7.82012939453125e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.2159347534179688e-05s
INFO | --- Analysis for dbtune-magnatune took 10.04391860961914s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 180.4256579875946s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0007944107055664062s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.38635969161987305s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.021274089813232422s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.0001251697540283203s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.0251998901367188e-05s
INFO | --- Analysis for dbtune-musicbrainz took 433.80483841896057s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.3467240333557129s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.27935194969177246s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020934104919433594s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.412101745605469e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.1920928955078125e-05s
INFO | --- Analysis for dbtune-myspace took 3.2959814071655273s
Availability | SPARQL endpoint availability check for data.dcs took 4.291534423828125e-05s
Availability | VoID file availability check for data.dcs took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for data.dcs took 0.6155927181243896s
Reputation | Calculation of the PageRank for data.dcs took 0.021214723587036133s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.437301635742188e-05s
Believability | Calculation of trust value for data.dcs took 1.1444091796875e-05s
INFO | --- Analysis for dcs-sheffield took 3.145947217941284s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 5.817413330078125e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.31839609146118164s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.020829200744628906s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.62396240234375e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 1.239776611328125e-05s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.71600341796875s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 5.626678466796875e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.3299832344055176s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020849227905273438s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.649162292480469e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.3113021850585938e-05s
INFO | --- Analysis for debian-package-tracking-system took 5.122664928436279s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.410743713378906e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.2828946113586426s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.022317171096801758s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.933906555175781e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.33514404296875e-05s
INFO | --- Analysis for desaparecidos took 3.249722957611084s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 8.940696716308594e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.3127555847167969s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.021100282669067383s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.00087738037109375s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.00011897087097167969s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.2636184692382812e-05s
INFO | --- Analysis for deustoentrepreneurship took 5.195668458938599s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 8.869171142578125e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.3227059841156006s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.022192955017089844s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0010902881622314453s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.0001494884490966797s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.2874603271484375e-05s
INFO | --- Analysis for deustotech took 5.812467098236084s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.5081417560577393s
Availability | VoID file availability check for Deutsche Biographie took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.304004430770874s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.020669937133789062s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.6716461181640625e-05s
Believability | Calculation of trust value for Deutsche Biographie took 9.5367431640625e-06s
INFO | --- Analysis for deutsche-biographie took 4.641449689865112s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 9.250640869140625e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2887442111968994s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.984306335449219e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.33514404296875e-05s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.453774452209473s
Availability | SPARQL endpoint availability check for dev8d took 4.553794860839844e-05s
Availability | VoID file availability check for dev8d took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for dev8d took 0.4207146167755127s
Reputation | Calculation of the PageRank for dev8d took 0.021754980087280273s
Interlinking | Calculation of Degree of Connection for dev8d took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.818771362304688e-05s
Believability | Calculation of trust value for dev8d took 1.2636184692382812e-05s
INFO | --- Analysis for dev8d took 3.8765900135040283s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.180006504058838s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.000782012939453125s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.44817519187927246s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020999908447265625s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.3882598876953125e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.2636184692382812e-05s
INFO | --- Analysis for dewey_decimal_classification took 93.18861365318298s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 0.0001392364501953125s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.32929420471191406s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.02230978012084961s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.266334533691406e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 1.33514404296875e-05s
INFO | --- Analysis for DHSVM took 23.044224977493286s
Availability | SPARQL endpoint availability check for Diavgeia took 8.559226989746094e-05s
Availability | VoID file availability check for Diavgeia took 0.001318216323852539s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.3077361583709717s
Reputation | Calculation of the PageRank for Diavgeia took 0.02188706398010254s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.082389831542969e-05s
Believability | Calculation of trust value for Diavgeia took 8.58306884765625e-06s
INFO | --- Analysis for diavgeia took 5.98756217956543s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 9.560585021972656e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.2845039367675781s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00012159347534179688s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.2636184692382812e-05s
INFO | --- Analysis for didactalia took 10.661635160446167s
Availability | SPARQL endpoint availability check for DisGeNET took 1.9263012409210205s
Availability | VoID file availability check for DisGeNET took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.3119843006134033s
Reputation | Calculation of the PageRank for DisGeNET took 0.021483659744262695s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.0001506805419921875s
Believability | Calculation of trust value for DisGeNET took 1.1205673217773438e-05s
INFO | --- Analysis for disgenet took 8.256197452545166s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.291534423828125e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.29749608039855957s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020717620849609375s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 2.8371810913085938e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.1205673217773438e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 6.2020158767700195s
Availability | SPARQL endpoint availability check for DM2E took 8.559226989746094e-05s
Availability | VoID file availability check for DM2E took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for DM2E took 0.2974059581756592s
Reputation | Calculation of the PageRank for DM2E took 0.020534038543701172s
Interlinking | Calculation of Degree of Connection for DM2E took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DM2E took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00010848045349121094s
Believability | Calculation of trust value for DM2E took 1.2159347534179688e-05s
INFO | --- Analysis for dm2e took 3.3150148391723633s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 4.220008850097656e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.33541035652160645s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.022359609603881836s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00016617774963378906s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 1.3113021850585938e-05s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 8.05371642112732s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 8.845329284667969e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0011851787567138672s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.34226179122924805s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.02097034454345703s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.341934204101562e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 8.58306884765625e-06s
INFO | --- Analysis for doi took 7.901311159133911s
Availability | SPARQL endpoint availability check for Driggu Florentino took 8.869171142578125e-05s
Availability | VoID file availability check for Driggu Florentino took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.28914976119995117s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.022028446197509766s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 2.9802322387695312e-05s
Believability | Calculation of trust value for Driggu Florentino took 1.1682510375976562e-05s
INFO | --- Analysis for Driggu took 4.876734972000122s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.3402423858642578s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.2980334758758545s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.021565914154052734s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 4.100799560546875e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.3113021850585938e-05s
INFO | --- Analysis for drug-data-hifm took 16.5955650806427s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.7317817211151s
Availability | VoID file availability check for MetaLex Document Server took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.3241910934448242s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.021174907684326172s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.933906555175781e-05s
Believability | Calculation of trust value for MetaLex Document Server took 9.298324584960938e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 555.1939451694489s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.462967872619629s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.30403685569763184s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.02205204963684082s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.695487976074219e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 1.1205673217773438e-05s
INFO | --- Analysis for dutch-ships-and-sailors took 14.522992134094238s
Availability | SPARQL endpoint availability check for DWS-Group took 0.00013399124145507812s
Availability | VoID file availability check for DWS-Group took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.289583683013916s
Reputation | Calculation of the PageRank for DWS-Group took 0.020938396453857422s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010395050048828125s
Believability | Calculation of trust value for DWS-Group took 1.1205673217773438e-05s
INFO | --- Analysis for dws-group took 2.7956695556640625s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 9.608268737792969e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.30702805519104004s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.02085113525390625s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.0517578125e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.1205673217773438e-05s
INFO | --- Analysis for E1 took 4.333355665206909s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.06873130798339844s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.28870248794555664s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020901203155517578s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011515617370605469s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-alaska took 2.851989269256592s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.04723000526428223s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.3049614429473877s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020969629287719727s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.626678466796875e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-cau took 2.940661907196045s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.05002641677856445s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.3087046146392822s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.022858381271362305s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.771087646484375e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 2.5510787963867188e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.82761549949646s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.08024048805236816s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.2996068000793457s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.021097660064697266s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.417533874511719e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-cdrewu took 2.901571273803711s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.053917884826660156s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004315376281738281s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.32773542404174805s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.022789955139160156s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00014138221740722656s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-dartmouth took 2.8809070587158203s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.035611629486083984s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.2993779182434082s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.020903587341308594s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.821487426757812e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-famu took 2.858376979827881s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.04207873344421387s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.3497486114501953s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.02135467529296875s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00012922286987304688s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-harvard took 2.901071786880493s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.05024409294128418s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.31756067276000977s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.02268695831298828s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012969970703125s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.8897852897644043s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.058565616607666016s
Availability | VoID file availability check for eagle-i @ Howard University took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.29735589027404785s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.022672176361083984s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0008656978607177734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 7.486343383789062e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-howard took 2.872572183609009s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.041266441345214844s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.3019375801086426s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.021127700805664062s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0009949207305908203s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.915496826171875e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.8099634647369385s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.05692648887634277s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.33708786964416504s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.021555423736572266s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011610984802246094s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-jsu took 2.7959251403808594s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.05463147163391113s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.3113744258880615s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.02105569839477539s
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.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.743171691894531e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-meharry took 2.8238749504089355s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.05047917366027832s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.26306819915771484s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.0209958553314209s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.489059448242188e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.0013580322265625e-05s
INFO | --- Analysis for eagle-i-montana took 2.683624029159546s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.036078453063964844s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.30631279945373535s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.021086931228637695s
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.0007238388061523438s
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.1205673217773438e-05s
INFO | --- Analysis for eagle-i-msm took 2.804283618927002s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.047405242919921875s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.3267049789428711s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.020852327346801758s
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.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00013113021850585938s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i-ohsu took 2.9448747634887695s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.053887367248535156s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2868356704711914s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.02156543731689453s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.175041198730469e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-psm took 2.812352418899536s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.04286003112792969s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.2859623432159424s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.02088761329650879s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.198883056640625e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-tsu took 2.8541929721832275s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.04598665237426758s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.3080267906188965s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.02081441879272461s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.198883056640625e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-tuskegee took 2.7861437797546387s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.04487895965576172s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.3393115997314453s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.02129387855529785s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00010395050048828125s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i-uccaribe took 2.7659263610839844s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.04297065734863281s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.3175978660583496s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.02137017250061035s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0001239776611328125s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-upr took 2.7927968502044678s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.05444622039794922s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.263791561126709s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020918607711791992s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.127357482910156e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-utep took 2.694793224334717s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.04987287521362305s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.2942829132080078s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.021658897399902344s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 6.771087646484375e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-utsa took 2.8210856914520264s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.15613436698913574s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.3458740711212158s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.02059793472290039s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 8.7738037109375e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-vanderbilt took 2.901552438735962s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.06820535659790039s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.2877345085144043s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.021438121795654297s
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.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.128715515136719e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-xula took 2.697601795196533s
Availability | SPARQL endpoint availability check for Emergency situation took 0.6549127101898193s
Availability | VoID file availability check for Emergency situation took 0.0007221698760986328s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.2936251163482666s
Reputation | Calculation of the PageRank for Emergency situation took 0.021264314651489258s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.863739013671875e-05s
Believability | Calculation of trust value for Emergency situation took 1.1920928955078125e-05s
INFO | --- Analysis for Earthquake took 3.9878790378570557s
Availability | SPARQL endpoint availability check for ESO took 0.5419564247131348s
Availability | VoID file availability check for ESO took 0.000732421875s
Completeness | Calculation of interlinking completeness for ESO took 0.2656879425048828s
Reputation | Calculation of the PageRank for ESO took 0.020589113235473633s
Interlinking | Calculation of Degree of Connection for ESO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for ESO took 8.130073547363281e-05s
Believability | Calculation of trust value for ESO took 1.1205673217773438e-05s
INFO | --- Analysis for Earthquake_case took 4.355267286300659s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.12637805938720703s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.27666544914245605s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.021292686462402344s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010418891906738281s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for ecb-linked-data took 2.867555856704712s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 6.4624998569488525s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.27714014053344727s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020650625228881836s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.886222839355469e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 8.821487426757812e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 15.204670429229736s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 4.577326536178589s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.001032114028930664s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.32761526107788086s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.021078824996948242s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.747245788574219e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.0013580322265625e-05s
INFO | --- Analysis for ecco-tcp-linked-data took 13.021182298660278s
Availability | SPARQL endpoint availability check for ECLAP took 20.527738094329834s
Availability | VoID file availability check for ECLAP took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for ECLAP took 0.31210851669311523s
Reputation | Calculation of the PageRank for ECLAP took 0.022332429885864258s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.124641418457031e-05s
Believability | Calculation of trust value for ECLAP took 1.1205673217773438e-05s
INFO | --- Analysis for eclap took 53.446102142333984s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 8.463859558105469e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0007245540618896484s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.30115318298339844s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.1920928955078125e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.2636184692382812e-05s
INFO | --- Analysis for ECNU-GISer took 4.405757188796997s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.0001537799835205078s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2880427837371826s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.459785461425781e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.2874603271484375e-05s
INFO | --- Analysis for ecs took 2.8432469367980957s
Availability | SPARQL endpoint availability check for Edublogs took 8.606910705566406e-05s
Availability | VoID file availability check for Edublogs took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Edublogs took 0.3044705390930176s
Reputation | Calculation of the PageRank for Edublogs took 0.022258996963500977s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010156631469726562s
Believability | Calculation of trust value for Edublogs took 1.1444091796875e-05s
INFO | --- Analysis for edublogs took 3.5536580085754395s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.9173471927642822s
Availability | VoID file availability check for education.data.gov.uk took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.30370306968688965s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020725488662719727s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.678436279296875e-05s
Believability | Calculation of trust value for education.data.gov.uk took 8.821487426757812e-06s
INFO | --- Analysis for education-data-gov-uk took 6.632359504699707s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 391.46878004074097s
Availability | VoID file availability check for Educational programs - SISVU took 0.000774383544921875s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.6766536235809326s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.021650314331054688s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 5.817413330078125e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 6.127357482910156e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.4781951904296875e-05s
INFO | --- Analysis for educationalprograms_sisvu took 1321.8781039714813s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 0.9972233772277832s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.3011147975921631s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.02186131477355957s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.6253204345703125e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 5.4836273193359375e-06s
INFO | --- Analysis for eea took 9.779561281204224s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.4829432964324951s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.297818660736084s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.02272629737854004s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.459785461425781e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 9.298324584960938e-06s
INFO | --- Analysis for eea-rod took 5.591092109680176s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.18415021896362305s
Availability | VoID file availability check for EEA Vocabularies took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.2972564697265625s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.022819995880126953s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.749961853027344e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.049041748046875e-05s
INFO | --- Analysis for eea-vocabularies took 5.338615894317627s
Availability | SPARQL endpoint availability check for E-Government Ontology took 1.59832763671875s
Availability | VoID file availability check for E-Government Ontology took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.2844829559326172s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.02263808250427246s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for EGovOntology took 5.740838050842285s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6762518882751465s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0005292892456054688s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 3.898864269256592s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2652137279510498s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6512255668640137s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.8552320003509521s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.31952238082886s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.22260308265686s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4593698978424072s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9070379734039307s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2848548889160156s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.40940093994140625s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 5.669256925582886s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2703557014465332s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.38352417945861816s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5970802307128906s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3133218288421631s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.31927061080932617s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2695338726043701s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 10.45937180519104s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 7.796287536621094e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3185117244720459s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.26292920112609863s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.40639662742614746s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.27159786224365234s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3089940547943115s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9097356796264648s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.26721906661987305s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 6.063070774078369s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24004793167114258s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2818179130554199s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.28600335121154785s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0520286560058594s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03021717071533203s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.027384519577026367s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2509300708770752s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.181402921676636s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4425346851348877s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.20992112159729s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1502041816711426s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.0108561515808105s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03345894813537598s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4459080696105957s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3894360065460205s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3347.623564004898s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7371768951416016s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.021708965301513672s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.888938903808594e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.6689300537109375e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2159347534179688e-05s
INFO | --- Analysis for ei2a took 3584.673425912857s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 8.511543273925781e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.2866959571838379s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.0001049041748046875s
Believability | Calculation of trust value for EIONET RDF Data took 9.298324584960938e-06s
INFO | --- Analysis for eionet-rdf took 3.3844153881073s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.482269287109375e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.3135643005371094s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.020810604095458984s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.0517578125e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 1.0967254638671875e-05s
INFO | --- Analysis for ElgooG_ took 2.6427712440490723s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.173135042190552s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.30853724479675293s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.021025896072387695s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.271766662597656e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.4066696166992188e-05s
INFO | --- Analysis for elviajero took 19.48983597755432s
Availability | SPARQL endpoint availability check for EMN took 8.368492126464844e-05s
Availability | VoID file availability check for EMN took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for EMN took 0.27469587326049805s
Reputation | Calculation of the PageRank for EMN took 0.021463871002197266s
Interlinking | Calculation of Degree of Connection for EMN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for EMN took 4.1961669921875e-05s
Believability | Calculation of trust value for EMN took 1.239776611328125e-05s
INFO | --- Analysis for emn took 3.0422730445861816s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.267692565917969e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.28430604934692383s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.14984130859375e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-co2emission took 2.8223466873168945s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.3102385997772217s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.020892620086669922s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 3.910064697265625e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-crime took 2.5569393634796143s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 6.4849853515625e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.27503299713134766s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 3.981590270996094e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-energy took 2.7086708545684814s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.3386988639831543s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.012222290039062e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 8.58306884765625e-06s
INFO | --- Analysis for enakting-mortality took 2.7479116916656494s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 8.20159912109375e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.30262112617492676s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.02082371711730957s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 4.00543212890625e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 4.76837158203125e-06s
INFO | --- Analysis for enakting-nhs took 2.72160267829895s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00077056884765625s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.3168754577636719s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020755290985107422s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.2928924560546875e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 8.821487426757812e-06s
INFO | --- Analysis for enakting-population took 2.7288877964019775s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.5153162479400635s
Availability | VoID file availability check for English Heritage Periods List took 0.0004177093505859375s
Extra | Recovery of all triples for English Heritage Periods List took 0.3763878345489502s
Performance | Total latancy measurement for English Heritage Periods List took 1.53554105758667s
Amount of data | Number of triples check for English Heritage Periods List took 0.4424746036529541s
Versatility | Languages check for English Heritage Periods List took 0.307797908782959s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.49529385566711426s
Security | Check HTTPS for English Heritage Periods List took 0.2641124725341797s
Interpretability | RDF structures check for English Heritage Periods List took 0.29412841796875s
Versatility | Serialization formats check for English Heritage Periods List took 0.4632425308227539s
Availability | RDF dump link check for English Heritage Periods List took 0.287168025970459s
License | MR license check for English Heritage Periods List took 0.413163423538208s
License | HR license check for English Heritage Periods List took 0.3269655704498291s
Amount of data | Number of property check for English Heritage Periods List took 0.3224070072174072s
Understandability | Number of label check for English Heritage Periods List took 0.38764309883117676s
Understandability | URI regex check for English Heritage Periods List took 0.615731954574585s
Understandability | Vocabs check for English Heritage Periods List took 0.3390507698059082s
Verifiability | Authors check for English Heritage Periods List took 0.3650386333465576s
Verifiability | Publishers check for English Heritage Periods List took 0.322662353515625s
Performance | Throughput check for English Heritage Periods List took 12.283833265304565s
Amount of data | Check the number of entities for English Heritage Periods List took 7.009506225585938e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.3783223628997803s
Interlinking | sameAs chians check for English Heritage Periods List took 0.37836408615112305s
Interlinking | skos check for English Heritage Periods List took 0.37386035919189453s
Interlinking | skos check for English Heritage Periods List took 0.34102606773376465s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.44858837127685547s
Currency | Creation date check for English Heritage Periods List took 0.651862621307373s
Currency | Modification date check for English Heritage Periods List took 0.6846060752868652s
Rep.Conc. | URIs length for English Heritage Periods List took 0.7233097553253174s
Interoperability | New vocabularies check for English Heritage Periods List took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.3169281482696533s
Accuracy | Check Functional Property for English Heritage Periods List took 0.36739635467529297s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.3218836784362793s
Consistency | Disjoint class check for English Heritage Periods List took 0.2970621585845947s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.3737778663635254s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.4951722621917725s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00016307830810546875s
Security | Sign check for English Heritage Periods List took 0.360304594039917s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.2855563163757324s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.021236181259155273s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 4.1484832763671875e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Heritage Periods List took 6.4373016357421875e-06s
INFO | --- Analysis for english-heritage-periods-list took 53.8828604221344s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.4137861728668213s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0006117820739746094s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 1.4655187129974365s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 0.8736569881439209s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.42688441276550293s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.4522738456726074s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.3810601234436035s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 30.16977572441101s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.09554243087768555s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.35911011695861816s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.18946385383605957s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 52.402581453323364s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.3108937740325928s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.182637214660645s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.14642834663391113s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.3848116397857666s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.3689267635345459s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.21327543258666992s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.14415740966796875s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.33733034133911133s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 11.901071786880493s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 7.104873657226562e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.12220430374145508s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.2736215591430664s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.255687952041626s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.2056422233581543s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.13965749740600586s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 1.0552852153778076s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.2560245990753174s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 1.515878438949585s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.12572383880615234s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.1980752944946289s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.15130996704101562s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 1.0816519260406494s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 0.6499528884887695s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 1.2065153121948242s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.4543790817260742s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.00015163421630859375s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.3052480220794678s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.1375267505645752s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.3805961608886719s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02278733253479004s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.814697265625e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.430511474609375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 4.291534423828125e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 276.2707061767578s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.13630390167236328s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.00041222572326660156s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 1.2262144088745117s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.7958862781524658s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.6515414714813232s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.3663263320922852s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.871403694152832s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 30.167166233062744s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.13416147232055664s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.16598057746887207s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.2162938117980957s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 48.40613150596619s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.14284396171569824s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.151281118392944s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.19696617126464844s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.14626121520996094s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.3636496067047119s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.14857912063598633s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.20918607711791992s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.13965678215026855s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 12.216293573379517s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 4.9114227294921875e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.14142417907714844s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.1262221336364746s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.12956762313842773s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.13681936264038086s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.14613008499145508s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.4436814785003662s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.1411583423614502s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.8997735977172852s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.19973015785217285s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.14278340339660645s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.1586627960205078s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.15076112747192383s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.44007349014282227s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 1.3915822505950928s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.4219145774841309s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.0001804828643798828s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.2232685089111328s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.14465785026550293s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.3400142192840576s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.021443843841552734s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 4.482269287109375e-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 1.0251998901367188e-05s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 266.41101908683777s
Availability | SPARQL endpoint availability check for English WordNet took 4.315376281738281e-05s
Availability | VoID file availability check for English WordNet took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for English WordNet took 0.39224886894226074s
Reputation | Calculation of the PageRank for English WordNet took 0.021390199661254883s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.337860107421875e-05s
Believability | Calculation of trust value for English WordNet took 2.4080276489257812e-05s
INFO | --- Analysis for english-wordnet took 3.5815823078155518s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.0735616683959961s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.33887410163879395s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.021054744720458984s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 8.797645568847656e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 9.298324584960938e-06s
INFO | --- Analysis for enipedia took 2.8939192295074463s
Availability | SPARQL endpoint availability check for Enslaved.org took 8.440017700195312e-05s
Availability | VoID file availability check for Enslaved.org took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2902565002441406s
Reputation | Calculation of the PageRank for Enslaved.org took 0.02082514762878418s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.7670135498046875e-05s
Believability | Calculation of trust value for Enslaved.org took 1.0728836059570312e-05s
INFO | --- Analysis for enslaved.org took 5.164623260498047s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 5.30817174911499s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.2619471549987793s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.021709680557250977s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.3882598876953125e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 1.2636184692382812e-05s
INFO | --- Analysis for entice-graph took 8.160640478134155s
Availability | SPARQL endpoint availability check for Entrez Gene took 8.797645568847656e-05s
Availability | VoID file availability check for Entrez Gene took 0.0007383823394775391s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.2851240634918213s
Reputation | Calculation of the PageRank for Entrez Gene took 0.020445823669433594s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.4809112548828125e-05s
Believability | Calculation of trust value for Entrez Gene took 1.239776611328125e-05s
INFO | --- Analysis for entrez_gene took 27.514695644378662s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.0496270656585693s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.28061389923095703s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.021491527557373047s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.269050598144531e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 8.58306884765625e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 11.728202819824219s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.32000041007995605s
Availability | VoID file availability check for environment.data.gov.uk took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.3238871097564697s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.021680831909179688s
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.0007164478302001953s
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 1.0013580322265625e-05s
INFO | --- Analysis for environment-data-gov-uk took 9.73073935508728s
Availability | SPARQL endpoint availability check for EARTh took 271.80742835998535s
Availability | VoID file availability check for EARTh took 0.0008285045623779297s
Completeness | Calculation of interlinking completeness for EARTh took 0.29184412956237793s
Reputation | Calculation of the PageRank for EARTh took 0.022255897521972656s
Interlinking | Calculation of Degree of Connection for EARTh took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for EARTh took 9.679794311523438e-05s
Believability | Calculation of trust value for EARTh took 1.1682510375976562e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 569.4570679664612s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.9532270431518555s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.31906747817993164s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.02096271514892578s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 2.8133392333984375e-05s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 1.1444091796875e-05s
INFO | --- Analysis for EO_metadata took 4.256231307983398s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.220008850097656e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.2924044132232666s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.02110433578491211s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 2.765655517578125e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 9.775161743164062e-06s
INFO | --- Analysis for EOKP-Datasets took 3.362919569015503s
Availability | SPARQL endpoint availability check for EPA-CDR took 0.00010156631469726562s
Availability | VoID file availability check for EPA-CDR took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.3020942211151123s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.3855438232421875e-05s
Believability | Calculation of trust value for EPA-CDR took 9.5367431640625e-06s
INFO | --- Analysis for epa-cdr took 7.396513223648071s
Availability | SPARQL endpoint availability check for EPA-FRS took 8.821487426757812e-05s
Availability | VoID file availability check for EPA-FRS took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.3051924705505371s
Reputation | Calculation of the PageRank for EPA-FRS took 0.022138595581054688s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 6.842613220214844e-05s
Believability | Calculation of trust value for EPA-FRS took 9.5367431640625e-06s
INFO | --- Analysis for epa-frs took 6.336092233657837s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.100799560546875e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.2930152416229248s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.02106165885925293s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.528594970703125e-05s
Believability | Calculation of trust value for EPA-RCRA took 8.344650268554688e-06s
INFO | --- Analysis for epa-rcra took 6.162439823150635s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.172325134277344e-05s
Availability | VoID file availability check for EPA-SRS took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.27721357345581055s
Reputation | Calculation of the PageRank for EPA-SRS took 0.021030187606811523s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.271766662597656e-05s
Believability | Calculation of trust value for EPA-SRS took 8.58306884765625e-06s
INFO | --- Analysis for epa-srs took 6.397303581237793s
Availability | SPARQL endpoint availability check for EPA-TRI took 8.511543273925781e-05s
Availability | VoID file availability check for EPA-TRI took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.2851753234863281s
Reputation | Calculation of the PageRank for EPA-TRI took 0.021755456924438477s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.147125244140625e-05s
Believability | Calculation of trust value for EPA-TRI took 8.58306884765625e-06s
INFO | --- Analysis for epa-tri took 6.259967803955078s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.036139488220214844s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.00041866302490234375s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.30541539192199707s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.021149396896362305s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00013208389282226562s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.8237552642822266s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.46387648582458496s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.29736876487731934s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 7.724761962890625e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 1.0251998901367188e-05s
INFO | --- Analysis for eprtr took 3.977862596511841s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.4622063636779785s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0004966259002685547s
Extra | Recovery of all triples for Railway Infrastructure KG took 61.55179786682129s
Performance | Total latancy measurement for Railway Infrastructure KG took 1.3247919082641602s
Amount of data | Number of triples check for Railway Infrastructure KG took 0.2830624580383301s
Interoperability | New terms check for Railway Infrastructure KG took 1.491473913192749s
Versatility | Languages check for Railway Infrastructure KG took 85.42594313621521s
Interpretability | Number of blank nodes check for Railway Infrastructure KG took 0.2486555576324463s
Interpretability | RDF structures check for Railway Infrastructure KG took 0.3664820194244385s
Versatility | Serialization formats check for Railway Infrastructure KG took 0.23860764503479004s
Availability | RDF dump link check for Railway Infrastructure KG took 0.22481870651245117s
License | MR license check for Railway Infrastructure KG took 0.27106571197509766s
License | HR license check for Railway Infrastructure KG took 65.6213686466217s
Amount of data | Number of property check for Railway Infrastructure KG took 0.23620843887329102s
Understandability | Number of label check for Railway Infrastructure KG took 0.49533581733703613s
Understandability | URI regex check for Railway Infrastructure KG took 0.4895188808441162s
Understandability | Vocabs check for Railway Infrastructure KG took 0.25782251358032227s
Verifiability | Authors check for Railway Infrastructure KG took 0.27896595001220703s
Verifiability | Publishers check for Railway Infrastructure KG took 0.2611727714538574s
Performance | Throughput check for Railway Infrastructure KG took 11.15889310836792s
Verifiability | Contribs. check for Railway Infrastructure KG took 0.29704785346984863s
Interlinking | sameAs chians check for Railway Infrastructure KG took 0.23532438278198242s
Interlinking | skos check for Railway Infrastructure KG took 0.2388019561767578s
Interlinking | skos check for Railway Infrastructure KG took 0.2848801612854004s
Timeliness | dataset update frequency check for Railway Infrastructure KG took 0.23508286476135254s
Currency | Creation date check for Railway Infrastructure KG took 0.49361085891723633s
Currency | Modification date check for Railway Infrastructure KG took 0.2482006549835205s
Rep.Conc. | URIs length for Railway Infrastructure KG took 23.35867142677307s
Interoperability | New vocabularies check for Railway Infrastructure KG took 5.884258270263672s
Consistency | Deprecated classes/propertiers check for Railway Infrastructure KG took 0.24869966506958008s
Accuracy | Check Functional Property for Railway Infrastructure KG took 0.2875692844390869s
Accuracy | Check Inverse Functional Property for Railway Infrastructure KG took 0.2696216106414795s
Accuracy | Check Empty annotation labels for Railway Infrastructure KG took 14.336892127990723s
Accuracy | Check White space in annotation for Railway Infrastructure KG took 2.542834997177124s
Accuracy | Check Datatype consistency for Railway Infrastructure KG took 2.6144988536834717s
Consistency | Disjoint class check for Railway Infrastructure KG took 0.2595396041870117s
Consistency | Check Misplaced properties for Railway Infrastructure KG took 1.749802827835083s
Consistency | Misplaced classes for Railway Infrastructure KG took 8.329915761947632s
Consistency | Check Ontology hijacking for Railway Infrastructure KG took 18.782938241958618s
Consistency | Check Invalid usage of undefined classes for Railway Infrastructure KG took 1.3604447841644287s
Consistency | Check Invalid usage of undefined properties for Railway Infrastructure KG took 2.8504598140716553s
Conciseness | Check Extensional conciseness for Railway Infrastructure KG took 2.918529748916626s
Conciseness | Check Intensional conciseness for Railway Infrastructure KG took 0.361724853515625s
Security | Sign check for Railway Infrastructure KG took 0.4425017833709717s
Availability | Check URIs Dereferenciability for Railway Infrastructure KG took 2466.929725408554s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.7089927196502686s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.022600173950195312s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 8.249282836914062e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 0.00010180473327636719s
Interoperability | Check the re-using of existing vocabs for Railway Infrastructure KG took 5.9706199169158936s
Believability | Calculation of trust value for Railway Infrastructure KG took 1.239776611328125e-05s
INFO | --- Analysis for ERAKG took 2908.5940976142883s
Availability | SPARQL endpoint availability check for reg took 8.606910705566406e-05s
Availability | VoID file availability check for reg took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for reg took 0.29887890815734863s
Reputation | Calculation of the PageRank for reg took 0.020871400833129883s
Interlinking | Calculation of Degree of Connection for reg took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for reg took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for reg took 1.1444091796875e-05s
Believability | Calculation of trust value for reg took 1.3828277587890625e-05s
INFO | --- Analysis for erg took 2.730595111846924s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.25002288818359375s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.28031039237976074s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.02048659324645996s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.0279159545898438e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 8.821487426757812e-06s
INFO | --- Analysis for es-msssi-drug-prices took 3.2131187915802s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 4.1484832763671875e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.3166084289550781s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02138996124267578s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 9.012222290039062e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 8.58306884765625e-06s
INFO | --- Analysis for esd-standards took 4.5682597160339355s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.315376281738281e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.2935936450958252s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.021563053131103516s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.176399230957031e-05s
Believability | Calculation of trust value for ESD-Toolkit took 8.344650268554688e-06s
INFO | --- Analysis for esd-toolkit took 3.47941517829895s
Availability | SPARQL endpoint availability check for Dataset Esis took 8.726119995117188e-05s
Availability | VoID file availability check for Dataset Esis took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.31549954414367676s
Reputation | Calculation of the PageRank for Dataset Esis took 0.02085566520690918s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.504753112792969e-05s
Believability | Calculation of trust value for Dataset Esis took 1.0728836059570312e-05s
INFO | --- Analysis for esislearning took 3.1669678688049316s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 5.2928924560546875e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.2867431640625s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020740032196044922s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007305145263671875s
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 9.5367431640625e-06s
INFO | --- Analysis for ESV took 3.884782552719116s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.6811487674713135s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.2873880863189697s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.02214503288269043s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.933906555175781e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.0967254638671875e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.535187005996704s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 7.069097518920898s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.2754983901977539s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.021680831909179688s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.0728836059570312e-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.62939453125e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 1.0013580322265625e-05s
INFO | --- Analysis for eu-agencies-bodies took 19.176360845565796s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 8.463859558105469e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.30864429473876953s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.176399230957031e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 8.58306884765625e-06s
INFO | --- Analysis for eu-institutions took 8.033910989761353s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.1286499500274658s
Availability | VoID file availability check for EU Parliament Media Library took 0.0012631416320800781s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.3086879253387451s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02094125747680664s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.552436828613281e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 8.821487426757812e-06s
INFO | --- Analysis for eu-parliament-media took 9.25947618484497s
Availability | SPARQL endpoint availability check for EU Who Is Who took 1.0900063514709473s
Availability | VoID file availability check for EU Who Is Who took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.27008867263793945s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.02098393440246582s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.5762786865234375e-05s
Believability | Calculation of trust value for EU Who Is Who took 1.1205673217773438e-05s
INFO | --- Analysis for eu-who-is-who took 13.02452301979065s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 1.5005931854248047s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.28920412063598633s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 3.838539123535156e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for eumida-linked-data took 10.884400129318237s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.37381410598754883s
Availability | VoID file availability check for European Nature Information System took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.29343485832214355s
Reputation | Calculation of the PageRank for European Nature Information System took 0.022916316986083984s
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.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010466575622558594s
Believability | Calculation of trust value for European Nature Information System took 9.298324584960938e-06s
INFO | --- Analysis for eunis took 4.516669988632202s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 6.00675630569458s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.29342222213745117s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.152557373046875e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for eur-lex-rdf took 17.548073291778564s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 1.0493850708007812s
Availability | VoID file availability check for Standard Eurobarometer took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.309053897857666s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.022484779357910156s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.1961669921875e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 8.344650268554688e-06s
INFO | --- Analysis for eurobarometer-standard took 11.064573287963867s
Availability | SPARQL endpoint availability check for European Election Results took 1.0726943016052246s
Availability | VoID file availability check for European Election Results took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for European Election Results took 0.30339503288269043s
Reputation | Calculation of the PageRank for European Election Results took 0.021673917770385742s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.600120544433594e-05s
Believability | Calculation of trust value for European Election Results took 7.62939453125e-06s
INFO | --- Analysis for european-election-results took 11.034300088882446s
Availability | SPARQL endpoint availability check for EPO patents took 0.32831239700317383s
Availability | VoID file availability check for EPO patents took 0.00049591064453125s
Extra | Recovery of all triples for EPO patents took 28.24082851409912s
Performance | Total latancy measurement for EPO patents took 1.1936285495758057s
Amount of data | Number of triples check for EPO patents took 90.24038577079773s
Versatility | Languages check for EPO patents took 100.26884841918945s
Interpretability | Number of blank nodes check for EPO patents took 90.27519369125366s
Interpretability | RDF structures check for EPO patents took 0.2641885280609131s
Versatility | Serialization formats check for EPO patents took 0.2691049575805664s
Availability | RDF dump link check for EPO patents took 0.2446424961090088s
License | MR license check for EPO patents took 0.27739787101745605s
License | HR license check for EPO patents took 90.22209906578064s
Amount of data | Number of property check for EPO patents took 0.2166447639465332s
Understandability | Number of label check for EPO patents took 90.21917176246643s
Understandability | URI regex check for EPO patents took 0.5125653743743896s
Understandability | Vocabs check for EPO patents took 0.23431754112243652s
Verifiability | Authors check for EPO patents took 0.3283531665802002s
Verifiability | Publishers check for EPO patents took 0.2568037509918213s
Performance | Throughput check for EPO patents took 11.152197360992432s
Amount of data | Check the number of entities for EPO patents took 7.200241088867188e-05s
Verifiability | Contribs. check for EPO patents took 0.19643855094909668s
Interlinking | sameAs chians check for EPO patents took 0.22704124450683594s
Interlinking | skos check for EPO patents took 0.2302684783935547s
Interlinking | skos check for EPO patents took 0.2505960464477539s
Timeliness | dataset update frequency check for EPO patents took 0.22906184196472168s
Currency | Creation date check for EPO patents took 0.40291261672973633s
Currency | Modification date check for EPO patents took 0.40323805809020996s
Rep.Conc. | URIs length for EPO patents took 131.73917293548584s
Interoperability | New vocabularies check for EPO patents took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.27788615226745605s
Accuracy | Check Empty annotation labels for EPO patents took 17.752543687820435s
Accuracy | Check White space in annotation for EPO patents took 2.9753189086914062s
Accuracy | Check Datatype consistency for EPO patents took 4.82707953453064s
Consistency | Disjoint class check for EPO patents took 0.27276039123535156s
Consistency | Check Misplaced properties for EPO patents took 100.42544651031494s
Consistency | Check Ontology hijacking for EPO patents took 22.910063982009888s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.5307798385620117s
Consistency | Check Invalid usage of undefined properties for EPO patents took 101.47893238067627s
Conciseness | Check Extensional conciseness for EPO patents took 2.8145785331726074s
Conciseness | Check Intensional conciseness for EPO patents took 0.37395596504211426s
Security | Sign check for EPO patents took 0.2460787296295166s
Availability | Check URIs Dereferenciability for EPO patents took 1.776641607284546s
Completeness | Calculation of interlinking completeness for EPO patents took 0.45877909660339355s
Reputation | Calculation of the PageRank for EPO patents took 0.021294832229614258s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for EPO patents took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 1.6689300537109375e-06s
Believability | Calculation of trust value for EPO patents took 7.3909759521484375e-06s
INFO | --- Analysis for European_Patent_Information took 1192.6705164909363s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.2438507080078125e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.00039505958557128906s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.31699156761169434s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.02086162567138672s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.107589721679688e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 7.867813110351562e-06s
INFO | --- Analysis for europeana-lod-v1 took 7.494138479232788s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.46767616271972656s
Availability | VoID file availability check for Europeana SPARQL took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.3018367290496826s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.02084660530090332s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.5789947509765625e-05s
Believability | Calculation of trust value for Europeana SPARQL took 6.67572021484375e-06s
INFO | --- Analysis for europeana-sparql took 6.5764007568359375s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.10022425651550293s
Availability | VoID file availability check for EuroSentiment took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.356121301651001s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02190995216369629s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.838539123535156e-05s
Believability | Calculation of trust value for EuroSentiment took 1.3828277587890625e-05s
INFO | --- Analysis for eurosentiment took 3.643402099609375s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 9.560585021972656e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.3019242286682129s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.02065563201904297s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.700920104980469e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 9.298324584960938e-06s
INFO | --- Analysis for eurostat-rdf took 11.497431755065918s
Availability | SPARQL endpoint availability check for EuroVoc took 0.1620616912841797s
Availability | VoID file availability check for EuroVoc took 0.0004527568817138672s
Extra | Recovery of all triples for EuroVoc took 205.8082251548767s
Performance | Total latancy measurement for EuroVoc took 0.5633561611175537s
Amount of data | Number of triples check for EuroVoc took 56.484545946121216s
Interoperability | New terms check for EuroVoc took 61.55669140815735s
Versatility | Languages check for EuroVoc took 300.0650520324707s
Interpretability | Number of blank nodes check for EuroVoc took 66.0302062034607s
Security | Check HTTPS for EuroVoc took 0.37559032440185547s
Interpretability | RDF structures check for EuroVoc took 0.2598567008972168s
Versatility | Serialization formats check for EuroVoc took 3.436690330505371s
Availability | RDF dump link check for EuroVoc took 0.25417089462280273s
License | MR license check for EuroVoc took 0.5647392272949219s
License | HR license check for EuroVoc took 300.09044194221497s
Amount of data | Number of property check for EuroVoc took 0.22195148468017578s
Understandability | Number of label check for EuroVoc took 1.7012977600097656s
Understandability | URI regex check for EuroVoc took 0.3791050910949707s
Understandability | Vocabs check for EuroVoc took 0.1103980541229248s
Verifiability | Authors check for EuroVoc took 0.23321294784545898s
Verifiability | Publishers check for EuroVoc took 0.22602272033691406s
Performance | Throughput check for EuroVoc took 10.661136627197266s
Amount of data | Check the number of entities for EuroVoc took 7.581710815429688e-05s
Verifiability | Contribs. check for EuroVoc took 0.17705917358398438s
Interlinking | sameAs chians check for EuroVoc took 6.665395736694336s
Interlinking | skos check for EuroVoc took 0.3833954334259033s
Interlinking | skos check for EuroVoc took 0.2940104007720947s
Timeliness | dataset update frequency check for EuroVoc took 0.319185733795166s
Currency | Creation date check for EuroVoc took 0.6492564678192139s
Currency | Modification date check for EuroVoc took 0.34036922454833984s
Rep.Conc. | URIs length for EuroVoc took 427.97010803222656s
Interoperability | New vocabularies check for EuroVoc took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.1892237663269043s
Accuracy | Check Functional Property for EuroVoc took 0.22210931777954102s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.15905141830444336s
Accuracy | Check Empty annotation labels for EuroVoc took 39.163066148757935s
Accuracy | Check White space in annotation for EuroVoc took 3.063847541809082s
Accuracy | Check Datatype consistency for EuroVoc took 2.542952537536621s
Consistency | Disjoint class check for EuroVoc took 0.1793360710144043s
Consistency | Check Misplaced properties for EuroVoc took 300.4335446357727s
Consistency | Misplaced classes for EuroVoc took 8.471762418746948s
Consistency | Check Ontology hijacking for EuroVoc took 36.622209548950195s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.3944387435913086s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.30498027801514s
Conciseness | Check Extensional conciseness for EuroVoc took 2.944936990737915s
Conciseness | Check Intensional conciseness for EuroVoc took 0.34702014923095703s
Security | Sign check for EuroVoc took 0.39434313774108887s
Availability | Check URIs Dereferenciability for EuroVoc took 2.8069961071014404s
Completeness | Calculation of interlinking completeness for EuroVoc took 0.7241272926330566s
Reputation | Calculation of the PageRank for EuroVoc took 0.022507190704345703s
Interlinking | Calculation of Degree of Connection for EuroVoc took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 8.368492126464844e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.6689300537109375e-06s
Believability | Calculation of trust value for EuroVoc took 1.2159347534179688e-05s
INFO | --- Analysis for eurovoc took 15141.349990606308s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 8.344650268554688e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0003857612609863281s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.33281898498535156s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.021044015884399414s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.482269287109375e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 4.76837158203125e-06s
INFO | --- Analysis for euskadi-farmacias took 5.714875936508179s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.9716439247131348s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.27791786193847656s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020865201950073242s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0009169578552246094s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.409385681152344e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 1.33514404296875e-05s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 6.158400297164917s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.2887392044067383s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0008070468902587891s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.29421544075012207s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.021108150482177734s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.581710815429688e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 1.2874603271484375e-05s
INFO | --- Analysis for eutc-productions took 6.6806559562683105s
Availability | SPARQL endpoint availability check for EventMedia took 0.40843725204467773s
Availability | VoID file availability check for EventMedia took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for EventMedia took 0.3123776912689209s
Reputation | Calculation of the PageRank for EventMedia took 0.02120041847229004s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00014328956604003906s
Believability | Calculation of trust value for EventMedia took 1.2874603271484375e-05s
INFO | --- Analysis for event-media took 19.835262775421143s
Availability | SPARQL endpoint availability check for EventKG took 8.463859558105469e-05s
Availability | VoID file availability check for EventKG took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for EventKG took 0.3063218593597412s
Reputation | Calculation of the PageRank for EventKG took 0.023015260696411133s
Interlinking | Calculation of Degree of Connection for EventKG took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.344650268554688e-05s
Believability | Calculation of trust value for EventKG took 9.5367431640625e-06s
INFO | --- Analysis for eventkg took 5.33616304397583s
Availability | SPARQL endpoint availability check for Eventseer took 4.3245320320129395s
Availability | VoID file availability check for Eventseer took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Eventseer took 0.2870948314666748s
Reputation | Calculation of the PageRank for Eventseer took 0.02134561538696289s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.8160552978515625e-05s
Believability | Calculation of trust value for Eventseer took 1.1682510375976562e-05s
INFO | --- Analysis for eventseer took 7.127176284790039s
Availability | SPARQL endpoint availability check for Face Link took 7.271766662597656e-05s
Availability | VoID file availability check for Face Link took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Face Link took 0.2796633243560791s
Reputation | Calculation of the PageRank for Face Link took 0.0206301212310791s
Interlinking | Calculation of Degree of Connection for Face Link took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.314018249511719e-05s
Believability | Calculation of trust value for Face Link took 1.239776611328125e-05s
INFO | --- Analysis for Face_Link took 2.697793483734131s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 60.056124687194824s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.27910327911376953s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.021680116653442383s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.8623809814453125e-05s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.049041748046875e-05s
INFO | --- Analysis for FADN_(2019) took 122.73545980453491s
Availability | SPARQL endpoint availability check for FAMEData took 8.511543273925781e-05s
Availability | VoID file availability check for FAMEData took 0.00031375885009765625s
Completeness | Calculation of interlinking completeness for FAMEData took 0.27942848205566406s
Reputation | Calculation of the PageRank for FAMEData took 0.020582199096679688s
Interlinking | Calculation of Degree of Connection for FAMEData took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FAMEData took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for FAMEData took 2.8848648071289062e-05s
Believability | Calculation of trust value for FAMEData took 5.0067901611328125e-06s
INFO | --- Analysis for famedata took 8.759973049163818s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 8.749961853027344e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.31574583053588867s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.020988941192626953s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.703636169433594e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 9.059906005859375e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 12.460271835327148s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.10929465293884277s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.26283812522888184s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020860671997070312s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010085105895996094s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for fao-linked-data took 2.8647000789642334s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 9.942054748535156e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.3032350540161133s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.021310806274414062s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.075599670410156e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.1682510375976562e-05s
INFO | --- Analysis for FAO_species took 2.6752119064331055s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.573264837265015s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.2916126251220703s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.649162292480469e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.0251998901367188e-05s
INFO | --- Analysis for farmbio-chembl took 66.63280272483826s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.172325134277344e-05s
Availability | VoID file availability check for I4.0-Onto took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.2940351963043213s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.02147984504699707s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.4809112548828125e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.1205673217773438e-05s
INFO | --- Analysis for fatimazahra took 2.722269296646118s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.2438507080078125e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.2966182231903076s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.02065420150756836s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 2.7179718017578125e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.0728836059570312e-05s
INFO | --- Analysis for FHIR_STU3 took 2.9862618446350098s
Availability | SPARQL endpoint availability check for FiESTA took 7.534027099609375e-05s
Availability | VoID file availability check for FiESTA took 0.0004241466522216797s
Completeness | Calculation of interlinking completeness for FiESTA took 0.30361080169677734s
Reputation | Calculation of the PageRank for FiESTA took 0.0203096866607666s
Interlinking | Calculation of Degree of Connection for FiESTA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FiESTA took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.600120544433594e-05s
Believability | Calculation of trust value for FiESTA took 1.1444091796875e-05s
INFO | --- Analysis for fiesta took 12.890484094619751s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 8.559226989746094e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.416840076446533s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02040839195251465s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.86102294921875e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.3113021850585938e-05s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 8.105852127075195s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 0.00010156631469726562s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.28362464904785156s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.021039724349975586s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.271766662597656e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 9.775161743164062e-06s
INFO | --- Analysis for finnish-municipalities took 3.7913873195648193s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 55.493274211883545s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.27597522735595703s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.020969152450561523s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 3.838539123535156e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 58.73290205001831s
Availability | SPARQL endpoint availability check for Fishes of Texas took 8.678436279296875e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.2867279052734375s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.020795583724975586s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.869171142578125e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.239776611328125e-05s
INFO | --- Analysis for fishes-of-texas took 4.521427869796753s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.1484832763671875e-05s
Availability | VoID file availability check for flickr? wrappr took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.33914613723754883s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.021640300750732422s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.441375732421875e-05s
Believability | Calculation of trust value for flickr? wrappr took 9.5367431640625e-06s
INFO | --- Analysis for flickr-wrappr took 3.4987595081329346s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.124641418457031e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.28278589248657227s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.021036624908447266s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0008528232574462891s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.170967102050781e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.0967254638671875e-05s
INFO | --- Analysis for FLUS took 127.61036133766174s
Availability | SPARQL endpoint availability check for Flybase took 3.577547311782837s
Availability | VoID file availability check for Flybase took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Flybase took 0.31646227836608887s
Reputation | Calculation of the PageRank for Flybase took 0.02082204818725586s
Interlinking | Calculation of Degree of Connection for Flybase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.6716461181640625e-05s
Believability | Calculation of trust value for Flybase took 1.0728836059570312e-05s
INFO | --- Analysis for flybase took 9.023153066635132s
Availability | SPARQL endpoint availability check for Flyted took 0.912527322769165s
Availability | VoID file availability check for Flyted took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Flyted took 0.3035857677459717s
Reputation | Calculation of the PageRank for Flyted took 0.02079916000366211s
Interlinking | Calculation of Degree of Connection for Flyted took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.314018249511719e-05s
Believability | Calculation of trust value for Flyted took 1.1920928955078125e-05s
INFO | --- Analysis for flyted took 5.911709785461426s
Availability | SPARQL endpoint availability check for Foodista took 1.4391560554504395s
Availability | VoID file availability check for Foodista took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for Foodista took 0.29233598709106445s
Reputation | Calculation of the PageRank for Foodista took 0.020624876022338867s
Interlinking | Calculation of Degree of Connection for Foodista took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Foodista took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Foodista took 2.9325485229492188e-05s
Believability | Calculation of trust value for Foodista took 1.1205673217773438e-05s
INFO | --- Analysis for foodista took 9.07251238822937s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.1782073974609375s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2764308452606201s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0208284854888916s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.319450378417969e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1444091796875e-05s
INFO | --- Analysis for foodpedia took 2.819075584411621s
Availability | SPARQL endpoint availability check for FrameBase schema took 8.749961853027344e-05s
Availability | VoID file availability check for FrameBase schema took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.2982215881347656s
Reputation | Calculation of the PageRank for FrameBase schema took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.38690185546875e-05s
Believability | Calculation of trust value for FrameBase schema took 1.2159347534179688e-05s
INFO | --- Analysis for framebase-schema took 8.164501428604126s
Availability | SPARQL endpoint availability check for Framester took 8.559226989746094e-05s
Availability | VoID file availability check for Framester took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for Framester took 0.3085319995880127s
Reputation | Calculation of the PageRank for Framester took 0.021434783935546875s
Interlinking | Calculation of Degree of Connection for Framester took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Framester took 7.390975952148438e-05s
Believability | Calculation of trust value for Framester took 1.2874603271484375e-05s
INFO | --- Analysis for framester took 4.131554126739502s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.05974864959716797s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2879214286804199s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.021591663360595703s
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.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.559226989746094e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 1.3828277587890625e-05s
INFO | --- Analysis for frb-linked-data took 2.8030858039855957s
Availability | SPARQL endpoint availability check for 1989shack Inc. E-Commerce  took 9.393692016601562e-05s
Availability | VoID file availability check for 1989shack Inc. E-Commerce  took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for 1989shack Inc. E-Commerce  took 0.27350354194641113s
Reputation | Calculation of the PageRank for 1989shack Inc. E-Commerce  took 0.020782947540283203s
Interlinking | Calculation of Degree of Connection for 1989shack Inc. E-Commerce  took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 1989shack Inc. E-Commerce  took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for 1989shack Inc. E-Commerce  took 0.0002689361572265625s
Believability | Calculation of trust value for 1989shack Inc. E-Commerce  took 1.0251998901367188e-05s
INFO | --- Analysis for freebase took 4.01875376701355s
Availability | SPARQL endpoint availability check for Freeyork took 9.942054748535156e-05s
Availability | VoID file availability check for Freeyork took 0.0010101795196533203s
Completeness | Calculation of interlinking completeness for Freeyork took 0.3089566230773926s
Reputation | Calculation of the PageRank for Freeyork took 0.02090001106262207s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.0001068115234375s
Believability | Calculation of trust value for Freeyork took 1.1682510375976562e-05s
INFO | --- Analysis for freeyork-org took 3.2283291816711426s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7249274253845215s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.2676661014556885s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.343292236328125e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 9.5367431640625e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.492995977401733s
Availability | SPARQL endpoint availability check for DailyMed took 0.667872428894043s
Availability | VoID file availability check for DailyMed took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for DailyMed took 0.35947299003601074s
Reputation | Calculation of the PageRank for DailyMed took 0.02066516876220703s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.560585021972656e-05s
Believability | Calculation of trust value for DailyMed took 1.1205673217773438e-05s
INFO | --- Analysis for fu-berlin-dailymed took 5.8155083656311035s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.7012653350830078s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.31021833419799805s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.416175842285156e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.1205673217773438e-05s
INFO | --- Analysis for fu-berlin-dblp took 4.577934503555298s
Availability | SPARQL endpoint availability check for Diseasome took 0.6653087139129639s
Availability | VoID file availability check for Diseasome took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Diseasome took 0.2882242202758789s
Reputation | Calculation of the PageRank for Diseasome took 0.020962953567504883s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.000110626220703125s
Believability | Calculation of trust value for Diseasome took 1.1682510375976562e-05s
INFO | --- Analysis for fu-berlin-diseasome took 5.670061826705933s
Availability | SPARQL endpoint availability check for DrugBank took 0.6634063720703125s
Availability | VoID file availability check for DrugBank took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for DrugBank took 0.30841994285583496s
Reputation | Calculation of the PageRank for DrugBank took 0.020896196365356445s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011706352233886719s
Believability | Calculation of trust value for DrugBank took 1.0967254638671875e-05s
INFO | --- Analysis for fu-berlin-drugbank took 5.634826898574829s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.6608784198760986s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.2975192070007324s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.00070953369140625s
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.0967254638671875e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 4.517014503479004s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.6753907203674316s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.2755873203277588s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.0203707218170166s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007281303405761719s
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.106231689453125e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.545299530029297s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.6903185844421387s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.2779209613800049s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.021297931671142578s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.2479248046875e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 1.0013580322265625e-05s
INFO | --- Analysis for fu-berlin-eures took 4.602701902389526s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.6701657772064209s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2934236526489258s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.02042078971862793s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.632110595703125e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 8.821487426757812e-06s
INFO | --- Analysis for fu-berlin-eurostat took 7.781934499740601s
Availability | SPARQL endpoint availability check for MediCare took 0.679978609085083s
Availability | VoID file availability check for MediCare took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for MediCare took 0.374600887298584s
Reputation | Calculation of the PageRank for MediCare took 0.02057051658630371s
Interlinking | Calculation of Degree of Connection for MediCare took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.2438507080078125e-05s
Believability | Calculation of trust value for MediCare took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-medicare took 5.2229015827178955s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.6956133842468262s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.3166844844818115s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020554780960083008s
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.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 6.961822509765625e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 6.198883056640625e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.548139333724976s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.6769182682037354s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.3252749443054199s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.022296428680419922s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.274482727050781e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.049041748046875e-05s
INFO | --- Analysis for fu-berlin-sider took 5.112698793411255s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.6825168132781982s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.3046267032623291s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.414817810058594e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.0251998901367188e-05s
INFO | --- Analysis for fu-berlin-stitch took 4.604556322097778s
Availability | SPARQL endpoint availability check for fvdb took 8.869171142578125e-05s
Availability | VoID file availability check for fvdb took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for fvdb took 0.28625941276550293s
Reputation | Calculation of the PageRank for fvdb took 0.02095770835876465s
Interlinking | Calculation of Degree of Connection for fvdb took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.075599670410156e-05s
Believability | Calculation of trust value for fvdb took 9.775161743164062e-06s
INFO | --- Analysis for fv took 12.788305521011353s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 8.821487426757812e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.3167123794555664s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.020839691162109375s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.0994415283203125e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 1.0013580322265625e-05s
INFO | --- Analysis for GACS took 3.2508087158203125s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 8.893013000488281e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.2730062007904053s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020847320556640625s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.029273986816406e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.770249605178833s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 8.678436279296875e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.306610107421875s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.021229028701782227s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 9.989738464355469e-05s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.0013580322265625e-05s
INFO | --- Analysis for garnicaplywood took 4.041372537612915s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 5.4836273193359375e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0011019706726074219s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.3296971321105957s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.02101278305053711s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.584426879882812e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.33514404296875e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 8.031849384307861s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.4090540409088135s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.3137214183807373s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020624876022338867s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 0.00011348724365234375s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.0967254638671875e-05s
INFO | --- Analysis for gemet took 5.462188482284546s
Availability | SPARQL endpoint availability check for gemet-annotated took 8.869171142578125e-05s
Availability | VoID file availability check for gemet-annotated took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.299396276473999s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020945310592651367s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.6716461181640625e-05s
Believability | Calculation of trust value for gemet-annotated took 1.049041748046875e-05s
INFO | --- Analysis for gemet-annotated took 3.282097339630127s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.6985838413238525s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.2887704372406006s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.021320819854736328s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 4.0531158447265625e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.2636184692382812e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.548031330108643s
Availability | SPARQL endpoint availability check for Super Ontology took 0.8045322895050049s
Availability | VoID file availability check for Super Ontology took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.32366085052490234s
Reputation | Calculation of the PageRank for Super Ontology took 0.02194380760192871s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for Super Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for Generalized_Super_Ontology took 4.046853303909302s
Availability | SPARQL endpoint availability check for Geographic detector model took 4.100799560546875e-05s
Availability | VoID file availability check for Geographic detector model took 0.0006833076477050781s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.3063340187072754s
Reputation | Calculation of the PageRank for Geographic detector model took 0.021869659423828125s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.24249267578125e-05s
Believability | Calculation of trust value for Geographic detector model took 1.049041748046875e-05s
INFO | --- Analysis for GeoDetector took 19.10183310508728s
Availability | SPARQL endpoint availability check for geodomainwn took 4.100799560546875e-05s
Availability | VoID file availability check for geodomainwn took 0.0004029273986816406s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.282825231552124s
Reputation | Calculation of the PageRank for geodomainwn took 0.020968914031982422s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.792213439941406e-05s
Believability | Calculation of trust value for geodomainwn took 1.0013580322265625e-05s
INFO | --- Analysis for geodomainwn took 6.951826095581055s
Availability | SPARQL endpoint availability check for GeoEcuador took 7.700920104980469e-05s
Availability | VoID file availability check for GeoEcuador took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.29433250427246094s
Reputation | Calculation of the PageRank for GeoEcuador took 0.021148681640625s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.985664367675781e-05s
Believability | Calculation of trust value for GeoEcuador took 7.152557373046875e-06s
INFO | --- Analysis for geoecuador took 12.909824132919312s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.2194664478302s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0007913112640380859s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.28565239906311035s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.020806312561035156s
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.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.508827209472656e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.1682510375976562e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 49.511902809143066s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.4801647663116455s
Availability | VoID file availability check for GeoLinkedData took 0.0009810924530029297s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.31957411766052246s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.021266937255859375s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.797645568847656e-05s
Believability | Calculation of trust value for GeoLinkedData took 9.059906005859375e-06s
INFO | --- Analysis for geolinkeddata took 4.246278762817383s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.21173501014709473s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0005803108215332031s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 8.678753852844238s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.39618587493896484s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.16243386268615723s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.3377399444580078s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.2301630973815918s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.16272521018981934s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.1791236400604248s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.09718823432922363s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.1121523380279541s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.06865239143371582s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.11285066604614258s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.8713617324829102s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.11255526542663574s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.11975502967834473s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.13831782341003418s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.10383915901184082s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.07152843475341797s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.10874462127685547s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.353286981582642s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 7.081031799316406e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.07745504379272461s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.05849647521972656s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.0963282585144043s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.06997442245483398s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.06194496154785156s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1746366024017334s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1643691062927246s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.3359670639038086s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 1.9148082733154297s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.10298967361450195s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06877279281616211s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06877827644348145s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.2955434322357178s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.0073986053466796875s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.23264718055725098s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.06935501098632812s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.2137737274169922s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5264248847961426s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 2.979818820953369s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.3739314079284668s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.5466158390045166s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.17574238777160645s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.06814336776733398s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.0859758853912354s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.33861231803894043s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020956993103027344s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.821487426757812e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 1.4933350086212158s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 1.2874603271484375e-05s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 55.465288400650024s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.267692565917969e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.2866952419281006s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.02269577980041504s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0005142688751220703s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.0251998901367188e-05s
INFO | --- Analysis for geonames-semantic-web took 3.679143190383911s
Availability | SPARQL endpoint availability check for Geospatial World  took 4.124641418457031e-05s
Availability | VoID file availability check for Geospatial World  took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.28160929679870605s
Reputation | Calculation of the PageRank for Geospatial World  took 0.022089481353759766s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010323524475097656s
Believability | Calculation of trust value for Geospatial World  took 1.0251998901367188e-05s
INFO | --- Analysis for geospatialworld-net took 3.1363630294799805s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5814063549041748s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.28241467475891113s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.0001327991485595703s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 9.298324584960938e-06s
INFO | --- Analysis for geospecies took 6.1465675830841064s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.076957702636719e-05s
Availability | VoID file availability check for GeoWordNet took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.2864048480987549s
Reputation | Calculation of the PageRank for GeoWordNet took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 4.76837158203125e-05s
Believability | Calculation of trust value for GeoWordNet took 1.1444091796875e-05s
INFO | --- Analysis for geowordnet took 8.189420938491821s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.08266329765319824s
Availability | VoID file availability check for German labor law thesaurus took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.3314056396484375s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.02097916603088379s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 7.963180541992188e-05s
Believability | Calculation of trust value for German labor law thesaurus took 1.0013580322265625e-05s
INFO | --- Analysis for german-labor-law-thesaurus took 3.742981195449829s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 8.940696716308594e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.28897953033447266s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.020925521850585938s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.172325134277344e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.239776611328125e-05s
INFO | --- Analysis for germlex took 3.1330668926239014s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.4471888542175293s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2227916717529297s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2792031764984131s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.021707773208618164s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.131431579589844e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.239776611328125e-05s
INFO | --- Analysis for gesis-thesoz took 7.502480983734131s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.760451078414917s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.2896156311035156s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.020794153213500977s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.62939453125e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 1.1444091796875e-05s
INFO | --- Analysis for getty-aat took 16.57143211364746s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.3209123611450195s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0007317066192626953s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.2876300811767578s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.078315734863281e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.0013580322265625e-05s
INFO | --- Analysis for getty-tgn took 14.02344012260437s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 7.098538637161255s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.329373836517334s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 2.8133392333984375e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 9.059906005859375e-06s
INFO | --- Analysis for gipuzkoademografia took 30.986088275909424s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 0.00010538101196289062s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.32967448234558105s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.020628929138183594s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.147125244140625e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 1.0251998901367188e-05s
INFO | --- Analysis for glastonbury-2011 took 5.616117238998413s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.6253204345703125e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.29528260231018066s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.02162337303161621s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 5.030632019042969e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 6.842613220214844e-05s
INFO | --- Analysis for global-hunger-index-2011 took 3.410601854324341s
Availability | SPARQL endpoint availability check for Glottolog took 8.535385131835938e-05s
Availability | VoID file availability check for Glottolog took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2960965633392334s
Reputation | Calculation of the PageRank for Glottolog took 0.020772218704223633s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.745887756347656e-05s
Believability | Calculation of trust value for Glottolog took 1.0251998901367188e-05s
INFO | --- Analysis for glottolog took 6.616647481918335s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 8.654594421386719e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.3156163692474365s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020524024963378906s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010585784912109375s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.2159347534179688e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 100.79137086868286s
Availability | SPARQL endpoint availability check for 1121 took 8.511543273925781e-05s
Availability | VoID file availability check for 1121 took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for 1121 took 0.2892444133758545s
Reputation | Calculation of the PageRank for 1121 took 0.020953893661499023s
Interlinking | Calculation of Degree of Connection for 1121 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.075599670410156e-05s
Believability | Calculation of trust value for 1121 took 1.0013580322265625e-05s
INFO | --- Analysis for God_ took 3.5484373569488525s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 8.7738037109375e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.291384220123291s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020793914794921875s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.125999450683594e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.0967254638671875e-05s
INFO | --- Analysis for gold took 4.384580135345459s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 0.0001461505889892578s
Availability | VoID file availability check for GoogleArt wrapper took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.26762819290161133s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.67572021484375e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 1.0251998901367188e-05s
INFO | --- Analysis for googleart-wrapper took 3.026216983795166s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.09932875633239746s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.2776961326599121s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.02161574363708496s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.52587890625e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0010797977447509766s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 5.030632019042969e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.1920928955078125e-05s
INFO | --- Analysis for govagribus-denmark took 35.12343502044678s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.4550068378448486s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.31336522102355957s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.021925687789916992s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 9.584426879882812e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 24.195695877075195s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.5970277786254883s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0007500648498535156s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.28956103324890137s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.022728919982910156s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.988380432128906e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 9.5367431640625e-06s
INFO | --- Analysis for govtrack took 10.625645637512207s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.1961669921875e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.2983086109161377s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.02218461036682129s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 5.745887756347656e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.4543533325195312e-05s
INFO | --- Analysis for greek-administrative-geography took 2.8448054790496826s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.20733261108398438s
Availability | VoID file availability check for Greek Wordnet took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.28054308891296387s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.022272825241088867s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.172325134277344e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.0251998901367188e-05s
INFO | --- Analysis for greek-wordnet took 2.959306240081787s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.26952409744262695s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007076263427734375s
Extra | Recovery of all triples for Greek prisons releases Jan 2018 - Dec 2023 took 18.006251096725464s
Performance | Total latancy measurement for Greek prisons releases Jan 2018 - Dec 2023 took 0.6329741477966309s
Amount of data | Number of triples check for Greek prisons releases Jan 2018 - Dec 2023 took 0.6725294589996338s
Interoperability | New terms check for Greek prisons releases Jan 2018 - Dec 2023 took 1.5791175365447998s
Versatility | Languages check for Greek prisons releases Jan 2018 - Dec 2023 took 1.80653715133667s
Interpretability | Number of blank nodes check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5338685512542725s
Interpretability | RDF structures check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13618254661560059s
Versatility | Serialization formats check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12113738059997559s
Availability | RDF dump link check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12739920616149902s
License | MR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13457036018371582s
License | HR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.4827582836151123s
Amount of data | Number of property check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13061785697937012s
Understandability | Number of label check for Greek prisons releases Jan 2018 - Dec 2023 took 0.20163393020629883s
Understandability | URI regex check for Greek prisons releases Jan 2018 - Dec 2023 took 0.25452136993408203s
Understandability | Vocabs check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1266648769378662s
Verifiability | Authors check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12181472778320312s
Verifiability | Publishers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11759138107299805s
Performance | Throughput check for Greek prisons releases Jan 2018 - Dec 2023 took 10.817461729049683s
Amount of data | Check the number of entities for Greek prisons releases Jan 2018 - Dec 2023 took 0.00010776519775390625s
Verifiability | Contribs. check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13082098960876465s
Interlinking | sameAs chians check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13174176216125488s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13017010688781738s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12970328330993652s
Timeliness | dataset update frequency check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13038301467895508s
Currency | Creation date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.25058484077453613s
Currency | Modification date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.24617266654968262s
Rep.Conc. | URIs length for Greek prisons releases Jan 2018 - Dec 2023 took 7.598609924316406s
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.13569927215576172s
Accuracy | Check Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.12893223762512207s
Accuracy | Check Inverse Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.11980986595153809s
Accuracy | Check Empty annotation labels for Greek prisons releases Jan 2018 - Dec 2023 took 2.2874886989593506s
Accuracy | Check White space in annotation for Greek prisons releases Jan 2018 - Dec 2023 took 0.2877662181854248s
Accuracy | Check Datatype consistency for Greek prisons releases Jan 2018 - Dec 2023 took 4.720912933349609s
Consistency | Disjoint class check for Greek prisons releases Jan 2018 - Dec 2023 took 0.14067649841308594s
Consistency | Check Misplaced properties for Greek prisons releases Jan 2018 - Dec 2023 took 1.1846132278442383s
Consistency | Check Ontology hijacking for Greek prisons releases Jan 2018 - Dec 2023 took 2.932886838912964s
Consistency | Check Invalid usage of undefined classes for Greek prisons releases Jan 2018 - Dec 2023 took 1.2874476909637451s
Consistency | Check Invalid usage of undefined properties for Greek prisons releases Jan 2018 - Dec 2023 took 2.4348714351654053s
Conciseness | Check Extensional conciseness for Greek prisons releases Jan 2018 - Dec 2023 took 2.872164011001587s
Security | Sign check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12046122550964355s
Availability | Check URIs Dereferenciability for Greek prisons releases Jan 2018 - Dec 2023 took 4874.446477174759s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.6845252513885498s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.021134376525878906s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 2.4080276489257812e-05s
Interoperability | Check the re-using of existing vocabs for Greek prisons releases Jan 2018 - Dec 2023 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 1.0013580322265625e-05s
INFO | --- Analysis for greek_prisons_releases took 4961.05145406723s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.7977504730224609s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2878997325897217s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020395755767822266s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.796287536621094e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 9.775161743164062e-06s
INFO | --- Analysis for greekchildrensartmuseum took 4.720468521118164s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.887580871582031e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0007574558258056641s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.2906064987182617s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.02182292938232422s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 9.989738464355469e-05s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.0967254638671875e-05s
INFO | --- Analysis for green-competitiveness-gnoss took 9.061142921447754s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.374981164932251s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.2939121723175049s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.021177053451538086s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 5.030632019042969e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 1.3113021850585938e-05s
INFO | --- Analysis for grrp took 3.2745304107666016s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.24833989143371582s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.31632518768310547s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.02232050895690918s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 7.05718994140625e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 9.775161743164062e-06s
INFO | --- Analysis for grrt took 2.956655502319336s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.1727120876312256s
Availability | VoID file availability check for Geological Timescale took 0.0007388591766357422s
Extra | Recovery of all triples for Geological Timescale took 2.3045079708099365s
Performance | Total latancy measurement for Geological Timescale took 3.164137363433838s
Amount of data | Number of triples check for Geological Timescale took 1.0331356525421143s
Interoperability | New terms check for Geological Timescale took 2.147235870361328s
Versatility | Languages check for Geological Timescale took 2.150883674621582s
Interpretability | Number of blank nodes check for Geological Timescale took 0.4739968776702881s
Security | Check HTTPS for Geological Timescale took 1.0125393867492676s
Interpretability | RDF structures check for Geological Timescale took 1.0027918815612793s
Versatility | Serialization formats check for Geological Timescale took 0.4027414321899414s
Availability | RDF dump link check for Geological Timescale took 1.2156956195831299s
License | MR license check for Geological Timescale took 0.42647790908813477s
License | HR license check for Geological Timescale took 0.4395740032196045s
Amount of data | Number of property check for Geological Timescale took 0.40346598625183105s
Understandability | Number of label check for Geological Timescale took 0.4646153450012207s
Understandability | URI regex check for Geological Timescale took 1.8998870849609375s
Understandability | Vocabs check for Geological Timescale took 0.40227651596069336s
Verifiability | Authors check for Geological Timescale took 0.4287748336791992s
Verifiability | Publishers check for Geological Timescale took 0.9641180038452148s
Performance | Throughput check for Geological Timescale took 18.33685874938965s
Amount of data | Check the number of entities for Geological Timescale took 0.020671367645263672s
Verifiability | Contribs. check for Geological Timescale took 0.9801392555236816s
Interlinking | sameAs chians check for Geological Timescale took 0.9720404148101807s
Interlinking | skos check for Geological Timescale took 0.9303743839263916s
Interlinking | skos check for Geological Timescale took 0.9531404972076416s
Timeliness | dataset update frequency check for Geological Timescale took 0.4755547046661377s
Currency | Creation date check for Geological Timescale took 0.8447866439819336s
Currency | Modification date check for Geological Timescale took 0.9794933795928955s
Rep.Conc. | URIs length for Geological Timescale took 2.083247661590576s
Interoperability | New vocabularies check for Geological Timescale took 2.0440430641174316s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 4.001389503479004s
Accuracy | Check Functional Property for Geological Timescale took 1.6132712364196777s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.9370591640472412s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.318922996520996s
Accuracy | Check White space in annotation for Geological Timescale took 0.015366792678833008s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07293152809143066s
Consistency | Disjoint class check for Geological Timescale took 0.40281176567077637s
Consistency | Check Misplaced properties for Geological Timescale took 1.9345967769622803s
Consistency | Misplaced classes for Geological Timescale took 0.49571657180786133s
Consistency | Check Ontology hijacking for Geological Timescale took 1.5716209411621094s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.1512494087219238s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.149444341659546s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.054860591888427734s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.450023889541626s
Security | Sign check for Geological Timescale took 0.4414703845977783s
Availability | Check URIs Dereferenciability for Geological Timescale took 3.469078302383423s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.31581664085388184s
Reputation | Calculation of the PageRank for Geological Timescale took 0.020735979080200195s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 8.940696716308594e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 1.7201523780822754s
Believability | Calculation of trust value for Geological Timescale took 7.62939453125e-06s
INFO | --- Analysis for GTS took 121.65762686729431s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.2994697093963623s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.022476673126220703s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.886222839355469e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for GTS-ont took 2.875701904296875s
Availability | SPARQL endpoint availability check for GUTSTOK  took 9.632110595703125e-05s
Availability | VoID file availability check for GUTSTOK  took 0.000518798828125s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.3226354122161865s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.02128458023071289s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.0279159545898438e-05s
Believability | Calculation of trust value for GUTSTOK  took 1.2874603271484375e-05s
INFO | --- Analysis for Guillaume_Forget took 2.5864672660827637s
Availability | SPARQL endpoint availability check for Project Gutenberg took 8.392333984375e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.2763173580169678s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 7.200241088867188e-05s
Believability | Calculation of trust value for Project Gutenberg took 1.239776611328125e-05s
INFO | --- Analysis for gutenberg took 16.12139081954956s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 8.821487426757812e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0008227825164794922s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.30760741233825684s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.02078700065612793s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.4809112548828125e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.0967254638671875e-05s
INFO | --- Analysis for gwa-ili took 5.942046403884888s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 8.630752563476562e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.33484888076782227s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.022214889526367188s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 4.458427429199219e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 1.3113021850585938e-05s
INFO | --- Analysis for GWR took 19.39414381980896s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 8.559226989746094e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.26734352111816406s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.02072930335998535s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.075599670410156e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 1.2159347534179688e-05s
INFO | --- Analysis for HASM took 20.690305709838867s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 3.7173819541931152s
Availability | VoID file availability check for HealthCare Ontology took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.394665002822876s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.021028518676757812s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.5762786865234375e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.239776611328125e-05s
INFO | --- Analysis for HealthCare_Ontology took 7.021685838699341s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 0.000102996826171875s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.3268239498138428s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.021920204162597656s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.175041198730469e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 1.430511474609375e-05s
INFO | --- Analysis for heartfailure took 3.098052501678467s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.4751238822937s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0008761882781982422s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.4167020320892334s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.022086620330810547s
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.049041748046875e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 4.696846008300781e-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.1920928955078125e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 119.21541285514832s
Availability | SPARQL endpoint availability check for Hedatuz took 0.25863146781921387s
Availability | VoID file availability check for Hedatuz took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.33432579040527344s
Reputation | Calculation of the PageRank for Hedatuz took 0.021246910095214844s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 4.00543212890625e-05s
Believability | Calculation of trust value for Hedatuz took 1.2636184692382812e-05s
INFO | --- Analysis for hedatuz took 3.2706832885742188s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.11066174507141113s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.28641271591186523s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.02089715003967285s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.0001266002655029297s
Believability | Calculation of trust value for Hellenic Fire Brigade took 8.344650268554688e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.915471315383911s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.025281667709350586s
Availability | VoID file availability check for Hellenic Police took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.2966933250427246s
Reputation | Calculation of the PageRank for Hellenic Police took 0.02113175392150879s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.0001323223114013672s
Believability | Calculation of trust value for Hellenic Police took 9.775161743164062e-06s
INFO | --- Analysis for hellenic-police took 2.818053722381592s
Availability | SPARQL endpoint availability check for Hermos took 8.749961853027344e-05s
Availability | VoID file availability check for Hermos took 0.0006430149078369141s
Completeness | Calculation of interlinking completeness for Hermos took 0.29533934593200684s
Reputation | Calculation of the PageRank for Hermos took 0.02086162567138672s
Interlinking | Calculation of Degree of Connection for Hermos took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Hermos took 3.0994415283203125e-05s
Believability | Calculation of trust value for Hermos took 1.2159347534179688e-05s
INFO | --- Analysis for Hermos took 3.233624219894409s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.38690185546875e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.2746570110321045s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.021277904510498047s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 2.9802322387695312e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 1.2636184692382812e-05s
INFO | --- Analysis for Himanshu_Mahawar took 2.6463735103607178s
Availability | SPARQL endpoint availability check for HITO took 0.4201970100402832s
Availability | VoID file availability check for HITO took 0.0012850761413574219s
Extra | Recovery of all triples for HITO took 0.20944595336914062s
Performance | Total latancy measurement for HITO took 0.9880948066711426s
Amount of data | Number of triples check for HITO took 0.2177581787109375s
Interoperability | New terms check for HITO took 1.378164529800415s
Versatility | Languages check for HITO took 0.25127506256103516s
Interpretability | Number of blank nodes check for HITO took 0.20931267738342285s
Interpretability | RDF structures check for HITO took 0.2201387882232666s
Versatility | Serialization formats check for HITO took 0.19514799118041992s
Availability | RDF dump link check for HITO took 0.1965186595916748s
License | MR license check for HITO took 0.21877694129943848s
License | HR license check for HITO took 0.2377150058746338s
Amount of data | Number of property check for HITO took 0.18898987770080566s
Understandability | Number of label check for HITO took 0.22095179557800293s
Understandability | URI regex check for HITO took 0.3939077854156494s
Understandability | Vocabs check for HITO took 0.18625140190124512s
Verifiability | Authors check for HITO took 0.19269824028015137s
Verifiability | Publishers check for HITO took 0.2001204490661621s
Performance | Throughput check for HITO took 11.21791958808899s
Amount of data | Check the number of entities for HITO took 6.628036499023438e-05s
Verifiability | Contribs. check for HITO took 0.20089221000671387s
Interlinking | sameAs chians check for HITO took 0.19604921340942383s
Interlinking | skos check for HITO took 0.22440314292907715s
Interlinking | skos check for HITO took 0.19892144203186035s
Timeliness | dataset update frequency check for HITO took 0.2112572193145752s
Currency | Creation date check for HITO took 0.4029703140258789s
Currency | Modification date check for HITO took 0.41354966163635254s
Rep.Conc. | URIs length for HITO took 0.9903128147125244s
Interoperability | New vocabularies check for HITO took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.20871806144714355s
Accuracy | Check Functional Property for HITO took 0.19678139686584473s
Accuracy | Check Inverse Functional Property for HITO took 0.18609309196472168s
Accuracy | Check Empty annotation labels for HITO took 0.49777650833129883s
Accuracy | Check White space in annotation for HITO took 0.013375282287597656s
Consistency | Disjoint class check for HITO took 0.19629764556884766s
Consistency | Check Misplaced properties for HITO took 0.5504188537597656s
Consistency | Misplaced classes for HITO took 0.1861860752105713s
Consistency | Check Ontology hijacking for HITO took 1.6278634071350098s
Consistency | Check Invalid usage of undefined properties for HITO took 1.4230611324310303s
Conciseness | Check Extensional conciseness for HITO took 0.00014066696166992188s
Conciseness | Check Intensional conciseness for HITO took 0.19571495056152344s
Security | Sign check for HITO took 0.2005627155303955s
Availability | Check URIs Dereferenciability for HITO took 1705.2429418563843s
Completeness | Calculation of interlinking completeness for HITO took 0.5372593402862549s
Reputation | Calculation of the PageRank for HITO took 0.023244619369506836s
Interlinking | Calculation of Degree of Connection for HITO took 6.842613220214844e-05s
Interlinking | Calculation of Centrality for HITO took 0.0008649826049804688s
Interlinking | Calculation of Clustering coefficient for HITO took 0.00010752677917480469s
Interoperability | Check the re-using of existing vocabs for HITO took 1.9073486328125e-06s
Believability | Calculation of trust value for HITO took 9.775161743164062e-06s
INFO | --- Analysis for hito took 1754.5686030387878s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 15.79970121383667s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.3216431140899658s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.02179741859436035s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 3.647804260253906e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 1.1920928955078125e-05s
INFO | --- Analysis for Hoa_Thinh_Phat took 51.580561876297s
Availability | SPARQL endpoint availability check for gseg took 8.940696716308594e-05s
Availability | VoID file availability check for gseg took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for gseg took 0.3012526035308838s
Reputation | Calculation of the PageRank for gseg took 0.023023605346679688s
Interlinking | Calculation of Degree of Connection for gseg took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for gseg took 3.0517578125e-05s
Believability | Calculation of trust value for gseg took 1.1444091796875e-05s
INFO | --- Analysis for hongse took 3.247291326522827s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 3.936922311782837s
Availability | VoID file availability check for COURAGE Dataset took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.3230304718017578s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.0211942195892334s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.5762786865234375e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 7.963627576828003s
Availability | SPARQL endpoint availability check for RoadTrb took 4.553794860839844e-05s
Availability | VoID file availability check for RoadTrb took 0.0004203319549560547s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.33190131187438965s
Reputation | Calculation of the PageRank for RoadTrb took 0.020864009857177734s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.075599670410156e-05s
Believability | Calculation of trust value for RoadTrb took 5.9604644775390625e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.695578098297119s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.3297700881958008s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.021031856536865234s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.1444091796875e-05s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 38.40135741233826s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 4.1961669921875e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.33936595916748047s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.022855043411254883s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.504753112792969e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.1920928955078125e-05s
INFO | --- Analysis for http:pakistan.com took 2.720231056213379s
Availability | SPARQL endpoint availability check for CEDICT took 8.535385131835938e-05s
Availability | VoID file availability check for CEDICT took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for CEDICT took 0.38896727561950684s
Reputation | Calculation of the PageRank for CEDICT took 0.02086186408996582s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for CEDICT took 2.9802322387695312e-05s
Believability | Calculation of trust value for CEDICT took 1.1205673217773438e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.336827993392944s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.507521629333496s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.26802515983581543s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02204442024230957s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.699562072753906e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.2159347534179688e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 5.05683970451355s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 0.0001068115234375s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.2662546634674072s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.020962953567504883s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0008132457733154297s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.0517578125e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 1.1444091796875e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 3.2955689430236816s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 8.392333984375e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.29561424255371094s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.020751953125s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.147125244140625e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.4543533325195312e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.650871753692627s
Availability | SPARQL endpoint availability check for Soccer Dataset took 8.58306884765625e-05s
Availability | VoID file availability check for Soccer Dataset took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.2615482807159424s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.021096229553222656s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 2.956390380859375e-05s
Believability | Calculation of trust value for Soccer Dataset took 1.1444091796875e-05s
INFO | --- Analysis for http:www.msm.com took 2.626396894454956s
Availability | SPARQL endpoint availability check for Game Ontology took 0.00013256072998046875s
Availability | VoID file availability check for Game Ontology took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.3250582218170166s
Reputation | Calculation of the PageRank for Game Ontology took 0.021105527877807617s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for Game Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for http:www.RAG.comgameonto# took 3.3124241828918457s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.726119995117188e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.32624363899230957s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.022257328033447266s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.123283386230469e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.2159347534179688e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.4232800006866455s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 8.96453857421875e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.30498790740966797s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.021685123443603516s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.3855438232421875e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.239776611328125e-05s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.756603479385376s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.649162292480469e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2852332592010498s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02083301544189453s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.075599670410156e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.152557373046875e-06s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.6976163387298584s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.655952453613281e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3098726272583008s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021428585052490234s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.218650817871094e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.239776611328125e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.6822304725646973s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.172325134277344e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.30113935470581055s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02118086814880371s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.528594970703125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1682510375976562e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.7433438301086426s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.845329284667969e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.337369441986084s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02248525619506836s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.956390380859375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.0728836059570312e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 4.124565839767456s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.00012087821960449219s
Availability | VoID file availability check for Indian Biodiversity took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3115525245666504s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02073979377746582s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.170967102050781e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2159347534179688e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.6705210208892822s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 8.678436279296875e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.30079102516174316s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020681381225585938s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.123283386230469e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.1920928955078125e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 4.33906626701355s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.106541395187378s
Availability | VoID file availability check for Bookkeeping took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.3072221279144287s
Reputation | Calculation of the PageRank for Bookkeeping took 0.02125239372253418s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.170967102050781e-05s
Believability | Calculation of trust value for Bookkeeping took 9.5367431640625e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 4.4179136753082275s
Availability | SPARQL endpoint availability check for Legal Ontology took 8.130073547363281e-05s
Availability | VoID file availability check for Legal Ontology took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.30597448348999023s
Reputation | Calculation of the PageRank for Legal Ontology took 0.022770166397094727s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Legal Ontology took 1.1444091796875e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 3.3280136585235596s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 8.916854858398438e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2850067615509033s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.557868957519531e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.0967254638671875e-05s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.94242787361145s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.1961669921875e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.289292573928833s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.021018505096435547s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 2.956390380859375e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 1.1444091796875e-05s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.895233392715454s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 0.5865533351898193s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.37452268600463867s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.021106243133544922s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00011157989501953125s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 1.5020370483398438e-05s
INFO | --- Analysis for hungarian-national-library-catalog took 3.22248911857605s
Availability | SPARQL endpoint availability check for IATE RDF took 8.988380432128906e-05s
Availability | VoID file availability check for IATE RDF took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.3001713752746582s
Reputation | Calculation of the PageRank for IATE RDF took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.528594970703125e-05s
Believability | Calculation of trust value for IATE RDF took 1.0728836059570312e-05s
INFO | --- Analysis for iate-rdf took 3.0017895698547363s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.332415342330933s
Availability | VoID file availability check for IATI as Linked Data took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.3285079002380371s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.020611286163330078s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.821487426757812e-05s
Believability | Calculation of trust value for IATI as Linked Data took 1.1682510375976562e-05s
INFO | --- Analysis for iati-as-linked-data took 14.165716171264648s
Availability | SPARQL endpoint availability check for ICANE took 0.33251094818115234s
Availability | VoID file availability check for ICANE took 0.0008654594421386719s
Completeness | Calculation of interlinking completeness for ICANE took 0.2827787399291992s
Reputation | Calculation of the PageRank for ICANE took 0.020923614501953125s
Interlinking | Calculation of Degree of Connection for ICANE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.58306884765625e-05s
Believability | Calculation of trust value for ICANE took 9.5367431640625e-06s
INFO | --- Analysis for icane took 3.8318545818328857s
Availability | SPARQL endpoint availability check for ichoose took 0.1729569435119629s
Availability | VoID file availability check for ichoose took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for ichoose took 0.315654993057251s
Reputation | Calculation of the PageRank for ichoose took 0.020866870880126953s
Interlinking | Calculation of Degree of Connection for ichoose took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.4849853515625e-05s
Believability | Calculation of trust value for ichoose took 1.239776611328125e-05s
INFO | --- Analysis for ichoose took 42.384955406188965s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 0.7219712734222412s
Availability | VoID file availability check for The Iconology Dataset took 0.0006630420684814453s
Extra | Recovery of all triples for The Iconology Dataset took 3.607414484024048s
Performance | Total latancy measurement for The Iconology Dataset took 0.4980049133300781s
Amount of data | Number of triples check for The Iconology Dataset took 0.21609997749328613s
Interoperability | New terms check for The Iconology Dataset took 1.2923715114593506s
Versatility | Languages check for The Iconology Dataset took 0.6222617626190186s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.23501348495483398s
Interpretability | RDF structures check for The Iconology Dataset took 0.1466357707977295s
Versatility | Serialization formats check for The Iconology Dataset took 0.1146092414855957s
Availability | RDF dump link check for The Iconology Dataset took 0.0943446159362793s
License | MR license check for The Iconology Dataset took 0.1207420825958252s
License | HR license check for The Iconology Dataset took 0.45410895347595215s
Amount of data | Number of property check for The Iconology Dataset took 0.10764837265014648s
Understandability | Number of label check for The Iconology Dataset took 0.1810598373413086s
Understandability | URI regex check for The Iconology Dataset took 0.17920422554016113s
Understandability | Vocabs check for The Iconology Dataset took 0.09397697448730469s
Verifiability | Authors check for The Iconology Dataset took 0.10604000091552734s
Verifiability | Publishers check for The Iconology Dataset took 0.09387516975402832s
Performance | Throughput check for The Iconology Dataset took 10.562042951583862s
Amount of data | Check the number of entities for The Iconology Dataset took 7.367134094238281e-05s
Verifiability | Contribs. check for The Iconology Dataset took 0.08678054809570312s
Interlinking | sameAs chians check for The Iconology Dataset took 0.09409070014953613s
Interlinking | skos check for The Iconology Dataset took 0.09081268310546875s
Interlinking | skos check for The Iconology Dataset took 0.08297562599182129s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.09171700477600098s
Currency | Creation date check for The Iconology Dataset took 0.17578864097595215s
Currency | Modification date check for The Iconology Dataset took 0.19039678573608398s
Rep.Conc. | URIs length for The Iconology Dataset took 1.1855154037475586s
Interoperability | New vocabularies check for The Iconology Dataset took 5.4836273193359375e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08043718338012695s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.27321934700012207s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.016641616821289062s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.42429232597351074s
Consistency | Disjoint class check for The Iconology Dataset took 0.08319950103759766s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.1608591079711914s
Consistency | Misplaced classes for The Iconology Dataset took 0.8654422760009766s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.4330294132232666s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.1294407844543457s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.20344877243042s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.2861518859863281s
Security | Sign check for The Iconology Dataset took 0.08325695991516113s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2586.5589094161987s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 0.7665941715240479s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.021600008010864258s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 6.961822509765625e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 2.2411346435546875e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The Iconology Dataset took 1.1444091796875e-05s
INFO | --- Analysis for iconology-dataset took 2642.1194105148315s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 9.965896606445312e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.2953145503997803s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.020876169204711914s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.82012939453125e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 1.1682510375976562e-05s
INFO | --- Analysis for idreffr took 3.9758195877075195s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.8672771453857422s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.32738614082336426s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020761966705322266s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.76837158203125e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 5.9604644775390625e-06s
INFO | --- Analysis for ids took 4.453876733779907s
Availability | SPARQL endpoint availability check for ietflang took 8.58306884765625e-05s
Availability | VoID file availability check for ietflang took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for ietflang took 0.3089902400970459s
Reputation | Calculation of the PageRank for ietflang took 0.02063298225402832s
Interlinking | Calculation of Degree of Connection for ietflang took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ietflang took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.3392181396484375e-05s
Believability | Calculation of trust value for ietflang took 1.1682510375976562e-05s
INFO | --- Analysis for ietflang took 14.460155725479126s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.6784186363220215s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.31989192962646484s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.0206453800201416s
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.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for IGVLL took 4.455287456512451s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.4610428810119629s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0005514621734619141s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.2464592456817627s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.953920841217041s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.2027297019958496s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.348130464553833s
Versatility | Languages check for 3LGM² IHE Ontology took 0.20730304718017578s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.16941285133361816s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.21707510948181152s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.18819761276245117s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.18924403190612793s
License | MR license check for 3LGM² IHE Ontology took 0.20057988166809082s
License | HR license check for 3LGM² IHE Ontology took 0.2245171070098877s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.1804337501525879s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.2244584560394287s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.3584926128387451s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.19811511039733887s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.20598673820495605s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.1860814094543457s
Performance | Throughput check for 3LGM² IHE Ontology took 11.241610288619995s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 7.462501525878906e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.17836833000183105s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.18156147003173828s
Interlinking | skos check for 3LGM² IHE Ontology took 0.2041788101196289s
Interlinking | skos check for 3LGM² IHE Ontology took 0.17959833145141602s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.18927907943725586s
Currency | Creation date check for 3LGM² IHE Ontology took 0.38956284523010254s
Currency | Modification date check for 3LGM² IHE Ontology took 0.3550868034362793s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.7716495990753174s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.18844127655029297s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.197068452835083s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.18006634712219238s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.3409745693206787s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.002160787582397461s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.04932904243469238s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.19002532958984375s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.4309821128845215s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.2758970260620117s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.466050386428833s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.1521375179290771s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.3949971199035645s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.03543257713317871s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.17928838729858398s
Security | Sign check for 3LGM² IHE Ontology took 0.1849982738494873s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 375.27535915374756s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.39481568336486816s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.02088761329650879s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 3.981590270996094e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.430511474609375e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for IHE took 421.17467403411865s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 2.9333302974700928s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0006070137023925781s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 7.864055395126343s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 9.127412557601929s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 21.104506731033325s
Interoperability | New terms check for Test Site, LOD Lab 317 took 7.95046067237854s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.78774857521057s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 2.021108627319336s
Security | Check HTTPS for Test Site, LOD Lab 317 took 1.2049274444580078s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 2.247332811355591s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.9883599281311035s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.8549981117248535s
License | MR license check for Test Site, LOD Lab 317 took 1.9963176250457764s
License | HR license check for Test Site, LOD Lab 317 took 2.1397593021392822s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.9578912258148193s
Understandability | Number of label check for Test Site, LOD Lab 317 took 2.08750319480896s
Understandability | URI regex check for Test Site, LOD Lab 317 took 3.6647958755493164s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.8370661735534668s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.8797907829284668s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 1.8532259464263916s
Performance | Throughput check for Test Site, LOD Lab 317 took 18.138171672821045s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 8.440017700195312e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.8305234909057617s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.8904047012329102s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.9144525527954102s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.8598825931549072s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.906938076019287s
Currency | Creation date check for Test Site, LOD Lab 317 took 3.6649534702301025s
Currency | Modification date check for Test Site, LOD Lab 317 took 3.7009799480438232s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 34.645989418029785s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.829850196838379s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.8309361934661865s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.8406243324279785s
Accuracy | Check Empty annotation labels for Test Site, LOD Lab 317 took 3.6404480934143066s
Accuracy | Check White space in annotation for Test Site, LOD Lab 317 took 0.030557870864868164s
Accuracy | Check Datatype consistency for Test Site, LOD Lab 317 took 0.02898859977722168s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.8400797843933105s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 24.456732273101807s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 2.423032283782959s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 5.100996017456055s
Consistency | Check Invalid usage of undefined classes for Test Site, LOD Lab 317 took 1.1820578575134277s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 24.443215370178223s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.032706499099731445s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.4832770824432373s
Security | Sign check for Test Site, LOD Lab 317 took 1.9110095500946045s
Availability | Check URIs Dereferenciability for Test Site, LOD Lab 317 took 9.378743648529053s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.3327178955078125s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.020899295806884766s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 4.649162292480469e-05s
Interoperability | Check the re-using of existing vocabs for Test Site, LOD Lab 317 took 1.430511474609375e-06s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 1.0728836059570312e-05s
INFO | --- Analysis for iislod-test took 551.1966035366058s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 8.630752563476562e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.3074779510498047s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.020386934280395508s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.0040740966796875e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 1.2159347534179688e-05s
INFO | --- Analysis for ILUSOC took 18.20530867576599s
Availability | SPARQL endpoint availability check for im@sparql took 7.144859075546265s
Availability | VoID file availability check for im@sparql took 0.0013675689697265625s
Completeness | Calculation of interlinking completeness for im@sparql took 0.3038668632507324s
Reputation | Calculation of the PageRank for im@sparql took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for im@sparql took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for im@sparql took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for im@sparql took 2.956390380859375e-05s
Believability | Calculation of trust value for im@sparql took 1.2159347534179688e-05s
INFO | --- Analysis for im@sparql took 14.19702434539795s
Availability | SPARQL endpoint availability check for imagery bailingniao took 9.107589721679688e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.2869143486022949s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.022735595703125s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.0994415283203125e-05s
Believability | Calculation of trust value for imagery bailingniao took 1.239776611328125e-05s
INFO | --- Analysis for imagery_bailingniao took 4.04065728187561s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.155029058456421s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0006432533264160156s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 20.10977005958557s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.4718048572540283s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 10.278236150741577s
Interoperability | New terms check for Imagesnippets Image Descriptions took 2.0799307823181152s
Versatility | Languages check for Imagesnippets Image Descriptions took 20.567644834518433s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.602266550064087s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.6879801750183105s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7479231357574463s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7205657958984375s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.6927270889282227s
License | MR license check for Imagesnippets Image Descriptions took 0.7265424728393555s
License | HR license check for Imagesnippets Image Descriptions took 30.708824157714844s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7150943279266357s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.6489343643188477s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.4662718772888184s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7255549430847168s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.707329511642456s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7293715476989746s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.909497499465942s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 6.794929504394531e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7304089069366455s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.7643780708312988s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7472395896911621s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.663794994354248s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.6974444389343262s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.4561429023742676s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.435502529144287s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 33.05083465576172s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.765988826751709s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7075924873352051s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7402291297912598s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 10.952244997024536s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.155524492263794s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.22987699508667s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7073137760162354s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.929815053939819s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 5.068270206451416s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.3091115951538086s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.537226676940918s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 2.8227298259735107s
Security | Sign check for Imagesnippets Image Descriptions took 0.7197487354278564s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 11.086511373519897s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.37670326232910156s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.0209043025970459s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.250640869140625e-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.198883056640625e-06s
INFO | --- Analysis for imagesnippets took 296.23377537727356s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.09105610847473145s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.3041574954986572s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.02150440216064453s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.96453857421875e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 1.1682510375976562e-05s
INFO | --- Analysis for imf-linked-data took 2.7768194675445557s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.100799560546875e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.2921898365020752s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.021178245544433594s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.049041748046875e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 1.049041748046875e-05s
INFO | --- Analysis for Imtiaz took 2.631868600845337s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.649162292480469e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.3133077621459961s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.02097773551940918s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 3.147125244140625e-05s
Believability | Calculation of trust value for Royalty Free Music took 7.62939453125e-06s
INFO | --- Analysis for inaudio.org took 4.181032180786133s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.5226082801818848s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.00038933753967285156s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.27118611335754395s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.02117443084716797s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.933906555175781e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 4.172577381134033s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.3392181396484375e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.00040650367736816406s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.28712940216064453s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.021268606185913086s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00010943412780761719s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 8.106231689453125e-06s
INFO | --- Analysis for ineverycrea took 15.119036674499512s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.00012111663818359375s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0004177093505859375s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.2969834804534912s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.5367431640625e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.106231689453125e-06s
INFO | --- Analysis for ineverycrea-argentina took 8.315556764602661s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 271.88190960884094s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.29326915740966797s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.020779848098754883s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.43865966796875e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for influence-tracker-dataset took 565.4759476184845s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.28520727157592773s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.02096867561340332s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 2.8848648071289062e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 1.1920928955078125e-05s
INFO | --- Analysis for instance-hub-fiscal-years took 2.849499225616455s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.1961669921875e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.3901500701904297s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.02103281021118164s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00011730194091796875s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.3113021850585938e-05s
INFO | --- Analysis for interactivemaps-gnoss took 9.477551698684692s
Availability | SPARQL endpoint availability check for intervalue took 0.1552269458770752s
Availability | VoID file availability check for intervalue took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for intervalue took 0.2855103015899658s
Reputation | Calculation of the PageRank for intervalue took 0.02207636833190918s
Interlinking | Calculation of Degree of Connection for intervalue took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for intervalue took 7.319450378417969e-05s
Believability | Calculation of trust value for intervalue took 1.4066696166992188e-05s
INFO | --- Analysis for intervalue took 2.7706193923950195s
Availability | SPARQL endpoint availability check for Inztrow took 4.1484832763671875e-05s
Availability | VoID file availability check for Inztrow took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for Inztrow took 0.2762482166290283s
Reputation | Calculation of the PageRank for Inztrow took 0.02126145362854004s
Interlinking | Calculation of Degree of Connection for Inztrow took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Inztrow took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Inztrow took 2.7894973754882812e-05s
Believability | Calculation of trust value for Inztrow took 1.2636184692382812e-05s
INFO | --- Analysis for Inztrow took 3.8114731311798096s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 0.00011372566223144531s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.2996797561645508s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.020677804946899414s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 2.9325485229492188e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for ipbes took 4.138980388641357s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 8.535385131835938e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.2978799343109131s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.021084070205688477s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.57763671875e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 1.2636184692382812e-05s
INFO | --- Analysis for iptc-newscodes took 3.8391306400299072s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 1.7095732688903809s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0014095306396484375s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.28623056411743164s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020483016967773438s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.489059448242188e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 1.1682510375976562e-05s
INFO | --- Analysis for iserve took 6.759582281112671s
Availability | SPARQL endpoint availability check for ISIC V4 took 21.51232385635376s
Availability | VoID file availability check for ISIC V4 took 0.0008342266082763672s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.2896385192871094s
Reputation | Calculation of the PageRank for ISIC V4 took 0.02109527587890625s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.6716461181640625e-05s
Believability | Calculation of trust value for ISIC V4 took 2.47955322265625e-05s
INFO | --- Analysis for isic-v4 took 116.46448063850403s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 9.989738464355469e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.29728055000305176s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.021429061889648438s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 8.034706115722656e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 9.059906005859375e-06s
INFO | --- Analysis for isil-dbpedia took 4.414087295532227s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.458427429199219e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0011394023895263672s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.28401875495910645s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.695487976074219e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 1.239776611328125e-05s
INFO | --- Analysis for iso-639-oasis took 3.3423831462860107s
Availability | SPARQL endpoint availability check for ISOcat took 8.940696716308594e-05s
Availability | VoID file availability check for ISOcat took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for ISOcat took 0.2894291877746582s
Reputation | Calculation of the PageRank for ISOcat took 0.020944595336914062s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.985664367675781e-05s
Believability | Calculation of trust value for ISOcat took 1.33514404296875e-05s
INFO | --- Analysis for isocat took 12.413153886795044s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.315376281738281e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.3180124759674072s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020410776138305664s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.266334533691406e-05s
Believability | Calculation of trust value for ISOcat-metadata took 1.2159347534179688e-05s
INFO | --- Analysis for isocat-metadata took 33.11157250404358s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.132432222366333s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0006108283996582031s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.347913503646851s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.27739739418029785s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1412651538848877s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.7246134281158447s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 93.11581587791443s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14258956909179688s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.03136587142944336s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10797834396362305s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10583996772766113s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09681057929992676s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14531588554382324s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.65034127235413s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08845281600952148s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.0740597248077393s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.299605131149292s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13009309768676758s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13637924194335938s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08772587776184082s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.279168128967285s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 6.771087646484375e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13025999069213867s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20052194595336914s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.42215514183044434s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3903462886810303s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14329934120178223s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1733994483947754s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08572769165039062s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 13.033226251602173s
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.08634305000305176s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1000819206237793s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09153199195861816s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.8145155906677246s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3113095760345459s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.26538515090942383s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08376836776733398s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.05989408493042s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.899768590927124s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.6274869441986084s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1456544399261475s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.21208930015564s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.28396129608154297s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09255123138427734s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1037144660949707s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.799863338470459s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.40389418601989746s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0261685848236084s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.393692016601562e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.430511474609375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1920928955078125e-05s
INFO | --- Analysis for ispra-lod-place took 447.2879285812378s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.05003786087036133s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0005793571472167969s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 5.24562668800354s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.2829864025115967s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.15283608436584473s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.7602012157440186s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 90.67397975921631s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.08555841445922852s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.032283782958984375s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.12174034118652344s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.10153460502624512s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.09193038940429688s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.15601134300231934s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 92.48626732826233s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.0879526138305664s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.3439602851867676s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.33721280097961426s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.14664196968078613s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.14693069458007812s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.08539104461669922s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.246601343154907s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 0.00014209747314453125s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.13805913925170898s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.1968975067138672s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.4164884090423584s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.38700246810913086s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.13477754592895508s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.17408347129821777s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.08537673950195312s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 12.956939935684204s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.08454179763793945s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.09565877914428711s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.08928728103637695s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 2.822985887527466s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.30780482292175293s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.2655031681060791s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.08726978302001953s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.034332990646362s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9014689922332764s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 2.729505777359009s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.1873743534088135s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.085241556167603s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.2945973873138428s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.08664512634277344s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.1027681827545166s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 8.563288927078247s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.4208986759185791s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.02117133140563965s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.38690185546875e-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.239776611328125e-05s
INFO | --- Analysis for ispra-lod-ron took 439.827832698822s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.6727409362792969s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.29198694229125977s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.020360469818115234s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.417533874511719e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 1.0728836059570312e-05s
INFO | --- Analysis for issa-agritrop took 5.0295915603637695s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 8.749961853027344e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.27660083770751953s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.8133392333984375e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 9.775161743164062e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.6766350269317627s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.315376281738281e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2990906238555908s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020647287368774414s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007376670837402344s
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 1.1444091796875e-05s
INFO | --- Analysis for ISSN:_0080-3626 took 3.0552053451538086s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 5.078315734863281e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0010635852813720703s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.315579891204834s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.020725727081298828s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 2.8133392333984375e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 1.0728836059570312e-05s
INFO | --- Analysis for ISSN:_0080-3626. took 3.0478925704956055s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 0.26696038246154785s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.3056778907775879s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.821487426757812e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 8.821487426757812e-06s
INFO | --- Analysis for istat-immigration took 3.0034430027008057s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.26324462890625s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.29819512367248535s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020758867263793945s
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.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 2.9802322387695312e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 6.198883056640625e-06s
INFO | --- Analysis for it-aifa-drug-prices took 3.2996675968170166s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 0.21826553344726562s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.27926182746887207s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.022144556045532227s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.390975952148438e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 1.1920928955078125e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 2.851534128189087s
Availability | SPARQL endpoint availability check for IWN took 7.891654968261719e-05s
Availability | VoID file availability check for IWN took 0.001135110855102539s
Completeness | Calculation of interlinking completeness for IWN took 0.29878687858581543s
Reputation | Calculation of the PageRank for IWN took 0.022588014602661133s
Interlinking | Calculation of Degree of Connection for IWN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IWN took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for IWN took 3.695487976074219e-05s
Believability | Calculation of trust value for IWN took 1.4781951904296875e-05s
INFO | --- Analysis for iwn took 6.132737636566162s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 5.963538408279419s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0008199214935302734s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.28683924674987793s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020838499069213867s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 5.984306335449219e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 1.0728836059570312e-05s
INFO | --- Analysis for jamendo-dbtune took 11.037498235702515s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 8.225440979003906e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.2626492977142334s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020809173583984375s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.744529724121094e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.850880146026611s
Availability | SPARQL endpoint availability check for JEL Classification took 8.511543273925781e-05s
Availability | VoID file availability check for JEL Classification took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2703092098236084s
Reputation | Calculation of the PageRank for JEL Classification took 0.022815465927124023s
Interlinking | Calculation of Degree of Connection for JEL Classification took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 2.86102294921875e-05s
Believability | Calculation of trust value for JEL Classification took 1.1205673217773438e-05s
INFO | --- Analysis for jel-classification took 5.069482326507568s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.1626486778259277s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.2844269275665283s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.021474599838256836s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.3855438232421875e-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.026302814483643s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.3218786716461s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0007398128509521484s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.31345367431640625s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.022336244583129883s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.963180541992188e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.239776611328125e-05s
INFO | --- Analysis for jita took 540.1607863903046s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.04108500480652s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0006773471832275391s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.8266019821166992s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.02081608772277832s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 8.749961853027344e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.049041748046875e-05s
INFO | --- Analysis for john-goodwins-family-tree took 63.4743492603302s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 8.749961853027344e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.00041103363037109375s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.2747189998626709s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.021394968032836914s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.6716461181640625e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 8.106231689453125e-06s
INFO | --- Analysis for jp-cos took 4.779646396636963s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 8.702278137207031e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.2757246494293213s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.021062612533569336s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 3.9577484130859375e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 1.0728836059570312e-05s
INFO | --- Analysis for jp-textbook took 4.539793252944946s
Availability | SPARQL endpoint availability check for JRC-Names took 4.553794860839844e-05s
Availability | VoID file availability check for JRC-Names took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.2712841033935547s
Reputation | Calculation of the PageRank for JRC-Names took 0.0208280086517334s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.647804260253906e-05s
Believability | Calculation of trust value for JRC-Names took 1.2874603271484375e-05s
INFO | --- Analysis for jrc-names-ec took 4.917521715164185s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.771148920059204s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.2777242660522461s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.021320819854736328s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 7.05718994140625e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 1.3113021850585938e-05s
INFO | --- Analysis for jrc-names-mlode took 4.703920602798462s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.1961669921875e-05s
Availability | VoID file availability check for JudaicaLink took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.27567577362060547s
Reputation | Calculation of the PageRank for JudaicaLink took 0.022680997848510742s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.0001068115234375s
Believability | Calculation of trust value for JudaicaLink took 1.1444091796875e-05s
INFO | --- Analysis for judaicalink took 4.518362522125244s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.0746755599975586s
Availability | VoID file availability check for Kallikratis municipalities took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.31766390800476074s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.036064147949219e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 9.059906005859375e-06s
INFO | --- Analysis for kallikratis-municipalities took 3.0877928733825684s
Availability | SPARQL endpoint availability check for EU Soccer League took 8.606910705566406e-05s
Availability | VoID file availability check for EU Soccer League took 0.0010485649108886719s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.3116781711578369s
Reputation | Calculation of the PageRank for EU Soccer League took 0.021173477172851562s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.0994415283203125e-05s
Believability | Calculation of trust value for EU Soccer League took 1.2874603271484375e-05s
INFO | --- Analysis for KG:Course_Submission took 4.709709644317627s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 8.988380432128906e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.31443166732788086s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.021053791046142578s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.239776611328125e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 7.867813110351562e-06s
INFO | --- Analysis for KING took 2.9350967407226562s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.5299530029296875e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.39768195152282715s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.580352783203125e-05s
Believability | Calculation of trust value for Klappstuhlclub took 9.298324584960938e-06s
INFO | --- Analysis for klappstuhlclub took 12.841008186340332s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.948217153549194s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.27742958068847656s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.02074742317199707s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 5.793571472167969e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 9.5367431640625e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.714767932891846s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.00543212890625e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.30763721466064453s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02054905891418457s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.9802322387695312e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.0728836059570312e-05s
INFO | --- Analysis for KnowledgeFusion took 2.664135694503784s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 8.702278137207031e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.2857093811035156s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020376205444335938s
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.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.341934204101562e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 1.2874603271484375e-05s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.460664510726929s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 8.58306884765625e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.26506757736206055s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.0279159545898438e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0251998901367188e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.50897479057312s
Availability | SPARQL endpoint availability check for Informatics Studies took 8.654594421386719e-05s
Availability | VoID file availability check for Informatics Studies took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.3156156539916992s
Reputation | Calculation of the PageRank for Informatics Studies took 0.021445035934448242s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0008766651153564453s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 3.647804260253906e-05s
Believability | Calculation of trust value for Informatics Studies took 1.33514404296875e-05s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 3.3779046535491943s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.07643556594848633s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2747316360473633s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.02047109603881836s
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.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.790855407714844e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 1.0728836059570312e-05s
INFO | --- Analysis for kupkb took 10.052255153656006s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 9.156975030899048s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.2642500400543213s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.02097296714782715s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.414817810058594e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 8.821487426757812e-06s
INFO | --- Analysis for l3s-dblp took 43.55096101760864s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 24.5389506816864s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.2941555976867676s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.02106332778930664s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 7.104873657226562e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 6.67572021484375e-06s
INFO | --- Analysis for lak-dataset took 67.96687960624695s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.20302939414978027s
Availability | VoID file availability check for  Language Name Authority List  took 0.0004737377166748047s
Extra | Recovery of all triples for  Language Name Authority List  took 173.90710401535034s
Performance | Total latancy measurement for  Language Name Authority List  took 0.6168644428253174s
Amount of data | Number of triples check for  Language Name Authority List  took 97.81489062309265s
Interoperability | New terms check for  Language Name Authority List  took 64.9917938709259s
Versatility | Languages check for  Language Name Authority List  took 300.06069135665894s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 101.92245697975159s
Security | Check HTTPS for  Language Name Authority List  took 0.3904891014099121s
Interpretability | RDF structures check for  Language Name Authority List  took 0.3250415325164795s
Versatility | Serialization formats check for  Language Name Authority List  took 5.436819791793823s
Availability | RDF dump link check for  Language Name Authority List  took 0.2743830680847168s
License | MR license check for  Language Name Authority List  took 0.32087087631225586s
License | HR license check for  Language Name Authority List  took 300.0890762805939s
Amount of data | Number of property check for  Language Name Authority List  took 0.17222356796264648s
Understandability | Number of label check for  Language Name Authority List  took 1.701444149017334s
Understandability | URI regex check for  Language Name Authority List  took 0.33921098709106445s
Understandability | Vocabs check for  Language Name Authority List  took 0.09688401222229004s
Verifiability | Authors check for  Language Name Authority List  took 0.1767733097076416s
Verifiability | Publishers check for  Language Name Authority List  took 0.2367868423461914s
Performance | Throughput check for  Language Name Authority List  took 10.626355648040771s
Amount of data | Check the number of entities for  Language Name Authority List  took 8.082389831542969e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.11204886436462402s
Interlinking | sameAs chians check for  Language Name Authority List  took 7.090566873550415s
Interlinking | skos check for  Language Name Authority List  took 0.3601388931274414s
Interlinking | skos check for  Language Name Authority List  took 0.1649773120880127s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.28172969818115234s
Currency | Creation date check for  Language Name Authority List  took 0.47131991386413574s
Currency | Modification date check for  Language Name Authority List  took 0.17890191078186035s
Rep.Conc. | URIs length for  Language Name Authority List  took 434.08747935295105s
Interoperability | New vocabularies check for  Language Name Authority List  took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.18384027481079102s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.2418346405029297s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.16688799858093262s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 39.87776255607605s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.2245566844940186s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.62445330619812s
Consistency | Disjoint class check for  Language Name Authority List  took 0.19882655143737793s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.41791224479675s
Consistency | Misplaced classes for  Language Name Authority List  took 8.64171552658081s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 45.01187825202942s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.512702226638794s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.2303502559662s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 3.016200542449951s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.3431837558746338s
Security | Sign check for  Language Name Authority List  took 0.5038626194000244s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 11.295857191085815s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 0.8390161991119385s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.021869897842407227s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.5367431640625e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.430511474609375e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.3589859008789062e-05s
INFO | --- Analysis for language-authority-list took 15158.62789440155s
Availability | SPARQL endpoint availability check for Lark took 384.2037889957428s
Availability | VoID file availability check for Lark took 0.00083160400390625s
Completeness | Calculation of interlinking completeness for Lark took 0.43678951263427734s
Reputation | Calculation of the PageRank for Lark took 0.021408796310424805s
Interlinking | Calculation of Degree of Connection for Lark took 5.984306335449219e-05s
Interlinking | Calculation of Centrality for Lark took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Lark took 7.748603820800781e-05s
Believability | Calculation of trust value for Lark took 1.2159347534179688e-05s
INFO | --- Analysis for LARK took 1675.7622215747833s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.5245907306671143s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.28522658348083496s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.02099466323852539s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 1.1444091796875e-05s
INFO | --- Analysis for LASLA took 4.4625043869018555s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.5465047359466553s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.2863271236419678s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.030266523361206055s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0014469623565673828s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 6.413459777832031e-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.3635876178741455s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.4813547134399414s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.2891852855682373s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.02102804183959961s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 1.2636184692382812e-05s
INFO | --- Analysis for LatinAffectus took 4.358534812927246s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.49651288986206055s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.2797129154205322s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.02287006378173828s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.1961669921875e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 1.1205673217773438e-05s
INFO | --- Analysis for LatinWordnetLiLa took 4.645925283432007s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.410743713378906e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.33509278297424316s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.020915746688842773s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011897087097167969s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.0967254638671875e-05s
INFO | --- Analysis for lcsh took 6.830817222595215s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 7.772445678710938e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0007097721099853516s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.3375825881958008s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.02084636688232422s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.463859558105469e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 1.1920928955078125e-05s
INFO | --- Analysis for lcsubjects took 3.26115083694458s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.543418169021606s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.28655147552490234s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.291534423828125e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.2874603271484375e-05s
INFO | --- Analysis for ldt@library took 35.52188467979431s
Availability | SPARQL endpoint availability check for U ime Legije took 4.315376281738281e-05s
Availability | VoID file availability check for U ime Legije took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.2900125980377197s
Reputation | Calculation of the PageRank for U ime Legije took 0.02201676368713379s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.4809112548828125e-05s
Believability | Calculation of trust value for U ime Legije took 1.1205673217773438e-05s
INFO | --- Analysis for LEGIJA_STRANACA took 2.6981606483459473s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.5605325698852539s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.27745938301086426s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.02207803726196289s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.152557373046875e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.0013580322265625e-05s
INFO | --- Analysis for LemmaBank took 4.698039531707764s
Availability | SPARQL endpoint availability check for lemonUby took 8.296966552734375e-05s
Availability | VoID file availability check for lemonUby took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for lemonUby took 0.3172588348388672s
Reputation | Calculation of the PageRank for lemonUby took 0.020839214324951172s
Interlinking | Calculation of Degree of Connection for lemonUby took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for lemonUby took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.461143493652344e-05s
Believability | Calculation of trust value for lemonUby took 9.775161743164062e-06s
INFO | --- Analysis for lemonuby took 3.4479970932006836s
Availability | SPARQL endpoint availability check for LemonWiktionary took 8.273124694824219e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.32340383529663086s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.022278785705566406s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.600120544433594e-05s
Believability | Calculation of trust value for LemonWiktionary took 1.0013580322265625e-05s
INFO | --- Analysis for lemonwiktionary took 4.537076473236084s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.4986441135406494s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.31647253036499023s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02103137969970703s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for LewisShort took 4.119603395462036s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.0663928985595703s
Availability | VoID file availability check for LEXIN-RDF took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.3203003406524658s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.02092432975769043s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.170967102050781e-05s
Believability | Calculation of trust value for LEXIN-RDF took 1.3828277587890625e-05s
INFO | --- Analysis for lexin-rdf took 6.016134023666382s
Availability | SPARQL endpoint availability check for lexinfo took 4.6253204345703125e-05s
Availability | VoID file availability check for lexinfo took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for lexinfo took 0.2872037887573242s
Reputation | Calculation of the PageRank for lexinfo took 0.021128416061401367s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.845329284667969e-05s
Believability | Calculation of trust value for lexinfo took 1.2636184692382812e-05s
INFO | --- Analysis for lexinfo took 3.137777805328369s
Availability | SPARQL endpoint availability check for Lexvo took 4.220008850097656e-05s
Availability | VoID file availability check for Lexvo took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Lexvo took 0.27436208724975586s
Reputation | Calculation of the PageRank for Lexvo took 0.022952795028686523s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.000171661376953125s
Believability | Calculation of trust value for Lexvo took 1.049041748046875e-05s
INFO | --- Analysis for lexvo took 3.2766690254211426s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.267692565917969e-05s
Availability | VoID file availability check for Lexvo.org took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.3017122745513916s
Reputation | Calculation of the PageRank for Lexvo.org took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.343292236328125e-05s
Believability | Calculation of trust value for Lexvo.org took 6.198883056640625e-06s
INFO | --- Analysis for lexvo-org took 2.829268217086792s
Availability | SPARQL endpoint availability check for LIBRIS took 0.35898375511169434s
Availability | VoID file availability check for LIBRIS took 0.0005886554718017578s
Extra | Recovery of all triples for LIBRIS took 6.086145877838135s
Performance | Total latancy measurement for LIBRIS took 0.7104184627532959s
Amount of data | Number of triples check for LIBRIS took 20.86871862411499s
Interoperability | New terms check for LIBRIS took 14.722191333770752s
Versatility | Languages check for LIBRIS took 0.18345928192138672s
Interpretability | Number of blank nodes check for LIBRIS took 300.0349624156952s
Security | Check HTTPS for LIBRIS took 0.6972548961639404s
Interpretability | RDF structures check for LIBRIS took 0.42721009254455566s
Versatility | Serialization formats check for LIBRIS took 0.2293558120727539s
Availability | RDF dump link check for LIBRIS took 0.13012027740478516s
License | MR license check for LIBRIS took 0.22877883911132812s
License | HR license check for LIBRIS took 0.26412129402160645s
Amount of data | Number of property check for LIBRIS took 0.1933598518371582s
Understandability | Number of label check for LIBRIS took 0.47432756423950195s
Understandability | URI regex check for LIBRIS took 0.33893895149230957s
Understandability | Vocabs check for LIBRIS took 0.13970160484313965s
Verifiability | Authors check for LIBRIS took 0.1628732681274414s
Verifiability | Publishers check for LIBRIS took 0.17424607276916504s
Performance | Throughput check for LIBRIS took 10.76421332359314s
Amount of data | Check the number of entities for LIBRIS took 6.699562072753906e-05s
Verifiability | Contribs. check for LIBRIS took 0.16590404510498047s
Interlinking | sameAs chians check for LIBRIS took 0.17131447792053223s
Interlinking | skos check for LIBRIS took 0.2906370162963867s
Interlinking | skos check for LIBRIS took 0.13509631156921387s
Timeliness | dataset update frequency check for LIBRIS took 0.149827241897583s
Currency | Creation date check for LIBRIS took 0.3899345397949219s
Currency | Modification date check for LIBRIS took 0.6798908710479736s
Rep.Conc. | URIs length for LIBRIS took 79.81245946884155s
Interoperability | New vocabularies check for LIBRIS took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.18966245651245117s
Accuracy | Check Functional Property for LIBRIS took 0.23958802223205566s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.1852734088897705s
Accuracy | Check Datatype consistency for LIBRIS took 0.2720804214477539s
Consistency | Disjoint class check for LIBRIS took 0.2579786777496338s
Consistency | Check Misplaced properties for LIBRIS took 60.939077854156494s
Consistency | Misplaced classes for LIBRIS took 1.1292853355407715s
Consistency | Check Ontology hijacking for LIBRIS took 3.1139867305755615s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.1506249904632568s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 61.78317737579346s
Conciseness | Check Extensional conciseness for LIBRIS took 0.27956438064575195s
Conciseness | Check Intensional conciseness for LIBRIS took 0.40274810791015625s
Security | Sign check for LIBRIS took 0.2536461353302002s
Availability | Check URIs Dereferenciability for LIBRIS took 9.327629327774048s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.4133889675140381s
Reputation | Calculation of the PageRank for LIBRIS took 0.020625829696655273s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0006773471832275391s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 9.846687316894531e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.430511474609375e-06s
Believability | Calculation of trust value for LIBRIS took 1.2874603271484375e-05s
INFO | --- Analysis for libris took 1057.2517874240875s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.06329631805419922s
Availability | VoID file availability check for Public Library of Veroia took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.27947568893432617s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.02078557014465332s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 8.296966552734375e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.1205673217773438e-05s
INFO | --- Analysis for libver took 4.384329795837402s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.14258456230163574s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.2901909351348877s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.020841121673583984s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.845329284667969e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 1.0251998901367188e-05s
INFO | --- Analysis for lichfield-spending took 2.9095466136932373s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 8.893013000488281e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0007638931274414062s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.29523754119873047s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.02085089683532715s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 4.839897155761719e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.1682510375976562e-05s
INFO | --- Analysis for lime took 7.6639909744262695s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 8.630752563476562e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.47635340690612793s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.29726290702819824s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.02163553237915039s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00011229515075683594s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.1682510375976562e-05s
INFO | --- Analysis for lingvoj took 15.280315160751343s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 8.702278137207031e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.2784891128540039s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 7.891654968261719e-05s
Believability | Calculation of trust value for Linked Crunchbase took 6.198883056640625e-06s
INFO | --- Analysis for linked-crunchbase took 15.21814227104187s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.357008695602417s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0012288093566894531s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.3122386932373047s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.02029585838317871s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.319450378417969e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.430511474609375e-05s
INFO | --- Analysis for linked-drugs took 7.388036489486694s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.124641418457031e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.29903340339660645s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.02045750617980957s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.393692016601562e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 8.821487426757812e-06s
INFO | --- Analysis for linked-edgar took 4.384076833724976s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 8.630752563476562e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.299532413482666s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.393692016601562e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 1.239776611328125e-05s
INFO | --- Analysis for linked-eurostat took 3.8608317375183105s
Availability | SPARQL endpoint availability check for linked hypernyms took 8.654594421386719e-05s
Availability | VoID file availability check for linked hypernyms took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.27005529403686523s
Reputation | Calculation of the PageRank for linked hypernyms took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.200241088867188e-05s
Believability | Calculation of trust value for linked hypernyms took 1.1205673217773438e-05s
INFO | --- Analysis for linked-hypernyms took 3.6037466526031494s
Availability | SPARQL endpoint availability check for Linked Life Data took 239.00884819030762s
Availability | VoID file availability check for Linked Life Data took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.4568464756011963s
Reputation | Calculation of the PageRank for Linked Life Data took 0.02724003791809082s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 4.982948303222656e-05s
Believability | Calculation of trust value for Linked Life Data took 1.1682510375976562e-05s
INFO | --- Analysis for linked-life-data took 698.5192182064056s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.26685309410095215s
Availability | VoID file availability check for Linked Logainm took 0.0005776882171630859s
Extra | Recovery of all triples for Linked Logainm took 3.4503262042999268s
Performance | Total latancy measurement for Linked Logainm took 0.5917267799377441s
Amount of data | Number of triples check for Linked Logainm took 0.19556021690368652s
Interoperability | New terms check for Linked Logainm took 1.3205878734588623s
Versatility | Languages check for Linked Logainm took 1.4707322120666504s
Interpretability | Number of blank nodes check for Linked Logainm took 0.15424799919128418s
Security | Check HTTPS for Linked Logainm took 0.2712283134460449s
Interpretability | RDF structures check for Linked Logainm took 0.3061501979827881s
Versatility | Serialization formats check for Linked Logainm took 0.17979073524475098s
Availability | RDF dump link check for Linked Logainm took 0.11538934707641602s
License | MR license check for Linked Logainm took 0.13457727432250977s
License | HR license check for Linked Logainm took 0.11204218864440918s
Amount of data | Number of property check for Linked Logainm took 0.1585698127746582s
Understandability | Number of label check for Linked Logainm took 0.23337984085083008s
Understandability | URI regex check for Linked Logainm took 0.21800732612609863s
Understandability | Vocabs check for Linked Logainm took 0.10580229759216309s
Verifiability | Authors check for Linked Logainm took 0.12781310081481934s
Verifiability | Publishers check for Linked Logainm took 0.12148666381835938s
Performance | Throughput check for Linked Logainm took 10.794471502304077s
Amount of data | Check the number of entities for Linked Logainm took 0.00011181831359863281s
Verifiability | Contribs. check for Linked Logainm took 0.11777281761169434s
Interlinking | sameAs chians check for Linked Logainm took 0.1585993766784668s
Interlinking | skos check for Linked Logainm took 0.15992188453674316s
Interlinking | skos check for Linked Logainm took 0.12434220314025879s
Timeliness | dataset update frequency check for Linked Logainm took 0.11433839797973633s
Currency | Creation date check for Linked Logainm took 0.272763729095459s
Currency | Modification date check for Linked Logainm took 0.25467967987060547s
Rep.Conc. | URIs length for Linked Logainm took 0.8700168132781982s
Interoperability | New vocabularies check for Linked Logainm took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.1443464756011963s
Accuracy | Check Functional Property for Linked Logainm took 0.2386770248413086s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.197861909866333s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.5327188968658447s
Accuracy | Check White space in annotation for Linked Logainm took 0.024315357208251953s
Accuracy | Check Datatype consistency for Linked Logainm took 0.027283668518066406s
Consistency | Disjoint class check for Linked Logainm took 0.19189763069152832s
Consistency | Check Misplaced properties for Linked Logainm took 0.31693339347839355s
Consistency | Misplaced classes for Linked Logainm took 0.2979705333709717s
Consistency | Check Ontology hijacking for Linked Logainm took 1.632838249206543s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.131246566772461s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.330331802368164s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.03173494338989258s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.19675254821777344s
Security | Sign check for Linked Logainm took 0.13733291625976562s
Availability | Check URIs Dereferenciability for Linked Logainm took 1033.8977518081665s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.4260275363922119s
Reputation | Calculation of the PageRank for Linked Logainm took 0.021467208862304688s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 6.151199340820312e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 8.559226989746094e-05s
Interoperability | Check the re-using of existing vocabs for Linked Logainm took 1.1920928955078125e-06s
Believability | Calculation of trust value for Linked Logainm took 1.0013580322265625e-05s
INFO | --- Analysis for linked-logainm took 1091.944081544876s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.172325134277344e-05s
Availability | VoID file availability check for Linked NUTS took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.29935574531555176s
Reputation | Calculation of the PageRank for Linked NUTS took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 4.839897155761719e-05s
Believability | Calculation of trust value for Linked NUTS took 1.0251998901367188e-05s
INFO | --- Analysis for linked-nuts took 2.8749539852142334s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 0.3758516311645508s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.30448007583618164s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007371902465820312s
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 3.2723195552825928s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.998887538909912s
Availability | VoID file availability check for Linked Open Commerce took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.3247871398925781s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.030199289321899414s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0010859966278076172s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 4.291534423828125e-05s
Believability | Calculation of trust value for Linked Open Commerce took 6.198883056640625e-06s
INFO | --- Analysis for linked-open-commerce took 14.043721437454224s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 0.635678768157959s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.310152530670166s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.02117180824279785s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010514259338378906s
Believability | Calculation of trust value for Linked Open Data of Ecology took 1.3828277587890625e-05s
INFO | --- Analysis for linked-open-data-of-ecology took 3.39528751373291s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 8.821487426757812e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.2911055088043213s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.96453857421875e-05s
Believability | Calculation of trust value for Linked Open Numbers took 1.239776611328125e-05s
INFO | --- Analysis for linked-open-numbers took 2.946499824523926s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.2767956256866455s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.020820140838623047s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.86102294921875e-05s
Believability | Calculation of trust value for Linked Open Piracy took 7.62939453125e-06s
INFO | --- Analysis for linked-open-piracy took 7.375434875488281s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 1.8043322563171387s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0005688667297363281s
Extra | Recovery of all triples for Linked Open Vocabularies (LOV) took 76.133953332901s
Performance | Total latancy measurement for Linked Open Vocabularies (LOV) took 2.1432905197143555s
Amount of data | Number of triples check for Linked Open Vocabularies (LOV) took 1.9251949787139893s
Interoperability | New terms check for Linked Open Vocabularies (LOV) took 2.2316019535064697s
Versatility | Languages check for Linked Open Vocabularies (LOV) took 14.664608240127563s
Interpretability | Number of blank nodes check for Linked Open Vocabularies (LOV) took 2.5093376636505127s
Interpretability | RDF structures check for Linked Open Vocabularies (LOV) took 0.9707715511322021s
Versatility | Serialization formats check for Linked Open Vocabularies (LOV) took 1.1012203693389893s
Availability | RDF dump link check for Linked Open Vocabularies (LOV) took 1.1451561450958252s
License | MR license check for Linked Open Vocabularies (LOV) took 0.5779178142547607s
License | HR license check for Linked Open Vocabularies (LOV) took 45.116764307022095s
Amount of data | Number of property check for Linked Open Vocabularies (LOV) took 2.051666498184204s
Understandability | Number of label check for Linked Open Vocabularies (LOV) took 1.581139087677002s
Understandability | URI regex check for Linked Open Vocabularies (LOV) took 0.7470409870147705s
Understandability | Vocabs check for Linked Open Vocabularies (LOV) took 0.42992615699768066s
Verifiability | Authors check for Linked Open Vocabularies (LOV) took 0.42990612983703613s
Verifiability | Publishers check for Linked Open Vocabularies (LOV) took 0.528888463973999s
Performance | Throughput check for Linked Open Vocabularies (LOV) took 11.864552736282349s
Amount of data | Check the number of entities for Linked Open Vocabularies (LOV) took 0.9710633754730225s
Verifiability | Contribs. check for Linked Open Vocabularies (LOV) took 0.48090195655822754s
Interlinking | sameAs chians check for Linked Open Vocabularies (LOV) took 0.3820798397064209s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.3842434883117676s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.26596879959106445s
Timeliness | dataset update frequency check for Linked Open Vocabularies (LOV) took 0.18674182891845703s
Currency | Creation date check for Linked Open Vocabularies (LOV) took 1.3375756740570068s
Currency | Modification date check for Linked Open Vocabularies (LOV) took 0.22318553924560547s
Rep.Conc. | URIs length for Linked Open Vocabularies (LOV) took 27.59841799736023s
Interoperability | New vocabularies check for Linked Open Vocabularies (LOV) took 27.465388298034668s
Consistency | Deprecated classes/propertiers check for Linked Open Vocabularies (LOV) took 0.5398805141448975s
Accuracy | Check Functional Property for Linked Open Vocabularies (LOV) took 0.7469785213470459s
Accuracy | Check Inverse Functional Property for Linked Open Vocabularies (LOV) took 0.2719111442565918s
Accuracy | Check Empty annotation labels for Linked Open Vocabularies (LOV) took 7.782105445861816s
Accuracy | Check White space in annotation for Linked Open Vocabularies (LOV) took 0.6867852210998535s
Accuracy | Check Datatype consistency for Linked Open Vocabularies (LOV) took 4.680381536483765s
Consistency | Disjoint class check for Linked Open Vocabularies (LOV) took 0.5496575832366943s
Consistency | Check Misplaced properties for Linked Open Vocabularies (LOV) took 7.887214660644531s
Consistency | Misplaced classes for Linked Open Vocabularies (LOV) took 0.39272570610046387s
Consistency | Check Ontology hijacking for Linked Open Vocabularies (LOV) took 5.938307762145996s
Consistency | Check Invalid usage of undefined classes for Linked Open Vocabularies (LOV) took 1.249830722808838s
Conciseness | Check Extensional conciseness for Linked Open Vocabularies (LOV) took 2.8384575843811035s
Conciseness | Check Intensional conciseness for Linked Open Vocabularies (LOV) took 2.4852144718170166s
Security | Sign check for Linked Open Vocabularies (LOV) took 0.24472284317016602s
Availability | Check URIs Dereferenciability for Linked Open Vocabularies (LOV) took 5647.74807715416s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.713857889175415s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.021606922149658203s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 6.604194641113281e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 6.222724914550781e-05s
Interoperability | Check the re-using of existing vocabs for Linked Open Vocabularies (LOV) took 19.0761878490448s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.3589859008789062e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 6702.6223175525665s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 9.083747863769531e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.2862536907196045s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.021474599838256836s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0009229183197021484s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 5.1021575927734375e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 5.7220458984375e-06s
INFO | --- Analysis for linked-periodicals took 3.0606307983398438s
Availability | SPARQL endpoint availability check for Linked Index took 4.363059997558594e-05s
Availability | VoID file availability check for Linked Index took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for Linked Index took 0.3304710388183594s
Reputation | Calculation of the PageRank for Linked Index took 0.02108144760131836s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.273124694824219e-05s
Believability | Calculation of trust value for Linked Index took 1.1205673217773438e-05s
INFO | --- Analysis for linked-stockindex took 3.3353443145751953s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 5.480019569396973s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.3009908199310303s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.020775556564331055s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.814697265625e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.049041748046875e-05s
INFO | --- Analysis for linked-structured-product-labels took 19.546284198760986s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.32279300689697266s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0004184246063232422s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.2963526248931885s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.021074295043945312s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.4809112548828125e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 1.2636184692382812e-05s
INFO | --- Analysis for linked-taiwan-geo-names took 3.344233989715576s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.279273748397827s
Availability | VoID file availability check for Linked TCGA took 0.000982522964477539s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.3229045867919922s
Reputation | Calculation of the PageRank for Linked TCGA took 0.020856380462646484s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.58306884765625e-05s
Believability | Calculation of trust value for Linked TCGA took 1.239776611328125e-05s
INFO | --- Analysis for linked-tcga took 63.15284466743469s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.08802437782287598s
Availability | VoID file availability check for Linked User Feedback took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.3314552307128906s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.02294635772705078s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.814697265625e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.0251998901367188e-05s
INFO | --- Analysis for linked-user-feedback took 2.870684862136841s
Availability | SPARQL endpoint availability check for USPTO Patent data took 8.630752563476562e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0008096694946289062s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.2982900142669678s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.021336793899536133s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 8.082389831542969e-05s
Believability | Calculation of trust value for USPTO Patent data took 1.049041748046875e-05s
INFO | --- Analysis for linked-uspto-patent-data took 53.3969087600708s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.0774083137512207s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.32204699516296387s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.02264404296875s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.5762786865234375e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.0728836059570312e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 3.1816015243530273s
Availability | SPARQL endpoint availability check for LinkedCT took 1.549654483795166s
Availability | VoID file availability check for LinkedCT took 0.0012791156768798828s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.3114638328552246s
Reputation | Calculation of the PageRank for LinkedCT took 0.021170616149902344s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.00010180473327636719s
Believability | Calculation of trust value for LinkedCT took 6.67572021484375e-06s
INFO | --- Analysis for linkedct took 5.627457618713379s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.1633758544921875s
Availability | VoID file availability check for LinkedGeoData took 0.00029349327087402344s
Extra | Recovery of all triples for LinkedGeoData took 7.405981779098511s
Performance | Total latancy measurement for LinkedGeoData took 0.6507275104522705s
Amount of data | Number of triples check for LinkedGeoData took 51.80850410461426s
Interoperability | New terms check for LinkedGeoData took 90.70268964767456s
Versatility | Languages check for LinkedGeoData took 180.37193751335144s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.21864533424377441s
Security | Check HTTPS for LinkedGeoData took 0.31613755226135254s
Interpretability | RDF structures check for LinkedGeoData took 0.1715097427368164s
Versatility | Serialization formats check for LinkedGeoData took 0.15889954566955566s
Availability | RDF dump link check for LinkedGeoData took 0.12518572807312012s
License | MR license check for LinkedGeoData took 0.12328243255615234s
License | HR license check for LinkedGeoData took 94.12930369377136s
Amount of data | Number of property check for LinkedGeoData took 0.15621471405029297s
Understandability | Number of label check for LinkedGeoData took 1.0207650661468506s
Understandability | URI regex check for LinkedGeoData took 0.293992280960083s
Understandability | Vocabs check for LinkedGeoData took 0.17069244384765625s
Verifiability | Authors check for LinkedGeoData took 0.13833999633789062s
Verifiability | Publishers check for LinkedGeoData took 0.11966538429260254s
Performance | Throughput check for LinkedGeoData took 10.54481840133667s
Amount of data | Check the number of entities for LinkedGeoData took 0.06255722045898438s
Verifiability | Contribs. check for LinkedGeoData took 0.12067341804504395s
Interlinking | sameAs chians check for LinkedGeoData took 0.19563055038452148s
Interlinking | skos check for LinkedGeoData took 0.18592524528503418s
Interlinking | skos check for LinkedGeoData took 0.1192939281463623s
Timeliness | dataset update frequency check for LinkedGeoData took 0.1310122013092041s
Currency | Creation date check for LinkedGeoData took 0.28455376625061035s
Currency | Modification date check for LinkedGeoData took 0.29850077629089355s
Rep.Conc. | URIs length for LinkedGeoData took 271.176255941391s
Interoperability | New vocabularies check for LinkedGeoData took 17.764943838119507s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.15879130363464355s
Accuracy | Check Functional Property for LinkedGeoData took 0.16030335426330566s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.13253569602966309s
Accuracy | Check Empty annotation labels for LinkedGeoData took 1.8281075954437256s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15886855125427246s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.13206100463867188s
Consistency | Disjoint class check for LinkedGeoData took 0.1377103328704834s
Consistency | Check Misplaced properties for LinkedGeoData took 182.04632210731506s
Consistency | Misplaced classes for LinkedGeoData took 0.7666759490966797s
Consistency | Check Ontology hijacking for LinkedGeoData took 3.461883783340454s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.1551287174224854s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 182.56705570220947s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.14821529388427734s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.3016245365142822s
Security | Sign check for LinkedGeoData took 0.1551046371459961s
Availability | Check URIs Dereferenciability for LinkedGeoData took 22.86174488067627s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.4110863208770752s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.022191524505615234s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.0001323223114013672s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 18.056535482406616s
Believability | Calculation of trust value for LinkedGeoData took 1.1205673217773438e-05s
INFO | --- Analysis for linkedgeodata took 2186.72859787941s
Availability | SPARQL endpoint availability check for LinkedLCCN took 10.114669561386108s
Availability | VoID file availability check for LinkedLCCN took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.32819581031799316s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.02118849754333496s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0010251998901367188s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00012683868408203125s
Believability | Calculation of trust value for LinkedLCCN took 1.1920928955078125e-05s
INFO | --- Analysis for linkedlccn took 27.553937911987305s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.1961669921875e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.3084700107574463s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.02220320701599121s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.600120544433594e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.2636184692382812e-05s
INFO | --- Analysis for linkedmarkmail took 2.9961655139923096s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.61989784240723s
Availability | VoID file availability check for Linked Movie DataBase took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.3195011615753174s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.02101755142211914s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00013256072998046875s
Believability | Calculation of trust value for Linked Movie DataBase took 1.2159347534179688e-05s
INFO | --- Analysis for linkedmdb took 133.70967030525208s
Availability | SPARQL endpoint availability check for LinkedSpending took 0.5359096527099609s
Availability | VoID file availability check for LinkedSpending took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for LinkedSpending took 0.3169736862182617s
Reputation | Calculation of the PageRank for LinkedSpending took 0.0205078125s
Interlinking | Calculation of Degree of Connection for LinkedSpending took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LinkedSpending took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for LinkedSpending took 7.152557373046875e-05s
Believability | Calculation of trust value for LinkedSpending took 9.775161743164062e-06s
INFO | --- Analysis for linkedspending took 4.47974967956543s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.11384296417236328s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0010318756103515625s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.2884526252746582s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.021823406219482422s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00012731552124023438s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.2159347534179688e-05s
INFO | --- Analysis for linklion took 2.801306962966919s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 320.29419469833374s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.3462193012237549s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020981788635253906s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.9604644775390625e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 1.0967254638671875e-05s
INFO | --- Analysis for lista-encabezamientos-materia took 625.0175211429596s
Availability | SPARQL endpoint availability check for lobid-organisations took 0.9573650360107422s
Availability | VoID file availability check for lobid-organisations took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.3198990821838379s
Reputation | Calculation of the PageRank for lobid-organisations took 0.023639917373657227s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.870529174804688e-05s
Believability | Calculation of trust value for lobid-organisations took 1.33514404296875e-05s
INFO | --- Analysis for lobid-organisations took 5.7292702198028564s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.7997288703918457s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.27443456649780273s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.021924257278442383s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00010085105895996094s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 1.0728836059570312e-05s
INFO | --- Analysis for lobid-resources took 7.302987813949585s
Availability | SPARQL endpoint availability check for Linked Open Colors took 8.535385131835938e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.2993319034576416s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.021982908248901367s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 7.367134094238281e-05s
Believability | Calculation of trust value for Linked Open Colors took 1.33514404296875e-05s
INFO | --- Analysis for loc took 7.318933963775635s
Availability | SPARQL endpoint availability check for Location Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Location Ontology took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.3083159923553467s
Reputation | Calculation of the PageRank for Location Ontology took 0.021108150482177734s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.504753112792969e-05s
Believability | Calculation of trust value for Location Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for Location_Ontology took 4.377809762954712s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 8.606910705566406e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0004184246063232422s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.2983567714691162s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.021520376205444336s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.62396240234375e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 1.1205673217773438e-05s
INFO | --- Analysis for locv took 33.790136098861694s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7490191459655762s
Availability | VoID file availability check for LOD-a-lot took 0.0007622241973876953s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.2892954349517822s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.147125244140625e-05s
Believability | Calculation of trust value for LOD-a-lot took 1.0967254638671875e-05s
INFO | --- Analysis for lod-a-lot took 14.2279691696167s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.220008850097656e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.3296239376068115s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.02132701873779297s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.749961853027344e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 1.1682510375976562e-05s
INFO | --- Analysis for lod2-project-wiki took 3.607187271118164s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.6306650638580322s
Availability | VoID file availability check for LODAC BDLS took 0.0012192726135253906s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.300457239151001s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.022069931030273438s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.128715515136719e-05s
Believability | Calculation of trust value for LODAC BDLS took 9.775161743164062e-06s
INFO | --- Analysis for lodac-bdls took 13.930898904800415s
Availability | SPARQL endpoint availability check for lofd took 0.1435556411743164s
Availability | VoID file availability check for lofd took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for lofd took 0.29672980308532715s
Reputation | Calculation of the PageRank for lofd took 0.02097606658935547s
Interlinking | Calculation of Degree of Connection for lofd took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for lofd took 3.147125244140625e-05s
Believability | Calculation of trust value for lofd took 1.0251998901367188e-05s
INFO | --- Analysis for lofd took 2.9405176639556885s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 272.02126812934875s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.2952909469604492s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.02146768569946289s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.7220458984375e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 8.106231689453125e-06s
INFO | --- Analysis for loius took 586.1556174755096s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.6276769638061523s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.2900068759918213s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.022990942001342773s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.173683166503906e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 4.76837158203125e-06s
INFO | --- Analysis for london-gazette took 4.3291966915130615s
Availability | SPARQL endpoint availability check for Weather Stations took 8.654594421386719e-05s
Availability | VoID file availability check for Weather Stations took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.3008463382720947s
Reputation | Calculation of the PageRank for Weather Stations took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.082389831542969e-05s
Believability | Calculation of trust value for Weather Stations took 1.1682510375976562e-05s
INFO | --- Analysis for los_metar took 10.746049880981445s
Availability | SPARQL endpoint availability check for Lotico took 0.9095160961151123s
Availability | VoID file availability check for Lotico took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for Lotico took 0.3052213191986084s
Reputation | Calculation of the PageRank for Lotico took 0.021053552627563477s
Interlinking | Calculation of Degree of Connection for Lotico took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.249282836914062e-05s
Believability | Calculation of trust value for Lotico took 1.1682510375976562e-05s
INFO | --- Analysis for lotico took 6.755321264266968s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.3488950729370117s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0006847381591796875s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 1.4950823783874512s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 0.821746826171875s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.24292540550231934s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.564408302307129s
Versatility | Languages check for Lower Layer Super Output Areas took 0.40502262115478516s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 30.209430694580078s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.1294705867767334s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.33510684967041016s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.23864293098449707s
Availability | RDF dump link check for Lower Layer Super Output Areas took 56.41518568992615s
License | MR license check for Lower Layer Super Output Areas took 0.25444984436035156s
License | HR license check for Lower Layer Super Output Areas took 30.173550605773926s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.16168427467346191s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.324540376663208s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.28280067443847656s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.14911317825317383s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.12836027145385742s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.27432918548583984s
Performance | Throughput check for Lower Layer Super Output Areas took 11.297829866409302s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 7.62939453125e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.12561893463134766s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.3370213508605957s
Interlinking | skos check for Lower Layer Super Output Areas took 0.25298595428466797s
Interlinking | skos check for Lower Layer Super Output Areas took 0.1585853099822998s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.19820308685302734s
Currency | Creation date check for Lower Layer Super Output Areas took 0.3262145519256592s
Currency | Modification date check for Lower Layer Super Output Areas took 0.3015868663787842s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 1.3550615310668945s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.7314791679382324s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.1553022861480713s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.13393020629882812s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.2645275592803955s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 0.6375393867492676s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 1.6270432472229004s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.3503081798553467s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.00014710426330566406s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.4566681385040283s
Security | Sign check for Lower Layer Super Output Areas took 0.22322416305541992s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.3490331172943115s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.022054433822631836s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 4.076957702636719e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 1.430511474609375e-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.16218185424805s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9000895023345947s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.29500246047973633s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.020898818969726562s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.314018249511719e-05s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1205673217773438e-05s
INFO | --- Analysis for LPIS_(Poland) took 4.261615037918091s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5920975208282471s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.000579833984375s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.28701281547546387s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.021432161331176758s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.9087066650390625e-05s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 3.9671120643615723s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.482269287109375e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.2980191707611084s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.021860122680664062s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.409385681152344e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 1.3589859008789062e-05s
INFO | --- Analysis for lremap-auth took 3.339221715927124s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.267692565917969e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.29270267486572266s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.020900964736938477s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.147125244140625e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.2636184692382812e-05s
INFO | --- Analysis for lremap-conf took 3.028614044189453s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 8.273124694824219e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.2958540916442871s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.0211789608001709s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 2.9325485229492188e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.0967254638671875e-05s
INFO | --- Analysis for lremap-ri took 2.9864797592163086s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 8.463859558105469e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.2796316146850586s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.022370576858520508s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007224082946777344s
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.2636184692382812e-05s
INFO | --- Analysis for lremap-sub took 2.9520423412323s
Availability | SPARQL endpoint availability check for LSQ took 4.172325134277344e-05s
Availability | VoID file availability check for LSQ took 0.000640869140625s
Completeness | Calculation of interlinking completeness for LSQ took 0.2667272090911865s
Reputation | Calculation of the PageRank for LSQ took 0.020962953567504883s
Interlinking | Calculation of Degree of Connection for LSQ took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.075599670410156e-05s
Believability | Calculation of trust value for LSQ took 1.33514404296875e-05s
INFO | --- Analysis for lsq took 3.8216466903686523s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.6167664527893066s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.2670872211456299s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.02191781997680664s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 5.1021575927734375e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for LucaniPharsalia took 4.39113187789917s
Availability | SPARQL endpoint availability check for Linked rules took 9.393692016601562e-05s
Availability | VoID file availability check for Linked rules took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Linked rules took 0.2943105697631836s
Reputation | Calculation of the PageRank for Linked rules took 0.020968198776245117s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.3855438232421875e-05s
Believability | Calculation of trust value for Linked rules took 1.239776611328125e-05s
INFO | --- Analysis for Luminaires_senlis took 2.7044472694396973s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.324340343475342s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.2964599132537842s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020949602127075195s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 2.9802322387695312e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 1.0013580322265625e-05s
INFO | --- Analysis for makg took 63.618590354919434s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.2438507080078125e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.2981886863708496s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.020760297775268555s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.4809112548828125e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 1.1444091796875e-05s
INFO | --- Analysis for manchester-university-reading-lists took 5.6119749546051025s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 8.368492126464844e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.301025390625s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020712852478027344s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 2.8371810913085938e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.1205673217773438e-05s
INFO | --- Analysis for manish took 2.690114736557007s
Availability | SPARQL endpoint availability check for MARC Codes List took 0.00011420249938964844s
Availability | VoID file availability check for MARC Codes List took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.3049044609069824s
Reputation | Calculation of the PageRank for MARC Codes List took 0.02205967903137207s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00012874603271484375s
Believability | Calculation of trust value for MARC Codes List took 1.1205673217773438e-05s
INFO | --- Analysis for marc-codes took 13.354638814926147s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 8.678436279296875e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0011615753173828125s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.39417195320129395s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.814697265625e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.1920928955078125e-05s
INFO | --- Analysis for masc took 6.198292016983032s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 8.797645568847656e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.3004322052001953s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.022264480590820312s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.62396240234375e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.1205673217773438e-05s
INFO | --- Analysis for masc-bn-nif took 2.7973079681396484s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.2234234809875488s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.26864075660705566s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.0208437442779541s
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.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 2.7894973754882812e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 7.152557373046875e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 4.148784160614014s
Availability | SPARQL endpoint availability check for medline took 8.559226989746094e-05s
Availability | VoID file availability check for medline took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for medline took 0.3450181484222412s
Reputation | Calculation of the PageRank for medline took 0.022627592086791992s
Interlinking | Calculation of Degree of Connection for medline took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for medline took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for medline took 3.314018249511719e-05s
Believability | Calculation of trust value for medline took 1.049041748046875e-05s
INFO | --- Analysis for medline took 7.246048212051392s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.5899109840393066s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.276761531829834s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.02076244354248047s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.67572021484375e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 7.152557373046875e-06s
INFO | --- Analysis for meducator took 11.16760778427124s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.267692565917969e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.3078439235687256s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.020496129989624023s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 6.747245788574219e-05s
Believability | Calculation of trust value for MetaShare metadata model took 1.1682510375976562e-05s
INFO | --- Analysis for metashare took 2.715505361557007s
Availability | SPARQL endpoint availability check for MExiCo took 4.315376281738281e-05s
Availability | VoID file availability check for MExiCo took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for MExiCo took 0.3302345275878906s
Reputation | Calculation of the PageRank for MExiCo took 0.021228551864624023s
Interlinking | Calculation of Degree of Connection for MExiCo took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MExiCo took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for MExiCo took 5.316734313964844e-05s
Believability | Calculation of trust value for MExiCo took 1.0967254638671875e-05s
INFO | --- Analysis for mexico took 23.05512046813965s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.0362684726715088s
Availability | VoID file availability check for Coronavirus dataset took 0.0010387897491455078s
Extra | Recovery of all triples for Coronavirus dataset took 6.038132667541504s
Performance | Total latancy measurement for Coronavirus dataset took 2.4998369216918945s
Amount of data | Number of triples check for Coronavirus dataset took 1.2304463386535645s
Interoperability | New terms check for Coronavirus dataset took 2.500901222229004s
Versatility | Languages check for Coronavirus dataset took 60.53108310699463s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.663351058959961s
Interpretability | RDF structures check for Coronavirus dataset took 0.5493776798248291s
Versatility | Serialization formats check for Coronavirus dataset took 0.5535459518432617s
Availability | RDF dump link check for Coronavirus dataset took 0.49695873260498047s
License | MR license check for Coronavirus dataset took 0.5615808963775635s
License | HR license check for Coronavirus dataset took 42.26830339431763s
Amount of data | Number of property check for Coronavirus dataset took 0.5370578765869141s
Understandability | Number of label check for Coronavirus dataset took 1.415649652481079s
Understandability | URI regex check for Coronavirus dataset took 0.9944980144500732s
Understandability | Vocabs check for Coronavirus dataset took 0.4925403594970703s
Verifiability | Authors check for Coronavirus dataset took 0.529604434967041s
Verifiability | Publishers check for Coronavirus dataset took 0.49919581413269043s
Performance | Throughput check for Coronavirus dataset took 13.923409223556519s
Amount of data | Check the number of entities for Coronavirus dataset took 0.00010180473327636719s
Verifiability | Contribs. check for Coronavirus dataset took 0.4973886013031006s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5343887805938721s
Interlinking | skos check for Coronavirus dataset took 0.5857007503509521s
Interlinking | skos check for Coronavirus dataset took 0.5003743171691895s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.5070884227752686s
Currency | Creation date check for Coronavirus dataset took 1.0253729820251465s
Currency | Modification date check for Coronavirus dataset took 1.035045862197876s
Rep.Conc. | URIs length for Coronavirus dataset took 8.302473306655884s
Interoperability | New vocabularies check for Coronavirus dataset took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5497329235076904s
Accuracy | Check Functional Property for Coronavirus dataset took 0.792504072189331s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.5446796417236328s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.080379009246826s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.022399187088012695s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.027587413787841797s
Consistency | Disjoint class check for Coronavirus dataset took 1.0857372283935547s
Consistency | Check Misplaced properties for Coronavirus dataset took 7.479988098144531s
Consistency | Misplaced classes for Coronavirus dataset took 0.613670825958252s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.2632172107696533s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.1486315727233887s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.500594139099121s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.034201622009277344s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.525475263595581s
Security | Sign check for Coronavirus dataset took 0.518989086151123s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3189.5900700092316s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.7337863445281982s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.031615257263183594s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for Coronavirus dataset took 1.1682510375976562e-05s
INFO | --- Analysis for micro-coronavirus took 3431.7736909389496s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 4.410743713378906e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.3475944995880127s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.021517276763916016s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010085105895996094s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 8.106231689453125e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 6.694082975387573s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 8.797645568847656e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.29718756675720215s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020947694778442383s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00011157989501953125s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.1205673217773438e-05s
INFO | --- Analysis for mismuseos-gnoss took 8.811545610427856s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.11013960838317871s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.2945382595062256s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.022072315216064453s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.172325134277344e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.0251998901367188e-05s
INFO | --- Analysis for mlsa took 3.378948450088501s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 8.463859558105469e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.2877676486968994s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020737409591674805s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 2.8371810913085938e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 1.1682510375976562e-05s
INFO | --- Analysis for model took 32.65130090713501s
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 9.012222290039062e-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.0006282329559326172s
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.3080296516418457s
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.021172523498535156s
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.049041748046875e-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.0007045269012451172s
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 2.9087066650390625e-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.2636184692382812e-05s
INFO | --- Analysis for model1 took 20.78401756286621s
Availability | SPARQL endpoint availability check for MORElab took 0.9996469020843506s
Availability | VoID file availability check for MORElab took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for MORElab took 0.32128262519836426s
Reputation | Calculation of the PageRank for MORElab took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for MORElab took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.416175842285156e-05s
Believability | Calculation of trust value for MORElab took 1.2159347534179688e-05s
INFO | --- Analysis for morelab took 5.758772611618042s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 2.0070934295654297s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.2969634532928467s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.021120548248291016s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.869171142578125e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 1.1205673217773438e-05s
INFO | --- Analysis for msc took 16.95641541481018s
Availability | SPARQL endpoint availability check for Multext-East took 9.489059448242188e-05s
Availability | VoID file availability check for Multext-East took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for Multext-East took 0.27578115463256836s
Reputation | Calculation of the PageRank for Multext-East took 0.02145838737487793s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.4809112548828125e-05s
Believability | Calculation of trust value for Multext-East took 1.049041748046875e-05s
INFO | --- Analysis for multext-east took 2.7314913272857666s
Availability | SPARQL endpoint availability check for Multimedia Lab took 8.654594421386719e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.2803459167480469s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.02098369598388672s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.62396240234375e-05s
Believability | Calculation of trust value for Multimedia Lab took 1.0013580322265625e-05s
INFO | --- Analysis for multimedia-lab took 2.734849214553833s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.7830138206481934s
Availability | VoID file availability check for Muninn World War I took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.2814767360687256s
Reputation | Calculation of the PageRank for Muninn World War I took 0.0217282772064209s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0011470317840576172s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 0.00014519691467285156s
Believability | Calculation of trust value for Muninn World War I took 1.2159347534179688e-05s
INFO | --- Analysis for muninn-world-war-i took 11.2344810962677s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 9.489059448242188e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.2929208278656006s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.021386146545410156s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00010776519775390625s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.049041748046875e-05s
INFO | --- Analysis for museosespania-gnoss took 61.8135781288147s
Availability | SPARQL endpoint availability check for Italian Museums took 0.4297523498535156s
Availability | VoID file availability check for Italian Museums took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.27457523345947266s
Reputation | Calculation of the PageRank for Italian Museums took 0.0223691463470459s
Interlinking | Calculation of Degree of Connection for Italian Museums took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 7.891654968261719e-05s
Believability | Calculation of trust value for Italian Museums took 9.775161743164062e-06s
INFO | --- Analysis for museums-in-italy took 3.2528371810913086s
Availability | SPARQL endpoint availability check for Muziekweb took 0.7504727840423584s
Availability | VoID file availability check for Muziekweb took 0.0006062984466552734s
Extra | Recovery of all triples for Muziekweb took 1.609212875366211s
Performance | Total latancy measurement for Muziekweb took 1.620757818222046s
Amount of data | Number of triples check for Muziekweb took 0.38996148109436035s
Interoperability | New terms check for Muziekweb took 1.5305149555206299s
Versatility | Languages check for Muziekweb took 54.79309701919556s
Interpretability | Number of blank nodes check for Muziekweb took 0.33875322341918945s
Interpretability | RDF structures check for Muziekweb took 0.30748581886291504s
Versatility | Serialization formats check for Muziekweb took 0.35222887992858887s
Availability | RDF dump link check for Muziekweb took 0.339123010635376s
License | MR license check for Muziekweb took 0.38150739669799805s
License | HR license check for Muziekweb took 11.672708511352539s
Amount of data | Number of property check for Muziekweb took 0.3416633605957031s
Understandability | Number of label check for Muziekweb took 0.46170759201049805s
Understandability | URI regex check for Muziekweb took 0.7118053436279297s
Understandability | Vocabs check for Muziekweb took 0.35776424407958984s
Verifiability | Authors check for Muziekweb took 0.33564186096191406s
Verifiability | Publishers check for Muziekweb took 0.33393049240112305s
Performance | Throughput check for Muziekweb took 12.920948266983032s
Amount of data | Check the number of entities for Muziekweb took 6.699562072753906e-05s
Verifiability | Contribs. check for Muziekweb took 0.33406567573547363s
Interlinking | sameAs chians check for Muziekweb took 0.39061546325683594s
Interlinking | skos check for Muziekweb took 0.3443295955657959s
Interlinking | skos check for Muziekweb took 0.2998049259185791s
Timeliness | dataset update frequency check for Muziekweb took 0.3243417739868164s
Currency | Creation date check for Muziekweb took 0.8667480945587158s
Currency | Modification date check for Muziekweb took 0.9030287265777588s
Rep.Conc. | URIs length for Muziekweb took 1.901681900024414s
Interoperability | New vocabularies check for Muziekweb took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.3217611312866211s
Accuracy | Check Empty annotation labels for Muziekweb took 0.9554927349090576s
Accuracy | Check White space in annotation for Muziekweb took 0.03674602508544922s
Accuracy | Check Datatype consistency for Muziekweb took 0.029613494873046875s
Consistency | Disjoint class check for Muziekweb took 0.559429407119751s
Consistency | Check Misplaced properties for Muziekweb took 1.2366063594818115s
Consistency | Check Ontology hijacking for Muziekweb took 1.926525592803955s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.1486599445343018s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.449939489364624s
Conciseness | Check Extensional conciseness for Muziekweb took 0.033944129943847656s
Conciseness | Check Intensional conciseness for Muziekweb took 0.3384435176849365s
Security | Sign check for Muziekweb took 0.3410677909851074s
Availability | Check URIs Dereferenciability for Muziekweb took 2275.433094739914s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.532062292098999s
Reputation | Calculation of the PageRank for Muziekweb took 0.021146535873413086s
Interlinking | Calculation of Degree of Connection for Muziekweb took 6.556510925292969e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 5.936622619628906e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.430511474609375e-06s
Believability | Calculation of trust value for Muziekweb took 1.1920928955078125e-05s
INFO | --- Analysis for muziekweb took 2405.780841588974s
Availability | SPARQL endpoint availability check for myExperiment took 0.5467827320098877s
Availability | VoID file availability check for myExperiment took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for myExperiment took 0.3451216220855713s
Reputation | Calculation of the PageRank for myExperiment took 0.02153301239013672s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00011587142944335938s
Believability | Calculation of trust value for myExperiment took 1.239776611328125e-05s
INFO | --- Analysis for my-experiment took 8.44796347618103s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.08425045013427734s
Availability | VoID file availability check for My Family Lineage took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.27341294288635254s
Reputation | Calculation of the PageRank for My Family Lineage took 0.021678447723388672s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 9.274482727050781e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 9.179115295410156e-05s
Believability | Calculation of trust value for My Family Lineage took 1.2636184692382812e-05s
INFO | --- Analysis for my-family-lineage took 5.020862579345703s
Availability | SPARQL endpoint availability check for My ontology test took 2.9774482250213623s
Availability | VoID file availability check for My ontology test took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for My ontology test took 0.29528260231018066s
Reputation | Calculation of the PageRank for My ontology test took 0.02147364616394043s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.0994415283203125e-05s
Believability | Calculation of trust value for My ontology test took 1.2159347534179688e-05s
INFO | --- Analysis for myontologytest took 6.171781778335571s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 9.131431579589844e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.2825484275817871s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.02084970474243164s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.00010538101196289062s
Believability | Calculation of trust value for myopenlink dataspaces took 1.0013580322265625e-05s
INFO | --- Analysis for myopenlink-dataspaces took 3.2487952709198s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 7.232917308807373s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.4502143859863281s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.023474454879760742s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.747245788574219e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for n-lex-as-linked-data took 17.79088258743286s
Availability | SPARQL endpoint availability check for NAICS 2007 took 27.350008249282837s
Availability | VoID file availability check for NAICS 2007 took 0.0009429454803466797s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.30210304260253906s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.021857738494873047s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.696846008300781e-05s
Believability | Calculation of trust value for NAICS 2007 took 8.58306884765625e-06s
INFO | --- Analysis for naics-2007 took 126.21336054801941s
Availability | SPARQL endpoint availability check for NAICS 2012 took 25.586681127548218s
Availability | VoID file availability check for NAICS 2012 took 0.0008635520935058594s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.36577510833740234s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.023000478744506836s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 4.744529724121094e-05s
Believability | Calculation of trust value for NAICS 2012 took 8.106231689453125e-06s
INFO | --- Analysis for naics-2012 took 124.14180898666382s
Availability | SPARQL endpoint availability check for Usernames  took 4.410743713378906e-05s
Availability | VoID file availability check for Usernames  took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Usernames  took 0.3060603141784668s
Reputation | Calculation of the PageRank for Usernames  took 0.021248340606689453s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.266334533691406e-05s
Believability | Calculation of trust value for Usernames  took 1.1444091796875e-05s
INFO | --- Analysis for Names took 2.8448069095611572s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 0.9384779930114746s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0007674694061279297s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 2.472877025604248s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 3.153109312057495s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.296506404876709s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 14.508537769317627s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.7926702499389648s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.912314653396606s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.32532644271850586s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.38120007514953613s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.3779447078704834s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.7935488224029541s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.3703453540802002s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.35764384269714s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.44454360008239746s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 5.956168174743652s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.7715859413146973s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.38419008255004883s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.8415467739105225s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.3868718147277832s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.903634786605835s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 8.463859558105469e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.3922288417816162s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.936469316482544s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.5772018432617188s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.0350735187530518s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.3700985908508301s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.5733399391174316s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 1.1749536991119385s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 0.785609245300293s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.3775060176849365s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.41446375846862793s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.36441731452941895s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.39083099365234375s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007672309875488281s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0010099411010742188s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.3440389633178711s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.7751631736755371s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.35781025886535645s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.5367670059204102s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.1685152053833008s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.5851409435272217s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0006556510925292969s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.3816370964050293s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 5.4825239181518555s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.30048203468322754s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.021215200424194336s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 7.104873657226562e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.1920928955078125e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 9.059906005859375e-06s
INFO | --- Analysis for national-diet-library-authorities took 235.9472484588623s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.3457489013671875s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0006105899810791016s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 0.9316506385803223s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 2.742347002029419s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.505645275115967s
Interoperability | New terms check for National Diet Library of Japan subject headings took 14.911661148071289s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.382138729095459s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.412472248077393s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.3873915672302246s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.356095552444458s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.3497128486633301s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.36716270446777344s
License | MR license check for National Diet Library of Japan subject headings took 0.3734745979309082s
License | HR license check for National Diet Library of Japan subject headings took 90.85740804672241s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8279592990875244s
Understandability | Number of label check for National Diet Library of Japan subject headings took 4.807437896728516s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.7612428665161133s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.777087926864624s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.3605325222015381s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.8241887092590332s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.607042074203491s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.177757263183594e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.369016170501709s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.4737122058868408s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.341749668121338s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.2606556415557861s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.36148810386657715s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.5576989650726318s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.7576508522033691s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.6766848564147949s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.364119291305542s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.8217155933380127s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.3704233169555664s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.36017799377441406s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007326602935791016s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0010366439819335938s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.34216856956481934s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.7483060359954834s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.3296215534210205s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.542515754699707s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.1291797161102295s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.9405834674835205s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0007007122039794922s
Security | Sign check for National Diet Library of Japan subject headings took 0.3790566921234131s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 5.4754862785339355s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.32736992835998535s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.023268461227416992s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 6.222724914550781e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 9.775161743164062e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 227.61671686172485s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.1817803382873535s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.29195165634155273s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.02066516876220703s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.3392181396484375e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 8.344650268554688e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 5.779376268386841s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.4345855712890625e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.3254272937774658s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02267313003540039s
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.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.794929504394531e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.33514404296875e-05s
INFO | --- Analysis for Naturopathy took 3.397103786468506s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.442216634750366s
Availability | VoID file availability check for COVID-19 Data took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.31572532653808594s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.022729873657226562s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.075599670410156e-05s
Believability | Calculation of trust value for COVID-19 Data took 5.7220458984375e-06s
INFO | --- Analysis for NCMI-COVID-19 took 7.8835389614105225s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.382327079772949s
Availability | VoID file availability check for NCMI-COVID-19 took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.29077959060668945s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.239776611328125e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 1.0251998901367188e-05s
INFO | --- Analysis for NCMICOVID-19 took 7.871195077896118s
Availability | SPARQL endpoint availability check for Near took 8.845329284667969e-05s
Availability | VoID file availability check for Near took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Near took 0.325977087020874s
Reputation | Calculation of the PageRank for Near took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for Near took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Near took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Near took 9.489059448242188e-05s
Believability | Calculation of trust value for Near took 1.0967254638671875e-05s
INFO | --- Analysis for near took 8.563362836837769s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 0.00011587142944335938s
Availability | VoID file availability check for NeuroLex Wiki took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.3259098529815674s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.021577835083007812s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.147125244140625e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.1444091796875e-05s
INFO | --- Analysis for neurolex-wiki took 2.8569395542144775s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 4.291534423828125e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.28908848762512207s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.02074408531188965s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.5299530029296875e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 1.0728836059570312e-05s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 4.990686416625977s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 8.797645568847656e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.31259918212890625s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.02079296112060547s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.699562072753906e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 1.239776611328125e-05s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.40339207649231s
Availability | SPARQL endpoint availability check for neXtProt took 1.752725601196289s
Availability | VoID file availability check for neXtProt took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for neXtProt took 0.2831251621246338s
Reputation | Calculation of the PageRank for neXtProt took 0.021369218826293945s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.719329833984375e-05s
Believability | Calculation of trust value for neXtProt took 1.049041748046875e-05s
INFO | --- Analysis for nextprot took 5.171173572540283s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.649162292480469e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0008234977722167969s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.5649027824401855s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.021485090255737305s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010514259338378906s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.1205673217773438e-05s
INFO | --- Analysis for nextweb-gnoss took 511.8929855823517s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.1961669921875e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.2976706027984619s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.022075176239013672s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 7.987022399902344e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 8.821487426757812e-06s
INFO | --- Analysis for nhs-jargon took 3.084516763687134s
Availability | SPARQL endpoint availability check for NIT Patna took 9.036064147949219e-05s
Availability | VoID file availability check for NIT Patna took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.3381309509277344s
Reputation | Calculation of the PageRank for NIT Patna took 0.02099299430847168s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.866455078125e-05s
Believability | Calculation of trust value for NIT Patna took 1.2636184692382812e-05s
INFO | --- Analysis for NITP took 3.579010248184204s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 8.630752563476562e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.3018147945404053s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.337860107421875e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for nlr-dataset-mod took 4.194381475448608s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.6638402938842773s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.2928168773651123s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.719329833984375e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 5.4836273193359375e-06s
INFO | --- Analysis for NLW took 4.5589025020599365s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.5522353649139404s
Availability | VoID file availability check for Nobel Prizes took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.3147299289703369s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.021883249282836914s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.1552734375e-05s
Believability | Calculation of trust value for Nobel Prizes took 1.0013580322265625e-05s
INFO | --- Analysis for nobelprizes took 9.543434143066406s
Availability | SPARQL endpoint availability check for NoiPA took 0.398967981338501s
Availability | VoID file availability check for NoiPA took 0.00023126602172851562s
Extra | Recovery of all triples for NoiPA took 1.8162167072296143s
Performance | Total latancy measurement for NoiPA took 0.8578305244445801s
Amount of data | Number of triples check for NoiPA took 1.5257458686828613s
Interoperability | New terms check for NoiPA took 2.7776150703430176s
Versatility | Languages check for NoiPA took 60.3695113658905s
Interpretability | Number of blank nodes check for NoiPA took 0.21764731407165527s
Interpretability | RDF structures check for NoiPA took 0.4679241180419922s
Versatility | Serialization formats check for NoiPA took 0.2226102352142334s
Availability | RDF dump link check for NoiPA took 0.28525304794311523s
License | MR license check for NoiPA took 0.7658991813659668s
License | HR license check for NoiPA took 60.272257804870605s
Amount of data | Number of property check for NoiPA took 0.2666811943054199s
Understandability | Number of label check for NoiPA took 0.8775224685668945s
Understandability | URI regex check for NoiPA took 0.6179592609405518s
Understandability | Vocabs check for NoiPA took 0.2394704818725586s
Verifiability | Authors check for NoiPA took 0.1672816276550293s
Verifiability | Publishers check for NoiPA took 0.2219233512878418s
Performance | Throughput check for NoiPA took 11.399341583251953s
Amount of data | Check the number of entities for NoiPA took 7.176399230957031e-05s
Verifiability | Contribs. check for NoiPA took 0.25110602378845215s
Interlinking | sameAs chians check for NoiPA took 0.11021113395690918s
Interlinking | skos check for NoiPA took 0.8613677024841309s
Interlinking | skos check for NoiPA took 0.20052433013916016s
Timeliness | dataset update frequency check for NoiPA took 0.15453195571899414s
Currency | Creation date check for NoiPA took 0.5090138912200928s
Currency | Modification date check for NoiPA took 0.16163396835327148s
Rep.Conc. | URIs length for NoiPA took 18.62723970413208s
Interoperability | New vocabularies check for NoiPA took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.25903940200805664s
Accuracy | Check Functional Property for NoiPA took 0.17420434951782227s
Accuracy | Check Inverse Functional Property for NoiPA took 0.20699119567871094s
Accuracy | Check Empty annotation labels for NoiPA took 0.40595364570617676s
Accuracy | Check White space in annotation for NoiPA took 0.026218891143798828s
Accuracy | Check Datatype consistency for NoiPA took 0.028171300888061523s
Consistency | Disjoint class check for NoiPA took 0.20241880416870117s
Consistency | Check Misplaced properties for NoiPA took 16.78521704673767s
Consistency | Misplaced classes for NoiPA took 0.27625226974487305s
Consistency | Check Ontology hijacking for NoiPA took 1.6619887351989746s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.1200189590454102s
Consistency | Check Invalid usage of undefined properties for NoiPA took 17.71522617340088s
Conciseness | Check Extensional conciseness for NoiPA took 0.03330492973327637s
Conciseness | Check Intensional conciseness for NoiPA took 0.15163779258728027s
Security | Sign check for NoiPA took 0.20442628860473633s
Availability | Check URIs Dereferenciability for NoiPA took 18.531062602996826s
Completeness | Calculation of interlinking completeness for NoiPA took 1.0041749477386475s
Reputation | Calculation of the PageRank for NoiPA took 0.021116971969604492s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for NoiPA took 3.504753112792969e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.1920928955078125e-06s
Believability | Calculation of trust value for NoiPA took 1.1205673217773438e-05s
INFO | --- Analysis for NoiPA took 508.5541536808014s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 1.1493761539459229s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.3213920593261719s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.020980119705200195s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.226799011230469e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.0013580322265625e-05s
INFO | --- Analysis for nom took 8.98282265663147s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 26.61135768890381s
Availability | VoID file availability check for Nomenclator Asturias took 0.0007736682891845703s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.2929213047027588s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.02094864845275879s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 7.891654968261719e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 5.9604644775390625e-06s
INFO | --- Analysis for nomenclator-asturias took 138.57571411132812s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.5515649318695068s
Availability | VoID file availability check for Nomisma.org  took 0.0005452632904052734s
Extra | Recovery of all triples for Nomisma.org  took 300.08280754089355s
Performance | Total latancy measurement for Nomisma.org  took 2.5351169109344482s
Amount of data | Number of triples check for Nomisma.org  took 40.081090450286865s
Interoperability | New terms check for Nomisma.org  took 6.9430320262908936s
Versatility | Languages check for Nomisma.org  took 109.82790780067444s
Interpretability | Number of blank nodes check for Nomisma.org  took 53.755109786987305s
Security | Check HTTPS for Nomisma.org  took 3.4081532955169678s
Interpretability | RDF structures check for Nomisma.org  took 0.7902462482452393s
Versatility | Serialization formats check for Nomisma.org  took 1.0757920742034912s
Availability | RDF dump link check for Nomisma.org  took 1660.3364734649658s
License | MR license check for Nomisma.org  took 0.8686614036560059s
License | HR license check for Nomisma.org  took 89.6124439239502s
Amount of data | Number of property check for Nomisma.org  took 1.1288163661956787s
Understandability | Number of label check for Nomisma.org  took 10.792629718780518s
Understandability | URI regex check for Nomisma.org  took 2.5725173950195312s
Understandability | Vocabs check for Nomisma.org  took 0.8301410675048828s
Verifiability | Authors check for Nomisma.org  took 0.574350118637085s
Verifiability | Publishers check for Nomisma.org  took 2.415440082550049s
Performance | Throughput check for Nomisma.org  took 14.037774562835693s
Amount of data | Check the number of entities for Nomisma.org  took 0.00010132789611816406s
Verifiability | Contribs. check for Nomisma.org  took 1.6344645023345947s
Interlinking | sameAs chians check for Nomisma.org  took 0.9786956310272217s
Interlinking | skos check for Nomisma.org  took 52.30149483680725s
Interlinking | skos check for Nomisma.org  took 30.975667715072632s
Timeliness | dataset update frequency check for Nomisma.org  took 1.8389616012573242s
Currency | Creation date check for Nomisma.org  took 1.7684121131896973s
Currency | Modification date check for Nomisma.org  took 1.5282118320465088s
Rep.Conc. | URIs length for Nomisma.org  took 351.82812690734863s
Interoperability | New vocabularies check for Nomisma.org  took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 2.0850679874420166s
Accuracy | Check Functional Property for Nomisma.org  took 1.1264088153839111s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 7.660345792770386s
Consistency | Disjoint class check for Nomisma.org  took 0.6997020244598389s
Consistency | Check Misplaced properties for Nomisma.org  took 42.64437508583069s
Consistency | Check Ontology hijacking for Nomisma.org  took 300.0400321483612s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 41.52791237831116s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.00016188621520996094s
Conciseness | Check Intensional conciseness for Nomisma.org  took 1.137988805770874s
Security | Sign check for Nomisma.org  took 0.521834135055542s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 0.7095918655395508s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.021576642990112305s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 4.839897155761719e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.430511474609375e-06s
Believability | Calculation of trust value for Nomisma.org  took 1.2159347534179688e-05s
INFO | --- Analysis for nomisma_org took 5806.5439512729645s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.39804649353027344s
Availability | VoID file availability check for Curriculum Vitae took 0.0005109310150146484s
Extra | Recovery of all triples for Curriculum Vitae took 0.48542046546936035s
Performance | Total latancy measurement for Curriculum Vitae took 1.009232521057129s
Amount of data | Number of triples check for Curriculum Vitae took 0.1389784812927246s
Interoperability | New terms check for Curriculum Vitae took 1.3576033115386963s
Versatility | Languages check for Curriculum Vitae took 0.23852229118347168s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.164320707321167s
Interpretability | RDF structures check for Curriculum Vitae took 0.1830456256866455s
Versatility | Serialization formats check for Curriculum Vitae took 0.16428089141845703s
Availability | RDF dump link check for Curriculum Vitae took 0.14878010749816895s
License | MR license check for Curriculum Vitae took 0.13401293754577637s
License | HR license check for Curriculum Vitae took 0.13922953605651855s
Amount of data | Number of property check for Curriculum Vitae took 0.14819717407226562s
Understandability | Number of label check for Curriculum Vitae took 0.1242833137512207s
Understandability | URI regex check for Curriculum Vitae took 0.3706645965576172s
Understandability | Vocabs check for Curriculum Vitae took 0.13709092140197754s
Verifiability | Authors check for Curriculum Vitae took 0.16529369354248047s
Verifiability | Publishers check for Curriculum Vitae took 0.13993597030639648s
Performance | Throughput check for Curriculum Vitae took 10.403205633163452s
Amount of data | Check the number of entities for Curriculum Vitae took 7.104873657226562e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.16800999641418457s
Interlinking | sameAs chians check for Curriculum Vitae took 0.13931632041931152s
Interlinking | skos check for Curriculum Vitae took 0.33304381370544434s
Interlinking | skos check for Curriculum Vitae took 0.15204381942749023s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.12846922874450684s
Currency | Creation date check for Curriculum Vitae took 0.2956218719482422s
Currency | Modification date check for Curriculum Vitae took 0.2940254211425781s
Rep.Conc. | URIs length for Curriculum Vitae took 0.3033487796783447s
Interoperability | New vocabularies check for Curriculum Vitae took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.12525081634521484s
Accuracy | Check Functional Property for Curriculum Vitae took 0.1143343448638916s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.1343979835510254s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.151533842086792s
Accuracy | Check White space in annotation for Curriculum Vitae took 8.916854858398438e-05s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.004964590072631836s
Consistency | Disjoint class check for Curriculum Vitae took 0.12869882583618164s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.3140830993652344s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.3091881275177002s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.1724050045013428s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.315197467803955s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0016274452209472656s
Security | Sign check for Curriculum Vitae took 0.12355208396911621s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 19.357876777648926s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.29288816452026367s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.022807598114013672s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 3.075599670410156e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.6689300537109375e-06s
Believability | Calculation of trust value for Curriculum Vitae took 1.239776611328125e-05s
INFO | --- Analysis for Nordine_Bittich took 56.51387643814087s
Availability | SPARQL endpoint availability check for NorPark took 0.19301772117614746s
Availability | VoID file availability check for NorPark took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for NorPark took 0.27597737312316895s
Reputation | Calculation of the PageRank for NorPark took 0.0214231014251709s
Interlinking | Calculation of Degree of Connection for NorPark took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.291534423828125e-05s
Believability | Calculation of trust value for NorPark took 1.049041748046875e-05s
INFO | --- Analysis for norpark took 3.0274817943573s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.025587797164916992s
Availability | VoID file availability check for Parking Dataset took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.290879487991333s
Reputation | Calculation of the PageRank for Parking Dataset took 0.0223391056060791s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 8.034706115722656e-05s
Believability | Calculation of trust value for Parking Dataset took 1.2636184692382812e-05s
INFO | --- Analysis for norpark2 took 2.7262215614318848s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.9531762599945068s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.3110191822052002s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.02126932144165039s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 3.218650817871094e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset took 1.0728836059570312e-05s
INFO | --- Analysis for Norway_Fishery_ took 4.325446605682373s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.3579890727996826s
Availability | VoID file availability check for Norwegian geo-divisions took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.2626471519470215s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.022511720657348633s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.601478576660156e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.3113021850585938e-05s
INFO | --- Analysis for norwegian-geo-divisions took 6.927996635437012s
Availability | SPARQL endpoint availability check for NITP took 4.0531158447265625e-05s
Availability | VoID file availability check for NITP took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for NITP took 0.2893543243408203s
Reputation | Calculation of the PageRank for NITP took 0.020969390869140625s
Interlinking | Calculation of Degree of Connection for NITP took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NITP took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for NITP took 6.890296936035156e-05s
Believability | Calculation of trust value for NITP took 1.3113021850585938e-05s
INFO | --- Analysis for notIdentifier took 3.499406576156616s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 8.7738037109375e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.2975883483886719s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.5762786865234375e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 1.2159347534179688e-05s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 3.0425753593444824s
Availability | SPARQL endpoint availability check for NPM took 8.153915405273438e-05s
Availability | VoID file availability check for NPM took 0.0010800361633300781s
Completeness | Calculation of interlinking completeness for NPM took 0.2717163562774658s
Reputation | Calculation of the PageRank for NPM took 0.020828723907470703s
Interlinking | Calculation of Degree of Connection for NPM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for NPM took 3.409385681152344e-05s
Believability | Calculation of trust value for NPM took 6.9141387939453125e-06s
INFO | --- Analysis for npm took 3.426171064376831s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.05350136756896973s
Availability | VoID file availability check for NTNU special collections took 0.0010569095611572266s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.3249657154083252s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.4836273193359375e-05s
Believability | Calculation of trust value for NTNU special collections took 1.049041748046875e-05s
INFO | --- Analysis for ntnusc took 5.430872917175293s
Availability | SPARQL endpoint availability check for links took 8.463859558105469e-05s
Availability | VoID file availability check for links took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for links took 0.30901145935058594s
Reputation | Calculation of the PageRank for links took 0.02097773551940918s
Interlinking | Calculation of Degree of Connection for links took 1.52587890625e-05s
Interlinking | Calculation of Centrality for links took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for links took 1.239776611328125e-05s
Believability | Calculation of trust value for links took 7.3909759521484375e-06s
INFO | --- Analysis for nugmyanmar took 2.776695489883423s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.1961669921875e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.30974721908569336s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.023006677627563477s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.703636169433594e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 8.821487426757812e-06s
INFO | --- Analysis for nuts-geovocab took 2.9126322269439697s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.41490697860717773s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.6427834033966064s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.02122664451599121s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.556510925292969e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 1.049041748046875e-05s
INFO | --- Analysis for nvd took 4.622349977493286s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.7772200107574463s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.297227144241333s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.021001338958740234s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 7.772445678710938e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.0728836059570312e-05s
INFO | --- Analysis for nvs took 9.8688485622406s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 8.58306884765625e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.27811646461486816s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.020922183990478516s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00018334388732910156s
Believability | Calculation of trust value for New York Times - Linked Open Data took 1.049041748046875e-05s
INFO | --- Analysis for nytimes-linked-open-data took 2.6694490909576416s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.5068454742431641s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0007586479187011719s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.5079879760742188s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.7942304611206055s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 4.477047443389893s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.7289514541625977s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 58.19723081588745s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.6644082069396973s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.27844786643981934s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.3350827693939209s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.3715829849243164s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.4403667449951172s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.5025002956390381s
License | HR license check for Italian Chamber of Deputies - official dataset took 58.25560474395752s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.370375394821167s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.9797267913818359s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.6954901218414307s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.398482084274292s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.3322150707244873s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.36059069633483887s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 10.998421430587769s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 6.818771362304688e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.3669118881225586s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.4141216278076172s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.33169007301330566s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.37098026275634766s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.34056854248046875s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.8179028034210205s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.3804962635040283s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 16.954822063446045s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.3490610122680664s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.37374353408813477s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.35159778594970703s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.7201862335205078s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.03058767318725586s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.02790689468383789s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.3508760929107666s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 12.635127544403076s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.40497422218322754s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 1.7787039279937744s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.1434733867645264s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 13.403221368789673s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.031373023986816406s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.39568448066711426s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.3531055450439453s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 22.857402086257935s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.3548309803009033s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.0207216739654541s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00010561943054199219s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 2.1457672119140625e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 1.1920928955078125e-05s
INFO | --- Analysis for ocd took 399.44551396369934s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 5.340576171875e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.2914731502532959s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.022281646728515625s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.7670135498046875e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.52587890625e-05s
INFO | --- Analysis for oceandrilling-borehole took 3.6824517250061035s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 2.864919424057007s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.2996861934661865s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.022027969360351562s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.559226989746094e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.1920928955078125e-05s
INFO | --- Analysis for oceandrilling-codices took 9.285672187805176s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 3.0092761516571045s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.2828352451324463s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.020653486251831055s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.266334533691406e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 6.9141387939453125e-06s
INFO | --- Analysis for oceandrilling-dbseabed took 7.441905498504639s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 2.9819369316101074s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.308793306350708s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.3855438232421875e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.2159347534179688e-05s
INFO | --- Analysis for oceandrilling-forams took 7.816181659698486s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 2.7345173358917236s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0008041858673095703s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.29513001441955566s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020864248275756836s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 4.1484832763671875e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.2636184692382812e-05s
INFO | --- Analysis for oceandrilling-janus took 7.697654485702515s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 13.193209409713745s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0008137226104736328s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.28630566596984863s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.021032094955444336s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.4332275390625e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.049041748046875e-05s
INFO | --- Analysis for oceandrilling-janusamp took 18.18197202682495s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.989082098007202s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0008153915405273438s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.29979515075683594s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0207977294921875s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.123283386230469e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.4066696166992188e-05s
INFO | --- Analysis for oceandrilling-ldeo took 7.874464511871338s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 8.7738037109375e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.31979918479919434s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.02306842803955078s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.7697296142578125e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.2636184692382812e-05s
INFO | --- Analysis for oclc-fast took 9.101381540298462s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 8.392333984375e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.30152034759521484s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.023273468017578125s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.0279159545898438e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 9.775161743164062e-06s
INFO | --- Analysis for odc-imd-environment-score took 5.714216232299805s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.16329288482666016s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0005986690521240234s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 1.1911084651947021s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 0.8235511779785156s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.24240708351135254s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.4014344215393066s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.39418959617614746s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 30.161176204681396s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.09198403358459473s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.1543126106262207s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.1911466121673584s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 52.70533204078674s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.18246698379516602s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 30.179596424102783s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.1432650089263916s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.2393336296081543s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.5997536182403564s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.21777749061584473s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.28125810623168945s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.2089691162109375s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 10.727327823638916s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 0.00010800361633300781s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.13343477249145508s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.1546032428741455s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.14850068092346191s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.20743083953857422s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.21766972541809082s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.4549534320831299s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.15029335021972656s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 1.9575927257537842s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.19765663146972656s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.1615896224975586s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.15867137908935547s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.1493701934814453s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.4546198844909668s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 1.6819658279418945s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.3283495903015137s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.00015044212341308594s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.38277482986450195s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.13164830207824707s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.4045732021331787s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.021033048629760742s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.9577484130859375e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 1.1920928955078125e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 8.106231689453125e-06s
INFO | --- Analysis for odc-lsoa took 269.86668276786804s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.14818882942199707s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0004105567932128906s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.3009204864501953s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.022617101669311523s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0001010894775390625s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for oecd-linked-data took 2.926644802093506s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.223604202270508s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0007724761962890625s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.2801668643951416s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.023132801055908203s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.792213439941406e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 1.049041748046875e-05s
INFO | --- Analysis for ogolod took 103.04447150230408s
Availability | SPARQL endpoint availability check for OLAC Metadata took 9.322166442871094e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.31980109214782715s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.023102521896362305s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 3.7670135498046875e-05s
Believability | Calculation of trust value for OLAC Metadata took 1.1682510375976562e-05s
INFO | --- Analysis for olac took 23.289907455444336s
Availability | SPARQL endpoint availability check for OLiA took 8.296966552734375e-05s
Availability | VoID file availability check for OLiA took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for OLiA took 0.32779908180236816s
Reputation | Calculation of the PageRank for OLiA took 0.022211074829101562s
Interlinking | Calculation of Degree of Connection for OLiA took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.0001220703125s
Believability | Calculation of trust value for OLiA took 1.1205673217773438e-05s
INFO | --- Analysis for olia took 12.086940288543701s
Availability | SPARQL endpoint availability check for OLiA Discourse took 8.296966552734375e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.28479552268981934s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020873308181762695s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 3.910064697265625e-05s
Believability | Calculation of trust value for OLiA Discourse took 1.0967254638671875e-05s
INFO | --- Analysis for olia-discourse took 7.414834260940552s
Availability | SPARQL endpoint availability check for Open Land Use took 0.5615825653076172s
Availability | VoID file availability check for Open Land Use took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.2974717617034912s
Reputation | Calculation of the PageRank for Open Land Use took 0.020977497100830078s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 3.0040740966796875e-05s
Believability | Calculation of trust value for Open Land Use took 1.0967254638671875e-05s
INFO | --- Analysis for OLU took 3.7706072330474854s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.7143573760986328s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0004177093505859375s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.2912404537200928s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.020757675170898438s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-als took 3.8115906715393066s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.3156585693359375s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.2928760051727295s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 2.7418136596679688e-05s
INFO | --- Analysis for omwn-arb took 3.4588754177093506s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.26140856742858887s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.27391934394836426s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.022809982299804688s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-bul took 3.2746973037719727s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2555091381072998s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2893226146697998s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.02071404457092285s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-cow took 3.2184853553771973s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2774670124053955s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.31220364570617676s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.02092885971069336s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-cwn took 3.469727039337158s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.2752034664154053s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.3292858600616455s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-dan took 3.3482613563537598s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.25778651237487793s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.2891685962677002s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-ell took 3.360445499420166s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.24656891822814941s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.3008449077606201s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-eng took 3.3545758724212646s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.23595523834228516s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.3143599033355713s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.021487712860107422s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-fas took 3.339172124862671s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2694716453552246s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2995760440826416s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0206601619720459s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-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.2872233390808105s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.2573716640472412s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.3029613494873047s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.02063584327697754s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.528594970703125e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-fra took 3.2407126426696777s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.24560022354125977s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.30472731590270996s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.020799636840820312s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-heb took 3.379223346710205s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.25001096725463867s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.3557107448577881s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.021814823150634766s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
INFO | --- Analysis for omwn-hrv took 3.4105172157287598s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2794613838195801s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2777860164642334s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.02079939842224121s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-isl took 3.4428722858428955s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.2565493583679199s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.2978987693786621s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.020426273345947266s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-ita took 3.3489441871643066s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.25105881690979004s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.2777564525604248s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.022739171981811523s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-iwn took 3.404285192489624s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.2428913116455078s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.3303699493408203s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.022889137268066406s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-jpn took 3.3963444232940674s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.2627592086791992s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.3361692428588867s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.02202320098876953s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-mcr took 3.442931652069092s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.28397154808044434s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2882716655731201s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-msa took 3.3571417331695557s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.23583412170410156s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.32746052742004395s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-nld took 3.3239967823028564s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.2384016513824463s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.27534937858581543s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.02078080177307129s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-nor took 3.4122066497802734s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.25769686698913574s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004150867462158203s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.29175734519958496s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.02096104621887207s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-pol took 3.25734543800354s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2492964267730713s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.28425121307373047s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.02088785171508789s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-por took 3.2878894805908203s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.24517536163330078s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.26668763160705566s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.02217888832092285s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
INFO | --- Analysis for omwn-ron took 3.30578875541687s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.24553847312927246s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.29104113578796387s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.02207779884338379s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.552436828613281e-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.3028228282928467s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.2681550979614258s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.32767152786254883s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020668506622314453s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-slv took 3.4491188526153564s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.23829150199890137s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.30965709686279297s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.021040916442871094s
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.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.3589859008789062e-05s
INFO | --- Analysis for omwn-swe took 3.2879507541656494s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.24607205390930176s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2765793800354004s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 1.3589859008789062e-05s
INFO | --- Analysis for omwn-tha took 3.3486573696136475s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 4.3495166301727295s
Availability | VoID file availability check for OntoBeef Domain took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.30315518379211426s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.022248506546020508s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.363059997558594e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.049041748046875e-05s
INFO | --- Analysis for ontobeef-domain took 28.275755405426025s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.172325134277344e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.30574774742126465s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.131431579589844e-05s
Believability | Calculation of trust value for Ontos News Portal took 1.049041748046875e-05s
INFO | --- Analysis for ontos-news-portal took 6.449827671051025s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 8.296966552734375e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.3154735565185547s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.021526336669921875s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.1948089599609375e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 1.0251998901367188e-05s
INFO | --- Analysis for ookaboo-rdf-dump took 2.81292724609375s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 7.748603820800781e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.28514695167541504s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.02255535125732422s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.790855407714844e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 1.1444091796875e-05s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 10.546608686447144s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 8.511543273925781e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.30397701263427734s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.021342754364013672s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.673004150390625e-05s
Believability | Calculation of trust value for Open Data Euskadi took 8.821487426757812e-06s
INFO | --- Analysis for open-data-euskadi took 8.480043649673462s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 8.487701416015625e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.29938721656799316s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.021838665008544922s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010204315185546875s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 1.049041748046875e-05s
INFO | --- Analysis for open-data-risp took 8.95473861694336s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.19399142265319824s
Availability | VoID file availability check for Open Data Thesaurus took 0.0006656646728515625s
Extra | Recovery of all triples for Open Data Thesaurus took 1.05753493309021s
Performance | Total latancy measurement for Open Data Thesaurus took 0.48605799674987793s
Amount of data | Number of triples check for Open Data Thesaurus took 0.1271522045135498s
Interoperability | New terms check for Open Data Thesaurus took 1.283604621887207s
Versatility | Languages check for Open Data Thesaurus took 0.11322379112243652s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.1172478199005127s
Security | Check HTTPS for Open Data Thesaurus took 0.3219120502471924s
Interpretability | RDF structures check for Open Data Thesaurus took 0.12593698501586914s
Versatility | Serialization formats check for Open Data Thesaurus took 0.11766219139099121s
Availability | RDF dump link check for Open Data Thesaurus took 1.0834596157073975s
License | MR license check for Open Data Thesaurus took 0.11490082740783691s
License | HR license check for Open Data Thesaurus took 0.08399248123168945s
Amount of data | Number of property check for Open Data Thesaurus took 0.11550188064575195s
Understandability | Number of label check for Open Data Thesaurus took 0.11562871932983398s
Understandability | URI regex check for Open Data Thesaurus took 0.17374300956726074s
Understandability | Vocabs check for Open Data Thesaurus took 0.12332987785339355s
Verifiability | Authors check for Open Data Thesaurus took 0.11459708213806152s
Verifiability | Publishers check for Open Data Thesaurus took 0.12428045272827148s
Performance | Throughput check for Open Data Thesaurus took 10.597448825836182s
Amount of data | Check the number of entities for Open Data Thesaurus took 0.00010657310485839844s
Verifiability | Contribs. check for Open Data Thesaurus took 0.11653470993041992s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.11611247062683105s
Interlinking | skos check for Open Data Thesaurus took 0.10869884490966797s
Interlinking | skos check for Open Data Thesaurus took 0.08701181411743164s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.08810853958129883s
Currency | Creation date check for Open Data Thesaurus took 0.16758489608764648s
Currency | Modification date check for Open Data Thesaurus took 0.20511841773986816s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.45066261291503906s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.11278653144836426s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.0913686752319336s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.08675241470336914s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.1863248348236084s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011317729949951172s
Consistency | Disjoint class check for Open Data Thesaurus took 0.09485793113708496s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.16425704956054688s
Consistency | Misplaced classes for Open Data Thesaurus took 0.08936238288879395s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.2952158451080322s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.1919560432434082s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00015282630920410156s
Security | Sign check for Open Data Thesaurus took 0.08788442611694336s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.3372185230255127s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0006747245788574219s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 7.772445678710938e-05s
Believability | Calculation of trust value for Open Data Thesaurus took 1.1444091796875e-05s
INFO | --- Analysis for open-data-thesaurus took 83.88775062561035s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.172325134277344e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.32517409324645996s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.628036499023438e-05s
Believability | Calculation of trust value for Open Election Data Project took 8.344650268554688e-06s
INFO | --- Analysis for open-election-data-project took 42.85473585128784s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.966832160949707s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.33816957473754883s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.020719051361083984s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.535385131835938e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 9.775161743164062e-06s
INFO | --- Analysis for open-energy-info-wiki took 14.10670781135559s
Availability | SPARQL endpoint availability check for Open Library took 8.535385131835938e-05s
Availability | VoID file availability check for Open Library took 0.0008535385131835938s
Completeness | Calculation of interlinking completeness for Open Library took 0.32206177711486816s
Reputation | Calculation of the PageRank for Open Library took 0.020905494689941406s
Interlinking | Calculation of Degree of Connection for Open Library took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.866455078125e-05s
Believability | Calculation of trust value for Open Library took 1.2159347534179688e-05s
INFO | --- Analysis for open-library took 10.015060901641846s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.5776865482330322s
Availability | VoID file availability check for Open Land Use @PSNC took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.3180117607116699s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.022904634475708008s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 3.0040740966796875e-05s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.0728836059570312e-05s
INFO | --- Analysis for Open_Land_Use took 3.9199724197387695s
Availability | SPARQL endpoint availability check for flyatlas took 1.4001080989837646s
Availability | VoID file availability check for flyatlas took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for flyatlas took 0.33763957023620605s
Reputation | Calculation of the PageRank for flyatlas took 0.021585702896118164s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.0517578125e-05s
Believability | Calculation of trust value for flyatlas took 1.1920928955078125e-05s
INFO | --- Analysis for openbiomed-flyatlas took 6.016513347625732s
Availability | SPARQL endpoint availability check for OpenCalais took 9.942054748535156e-05s
Availability | VoID file availability check for OpenCalais took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.3431520462036133s
Reputation | Calculation of the PageRank for OpenCalais took 0.0225982666015625s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010895729064941406s
Believability | Calculation of trust value for OpenCalais took 1.1682510375976562e-05s
INFO | --- Analysis for opencalais took 6.8563432693481445s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 8.678436279296875e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.5386383533477783s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.02184438705444336s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.152557373046875e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 8.58306884765625e-06s
INFO | --- Analysis for opencorporates took 3.2008094787597656s
Availability | SPARQL endpoint availability check for OpenCyc took 4.0531158447265625e-05s
Availability | VoID file availability check for OpenCyc took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.2757680416107178s
Reputation | Calculation of the PageRank for OpenCyc took 0.020986557006835938s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010323524475097656s
Believability | Calculation of trust value for OpenCyc took 1.0013580322265625e-05s
INFO | --- Analysis for opencyc took 2.6457455158233643s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 8.392333984375e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.29619312286376953s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.4332275390625e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 3.348482131958008s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 8.678436279296875e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.3049001693725586s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.021903276443481445s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 5.198138952255249s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007367134094238281s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.29706907272338867s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.022481679916381836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.852705717086792s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.36865806579589844s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.02367091178894043s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.001108407974243164s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 4.649162292480469e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.835716724395752s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 0.0001068115234375s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.27426815032958984s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.021883726119995117s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0008029937744140625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.4148831367492676s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 5.412101745605469e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.3476119041442871s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.02177262306213379s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0009450912475585938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 4.744529724121094e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 4.869196653366089s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.26259398460388184s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.021091938018798828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 3.598947286605835s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 8.416175842285156e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.31310462951660156s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020989656448364258s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.5709056854248047s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.3080313205718994s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.02104330062866211s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.3639585971832275s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 8.654594421386719e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.2841217517852783s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020992755889892578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 3.4006896018981934s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 8.535385131835938e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.3678581714630127s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020772933959960938s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 3.412419557571411s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 8.869171142578125e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.32834410667419434s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.021664857864379883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 3.3430685997009277s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 8.487701416015625e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.30573606491088867s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.021155357360839844s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 5.4836273193359375e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 3.390381097793579s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 0.00011730194091796875s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.2975022792816162s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.7769315242767334s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 8.654594421386719e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.3030247688293457s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020950794219970703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 3.6695051193237305s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.30236101150512695s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.02163100242614746s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 3.46773362159729s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 8.273124694824219e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.30179333686828613s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.02300739288330078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.5697081089019775s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 8.225440979003906e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.2757279872894287s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.021345853805541992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.9591064453125e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 3.383687973022461s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 8.797645568847656e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.2886698246002197s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.022619962692260742s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.6361489295959473s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 9.250640869140625e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.3058028221130371s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.021016359329223633s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.5968806743621826s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 8.726119995117188e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.3078949451446533s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.020937204360961914s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 3.472822904586792s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 8.463859558105469e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.294600248336792s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 3.635132074356079s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 8.440017700195312e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.27172303199768066s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020610570907592773s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 5.4836273193359375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.097777843475342s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.00010204315185546875s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.32517099380493164s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.022136211395263672s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 3.971930980682373s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 8.535385131835938e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.3228142261505127s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.022578954696655273s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 5.272531986236572s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 8.845329284667969e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007700920104980469s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.30789756774902344s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.02081465721130371s
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.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 3.988943338394165s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007381439208984375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.2761690616607666s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.021791458129882812s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 9.775161743164062e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 3.742659568786621s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0003027915954589844s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.29857635498046875s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.021138429641723633s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.38690185546875e-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.507841348648071s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 8.630752563476562e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.3355562686920166s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.021564960479736328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 5.03522801399231s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 8.487701416015625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.2928497791290283s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.022792816162109375s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 3.898364543914795s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.30475592613220215s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.021181821823120117s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 5.243898630142212s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 8.535385131835938e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007653236389160156s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.29852843284606934s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.022552967071533203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.263596534729004s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 8.392333984375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.28618526458740234s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.023309707641601562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 3.9711716175079346s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.559226989746094e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.29532814025878906s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.021133899688720703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.76837158203125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 7.033348083496094e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.7311506271362305s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 8.726119995117188e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.28603172302246094s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.021515369415283203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.6315152645111084s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 8.511543273925781e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007441043853759766s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.31728196144104004s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.020331144332885742s
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.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 3.991220474243164s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 8.869171142578125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.2703218460083008s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.021001100540161133s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 9.059906005859375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 3.6378700733184814s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.29540443420410156s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.021093368530273438s
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.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 4.004669427871704s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 8.606910705566406e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007874965667724609s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.2879302501678467s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.022568225860595703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.2815210819244385s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.00010728836059570312s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007529258728027344s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.30716848373413086s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0208280086517334s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007033348083496094s
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.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 3.4909346103668213s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.308699369430542s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.02100348472595215s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.5778250694274902s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.2845280170440674s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.02094578742980957s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.08922553062439s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.00010848045349121094s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.31485772132873535s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.021539688110351562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 4.1882243156433105s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 8.629388332366943s
Availability | VoID file availability check for Open Data of Ecuador took 0.0003781318664550781s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.2708320617675781s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.021182537078857422s
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.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.535385131835938e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.3589859008789062e-05s
INFO | --- Analysis for opendataec took 17.8568594455719s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 8.797645568847656e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.2911560535430908s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.02103424072265625s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.3113021850585938e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 7.136987686157227s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0003132820129394531s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.2750840187072754s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 1.0013580322265625e-05s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 3.8590781688690186s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.1961669921875e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0003085136413574219s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.27910566329956055s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020761489868164062s
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.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 5.9604644775390625e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.6659750938415527s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.38690185546875e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.00033354759216308594s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.2969491481781006s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 5.9604644775390625e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 3.9200875759124756s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.30124616622924805s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.022130250930786133s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 4.696846008300781e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.0013580322265625e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 3.7279574871063232s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 0.0001227855682373047s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.2943863868713379s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.02137470245361328s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 1.0013580322265625e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 4.04726767539978s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 8.487701416015625e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.3086509704589844s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.021675825119018555s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 9.5367431640625e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 3.7508046627044678s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.482269287109375e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.2783224582672119s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.02264404296875s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 1.0013580322265625e-05s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 3.7499053478240967s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.27445101737976074s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 5.9604644775390625e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.641963005065918s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.452773571014404s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.28365039825439453s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020828962326049805s
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.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 2.9087066650390625e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.1444091796875e-05s
INFO | --- Analysis for openlink-lod-cache took 63.132972955703735s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 9.202957153320312e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.36597633361816406s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.655952453613281e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 5.4836273193359375e-06s
INFO | --- Analysis for openlinksw-dataspaces took 3.349583387374878s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 8.845329284667969e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.29511594772338867s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.298324584960938e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 9.059906005859375e-06s
INFO | --- Analysis for openlylocal took 6.649460554122925s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.671149492263794s
Availability | VoID file availability check for OpenMobileNetwork took 0.0007071495056152344s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.2982749938964844s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.021213769912719727s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 8.20159912109375e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 1.0013580322265625e-05s
INFO | --- Analysis for openmobilenetwork took 5.59704065322876s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.9556496143341064s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0007333755493164062s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.3199169635772705s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.022197246551513672s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.679794311523438e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 1.1444091796875e-05s
INFO | --- Analysis for ordnance-survey-linked-data took 5.741492509841919s
Availability | SPARQL endpoint availability check for oreilly took 5.6743621826171875e-05s
Availability | VoID file availability check for oreilly took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for oreilly took 0.30940890312194824s
Reputation | Calculation of the PageRank for oreilly took 0.02293705940246582s
Interlinking | Calculation of Degree of Connection for oreilly took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for oreilly took 5.030632019042969e-05s
Believability | Calculation of trust value for oreilly took 1.0728836059570312e-05s
INFO | --- Analysis for oreilly took 4.776502847671509s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.399955987930298s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.3290541172027588s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.02147388458251953s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.647804260253906e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 1.0013580322265625e-05s
INFO | --- Analysis for Organchem-Data took 7.582644701004028s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.09348583221435547s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.3513193130493164s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 8.463859558105469e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.0728836059570312e-05s
INFO | --- Analysis for organic-edunet took 9.168697595596313s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.5177774429321289s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0005462169647216797s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 6.144859313964844s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.8067948818206787s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.17247867584228516s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.5001604557037354s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 6.219283580780029s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.14520978927612305s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.45909786224365234s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.15651488304138184s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.13136577606201172s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.16030502319335938s
License | HR license check for Open Research Knowledge Graph (ORKG) took 3.8021857738494873s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.18364787101745605s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.17944812774658203s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.3072848320007324s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.13327884674072266s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.161668062210083s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.15155863761901855s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.69158124923706s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 0.00010061264038085938s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.17135930061340332s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.16935324668884277s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.16001319885253906s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.16521120071411133s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.1441948413848877s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.29734015464782715s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.2770872116088867s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 3.8040475845336914s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.14499688148498535s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.16396498680114746s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.14881229400634766s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 2.4243087768554688s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.284029483795166s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.2655320167541504s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.30333971977233887s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.4166948795318604s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.8894882202148438s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 3.1240923404693604s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.2029900550842285s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.084144353866577s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.2860293388366699s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.1714932918548584s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.12206506729125977s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2088.8692877292633s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.854083776473999s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.021795272827148438s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 3.457069396972656e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 2.0742416381835938e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 5.9604644775390625e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.2874603271484375e-05s
INFO | --- Analysis for orkg took 2343.4093582630157s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.9292778968811035s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.31137514114379883s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.02082204818725586s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 9.131431579589844e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 9.5367431640625e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 30.86817193031311s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.670461893081665s
Availability | VoID file availability check for OSM Semantic Network took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.3506460189819336s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.6716461181640625e-05s
Believability | Calculation of trust value for OSM Semantic Network took 1.4066696166992188e-05s
INFO | --- Analysis for osm-semantic-network took 9.08971095085144s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.781580924987793s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.3350546360015869s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.022024869918823242s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.600120544433594e-05s
Believability | Calculation of trust value for Open Transport Map @PSNC took 9.775161743164062e-06s
INFO | --- Analysis for OTM took 4.3354315757751465s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 5.694930076599121s
Availability | VoID file availability check for Pali English Lexicon took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.31656765937805176s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.02159404754638672s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 3.647804260253906e-05s
Believability | Calculation of trust value for Pali English Lexicon took 1.3828277587890625e-05s
INFO | --- Analysis for pali-english-lexicon took 24.279244422912598s
Availability | SPARQL endpoint availability check for PanLex took 61.8766872882843s
Availability | VoID file availability check for PanLex took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for PanLex took 0.3129713535308838s
Reputation | Calculation of the PageRank for PanLex took 0.021072864532470703s
Interlinking | Calculation of Degree of Connection for PanLex took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for PanLex took 8.702278137207031e-05s
Believability | Calculation of trust value for PanLex took 1.3828277587890625e-05s
INFO | --- Analysis for panlex took 64.9191722869873s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 8.416175842285156e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.3384273052215576s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020775318145751953s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 4.1961669921875e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.2159347534179688e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 6.561593532562256s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.08617639541625977s
Availability | VoID file availability check for patents.data.gov.uk took 0.0009970664978027344s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.30937743186950684s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.02165818214416504s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 5.173683166503906e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 1.0013580322265625e-05s
INFO | --- Analysis for patents-data-gov-uk took 3.0265612602233887s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 5.817413330078125e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.3184323310852051s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.020760297775268555s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.743171691894531e-05s
Believability | Calculation of trust value for PDEV-Lemon took 6.628036499023438e-05s
INFO | --- Analysis for pdev-lemon took 4.398459196090698s
Availability | SPARQL endpoint availability check for pdevlemon took 8.440017700195312e-05s
Availability | VoID file availability check for pdevlemon took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.31516098976135254s
Reputation | Calculation of the PageRank for pdevlemon took 0.021013736724853516s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.266334533691406e-05s
Believability | Calculation of trust value for pdevlemon took 1.2159347534179688e-05s
INFO | --- Analysis for pdevlemon took 3.583646297454834s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 0.00010371208190917969s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0007984638214111328s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.3367898464202881s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 7.891654968261719e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 8.106231689453125e-06s
INFO | --- Analysis for periodo took 19.840633869171143s
Availability | SPARQL endpoint availability check for Personal_Homepages took 8.177757263183594e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.3262357711791992s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020883798599243164s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.0003871917724609375s
Believability | Calculation of trust value for Personal_Homepages took 1.1205673217773438e-05s
INFO | --- Analysis for personal-homepages took 2.8592116832733154s
Availability | SPARQL endpoint availability check for Ontology of University People took 8.511543273925781e-05s
Availability | VoID file availability check for Ontology of University People took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.3096580505371094s
Reputation | Calculation of the PageRank for Ontology of University People took 0.020877838134765625s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 3.075599670410156e-05s
Believability | Calculation of trust value for Ontology of University People took 7.3909759521484375e-06s
INFO | --- Analysis for PersonOnto took 2.838601589202881s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 4.173643350601196s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.3208138942718506s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020942211151123047s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1920928955078125e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3828277587890625e-05s
INFO | --- Analysis for PFKHS took 8.918316125869751s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 2.248786449432373s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.3401515483856201s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007085800170898438s
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 1.3113021850585938e-05s
INFO | --- Analysis for PFRPPH took 6.996211528778076s
Availability | SPARQL endpoint availability check for PGxLOD took 0.45524024963378906s
Availability | VoID file availability check for PGxLOD took 0.0005917549133300781s
Extra | Recovery of all triples for PGxLOD took 2.0255191326141357s
Performance | Total latancy measurement for PGxLOD took 0.9044094085693359s
Amount of data | Number of triples check for PGxLOD took 0.8341066837310791s
Interoperability | New terms check for PGxLOD took 1.857149600982666s
Versatility | Languages check for PGxLOD took 60.25792217254639s
Interpretability | Number of blank nodes check for PGxLOD took 1.498711109161377s
Interpretability | RDF structures check for PGxLOD took 0.4236314296722412s
Versatility | Serialization formats check for PGxLOD took 0.2207033634185791s
Availability | RDF dump link check for PGxLOD took 18.677536725997925s
License | MR license check for PGxLOD took 0.20105934143066406s
License | HR license check for PGxLOD took 60.26473307609558s
Amount of data | Number of property check for PGxLOD took 0.1889965534210205s
Understandability | Number of label check for PGxLOD took 0.8757023811340332s
Understandability | URI regex check for PGxLOD took 0.38611769676208496s
Understandability | Vocabs check for PGxLOD took 0.18458986282348633s
Verifiability | Authors check for PGxLOD took 0.19529509544372559s
Verifiability | Publishers check for PGxLOD took 0.18914103507995605s
Performance | Throughput check for PGxLOD took 11.10496211051941s
Amount of data | Check the number of entities for PGxLOD took 0.12260580062866211s
Verifiability | Contribs. check for PGxLOD took 0.18947958946228027s
Interlinking | sameAs chians check for PGxLOD took 0.3069751262664795s
Interlinking | skos check for PGxLOD took 0.24144554138183594s
Interlinking | skos check for PGxLOD took 0.2198772430419922s
Timeliness | dataset update frequency check for PGxLOD took 0.19747328758239746s
Currency | Creation date check for PGxLOD took 0.38187646865844727s
Currency | Modification date check for PGxLOD took 0.39722442626953125s
Rep.Conc. | URIs length for PGxLOD took 6.821138381958008s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.19132208824157715s
Accuracy | Check Functional Property for PGxLOD took 0.22082233428955078s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.21831083297729492s
Accuracy | Check Empty annotation labels for PGxLOD took 0.80389404296875s
Accuracy | Check White space in annotation for PGxLOD took 0.03624153137207031s
Accuracy | Check Datatype consistency for PGxLOD took 0.02901625633239746s
Consistency | Disjoint class check for PGxLOD took 0.1857001781463623s
Consistency | Check Misplaced properties for PGxLOD took 6.645700454711914s
Consistency | Misplaced classes for PGxLOD took 0.3283560276031494s
Consistency | Check Ontology hijacking for PGxLOD took 2.368425130844116s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.1476795673370361s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 7.138630390167236s
Conciseness | Check Extensional conciseness for PGxLOD took 0.03310418128967285s
Conciseness | Check Intensional conciseness for PGxLOD took 0.29050254821777344s
Security | Sign check for PGxLOD took 0.20516538619995117s
Availability | Check URIs Dereferenciability for PGxLOD took 2403.33171749115s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.5532345771789551s
Reputation | Calculation of the PageRank for PGxLOD took 0.021515607833862305s
Interlinking | Calculation of Degree of Connection for PGxLOD took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 6.0558319091796875e-05s
Believability | Calculation of trust value for PGxLOD took 1.3589859008789062e-05s
INFO | --- Analysis for PGxLOD took 3771.0221512317657s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.9902973175048828s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007140636444091797s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.32248425483703613s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.020816564559936523s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.4332275390625e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 1.3113021850585938e-05s
INFO | --- Analysis for phoible took 5.1473329067230225s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 4.363059997558594e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.31812524795532227s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.021837711334228516s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.1948089599609375e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 1.1444091796875e-05s
INFO | --- Analysis for PISM took 13.59736967086792s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 8.58306884765625e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.2957477569580078s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.021085739135742188s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.940696716308594e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 7.62939453125e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.8846426010131836s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.0101816654205322s
Availability | VoID file availability check for digitized plant specimen took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.29302024841308594s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.021647930145263672s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 6.937980651855469e-05s
Believability | Calculation of trust value for digitized plant specimen took 1.3113021850585938e-05s
INFO | --- Analysis for plant-specimen took 3.8938324451446533s
Availability | SPARQL endpoint availability check for Pleiades took 5.936622619628906e-05s
Availability | VoID file availability check for Pleiades took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Pleiades took 0.3615598678588867s
Reputation | Calculation of the PageRank for Pleiades took 0.021596193313598633s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.749961853027344e-05s
Believability | Calculation of trust value for Pleiades took 1.1920928955078125e-05s
INFO | --- Analysis for pleiades took 16.384597778320312s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 8.58306884765625e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0007369518280029297s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.3124983310699463s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020928144454956055s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0008070468902587891s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.62396240234375e-05s
Believability | Calculation of trust value for podorozhnyk.com took 1.239776611328125e-05s
INFO | --- Analysis for podorozhnyk took 3.5699105262756348s
Availability | SPARQL endpoint availability check for Poképédia took 4.267692565917969e-05s
Availability | VoID file availability check for Poképédia took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Poképédia took 0.29897570610046387s
Reputation | Calculation of the PageRank for Poképédia took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Poképédia took 6.866455078125e-05s
Believability | Calculation of trust value for Poképédia took 1.2874603271484375e-05s
INFO | --- Analysis for pokepedia-fr took 3.1197357177734375s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 8.797645568847656e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007486343383789062s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.31809520721435547s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.343292236328125e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.3589859008789062e-05s
INFO | --- Analysis for polymath-virtual-library took 6.922592401504517s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2873401641845703s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0006890296936035156s
Extra | Recovery of all triples for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.73217248916626s
Performance | Total latancy measurement for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.6562864780426025s
Amount of data | Number of triples check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.41171741485595703s
Interoperability | New terms check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.4557533264160156s
Versatility | Languages check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.2392380237579346s
Interpretability | Number of blank nodes check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.38939952850341797s
Interpretability | RDF structures check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1320803165435791s
Versatility | Serialization formats check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12997102737426758s
Availability | RDF dump link check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12741374969482422s
License | MR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12824225425720215s
License | HR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.656494379043579s
Amount of data | Number of property check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1297907829284668s
Understandability | Number of label check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.19132184982299805s
Understandability | URI regex check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2565479278564453s
Understandability | Vocabs check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12823939323425293s
Verifiability | Authors check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12938141822814941s
Verifiability | Publishers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12843108177185059s
Performance | Throughput check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.319316387176514s
Amount of data | Check the number of entities for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.00010466575622558594s
Verifiability | Contribs. check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12935900688171387s
Interlinking | sameAs chians check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12825536727905273s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12837505340576172s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1293506622314453s
Timeliness | dataset update frequency check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1286466121673584s
Currency | Creation date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2592012882232666s
Currency | Modification date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2585484981536865s
Rep.Conc. | URIs length for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.2980568408966064s
Interoperability | New vocabularies check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13063955307006836s
Accuracy | Check Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12680935859680176s
Accuracy | Check Inverse Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1278674602508545s
Accuracy | Check Empty annotation labels for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.1732311248779297s
Accuracy | Check White space in annotation for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1932382583618164s
Accuracy | Check Datatype consistency for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.8000214099884033s
Consistency | Disjoint class check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1284797191619873s
Consistency | Check Misplaced properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.9068541526794434s
Consistency | Check Ontology hijacking for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.3088159561157227s
Consistency | Check Invalid usage of undefined classes for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.178361415863037s
Consistency | Check Invalid usage of undefined properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.956345558166504s
Conciseness | Check Extensional conciseness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.4746651649475098s
Security | Sign check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1269690990447998s
Availability | Check URIs Dereferenciability for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 5027.202011108398s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.9862828254699707s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.021895885467529297s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 9.989738464355469e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.3113021850585938e-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 1.2636184692382812e-05s
INFO | --- Analysis for portuguese_prisons_releases took 5098.392327547073s
Availability | SPARQL endpoint availability check for prefix.cc took 9.465217590332031e-05s
Availability | VoID file availability check for prefix.cc took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.31154394149780273s
Reputation | Calculation of the PageRank for prefix.cc took 0.021038293838500977s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.981590270996094e-05s
Believability | Calculation of trust value for prefix.cc took 1.049041748046875e-05s
INFO | --- Analysis for prefix-cc took 3.474334955215454s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.8866779804229736s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0003597736358642578s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.35306262969970703s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.696846008300781e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.0013580322265625e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 10.444772958755493s
Availability | SPARQL endpoint availability check for PreLex took 6.263472557067871s
Availability | VoID file availability check for PreLex took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for PreLex took 0.33618903160095215s
Reputation | Calculation of the PageRank for PreLex took 0.021128177642822266s
Interlinking | Calculation of Degree of Connection for PreLex took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for PreLex took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.176399230957031e-05s
Believability | Calculation of trust value for PreLex took 1.0967254638671875e-05s
INFO | --- Analysis for prelex took 18.434260368347168s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.195629119873047s
Availability | VoID file availability check for Prelinger Archives took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.31000661849975586s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.147125244140625e-05s
Believability | Calculation of trust value for Prelinger Archives took 1.049041748046875e-05s
INFO | --- Analysis for prelinger_archives took 12.251446962356567s
Availability | SPARQL endpoint availability check for PreMOn took 0.46634554862976074s
Availability | VoID file availability check for PreMOn took 0.0005061626434326172s
Extra | Recovery of all triples for PreMOn took 6.153196573257446s
Performance | Total latancy measurement for PreMOn took 2.6226534843444824s
Amount of data | Number of triples check for PreMOn took 0.5206658840179443s
Interoperability | New terms check for PreMOn took 2.169421434402466s
Versatility | Languages check for PreMOn took 61.70599889755249s
Interpretability | Number of blank nodes check for PreMOn took 0.1619410514831543s
Security | Check HTTPS for PreMOn took 0.0779881477355957s
Interpretability | RDF structures check for PreMOn took 0.18283724784851074s
Versatility | Serialization formats check for PreMOn took 0.3103463649749756s
Availability | RDF dump link check for PreMOn took 0.16172575950622559s
License | MR license check for PreMOn took 0.358365535736084s
License | HR license check for PreMOn took 0.9397284984588623s
Amount of data | Number of property check for PreMOn took 0.18096375465393066s
Understandability | Number of label check for PreMOn took 0.8789103031158447s
Understandability | URI regex check for PreMOn took 0.33788061141967773s
Understandability | Vocabs check for PreMOn took 0.2635986804962158s
Verifiability | Authors check for PreMOn took 0.1655128002166748s
Verifiability | Publishers check for PreMOn took 0.2753915786743164s
Performance | Throughput check for PreMOn took 10.563104152679443s
Amount of data | Check the number of entities for PreMOn took 6.866455078125e-05s
Verifiability | Contribs. check for PreMOn took 0.16800880432128906s
Interlinking | sameAs chians check for PreMOn took 0.1669178009033203s
Interlinking | skos check for PreMOn took 0.2694971561431885s
Interlinking | skos check for PreMOn took 0.13429594039916992s
Timeliness | dataset update frequency check for PreMOn took 0.16964197158813477s
Currency | Creation date check for PreMOn took 0.3339507579803467s
Currency | Modification date check for PreMOn took 0.33222103118896484s
Rep.Conc. | URIs length for PreMOn took 3.919384002685547s
Interoperability | New vocabularies check for PreMOn took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for PreMOn took 0.16808271408081055s
Accuracy | Check Functional Property for PreMOn took 0.18364977836608887s
Accuracy | Check Inverse Functional Property for PreMOn took 0.19573664665222168s
Accuracy | Check Empty annotation labels for PreMOn took 1.1811394691467285s
Accuracy | Check White space in annotation for PreMOn took 0.08036136627197266s
Accuracy | Check Datatype consistency for PreMOn took 0.08192300796508789s
Consistency | Disjoint class check for PreMOn took 0.1614682674407959s
Consistency | Check Misplaced properties for PreMOn took 1.8852903842926025s
Consistency | Misplaced classes for PreMOn took 0.4098343849182129s
Consistency | Check Ontology hijacking for PreMOn took 2.531494617462158s
Consistency | Check Invalid usage of undefined classes for PreMOn took 1.1620442867279053s
Consistency | Check Invalid usage of undefined properties for PreMOn took 2.887017250061035s
Conciseness | Check Extensional conciseness for PreMOn took 0.08841085433959961s
Conciseness | Check Intensional conciseness for PreMOn took 0.17704176902770996s
Security | Sign check for PreMOn took 0.17069649696350098s
Availability | Check URIs Dereferenciability for PreMOn took 1505.8087286949158s
Completeness | Calculation of interlinking completeness for PreMOn took 0.41999173164367676s
Reputation | Calculation of the PageRank for PreMOn took 0.022089004516601562s
Interlinking | Calculation of Degree of Connection for PreMOn took 8.58306884765625e-05s
Interlinking | Calculation of Centrality for PreMOn took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for PreMOn took 6.4849853515625e-05s
Interoperability | Check the re-using of existing vocabs for PreMOn took 2.1457672119140625e-06s
Believability | Calculation of trust value for PreMOn took 5.7220458984375e-06s
INFO | --- Analysis for premon took 1641.904248714447s
Availability | SPARQL endpoint availability check for Previsible took 7.390975952148438e-05s
Availability | VoID file availability check for Previsible took 0.0002117156982421875s
Completeness | Calculation of interlinking completeness for Previsible took 0.36489248275756836s
Reputation | Calculation of the PageRank for Previsible took 0.021053314208984375s
Interlinking | Calculation of Degree of Connection for Previsible took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.2159347534179688e-05s
Believability | Calculation of trust value for Previsible took 5.4836273193359375e-06s
INFO | --- Analysis for Previsible took 3.35891056060791s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 4.172325134277344e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.340923547744751s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020803213119506836s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.793571472167969e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 5.4836273193359375e-06s
INFO | --- Analysis for princeton-library-findingaids took 5.0205206871032715s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.5844142436981201s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.3195686340332031s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020969152450561523s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 6.198883056640625e-06s
INFO | --- Analysis for PrinParLat took 4.860514402389526s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.395552396774292s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.32484912872314453s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.021124839782714844s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.296966552734375e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 5.245208740234375e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.480872392654419s
Availability | SPARQL endpoint availability check for Prior Panel took 7.343292236328125e-05s
Availability | VoID file availability check for Prior Panel took 0.00021147727966308594s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.2972080707550049s
Reputation | Calculation of the PageRank for Prior Panel took 0.020993947982788086s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.4332275390625e-05s
Believability | Calculation of trust value for Prior Panel took 5.9604644775390625e-06s
INFO | --- Analysis for Prior_Panel took 2.669095277786255s
Availability | SPARQL endpoint availability check for ProductDB took 0.7355341911315918s
Availability | VoID file availability check for ProductDB took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for ProductDB took 0.29673099517822266s
Reputation | Calculation of the PageRank for ProductDB took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.462501525878906e-05s
Believability | Calculation of trust value for ProductDB took 1.0967254638671875e-05s
INFO | --- Analysis for productdb took 3.9842755794525146s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Product Types Ontology took 0.00039267539978027344s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.28242945671081543s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.021104812622070312s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.772445678710938e-05s
Believability | Calculation of trust value for Product Types Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for productontology took 4.058643341064453s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.124641418457031e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.2902522087097168s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.02106928825378418s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010347366333007812s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 5.7220458984375e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 7.346822261810303s
Availability | SPARQL endpoint availability check for provenanceweb took 0.04780697822570801s
Availability | VoID file availability check for provenanceweb took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.30946850776672363s
Reputation | Calculation of the PageRank for provenanceweb took 0.02140212059020996s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 7.82012939453125e-05s
Believability | Calculation of trust value for provenanceweb took 1.0728836059570312e-05s
INFO | --- Analysis for provenanceweb took 64.05998086929321s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 8.654594421386719e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.43474626541137695s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.022211074829101562s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.001134634017944336s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00013780593872070312s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.239776611328125e-05s
INFO | --- Analysis for proyectoapadrina took 8.539507389068604s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.439591884613037s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.000885009765625s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.3037376403808594s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.023043155670166016s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.7670135498046875e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 8.821487426757812e-06s
INFO | --- Analysis for pscs-catalogue took 126.77734470367432s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.1484832763671875e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.3024909496307373s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.02178168296813965s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 6.914138793945312e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 1.3113021850585938e-05s
INFO | --- Analysis for psh-subject-headings took 3.2376420497894287s
Availability | SPARQL endpoint availability check for Depression took 0.6314787864685059s
Availability | VoID file availability check for Depression took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Depression took 0.2954554557800293s
Reputation | Calculation of the PageRank for Depression took 0.023086071014404297s
Interlinking | Calculation of Degree of Connection for Depression took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Depression took 3.0279159545898438e-05s
Believability | Calculation of trust value for Depression took 1.5735626220703125e-05s
INFO | --- Analysis for Psychology took 3.3495113849639893s
Availability | SPARQL endpoint availability check for PubChem RDF took 4.506111145019531e-05s
Availability | VoID file availability check for PubChem RDF took 0.001201629638671875s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.3007774353027344s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020733356475830078s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 3.910064697265625e-05s
Believability | Calculation of trust value for PubChem RDF took 1.239776611328125e-05s
INFO | --- Analysis for PubChem_RDF took 5.413061857223511s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 60.06681561470032s
Availability | VoID file availability check for Public Spending in Greece took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.3019230365753174s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.02197718620300293s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 9.1552734375e-05s
Believability | Calculation of trust value for Public Spending in Greece took 1.0967254638671875e-05s
INFO | --- Analysis for public-spending-in-greece took 147.70212483406067s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.20569157600402832s
Availability | VoID file availability check for Publications Office Authority tables took 0.0006895065307617188s
Extra | Recovery of all triples for Publications Office Authority tables took 233.6314492225647s
Performance | Total latancy measurement for Publications Office Authority tables took 0.5905675888061523s
Amount of data | Number of triples check for Publications Office Authority tables took 58.29131555557251s
Interoperability | New terms check for Publications Office Authority tables took 62.37285900115967s
Versatility | Languages check for Publications Office Authority tables took 300.1315050125122s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 61.1723313331604s
Security | Check HTTPS for Publications Office Authority tables took 1.1590373516082764s
Interpretability | RDF structures check for Publications Office Authority tables took 0.2815515995025635s
Versatility | Serialization formats check for Publications Office Authority tables took 4.377373456954956s
Availability | RDF dump link check for Publications Office Authority tables took 0.28792858123779297s
License | MR license check for Publications Office Authority tables took 0.35852599143981934s
License | HR license check for Publications Office Authority tables took 300.0726532936096s
Amount of data | Number of property check for Publications Office Authority tables took 0.19691014289855957s
Understandability | Number of label check for Publications Office Authority tables took 1.5399584770202637s
Understandability | URI regex check for Publications Office Authority tables took 0.4243745803833008s
Understandability | Vocabs check for Publications Office Authority tables took 0.1045236587524414s
Verifiability | Authors check for Publications Office Authority tables took 0.11936473846435547s
Verifiability | Publishers check for Publications Office Authority tables took 0.18587613105773926s
Performance | Throughput check for Publications Office Authority tables took 10.777488708496094s
Amount of data | Check the number of entities for Publications Office Authority tables took 7.772445678710938e-05s
Verifiability | Contribs. check for Publications Office Authority tables took 0.11458182334899902s
Interlinking | sameAs chians check for Publications Office Authority tables took 7.7696921825408936s
Interlinking | skos check for Publications Office Authority tables took 0.19778728485107422s
Interlinking | skos check for Publications Office Authority tables took 0.16630768775939941s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.26181769371032715s
Currency | Creation date check for Publications Office Authority tables took 0.4603121280670166s
Currency | Modification date check for Publications Office Authority tables took 0.173936128616333s
Rep.Conc. | URIs length for Publications Office Authority tables took 409.752774477005s
Interoperability | New vocabularies check for Publications Office Authority tables took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.16959357261657715s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.22541475296020508s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.1599729061126709s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 39.283111333847046s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.0733163356781006s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.631317138671875s
Consistency | Disjoint class check for Publications Office Authority tables took 0.14083504676818848s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.482159614563s
Consistency | Misplaced classes for Publications Office Authority tables took 8.412141799926758s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 37.80791664123535s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.4188828468322754s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.33813738822937s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 2.960360288619995s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.38356447219848633s
Security | Sign check for Publications Office Authority tables took 0.3823418617248535s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 17.10241937637329s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 0.8456695079803467s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.025548696517944336s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 5.507469177246094e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.9073486328125e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 9.775161743164062e-06s
INFO | --- Analysis for publications_office_authority_tables took 15697.202586174011s
Availability | SPARQL endpoint availability check for QBOAirbase took 8.606910705566406e-05s
Availability | VoID file availability check for QBOAirbase took 0.0007460117340087891s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.33928823471069336s
Reputation | Calculation of the PageRank for QBOAirbase took 0.021111488342285156s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 6.198883056640625e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 8.130073547363281e-05s
Believability | Calculation of trust value for QBOAirbase took 1.1682510375976562e-05s
INFO | --- Analysis for qboairbase took 138.15851736068726s
Availability | SPARQL endpoint availability check for Qualité de l'air took 9.059906005859375e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.3228306770324707s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.0220339298248291s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 3.24249267578125e-05s
Believability | Calculation of trust value for Qualité de l'air took 1.2874603271484375e-05s
INFO | --- Analysis for Qualité_de_l'air took 3.3245110511779785s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 8.440017700195312e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.3137941360473633s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.02090764045715332s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 2.9802322387695312e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 1.1682510375976562e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 51.47100114822388s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.7144618034362793s
Availability | VoID file availability check for Querolus in LiLa took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.31795668601989746s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.023523330688476562s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.600120544433594e-05s
Believability | Calculation of trust value for Querolus in LiLa took 1.1205673217773438e-05s
INFO | --- Analysis for Querolus took 4.716052293777466s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.3476693630218506s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007183551788330078s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 28.964576244354248s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.7692146301269531s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.2374229431152344s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.6868677139282227s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.624508142471313s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.387605905532837s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1871321201324463s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1555013656616211s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15405035018920898s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15380311012268066s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1561741828918457s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15306949615478516s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15478062629699707s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.3065929412841797s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15572881698608398s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15572547912597656s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15420222282409668s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.730836153030396s
Amount of data | Check the number of entities for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.152557373046875e-05s
Verifiability | Contribs. check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1533665657043457s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15469861030578613s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1528949737548828s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15280652046203613s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15383505821228027s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.30840516090393066s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.30719685554504395s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 21.882554054260254s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15139007568359375s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15085172653198242s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1511518955230713s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1534571647644043s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.002716064453125e-05s
Accuracy | Check Datatype consistency for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.10977029800415s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1550295352935791s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.401480674743652s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.677489280700684s
Consistency | Check Invalid usage of undefined classes for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.215867280960083s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.666406631469727s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.7711901664733887s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15010976791381836s
Availability | Check URIs Dereferenciability for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 14.672669172286987s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.41440701484680176s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.8160552978515625e-05s
Interoperability | Check the re-using of existing vocabs for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.6689300537109375e-06s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.9141387939453125e-06s
INFO | --- Analysis for racai-legalnero took 159.06868624687195s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 4.2438507080078125e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.3027830123901367s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 2.9325485229492188e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 1.0967254638671875e-05s
INFO | --- Analysis for racai-llod-corola-we took 3.0540266036987305s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.15534758567810059s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0005984306335449219s
Extra | Recovery of all triples for PARSEME-Ro corpus took 30.24939465522766s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.7592363357543945s
Amount of data | Number of triples check for PARSEME-Ro corpus took 6.776120901107788s
Interoperability | New terms check for PARSEME-Ro corpus took 2.029576063156128s
Versatility | Languages check for PARSEME-Ro corpus took 18.122655868530273s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.606320858001709s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.15542244911193848s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.15369224548339844s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.15174412727355957s
License | MR license check for PARSEME-Ro corpus took 0.15559148788452148s
License | HR license check for PARSEME-Ro corpus took 10.15447449684143s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.1529841423034668s
Understandability | Number of label check for PARSEME-Ro corpus took 0.19933605194091797s
Understandability | URI regex check for PARSEME-Ro corpus took 0.3151416778564453s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.1537468433380127s
Verifiability | Authors check for PARSEME-Ro corpus took 0.15409564971923828s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.15696024894714355s
Performance | Throughput check for PARSEME-Ro corpus took 10.790326118469238s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 7.605552673339844e-05s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.15294361114501953s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 0.15291905403137207s
Interlinking | skos check for PARSEME-Ro corpus took 0.1532306671142578s
Interlinking | skos check for PARSEME-Ro corpus took 0.1549844741821289s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 0.1537177562713623s
Currency | Creation date check for PARSEME-Ro corpus took 0.30855846405029297s
Currency | Modification date check for PARSEME-Ro corpus took 0.3070676326751709s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 78.48205304145813s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.15450644493103027s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.15294408798217773s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.15308761596679688s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 2.175149440765381s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.2317342758178711s
Accuracy | Check Datatype consistency for PARSEME-Ro corpus took 3.968761682510376s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.15536856651306152s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 10.713843822479248s
Consistency | Check Ontology hijacking for PARSEME-Ro corpus took 29.766390800476074s
Consistency | Check Invalid usage of undefined classes for PARSEME-Ro corpus took 1.4374258518218994s
Consistency | Check Invalid usage of undefined properties for PARSEME-Ro corpus took 12.990426778793335s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 2.801605701446533s
Security | Sign check for PARSEME-Ro corpus took 0.15042328834533691s
Availability | Check URIs Dereferenciability for PARSEME-Ro corpus took 7.307445764541626s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.4570603370666504s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020518064498901367s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0006718635559082031s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.5762786865234375e-05s
Interoperability | Check the re-using of existing vocabs for PARSEME-Ro corpus took 1.9073486328125e-06s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.239776611328125e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 277.03812885284424s
Availability | SPARQL endpoint availability check for RoLEX took 0.15318918228149414s
Availability | VoID file availability check for RoLEX took 0.0006406307220458984s
Extra | Recovery of all triples for RoLEX took 33.94183135032654s
Performance | Total latancy measurement for RoLEX took 0.7637269496917725s
Amount of data | Number of triples check for RoLEX took 1.5819506645202637s
Interoperability | New terms check for RoLEX took 1.573990821838379s
Versatility | Languages check for RoLEX took 4.1226091384887695s
Interpretability | Number of blank nodes check for RoLEX took 1.0172834396362305s
Interpretability | RDF structures check for RoLEX took 0.1618788242340088s
Versatility | Serialization formats check for RoLEX took 0.15276050567626953s
Availability | RDF dump link check for RoLEX took 0.15245461463928223s
License | MR license check for RoLEX took 0.15352749824523926s
License | HR license check for RoLEX took 0.15374398231506348s
Amount of data | Number of property check for RoLEX took 0.15372800827026367s
Understandability | Number of label check for RoLEX took 0.15387272834777832s
Understandability | URI regex check for RoLEX took 0.3191030025482178s
Understandability | Vocabs check for RoLEX took 0.16507339477539062s
Verifiability | Authors check for RoLEX took 0.16028618812561035s
Verifiability | Publishers check for RoLEX took 0.15526866912841797s
Performance | Throughput check for RoLEX took 10.787564039230347s
Amount of data | Check the number of entities for RoLEX took 7.05718994140625e-05s
Verifiability | Contribs. check for RoLEX took 0.15578079223632812s
Interlinking | sameAs chians check for RoLEX took 0.15526413917541504s
Interlinking | skos check for RoLEX took 0.15503311157226562s
Interlinking | skos check for RoLEX took 0.15450048446655273s
Timeliness | dataset update frequency check for RoLEX took 0.15468335151672363s
Currency | Creation date check for RoLEX took 0.3206796646118164s
Currency | Modification date check for RoLEX took 0.30908942222595215s
Rep.Conc. | URIs length for RoLEX took 51.44925284385681s
Interoperability | New vocabularies check for RoLEX took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for RoLEX took 0.15130257606506348s
Accuracy | Check Functional Property for RoLEX took 0.15257000923156738s
Accuracy | Check Inverse Functional Property for RoLEX took 0.15242838859558105s
Accuracy | Check Datatype consistency for RoLEX took 4.115226745605469s
Consistency | Disjoint class check for RoLEX took 0.15365266799926758s
Consistency | Check Misplaced properties for RoLEX took 2.546839475631714s
Consistency | Check Ontology hijacking for RoLEX took 8.130118370056152s
Consistency | Check Invalid usage of undefined classes for RoLEX took 1.7354423999786377s
Consistency | Check Invalid usage of undefined properties for RoLEX took 4.730518579483032s
Conciseness | Check Extensional conciseness for RoLEX took 3.0401196479797363s
Security | Sign check for RoLEX took 0.1515803337097168s
Availability | Check URIs Dereferenciability for RoLEX took 7.475283145904541s
Completeness | Calculation of interlinking completeness for RoLEX took 0.4533836841583252s
Reputation | Calculation of the PageRank for RoLEX took 0.021181344985961914s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for RoLEX took 4.100799560546875e-05s
Interoperability | Check the re-using of existing vocabs for RoLEX took 1.9073486328125e-06s
Believability | Calculation of trust value for RoLEX took 1.0251998901367188e-05s
INFO | --- Analysis for racai-llod-rolex took 169.676824092865s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 8.749961853027344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.3214731216430664s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.0210723876953125s
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.0006835460662841797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.123283386230469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.1682510375976562e-05s
INFO | --- Analysis for racai-llod-romanian-treebank took 3.1847896575927734s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.2438507080078125e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.3115863800048828s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.02071690559387207s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 2.8133392333984375e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 1.2636184692382812e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 3.024564743041992s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.124641418457031e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.3273916244506836s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.0211484432220459s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0009348392486572266s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.314018249511719e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 1.1444091796875e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 3.040692090988159s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 5.53131103515625e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.3144805431365967s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.020534753799438477s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 2.9325485229492188e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.1444091796875e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 3.169567346572876s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.15517854690551758s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0006206035614013672s
Extra | Recovery of all triples for ROBIN Technical Acquisition Speech Corpus took 9.406314373016357s
Performance | Total latancy measurement for ROBIN Technical Acquisition Speech Corpus took 0.7611913681030273s
Amount of data | Number of triples check for ROBIN Technical Acquisition Speech Corpus took 0.3301272392272949s
Interoperability | New terms check for ROBIN Technical Acquisition Speech Corpus took 1.3196804523468018s
Versatility | Languages check for ROBIN Technical Acquisition Speech Corpus took 0.5999271869659424s
Interpretability | Number of blank nodes check for ROBIN Technical Acquisition Speech Corpus took 0.2728915214538574s
Interpretability | RDF structures check for ROBIN Technical Acquisition Speech Corpus took 0.15176725387573242s
Versatility | Serialization formats check for ROBIN Technical Acquisition Speech Corpus took 0.1511402130126953s
Availability | RDF dump link check for ROBIN Technical Acquisition Speech Corpus took 0.15024995803833008s
License | MR license check for ROBIN Technical Acquisition Speech Corpus took 0.15460658073425293s
License | HR license check for ROBIN Technical Acquisition Speech Corpus took 0.15725255012512207s
Amount of data | Number of property check for ROBIN Technical Acquisition Speech Corpus took 0.15188050270080566s
Understandability | Number of label check for ROBIN Technical Acquisition Speech Corpus took 0.1582345962524414s
Understandability | URI regex check for ROBIN Technical Acquisition Speech Corpus took 0.3058125972747803s
Understandability | Vocabs check for ROBIN Technical Acquisition Speech Corpus took 0.15340423583984375s
Verifiability | Authors check for ROBIN Technical Acquisition Speech Corpus took 0.15579533576965332s
Verifiability | Publishers check for ROBIN Technical Acquisition Speech Corpus took 0.1522202491760254s
Performance | Throughput check for ROBIN Technical Acquisition Speech Corpus took 10.71003794670105s
Amount of data | Check the number of entities for ROBIN Technical Acquisition Speech Corpus took 0.0001049041748046875s
Verifiability | Contribs. check for ROBIN Technical Acquisition Speech Corpus took 0.1526951789855957s
Interlinking | sameAs chians check for ROBIN Technical Acquisition Speech Corpus took 0.1524803638458252s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.15570497512817383s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.15148472785949707s
Timeliness | dataset update frequency check for ROBIN Technical Acquisition Speech Corpus took 0.15398859977722168s
Currency | Creation date check for ROBIN Technical Acquisition Speech Corpus took 0.3080430030822754s
Currency | Modification date check for ROBIN Technical Acquisition Speech Corpus took 0.3127167224884033s
Rep.Conc. | URIs length for ROBIN Technical Acquisition Speech Corpus took 2.5338685512542725s
Interoperability | New vocabularies check for ROBIN Technical Acquisition Speech Corpus took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for ROBIN Technical Acquisition Speech Corpus took 0.17046141624450684s
Accuracy | Check Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.15247488021850586s
Accuracy | Check Inverse Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.15417766571044922s
Accuracy | Check Empty annotation labels for ROBIN Technical Acquisition Speech Corpus took 0.41010475158691406s
Accuracy | Check White space in annotation for ROBIN Technical Acquisition Speech Corpus took 0.009686946868896484s
Accuracy | Check Datatype consistency for ROBIN Technical Acquisition Speech Corpus took 1.2100796699523926s
Consistency | Disjoint class check for ROBIN Technical Acquisition Speech Corpus took 0.15133190155029297s
Consistency | Check Misplaced properties for ROBIN Technical Acquisition Speech Corpus took 0.529329776763916s
Consistency | Check Ontology hijacking for ROBIN Technical Acquisition Speech Corpus took 1.8925058841705322s
Consistency | Check Invalid usage of undefined classes for ROBIN Technical Acquisition Speech Corpus took 1.157151222229004s
Consistency | Check Invalid usage of undefined properties for ROBIN Technical Acquisition Speech Corpus took 1.5105140209197998s
Conciseness | Check Extensional conciseness for ROBIN Technical Acquisition Speech Corpus took 0.820472240447998s
Security | Sign check for ROBIN Technical Acquisition Speech Corpus took 0.15128016471862793s
Availability | Check URIs Dereferenciability for ROBIN Technical Acquisition Speech Corpus took 3656.7367177009583s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.7176969051361084s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.02189469337463379s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 6.866455078125e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 4.1484832763671875e-05s
Interoperability | Check the re-using of existing vocabs for ROBIN Technical Acquisition Speech Corpus took 1.9073486328125e-06s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 1.0728836059570312e-05s
INFO | --- Analysis for racai-llod-rtasc took 3712.624929189682s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.15324664115905762s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0004963874816894531s
Extra | Recovery of all triples for SiMoNERo - the Romanian medical treebank took 33.858888387680054s
Performance | Total latancy measurement for SiMoNERo - the Romanian medical treebank took 0.7576014995574951s
Amount of data | Number of triples check for SiMoNERo - the Romanian medical treebank took 1.0799484252929688s
Interoperability | New terms check for SiMoNERo - the Romanian medical treebank took 1.4180152416229248s
Versatility | Languages check for SiMoNERo - the Romanian medical treebank took 2.395827054977417s
Interpretability | Number of blank nodes check for SiMoNERo - the Romanian medical treebank took 0.8181757926940918s
Interpretability | RDF structures check for SiMoNERo - the Romanian medical treebank took 0.15317153930664062s
Versatility | Serialization formats check for SiMoNERo - the Romanian medical treebank took 0.15535640716552734s
Availability | RDF dump link check for SiMoNERo - the Romanian medical treebank took 0.1523292064666748s
License | MR license check for SiMoNERo - the Romanian medical treebank took 0.1531047821044922s
License | HR license check for SiMoNERo - the Romanian medical treebank took 4.500190258026123s
Amount of data | Number of property check for SiMoNERo - the Romanian medical treebank took 0.1534266471862793s
Understandability | Number of label check for SiMoNERo - the Romanian medical treebank took 0.1584630012512207s
Understandability | URI regex check for SiMoNERo - the Romanian medical treebank took 0.30437421798706055s
Understandability | Vocabs check for SiMoNERo - the Romanian medical treebank took 0.1532285213470459s
Verifiability | Authors check for SiMoNERo - the Romanian medical treebank took 0.1535933017730713s
Verifiability | Publishers check for SiMoNERo - the Romanian medical treebank took 0.1532573699951172s
Performance | Throughput check for SiMoNERo - the Romanian medical treebank took 10.67650318145752s
Amount of data | Check the number of entities for SiMoNERo - the Romanian medical treebank took 6.794929504394531e-05s
Verifiability | Contribs. check for SiMoNERo - the Romanian medical treebank took 0.15291690826416016s
Interlinking | sameAs chians check for SiMoNERo - the Romanian medical treebank took 0.15311217308044434s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.1532759666442871s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.15249919891357422s
Timeliness | dataset update frequency check for SiMoNERo - the Romanian medical treebank took 0.15361261367797852s
Currency | Creation date check for SiMoNERo - the Romanian medical treebank took 0.3063497543334961s
Currency | Modification date check for SiMoNERo - the Romanian medical treebank took 0.3055727481842041s
Rep.Conc. | URIs length for SiMoNERo - the Romanian medical treebank took 9.242164611816406s
Interoperability | New vocabularies check for SiMoNERo - the Romanian medical treebank took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for SiMoNERo - the Romanian medical treebank took 0.15074586868286133s
Accuracy | Check Functional Property for SiMoNERo - the Romanian medical treebank took 0.15199923515319824s
Accuracy | Check Inverse Functional Property for SiMoNERo - the Romanian medical treebank took 0.15269851684570312s
Accuracy | Check Empty annotation labels for SiMoNERo - the Romanian medical treebank took 0.8433215618133545s
Accuracy | Check White space in annotation for SiMoNERo - the Romanian medical treebank took 0.01910114288330078s
Accuracy | Check Datatype consistency for SiMoNERo - the Romanian medical treebank took 4.082221984863281s
Consistency | Disjoint class check for SiMoNERo - the Romanian medical treebank took 0.15613031387329102s
Consistency | Check Misplaced properties for SiMoNERo - the Romanian medical treebank took 1.7092351913452148s
Consistency | Check Ontology hijacking for SiMoNERo - the Romanian medical treebank took 4.335158348083496s
Consistency | Check Invalid usage of undefined classes for SiMoNERo - the Romanian medical treebank took 1.2056686878204346s
Consistency | Check Invalid usage of undefined properties for SiMoNERo - the Romanian medical treebank took 2.6733176708221436s
Conciseness | Check Extensional conciseness for SiMoNERo - the Romanian medical treebank took 2.9210710525512695s
Security | Sign check for SiMoNERo - the Romanian medical treebank took 0.15278840065002441s
Availability | Check URIs Dereferenciability for SiMoNERo - the Romanian medical treebank took 1620.2068741321564s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.38660597801208496s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.02161693572998047s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 4.8160552978515625e-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.3828277587890625e-05s
INFO | --- Analysis for racai-llod-simonero took 1723.5112223625183s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.14636945724487305s
Availability | VoID file availability check for Rådata nå! took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.3080117702484131s
Reputation | Calculation of the PageRank for Rådata nå! took 0.021050691604614258s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.487701416015625e-05s
Believability | Calculation of trust value for Rådata nå! took 1.4066696166992188e-05s
INFO | --- Analysis for radatana took 4.899773836135864s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 5.650520324707031e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.34466099739074707s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.790855407714844e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 9.775161743164062e-06s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 17.285834550857544s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 13.019322872161865s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.31981372833251953s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.020760297775268555s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.719329833984375e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.1920928955078125e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 31.787654638290405s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 393.169225692749s
Availability | VoID file availability check for Polish LGU financial statements took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.37304162979125977s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.021013736724853516s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 3.600120544433594e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 1.3589859008789062e-05s
INFO | --- Analysis for Rb_PL_LGU took 668.2193715572357s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 9.34600830078125e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.3186984062194824s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020923376083374023s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 9.274482727050781e-05s
Believability | Calculation of trust value for RDF Book Mashup took 8.58306884765625e-06s
INFO | --- Analysis for rdf-book-mashup took 3.7275550365448s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.172325134277344e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.30324482917785645s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020931243896484375s
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.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00010013580322265625s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 1.0967254638671875e-05s
INFO | --- Analysis for rdfize-lastfm took 2.9221954345703125s
Availability | SPARQL endpoint availability check for RDFLicense took 260.54883074760437s
Availability | VoID file availability check for RDFLicense took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.3107011318206787s
Reputation | Calculation of the PageRank for RDFLicense took 0.02103400230407715s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.6716461181640625e-05s
Believability | Calculation of trust value for RDFLicense took 1.33514404296875e-05s
INFO | --- Analysis for rdflicense took 535.5849866867065s
Availability | SPARQL endpoint availability check for RDFohloh took 5.507469177246094e-05s
Availability | VoID file availability check for RDFohloh took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.29292964935302734s
Reputation | Calculation of the PageRank for RDFohloh took 0.02086496353149414s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 8.845329284667969e-05s
Believability | Calculation of trust value for RDFohloh took 7.3909759521484375e-06s
INFO | --- Analysis for rdfohloh took 7.560605525970459s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.560352087020874s
Availability | VoID file availability check for Reactome RDF took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.30672717094421387s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020403146743774414s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.5762786865234375e-05s
Believability | Calculation of trust value for Reactome RDF took 1.0251998901367188e-05s
INFO | --- Analysis for reactome-rdf took 4.131309509277344s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.14110207557678223s
Availability | VoID file availability check for Rechtspraak.nl took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.31255459785461426s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.021149873733520508s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.393692016601562e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 8.58306884765625e-06s
INFO | --- Analysis for rechtspraak took 3.0632288455963135s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 8.416175842285156e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0008249282836914062s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.31198978424072266s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.020952701568603516s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.559226989746094e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 1.2636184692382812e-05s
INFO | --- Analysis for red-uno-internacional-santillana took 8.525917053222656s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.06300187110900879s
Availability | VoID file availability check for reference.data.gov.uk took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.2935011386871338s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.021144866943359375s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00015091896057128906s
Believability | Calculation of trust value for reference.data.gov.uk took 9.059906005859375e-06s
INFO | --- Analysis for reference-data-gov-uk took 3.0429012775421143s
Availability | SPARQL endpoint availability check for RELD took 0.6343133449554443s
Availability | VoID file availability check for RELD took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for RELD took 0.31232476234436035s
Reputation | Calculation of the PageRank for RELD took 0.02111506462097168s
Interlinking | Calculation of Degree of Connection for RELD took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for RELD took 3.147125244140625e-05s
Believability | Calculation of trust value for RELD took 1.0967254638671875e-05s
INFO | --- Analysis for RELD took 4.261845350265503s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.21417903900146484s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0005640983581542969s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.2902116775512695s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.4624216556549072s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.3725106716156006s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.5542502403259277s
Versatility | Languages check for Repository for Linked Open Archival Data took 18.683319091796875s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 2.176708221435547s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.2282400131225586s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.30445075035095215s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.31870317459106445s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.16673874855041504s
License | MR license check for Repository for Linked Open Archival Data took 0.5067548751831055s
License | HR license check for Repository for Linked Open Archival Data took 8.93366265296936s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.14371037483215332s
Understandability | Number of label check for Repository for Linked Open Archival Data took 1.3361704349517822s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.565842866897583s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.10811805725097656s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.2041327953338623s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.21499323844909668s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.474663496017456s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 0.0001087188720703125s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.057123661041259766s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.13554167747497559s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.2001495361328125s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.0713493824005127s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.19112658500671387s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.1867527961730957s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.20618557929992676s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.7494096755981445s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.11262154579162598s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.11185717582702637s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.07059073448181152s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.34769415855407715s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.02771139144897461s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.029734373092651367s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.17151975631713867s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 2.1398391723632812s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.21860051155090332s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.504227638244629s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.1591832637786865s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 2.8143041133880615s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.03390932083129883s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.16864776611328125s
Security | Sign check for Repository for Linked Open Archival Data took 0.306795597076416s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 932.4235210418701s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.7499547004699707s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.02265024185180664s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 2.8371810913085938e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 4.839897155761719e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 2.1457672119140625e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 1.0967254638671875e-05s
INFO | --- Analysis for reload took 1056.8580031394958s
Availability | SPARQL endpoint availability check for Land use merced dataset took 4.482269287109375e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.31612300872802734s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.02083444595336914s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.24249267578125e-05s
Believability | Calculation of trust value for Land use merced dataset took 1.049041748046875e-05s
INFO | --- Analysis for remote_Sensing took 3.557748794555664s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 4.599823713302612s
Availability | VoID file availability check for Renewable Energy Generators took 0.000579833984375s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.29350805282592773s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.0215909481048584s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 5.221366882324219e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 9.059906005859375e-06s
INFO | --- Analysis for renewable_energy_generators took 127.71978044509888s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.09184765815734863s
Availability | VoID file availability check for research.data.gov.uk took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.31679821014404297s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020488977432250977s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.465217590332031e-05s
Believability | Calculation of trust value for research.data.gov.uk took 8.58306884765625e-06s
INFO | --- Analysis for research-data-gov-uk took 3.0381627082824707s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 0.00010037422180175781s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.30008411407470703s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.02091383934020996s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007059574127197266s
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.549611568450928s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.05808711051940918s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.31530046463012695s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007050037384033203s
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.1205673217773438e-05s
INFO | --- Analysis for revistas_turismo took 2.9358036518096924s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.293773889541626s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.28902721405029297s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.021045446395874023s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011730194091796875s
Believability | Calculation of trust value for Revyu.com - Review Anything took 1.0251998901367188e-05s
INFO | --- Analysis for revyu took 3.158458948135376s
Availability | SPARQL endpoint availability check for sdafsadf took 0.381669282913208s
Availability | VoID file availability check for sdafsadf took 0.00022149085998535156s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.31029272079467773s
Reputation | Calculation of the PageRank for sdafsadf took 0.021366357803344727s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.170967102050781e-05s
Believability | Calculation of trust value for sdafsadf took 1.1444091796875e-05s
INFO | --- Analysis for rgsdfg took 3.6874306201934814s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 8.606910705566406e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0006208419799804688s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.31165194511413574s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.021024703979492188s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.935264587402344e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 1.1682510375976562e-05s
INFO | --- Analysis for riese took 23.138015270233154s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.25820446014404297s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0005140304565429688s
Extra | Recovery of all triples for Répertoire International des Sources Musicales - RISM took 23.367897748947144s
Performance | Total latancy measurement for Répertoire International des Sources Musicales - RISM took 0.5346965789794922s
Amount of data | Number of triples check for Répertoire International des Sources Musicales - RISM took 55.941577196121216s
Interoperability | New terms check for Répertoire International des Sources Musicales - RISM took 1.8105294704437256s
Versatility | Languages check for Répertoire International des Sources Musicales - RISM took 164.6894314289093s
Interpretability | Number of blank nodes check for Répertoire International des Sources Musicales - RISM took 52.50339603424072s
Security | Check HTTPS for Répertoire International des Sources Musicales - RISM took 0.25264596939086914s
Interpretability | RDF structures check for Répertoire International des Sources Musicales - RISM took 0.17000079154968262s
Versatility | Serialization formats check for Répertoire International des Sources Musicales - RISM took 0.16524171829223633s
Availability | RDF dump link check for Répertoire International des Sources Musicales - RISM took 0.10367560386657715s
License | MR license check for Répertoire International des Sources Musicales - RISM took 0.1332721710205078s
License | HR license check for Répertoire International des Sources Musicales - RISM took 300.0639235973358s
Amount of data | Number of property check for Répertoire International des Sources Musicales - RISM took 0.18973040580749512s
Understandability | Number of label check for Répertoire International des Sources Musicales - RISM took 12.652692317962646s
Understandability | URI regex check for Répertoire International des Sources Musicales - RISM took 0.2649815082550049s
Understandability | Vocabs check for Répertoire International des Sources Musicales - RISM took 0.1107935905456543s
Verifiability | Authors check for Répertoire International des Sources Musicales - RISM took 0.1158287525177002s
Verifiability | Publishers check for Répertoire International des Sources Musicales - RISM took 0.10897231101989746s
Performance | Throughput check for Répertoire International des Sources Musicales - RISM took 10.767906665802002s
Amount of data | Check the number of entities for Répertoire International des Sources Musicales - RISM took 7.605552673339844e-05s
Verifiability | Contribs. check for Répertoire International des Sources Musicales - RISM took 0.11416077613830566s
Interlinking | sameAs chians check for Répertoire International des Sources Musicales - RISM took 1.2416532039642334s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.16544294357299805s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.11593413352966309s
Timeliness | dataset update frequency check for Répertoire International des Sources Musicales - RISM took 0.11274433135986328s
Currency | Creation date check for Répertoire International des Sources Musicales - RISM took 0.2610006332397461s
Currency | Modification date check for Répertoire International des Sources Musicales - RISM took 0.26239991188049316s
Rep.Conc. | URIs length for Répertoire International des Sources Musicales - RISM took 78.91933584213257s
Interoperability | New vocabularies check for Répertoire International des Sources Musicales - RISM took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Répertoire International des Sources Musicales - RISM took 0.15845394134521484s
Accuracy | Check Functional Property for Répertoire International des Sources Musicales - RISM took 0.14097380638122559s
Accuracy | Check Inverse Functional Property for Répertoire International des Sources Musicales - RISM took 0.11558794975280762s
Accuracy | Check Empty annotation labels for Répertoire International des Sources Musicales - RISM took 11.912176132202148s
Accuracy | Check White space in annotation for Répertoire International des Sources Musicales - RISM took 2.3696842193603516s
Accuracy | Check Datatype consistency for Répertoire International des Sources Musicales - RISM took 3.749236822128296s
Consistency | Disjoint class check for Répertoire International des Sources Musicales - RISM took 0.11646604537963867s
Consistency | Check Misplaced properties for Répertoire International des Sources Musicales - RISM took 46.447734117507935s
Consistency | Check Ontology hijacking for Répertoire International des Sources Musicales - RISM took 5.031883001327515s
Consistency | Check Invalid usage of undefined classes for Répertoire International des Sources Musicales - RISM took 1.233311414718628s
Consistency | Check Invalid usage of undefined properties for Répertoire International des Sources Musicales - RISM took 50.60766887664795s
Conciseness | Check Extensional conciseness for Répertoire International des Sources Musicales - RISM took 2.7322258949279785s
Security | Sign check for Répertoire International des Sources Musicales - RISM took 0.11899042129516602s
Availability | Check URIs Dereferenciability for Répertoire International des Sources Musicales - RISM took 1.7755095958709717s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.45339059829711914s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.0215451717376709s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 5.340576171875e-05s
Interoperability | Check the re-using of existing vocabs for Répertoire International des Sources Musicales - RISM took 3.814697265625e-06s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 1.33514404296875e-05s
INFO | --- Analysis for rism took 1252.007061958313s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.10137176513671875s
Availability | VoID file availability check for RISM Authority data took 0.00067138671875s
Extra | Recovery of all triples for RISM Authority data took 24.311477422714233s
Performance | Total latancy measurement for RISM Authority data took 0.579434871673584s
Amount of data | Number of triples check for RISM Authority data took 57.171228885650635s
Interoperability | New terms check for RISM Authority data took 1.387531042098999s
Versatility | Languages check for RISM Authority data took 165.70628428459167s
Interpretability | Number of blank nodes check for RISM Authority data took 46.13336205482483s
Security | Check HTTPS for RISM Authority data took 0.15565991401672363s
Interpretability | RDF structures check for RISM Authority data took 0.15512681007385254s
Versatility | Serialization formats check for RISM Authority data took 0.13427066802978516s
Availability | RDF dump link check for RISM Authority data took 0.10546231269836426s
License | MR license check for RISM Authority data took 0.13760590553283691s
License | HR license check for RISM Authority data took 300.02324533462524s
Amount of data | Number of property check for RISM Authority data took 0.14481067657470703s
Understandability | Number of label check for RISM Authority data took 5.5580644607543945s
Understandability | URI regex check for RISM Authority data took 0.24308443069458008s
Understandability | Vocabs check for RISM Authority data took 0.10085701942443848s
Verifiability | Authors check for RISM Authority data took 0.10416793823242188s
Verifiability | Publishers check for RISM Authority data took 0.10350918769836426s
Performance | Throughput check for RISM Authority data took 10.225789308547974s
Amount of data | Check the number of entities for RISM Authority data took 0.00013136863708496094s
Verifiability | Contribs. check for RISM Authority data took 0.10736846923828125s
Interlinking | sameAs chians check for RISM Authority data took 1.315843105316162s
Interlinking | skos check for RISM Authority data took 0.13473248481750488s
Interlinking | skos check for RISM Authority data took 0.1018064022064209s
Timeliness | dataset update frequency check for RISM Authority data took 0.10333466529846191s
Currency | Creation date check for RISM Authority data took 0.23558974266052246s
Currency | Modification date check for RISM Authority data took 0.23462843894958496s
Rep.Conc. | URIs length for RISM Authority data took 79.23465609550476s
Interoperability | New vocabularies check for RISM Authority data took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for RISM Authority data took 0.1450955867767334s
Accuracy | Check Functional Property for RISM Authority data took 0.13231587409973145s
Accuracy | Check Inverse Functional Property for RISM Authority data took 0.10443854331970215s
Accuracy | Check Empty annotation labels for RISM Authority data took 12.921084642410278s
Accuracy | Check White space in annotation for RISM Authority data took 2.3732218742370605s
Accuracy | Check Datatype consistency for RISM Authority data took 3.854567527770996s
Consistency | Disjoint class check for RISM Authority data took 0.10142922401428223s
Consistency | Check Misplaced properties for RISM Authority data took 46.08194303512573s
Consistency | Check Ontology hijacking for RISM Authority data took 5.307686805725098s
Consistency | Check Invalid usage of undefined classes for RISM Authority data took 1.220592975616455s
Consistency | Check Invalid usage of undefined properties for RISM Authority data took 47.15082001686096s
Conciseness | Check Extensional conciseness for RISM Authority data took 2.859916925430298s
Security | Sign check for RISM Authority data took 0.11685705184936523s
Availability | Check URIs Dereferenciability for RISM Authority data took 1.4716715812683105s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.6170737743377686s
Reputation | Calculation of the PageRank for RISM Authority data took 0.021369218826293945s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0006761550903320312s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 5.91278076171875e-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.1920928955078125e-05s
INFO | --- Analysis for rism-authorities took 1243.8198068141937s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 8.630752563476562e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.3130970001220703s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020975351333618164s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 4.6253204345703125e-05s
Believability | Calculation of trust value for engineering equipment ontology took 9.298324584960938e-06s
INFO | --- Analysis for rk took 2.8473029136657715s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.04220414161682129s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.31381750106811523s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.02247166633605957s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002238750457763672s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-acm took 2.9772043228149414s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.04806351661682129s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.30269646644592285s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.02141261100769043s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.0001354217529296875s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-budapest took 2.901966094970703s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.05162215232849121s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.30758047103881836s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.020770788192749023s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0006847381591796875s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.0001983642578125s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-citeseer took 2.9399116039276123s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.04953479766845703s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.3080906867980957s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.02095961570739746s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00017571449279785156s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-cordis took 2.906764030456543s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.043822288513183594s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00042319297790527344s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.30750226974487305s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.02306056022644043s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.0001552104949951172s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-courseware took 2.9323630332946777s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.0489044189453125s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.3343009948730469s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.0215909481048584s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007202625274658203s
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 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.950360059738159s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.03485393524169922s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.2900526523590088s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.021103382110595703s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00011849403381347656s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-curriculum took 2.9371390342712402s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.04904460906982422s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.31262779235839844s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.020650625228881836s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.1975250244140625e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.842588186264038s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0538640022277832s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.3085644245147705s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.02118062973022461s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002319812774658203s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-dblp took 2.9164857864379883s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.041208744049072266s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.30930519104003906s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.022258281707763672s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.414817810058594e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-deepblue took 2.932166814804077s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.32723474502563477s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.2979307174682617s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.02253127098083496s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.202957153320312e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-deploy took 4.162858486175537s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.0434112548828125s
Availability | VoID file availability check for digitaleconomy took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.3126673698425293s
Reputation | Calculation of the PageRank for digitaleconomy took 0.022690773010253906s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 4.029273986816406e-05s
Believability | Calculation of trust value for digitaleconomy took 5.245208740234375e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.9528543949127197s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.042508840560913086s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.3080103397369385s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.02268671989440918s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00013971328735351562s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-dotac took 2.8601601123809814s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.04215121269226074s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.31050848960876465s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.021921157836914062s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.553794860839844e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-ecs took 4.432250022888184s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.057280540466308594s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0004277229309082031s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.33540892601013184s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.02095198631286621s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00017595291137695312s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-eprints took 2.9709746837615967s
Availability | SPARQL endpoint availability check for epsrc took 0.0493016242980957s
Availability | VoID file availability check for epsrc took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for epsrc took 0.31377363204956055s
Reputation | Calculation of the PageRank for epsrc took 0.02111959457397461s
Interlinking | Calculation of Degree of Connection for epsrc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.888938903808594e-05s
Believability | Calculation of trust value for epsrc took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-epsrc took 2.8930747509002686s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.04362058639526367s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.33453869819641113s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0209658145904541s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.535385131835938e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-era took 2.934462785720825s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.034340620040893555s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.3342247009277344s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.02090740203857422s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010442733764648438s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 5.4836273193359375e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.955108165740967s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.40206098556518555s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.30524563789367676s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.021142244338989258s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.083747863769531e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-ft took 4.2850987911224365s
Availability | SPARQL endpoint availability check for fun took 0.04980659484863281s
Availability | VoID file availability check for fun took 0.00021147727966308594s
Completeness | Calculation of interlinking completeness for fun took 0.3093852996826172s
Reputation | Calculation of the PageRank for fun took 0.021016597747802734s
Interlinking | Calculation of Degree of Connection for fun took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for fun took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for fun took 7.104873657226562e-05s
Believability | Calculation of trust value for fun took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-fun took 2.879460096359253s
Availability | SPARQL endpoint availability check for gdlc took 0.05027580261230469s
Availability | VoID file availability check for gdlc took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for gdlc took 0.3172938823699951s
Reputation | Calculation of the PageRank for gdlc took 0.02141594886779785s
Interlinking | Calculation of Degree of Connection for gdlc took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.961822509765625e-05s
Believability | Calculation of trust value for gdlc took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.898491859436035s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.04695415496826172s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0002067089080810547s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.3126828670501709s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020665645599365234s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011301040649414062s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-ibm took 2.8857760429382324s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.04664754867553711s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00021982192993164062s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.30321550369262695s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020763635635375977s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.00012993812561035156s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.8601109981536865s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.030524015426635742s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.301375150680542s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00013446807861328125s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 5.4836273193359375e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.9000003337860107s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.030809402465820312s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.00021028518676757812s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.305417537689209s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 8.7738037109375e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.8381106853485107s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.04851961135864258s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.00020694732666015625s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.3026599884033203s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.021017789840698242s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.390975952148438e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 5.245208740234375e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.8283846378326416s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.031032800674438477s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0002148151397705078s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.30077457427978516s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.020746469497680664s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.38690185546875e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 5.4836273193359375e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.8782317638397217s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.04543590545654297s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.30837035179138184s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.022124290466308594s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00016355514526367188s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-kisti took 2.921234607696533s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.046054840087890625s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.00022339820861816406s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.3031001091003418s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.021007061004638672s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.0001456737518310547s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.787641763687134s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.04195690155029297s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0004208087921142578s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.30599117279052734s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.02095818519592285s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.508827209472656e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 2.8991775512695312s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.05014991760253906s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.00041031837463378906s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.3116116523742676s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.021327495574951172s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00015354156494140625s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.964829683303833s
Availability | SPARQL endpoint availability check for notube took 0.04999232292175293s
Availability | VoID file availability check for notube took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for notube took 0.31630873680114746s
Reputation | Calculation of the PageRank for notube took 0.02086615562438965s
Interlinking | Calculation of Degree of Connection for notube took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for notube took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for notube took 4.291534423828125e-05s
Believability | Calculation of trust value for notube took 1.3589859008789062e-05s
INFO | --- Analysis for rkb-explorer-notube took 2.9462802410125732s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.043192148208618164s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.31487512588500977s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00012922286987304688s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-nsf took 2.922429323196411s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.05177021026611328s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.30872678756713867s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.02106952667236328s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00015497207641601562s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-oai took 2.9557716846466064s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.05020499229431152s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0004153251647949219s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.33368706703186035s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.02248668670654297s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 3.647804260253906e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.367134094238281e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-os took 2.9648871421813965s
Availability | SPARQL endpoint availability check for photos took 0.04215121269226074s
Availability | VoID file availability check for photos took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for photos took 0.3134739398956299s
Reputation | Calculation of the PageRank for photos took 0.021121740341186523s
Interlinking | Calculation of Degree of Connection for photos took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for photos took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for photos took 6.985664367675781e-05s
Believability | Calculation of trust value for photos took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-photos took 2.9628913402557373s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.05028176307678223s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0004088878631591797s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.309734582901001s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.022303104400634766s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011348724365234375s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.8950116634368896s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.05762171745300293s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.00041222572326660156s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.28789639472961426s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.021088123321533203s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019121170043945312s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.902121067047119s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.05169177055358887s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00040078163146972656s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.30983519554138184s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.02102828025817871s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00013828277587890625s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.938636541366577s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.042682647705078125s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.00048828125s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.3098611831665039s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.021870851516723633s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.441375732421875e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-risks took 2.8914971351623535s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.04316973686218262s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.3172945976257324s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020850658416748047s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012731552124023438s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-roma took 2.9817464351654053s
Availability | SPARQL endpoint availability check for roni took 0.03388094902038574s
Availability | VoID file availability check for roni took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for roni took 0.33466124534606934s
Reputation | Calculation of the PageRank for roni took 0.022385835647583008s
Interlinking | Calculation of Degree of Connection for roni took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for roni took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for roni took 2.86102294921875e-05s
Believability | Calculation of trust value for roni took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-roni took 3.011199951171875s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.03357076644897461s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.31211256980895996s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0002143383026123047s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-southampton took 2.9057657718658447s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.04959702491760254s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.3117678165435791s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.020926475524902344s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00011157989501953125s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-ulm took 2.972872734069824s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.035613059997558594s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.3087906837463379s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.02066659927368164s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.72747802734375e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-unlocode took 2.928041458129883s
Availability | SPARQL endpoint availability check for webconf took 0.04952216148376465s
Availability | VoID file availability check for webconf took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for webconf took 0.29027247428894043s
Reputation | Calculation of the PageRank for webconf took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for webconf took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010061264038085938s
Believability | Calculation of trust value for webconf took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-webconf took 13.34424376487732s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.03470110893249512s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.36298370361328125s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 6.580352783203125e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-webscience took 3.035526990890503s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.04892444610595703s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.3348398208618164s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.02060389518737793s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00020194053649902344s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-wiki took 2.895322799682617s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.03533363342285156s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.3078887462615967s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.021189212799072266s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.465217590332031e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-wordnet took 2.9798500537872314s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.4193699359893799s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0005292892456054688s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 41.731096029281616s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.4662933349609375s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 1.4805817604064941s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.518864393234253s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 4.6011223793029785s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.2825813293457031s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.0970451831817627s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.09626221656799316s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.09612607955932617s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.09437012672424316s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.09481072425842285s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.10780501365661621s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.09623169898986816s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.19564461708068848s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.09656667709350586s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.09489035606384277s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.1025242805480957s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.261635303497314s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 5.626678466796875e-05s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.09284830093383789s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.09250593185424805s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.10735845565795898s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.09557151794433594s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.09295344352722168s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.1853947639465332s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.1896040439605713s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 21.770412921905518s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.0969088077545166s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.0932002067565918s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.09456110000610352s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 3.869685649871826s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.0956563949584961s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 2.8651957511901855s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 5.595314264297485s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.3639719486236572s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.13516902923584s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 3.024677038192749s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.0934133529663086s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 513.5252554416656s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.3880748748779297s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.02281975746154785s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 5.984306335449219e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 8.440017700195312e-05s
Interoperability | Check the re-using of existing vocabs for ROCEEH Out of Africa Database (ROAD) took 2.384185791015625e-06s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 1.33514404296875e-05s
INFO | --- Analysis for roceeh-road took 639.968138217926s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 4.8160552978515625e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0007126331329345703s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.3084557056427002s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 2.8371810913085938e-05s
Believability | Calculation of trust value for ontology terrorist attack took 7.152557373046875e-06s
INFO | --- Analysis for ROSHANI took 5.024385929107666s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.267692565917969e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.31189680099487305s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.314018249511719e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 7.152557373046875e-06s
INFO | --- Analysis for ROSHANI_SAHU took 2.756842851638794s
Availability | SPARQL endpoint availability check for x took 4.3392181396484375e-05s
Availability | VoID file availability check for x took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for x took 0.3059420585632324s
Reputation | Calculation of the PageRank for x took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for x took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for x took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for x took 2.8133392333984375e-05s
Believability | Calculation of trust value for x took 7.152557373046875e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.71646785736084s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.172325134277344e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.3095993995666504s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 9.775161743164062e-06s
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.508827209472656e-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.36175274848938s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.124641418457031e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.3080122470855713s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020702600479125977s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.033348083496094e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 5.245208740234375e-06s
INFO | --- Analysis for rubentaelman took 3.3403751850128174s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.029273986816406e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.2973911762237549s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.020430564880371094s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.034706115722656e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 5.7220458984375e-06s
INFO | --- Analysis for rubenverborgh took 3.5728516578674316s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 392.7917170524597s
Availability | VoID file availability check for Russian Universities Specialities took 0.0007455348968505859s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.28919148445129395s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.022054433822631836s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.935264587402344e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 7.62939453125e-06s
INFO | --- Analysis for russian-universities-specialities took 678.0596830844879s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 4.924953937530518s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.30913352966308594s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.02112412452697754s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.361701965332031e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 1.1444091796875e-05s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 10.466903448104858s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.0458436012268066s
Availability | VoID file availability check for SALDO-RDF took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.3010690212249756s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.02072930335998535s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for SALDO-RDF took 6.198883056640625e-06s
INFO | --- Analysis for saldo-rdf took 6.062172174453735s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6570098400115967s
Availability | VoID file availability check for SALDOM-RDF took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.3064136505126953s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020816802978515625s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.552436828613281e-05s
Believability | Calculation of trust value for SALDOM-RDF took 6.67572021484375e-06s
INFO | --- Analysis for saldom-rdf took 5.37733268737793s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 8.869171142578125e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.30631208419799805s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.02084946632385254s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010466575622558594s
Believability | Calculation of trust value for Salzburgerland DE took 5.7220458984375e-06s
INFO | --- Analysis for salzburgerland-com-de took 3.4968857765197754s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.267692565917969e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.31456971168518066s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.020522594451904297s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00010561943054199219s
Believability | Calculation of trust value for Salzburgerland EN took 6.9141387939453125e-06s
INFO | --- Analysis for salzburgerland-com-en took 3.274655818939209s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.2438507080078125e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.3133542537689209s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.020792245864868164s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00010061264038085938s
Believability | Calculation of trust value for Salzburgerland IT took 5.7220458984375e-06s
INFO | --- Analysis for salzburgerland-com-it took 3.3432157039642334s
Availability | SPARQL endpoint availability check for sandrart.net took 8.726119995117188e-05s
Availability | VoID file availability check for sandrart.net took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.31544971466064453s
Reputation | Calculation of the PageRank for sandrart.net took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.723403930664062e-05s
Believability | Calculation of trust value for sandrart.net took 1.1682510375976562e-05s
INFO | --- Analysis for sandrart-net took 4.587352991104126s
Availability | SPARQL endpoint availability check for Taxons  took 0.2369985580444336s
Availability | VoID file availability check for Taxons  took 0.00046753883361816406s
Extra | Recovery of all triples for Taxons  took 20.94009804725647s
Performance | Total latancy measurement for Taxons  took 0.5851023197174072s
Amount of data | Number of triples check for Taxons  took 2.2033298015594482s
Interoperability | New terms check for Taxons  took 1.7333862781524658s
Versatility | Languages check for Taxons  took 42.016212701797485s
Interpretability | Number of blank nodes check for Taxons  took 1.3024303913116455s
Security | Check HTTPS for Taxons  took 0.2585732936859131s
Interpretability | RDF structures check for Taxons  took 1.1838607788085938s
Versatility | Serialization formats check for Taxons  took 0.4521033763885498s
Availability | RDF dump link check for Taxons  took 0.2587594985961914s
License | MR license check for Taxons  took 1.889460802078247s
License | HR license check for Taxons  took 2.3371217250823975s
Amount of data | Number of property check for Taxons  took 0.1460573673248291s
Understandability | Number of label check for Taxons  took 3.4532570838928223s
Understandability | URI regex check for Taxons  took 0.8236312866210938s
Understandability | Vocabs check for Taxons  took 0.3419675827026367s
Verifiability | Authors check for Taxons  took 0.11952710151672363s
Verifiability | Publishers check for Taxons  took 0.11118602752685547s
Performance | Throughput check for Taxons  took 10.770450353622437s
Amount of data | Check the number of entities for Taxons  took 6.67572021484375e-05s
Verifiability | Contribs. check for Taxons  took 0.11374735832214355s
Interlinking | sameAs chians check for Taxons  took 0.2545456886291504s
Interlinking | skos check for Taxons  took 0.20899486541748047s
Interlinking | skos check for Taxons  took 0.11590933799743652s
Timeliness | dataset update frequency check for Taxons  took 0.7439641952514648s
Currency | Creation date check for Taxons  took 0.2700614929199219s
Currency | Modification date check for Taxons  took 0.26575183868408203s
Rep.Conc. | URIs length for Taxons  took 9.494294166564941s
Interoperability | New vocabularies check for Taxons  took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.1385669708251953s
Accuracy | Check Functional Property for Taxons  took 0.48357319831848145s
Accuracy | Check Inverse Functional Property for Taxons  took 0.25307369232177734s
Accuracy | Check Empty annotation labels for Taxons  took 4.383152961730957s
Accuracy | Check White space in annotation for Taxons  took 0.302640438079834s
Accuracy | Check Datatype consistency for Taxons  took 0.2608354091644287s
Consistency | Disjoint class check for Taxons  took 0.1574230194091797s
Consistency | Check Misplaced properties for Taxons  took 4.681122541427612s
Consistency | Misplaced classes for Taxons  took 1.004695177078247s
Consistency | Check Ontology hijacking for Taxons  took 4.813840389251709s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.1343183517456055s
Consistency | Check Invalid usage of undefined properties for Taxons  took 6.2804155349731445s
Conciseness | Check Extensional conciseness for Taxons  took 0.2823295593261719s
Conciseness | Check Intensional conciseness for Taxons  took 0.25230860710144043s
Security | Sign check for Taxons  took 1.5210776329040527s
Availability | Check URIs Dereferenciability for Taxons  took 1768.2640841007233s
Completeness | Calculation of interlinking completeness for Taxons  took 0.5346524715423584s
Reputation | Calculation of the PageRank for Taxons  took 0.02224278450012207s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Taxons  took 8.988380432128906e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 2.1457672119140625e-06s
Believability | Calculation of trust value for Taxons  took 1.239776611328125e-05s
INFO | --- Analysis for sandre took 1966.8955779075623s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 10.62924313545227s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.3100564479827881s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.022762060165405273s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 2.8133392333984375e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 1.1682510375976562e-05s
INFO | --- Analysis for sanskrit-english-lexicon took 32.149832010269165s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 265.5647039413452s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0007371902465820312s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.37200093269348145s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.020929574966430664s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 3.910064697265625e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 7.62939453125e-06s
INFO | --- Analysis for santillana_guide_dataset took 670.4319758415222s
Availability | SPARQL endpoint availability check for SATAR test  took 9.465217590332031e-05s
Availability | VoID file availability check for SATAR test  took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.3388998508453369s
Reputation | Calculation of the PageRank for SATAR test  took 0.021158456802368164s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 3.647804260253906e-05s
Believability | Calculation of trust value for SATAR test  took 1.4066696166992188e-05s
INFO | --- Analysis for SATAR_test took 5.640665292739868s
Availability | SPARQL endpoint availability check for SCBG Data took 22.27821373939514s
Availability | VoID file availability check for SCBG Data took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.315410852432251s
Reputation | Calculation of the PageRank for SCBG Data took 0.022713184356689453s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.296966552734375e-05s
Believability | Calculation of trust value for SCBG Data took 1.1444091796875e-05s
INFO | --- Analysis for SCBG-Data took 55.20400857925415s
Availability | SPARQL endpoint availability check for Schemantra took 8.344650268554688e-05s
Availability | VoID file availability check for Schemantra took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Schemantra took 0.317493200302124s
Reputation | Calculation of the PageRank for Schemantra took 0.021113157272338867s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Schemantra took 3.218650817871094e-05s
Believability | Calculation of trust value for Schemantra took 1.3113021850585938e-05s
INFO | --- Analysis for Schemantra took 2.8637053966522217s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 1.3533976078033447s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.001363515853881836s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.31365108489990234s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.021543502807617188s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.600120544433594e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 1.33514404296875e-05s
INFO | --- Analysis for schemapedia took 4.677343368530273s
Availability | SPARQL endpoint availability check for Scholarometer took 6.67572021484375e-05s
Availability | VoID file availability check for Scholarometer took 0.00040912628173828125s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.31162023544311523s
Reputation | Calculation of the PageRank for Scholarometer took 0.02105879783630371s
Interlinking | Calculation of Degree of Connection for Scholarometer took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.726119995117188e-05s
Believability | Calculation of trust value for Scholarometer took 1.0967254638671875e-05s
INFO | --- Analysis for scholarometer took 7.93215537071228s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 4.601478576660156e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.3364400863647461s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.022943735122680664s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 3.123283386230469e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 9.059906005859375e-06s
INFO | --- Analysis for scoreboard took 5.322855234146118s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 8.511543273925781e-05s
Availability | VoID file availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.3096475601196289s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.020885229110717773s
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.0251998901367188e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.8623809814453125e-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.1920928955078125e-05s
INFO | --- Analysis for SDDEC took 29.891294956207275s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 9.322166442871094e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.3195350170135498s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.020925283432006836s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 3.0517578125e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.2874603271484375e-05s
INFO | --- Analysis for SDG took 3.8015964031219482s
Availability | SPARQL endpoint availability check for sears.com took 8.869171142578125e-05s
Availability | VoID file availability check for sears.com took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for sears.com took 0.31876301765441895s
Reputation | Calculation of the PageRank for sears.com took 0.02254176139831543s
Interlinking | Calculation of Degree of Connection for sears.com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.699562072753906e-05s
Believability | Calculation of trust value for sears.com took 1.2159347534179688e-05s
INFO | --- Analysis for sears took 5.7971510887146s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.08991384506225586s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.3118913173675537s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0207977294921875s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.440017700195312e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.059906005859375e-06s
INFO | --- Analysis for sec-rdfabout took 6.8034703731536865s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.72789239883423s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.31879663467407227s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.021389007568359375s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 9.560585021972656e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for secold took 168.30838990211487s
Availability | SPARQL endpoint availability check for semanlink took 4.315376281738281e-05s
Availability | VoID file availability check for semanlink took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for semanlink took 0.31421780586242676s
Reputation | Calculation of the PageRank for semanlink took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for semanlink took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00014495849609375s
Believability | Calculation of trust value for semanlink took 1.1682510375976562e-05s
INFO | --- Analysis for semanlink took 4.109450340270996s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.08074283599853516s
Availability | VoID file availability check for Semantic Universe Data took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.3147311210632324s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.020978212356567383s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.266334533691406e-05s
Believability | Calculation of trust value for Semantic Universe Data took 1.2636184692382812e-05s
INFO | --- Analysis for semantic-universe took 3.0589964389801025s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.44956374168396s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.30910301208496094s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020830154418945312s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00012350082397460938s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.2636184692382812e-05s
INFO | --- Analysis for semantic-web-dog-food took 83.54993844032288s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 8.654594421386719e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0007178783416748047s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.3129394054412842s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020857572555541992s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.6253204345703125e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 1.2636184692382812e-05s
INFO | --- Analysis for semantic-web-grundlagen took 3.448659658432007s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 0.00014162063598632812s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.31504034996032715s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020792722702026367s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0009953975677490234s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 9.72747802734375e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 1.0013580322265625e-05s
INFO | --- Analysis for semantic-xbrl took 3.91567325592041s
Availability | SPARQL endpoint availability check for Semantic Quran took 7.031149625778198s
Availability | VoID file availability check for Semantic Quran took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Semantic Quran took 0.31728053092956543s
Reputation | Calculation of the PageRank for Semantic Quran took 0.020853042602539062s
Interlinking | Calculation of Degree of Connection for Semantic Quran took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic Quran took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Semantic Quran took 7.390975952148438e-05s
Believability | Calculation of trust value for Semantic Quran took 1.1920928955078125e-05s
INFO | --- Analysis for semanticquran took 16.21718406677246s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.1484832763671875e-05s
Availability | VoID file availability check for SemanticTweet took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.3161799907684326s
Reputation | Calculation of the PageRank for SemanticTweet took 0.020904064178466797s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.9604644775390625e-05s
Believability | Calculation of trust value for SemanticTweet took 1.0728836059570312e-05s
INFO | --- Analysis for semantictweet took 3.0101518630981445s
Availability | SPARQL endpoint availability check for semanticweb.org took 9.298324584960938e-05s
Availability | VoID file availability check for semanticweb.org took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.31085968017578125s
Reputation | Calculation of the PageRank for semanticweb.org took 0.02048516273498535s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.891654968261719e-05s
Believability | Calculation of trust value for semanticweb.org took 1.1205673217773438e-05s
INFO | --- Analysis for semanticweb-org took 23.197343587875366s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.09766221046447754s
Availability | VoID file availability check for Semantic CrunchBase took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.31293797492980957s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.021836042404174805s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.842613220214844e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 1.239776611328125e-05s
INFO | --- Analysis for semsol-crunchbase took 2.9923880100250244s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.28046274185180664s
Availability | VoID file availability check for SentimentWortschatz took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.31739163398742676s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020488262176513672s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.124641418457031e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.239776611328125e-05s
INFO | --- Analysis for sentiws took 4.59730863571167s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.019902229309082s
Availability | VoID file availability check for seoul-bike-data took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.3112905025482178s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.022348403930664062s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 3.9577484130859375e-05s
Believability | Calculation of trust value for seoul-bike-data took 1.0728836059570312e-05s
INFO | --- Analysis for seoul-bike-data took 73.24659252166748s
Availability | SPARQL endpoint availability check for Serendipity took 8.258904457092285s
Availability | VoID file availability check for Serendipity took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Serendipity took 0.3182516098022461s
Reputation | Calculation of the PageRank for Serendipity took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Serendipity took 7.62939453125e-05s
Believability | Calculation of trust value for Serendipity took 1.2636184692382812e-05s
INFO | --- Analysis for serendipity took 16.154154062271118s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 5.245208740234375e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.31569910049438477s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.022413969039916992s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 2.8848648071289062e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 1.0251998901367188e-05s
INFO | --- Analysis for Sherry_Wine took 3.013972759246826s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.1961669921875e-05s
Availability | VoID file availability check for Sherry Wine took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.3090035915374756s
Reputation | Calculation of the PageRank for Sherry Wine took 0.02090597152709961s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 2.765655517578125e-05s
Believability | Calculation of trust value for Sherry Wine took 1.0013580322265625e-05s
INFO | --- Analysis for Sherry_Wine_ took 2.7619173526763916s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.20281124114990234s
Availability | VoID file availability check for Shoah victims? names took 0.2602996826171875s
Extra | Recovery of all triples for Shoah victims? names took 1.3605232238769531s
Performance | Total latancy measurement for Shoah victims? names took 0.3761262893676758s
Amount of data | Number of triples check for Shoah victims? names took 1.4335150718688965s
Interoperability | New terms check for Shoah victims? names took 1.5221648216247559s
Versatility | Languages check for Shoah victims? names took 19.022396564483643s
Interpretability | Number of blank nodes check for Shoah victims? names took 2.13574481010437s
Security | Check HTTPS for Shoah victims? names took 0.2187049388885498s
Interpretability | RDF structures check for Shoah victims? names took 0.3094794750213623s
Versatility | Serialization formats check for Shoah victims? names took 0.27932024002075195s
Availability | RDF dump link check for Shoah victims? names took 0.1948862075805664s
License | MR license check for Shoah victims? names took 0.40222907066345215s
License | HR license check for Shoah victims? names took 10.58333420753479s
Amount of data | Number of property check for Shoah victims? names took 0.1435837745666504s
Understandability | Number of label check for Shoah victims? names took 1.488626480102539s
Understandability | URI regex check for Shoah victims? names took 0.5187883377075195s
Understandability | Vocabs check for Shoah victims? names took 0.1157522201538086s
Verifiability | Authors check for Shoah victims? names took 0.2000284194946289s
Verifiability | Publishers check for Shoah victims? names took 0.1815638542175293s
Performance | Throughput check for Shoah victims? names took 10.576097249984741s
Amount of data | Check the number of entities for Shoah victims? names took 7.605552673339844e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.07216072082519531s
Interlinking | sameAs chians check for Shoah victims? names took 0.1112673282623291s
Interlinking | skos check for Shoah victims? names took 0.25353407859802246s
Interlinking | skos check for Shoah victims? names took 0.06914377212524414s
Timeliness | dataset update frequency check for Shoah victims? names took 0.2657277584075928s
Currency | Creation date check for Shoah victims? names took 0.21094632148742676s
Currency | Modification date check for Shoah victims? names took 0.22434115409851074s
Rep.Conc. | URIs length for Shoah victims? names took 2.9374048709869385s
Interoperability | New vocabularies check for Shoah victims? names took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.10618019104003906s
Accuracy | Check Functional Property for Shoah victims? names took 0.10511660575866699s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.08114051818847656s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.4825155735015869s
Accuracy | Check White space in annotation for Shoah victims? names took 0.02776050567626953s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.03174543380737305s
Consistency | Disjoint class check for Shoah victims? names took 0.20836901664733887s
Consistency | Check Misplaced properties for Shoah victims? names took 1.934666633605957s
Consistency | Misplaced classes for Shoah victims? names took 0.20363998413085938s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.5193052291870117s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.111076831817627s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.0633511543273926s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.03291940689086914s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.17884230613708496s
Security | Sign check for Shoah victims? names took 0.6226556301116943s
Availability | Check URIs Dereferenciability for Shoah victims? names took 921.6788353919983s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.7401361465454102s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.021558761596679688s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 0.00015616416931152344s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 5.6743621826171875e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 2.384185791015625e-06s
Believability | Calculation of trust value for Shoah victims? names took 1.0967254638671875e-05s
INFO | --- Analysis for shoah-victims-names took 1040.6658322811127s
Availability | SPARQL endpoint availability check for Person took 6.222724914550781e-05s
Availability | VoID file availability check for Person took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Person took 0.30297303199768066s
Reputation | Calculation of the PageRank for Person took 0.02099442481994629s
Interlinking | Calculation of Degree of Connection for Person took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Person took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Person took 3.457069396972656e-05s
Believability | Calculation of trust value for Person took 1.2636184692382812e-05s
INFO | --- Analysis for Shripriya_Dubey took 2.817869186401367s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 4.696846008300781e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.30331921577453613s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.02073836326599121s
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.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 3.218650817871094e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 1.239776611328125e-05s
INFO | --- Analysis for Shutterstock took 2.8092312812805176s
Availability | SPARQL endpoint availability check for SIMPLE took 6.747245788574219e-05s
Availability | VoID file availability check for SIMPLE took 0.0003542900085449219s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.3036632537841797s
Reputation | Calculation of the PageRank for SIMPLE took 0.020679235458374023s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 3.814697265625e-05s
Believability | Calculation of trust value for SIMPLE took 7.3909759521484375e-06s
INFO | --- Analysis for simple took 8.188946962356567s
Availability | SPARQL endpoint availability check for SITC-V4 took 25.99197292327881s
Availability | VoID file availability check for SITC-V4 took 0.0008344650268554688s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.34145379066467285s
Reputation | Calculation of the PageRank for SITC-V4 took 0.0217440128326416s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.267692565917969e-05s
Believability | Calculation of trust value for SITC-V4 took 9.5367431640625e-06s
INFO | --- Analysis for sitc-v4 took 125.86907076835632s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.696846008300781e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.3104977607727051s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.458427429199219e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.0728836059570312e-05s
INFO | --- Analysis for sli_galnet_rdf took 13.015511274337769s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 9.560585021972656e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.31151390075683594s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.022278785705566406s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.2901763916015625e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 1.33514404296875e-05s
INFO | --- Analysis for slideshare2rdf took 2.9699859619140625s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.4985184669494629s
Availability | VoID file availability check for Linked Stage Graph took 0.00044727325439453125s
Extra | Recovery of all triples for Linked Stage Graph took 2.3904993534088135s
Performance | Total latancy measurement for Linked Stage Graph took 1.160506010055542s
Amount of data | Number of triples check for Linked Stage Graph took 0.24368071556091309s
Interoperability | New terms check for Linked Stage Graph took 1.4245123863220215s
Versatility | Languages check for Linked Stage Graph took 0.7072296142578125s
Interpretability | Number of blank nodes check for Linked Stage Graph took 0.26230740547180176s
Security | Check HTTPS for Linked Stage Graph took 0.14513349533081055s
Interpretability | RDF structures check for Linked Stage Graph took 0.32062435150146484s
Versatility | Serialization formats check for Linked Stage Graph took 0.23685026168823242s
Availability | RDF dump link check for Linked Stage Graph took 0.23311591148376465s
License | MR license check for Linked Stage Graph took 0.3286159038543701s
License | HR license check for Linked Stage Graph took 1.8701229095458984s
Amount of data | Number of property check for Linked Stage Graph took 0.23886752128601074s
Understandability | Number of label check for Linked Stage Graph took 0.44640207290649414s
Understandability | URI regex check for Linked Stage Graph took 0.4613931179046631s
Understandability | Vocabs check for Linked Stage Graph took 0.23492074012756348s
Verifiability | Authors check for Linked Stage Graph took 0.2405867576599121s
Verifiability | Publishers check for Linked Stage Graph took 0.23685002326965332s
Performance | Throughput check for Linked Stage Graph took 11.654484510421753s
Amount of data | Check the number of entities for Linked Stage Graph took 7.557868957519531e-05s
Verifiability | Contribs. check for Linked Stage Graph took 0.23395395278930664s
Interlinking | sameAs chians check for Linked Stage Graph took 0.23473405838012695s
Interlinking | skos check for Linked Stage Graph took 0.25764918327331543s
Interlinking | skos check for Linked Stage Graph took 0.23386740684509277s
Timeliness | dataset update frequency check for Linked Stage Graph took 0.3921642303466797s
Currency | Creation date check for Linked Stage Graph took 0.47127461433410645s
Currency | Modification date check for Linked Stage Graph took 0.4721543788909912s
Rep.Conc. | URIs length for Linked Stage Graph took 1.5847852230072021s
Interoperability | New vocabularies check for Linked Stage Graph took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Linked Stage Graph took 0.2322232723236084s
Accuracy | Check Functional Property for Linked Stage Graph took 0.23028206825256348s
Accuracy | Check Inverse Functional Property for Linked Stage Graph took 0.23195910453796387s
Accuracy | Check Empty annotation labels for Linked Stage Graph took 0.9422619342803955s
Accuracy | Check White space in annotation for Linked Stage Graph took 0.02462625503540039s
Accuracy | Check Datatype consistency for Linked Stage Graph took 0.028231143951416016s
Consistency | Disjoint class check for Linked Stage Graph took 0.2331380844116211s
Consistency | Check Misplaced properties for Linked Stage Graph took 1.0280940532684326s
Consistency | Misplaced classes for Linked Stage Graph took 0.5648367404937744s
Consistency | Check Ontology hijacking for Linked Stage Graph took 2.6340348720550537s
Consistency | Check Invalid usage of undefined classes for Linked Stage Graph took 1.1779768466949463s
Consistency | Check Invalid usage of undefined properties for Linked Stage Graph took 1.6864442825317383s
Conciseness | Check Extensional conciseness for Linked Stage Graph took 0.02779388427734375s
Conciseness | Check Intensional conciseness for Linked Stage Graph took 0.6259768009185791s
Security | Sign check for Linked Stage Graph took 0.323397159576416s
Availability | Check URIs Dereferenciability for Linked Stage Graph took 1032.1595323085785s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.4542398452758789s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.021398067474365234s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 6.151199340820312e-05s
Interoperability | Check the re-using of existing vocabs for Linked Stage Graph took 1.430511474609375e-06s
Believability | Calculation of trust value for Linked Stage Graph took 1.0728836059570312e-05s
INFO | --- Analysis for slod took 1099.8706412315369s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 60.0594539642334s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.3108556270599365s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.021032094955444336s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00011277198791503906s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 1.3828277587890625e-05s
INFO | --- Analysis for Smart_POI_dataset took 122.93388342857361s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 4.733203411102295s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0003516674041748047s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.31121063232421875s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.886222839355469e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 1.0728836059570312e-05s
INFO | --- Analysis for smartlink took 12.58262848854065s
Availability | SPARQL endpoint availability check for SNIK took 10.669871807098389s
Availability | VoID file availability check for SNIK took 0.0007312297821044922s
Completeness | Calculation of interlinking completeness for SNIK took 0.30548882484436035s
Reputation | Calculation of the PageRank for SNIK took 0.02159714698791504s
Interlinking | Calculation of Degree of Connection for SNIK took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for SNIK took 7.343292236328125e-05s
Believability | Calculation of trust value for SNIK took 1.1444091796875e-05s
INFO | --- Analysis for snik took 68.57288384437561s
Availability | SPARQL endpoint availability check for SocialLink took 1.399557113647461s
Availability | VoID file availability check for SocialLink took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for SocialLink took 0.30980706214904785s
Reputation | Calculation of the PageRank for SocialLink took 0.022054433822631836s
Interlinking | Calculation of Degree of Connection for SocialLink took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SocialLink took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for SocialLink took 8.058547973632812e-05s
Believability | Calculation of trust value for SocialLink took 1.1920928955078125e-05s
INFO | --- Analysis for SocialLink took 5.356892347335815s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 8.893013000488281e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0007297992706298828s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.351961612701416s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.022630691528320312s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 2.8848648071289062e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 1.1920928955078125e-05s
INFO | --- Analysis for SocialRoles took 10.185884952545166s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.21770787239074707s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0006952285766601562s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 15.44291615486145s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.5064051151275635s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.20203733444213867s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.369762659072876s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.4266853332519531s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.19364476203918457s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.35491466522216797s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.12953424453735352s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.12840628623962402s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.8104445934295654s
License | MR license check for Social Semantic Web Thesaurus took 0.1266648769378662s
License | HR license check for Social Semantic Web Thesaurus took 0.11433076858520508s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.1273958683013916s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.13170504570007324s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.1899120807647705s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.12683939933776855s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.12786507606506348s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.1272900104522705s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.521872520446777s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 6.914138793945312e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.12708711624145508s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.1268446445465088s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.12803387641906738s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.09680819511413574s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.09637594223022461s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.19730782508850098s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.22454571723937988s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.5544967651367188s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.12723827362060547s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.09619808197021484s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.09851360321044922s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.5087161064147949s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.0123443603515625s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.09576416015625s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.3182542324066162s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.09589838981628418s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 1.903836727142334s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.328932762145996s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.00014519691467285156s
Security | Sign check for Social Semantic Web Thesaurus took 0.09404778480529785s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 117.06782007217407s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.42260217666625977s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.703636169433594e-05s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 296.74743604660034s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.0157239437103271s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3158440589904785s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.02130722999572754s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.314018249511719e-05s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.775161743164062e-06s
INFO | --- Analysis for Soil_maps took 4.45712685585022s
Availability | SPARQL endpoint availability check for terrorrist ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.3065531253814697s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.022236108779907227s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for terrorrist ontology took 1.2874603271484375e-05s
INFO | --- Analysis for somya_omer took 2.8535187244415283s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.363059997558594e-05s
Availability | VoID file availability check for Sonclubcx took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.30985236167907715s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020571231842041016s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.2159347534179688e-05s
Believability | Calculation of trust value for Sonclubcx took 1.1205673217773438e-05s
INFO | --- Analysis for sonclubcx took 4.262731313705444s
Availability | SPARQL endpoint availability check for SORS took 4.506111145019531e-05s
Availability | VoID file availability check for SORS took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for SORS took 0.3168182373046875s
Reputation | Calculation of the PageRank for SORS took 0.02172994613647461s
Interlinking | Calculation of Degree of Connection for SORS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for SORS took 4.9114227294921875e-05s
Believability | Calculation of trust value for SORS took 8.106231689453125e-06s
INFO | --- Analysis for sors took 13.024075269699097s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 8.678436279296875e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.31727004051208496s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.02196025848388672s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.441375732421875e-05s
Believability | Calculation of trust value for southampton-ac-uk took 9.5367431640625e-06s
INFO | --- Analysis for southampton-ac-uk took 4.233755826950073s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.4650800228118896s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.3157846927642822s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.00070953369140625s
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 1.1444091796875e-05s
INFO | --- Analysis for southampton-ac-uk-apps took 11.534050226211548s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.2438507080078125e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.3177833557128906s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.02092146873474121s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.1552734375e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.3113021850585938e-05s
INFO | --- Analysis for southampton-ecs-eprints took 2.96103572845459s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.5474212169647217s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0005052089691162109s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 162.3568515777588s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.3081214427947998s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.252272129058838s
Interoperability | New terms check for Spanish Linguistic Datasets took 2.9068551063537598s
Versatility | Languages check for Spanish Linguistic Datasets took 44.47737526893616s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.0970940589904785s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.145219087600708s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.3191971778869629s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.31421685218811035s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.30487489700317383s
License | MR license check for Spanish Linguistic Datasets took 0.3121931552886963s
License | HR license check for Spanish Linguistic Datasets took 0.3969004154205322s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.31003427505493164s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.3633882999420166s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.6111977100372314s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.31148362159729004s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.31096434593200684s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.30913496017456055s
Performance | Throughput check for Spanish Linguistic Datasets took 12.115679740905762s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 6.890296936035156e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.3062324523925781s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.30787134170532227s
Interlinking | skos check for Spanish Linguistic Datasets took 0.3087000846862793s
Interlinking | skos check for Spanish Linguistic Datasets took 0.24253177642822266s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.3089752197265625s
Currency | Creation date check for Spanish Linguistic Datasets took 0.6221401691436768s
Currency | Modification date check for Spanish Linguistic Datasets took 0.6225359439849854s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 59.45520043373108s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.31295013427734375s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.304429292678833s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.30374670028686523s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 1.007155179977417s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010408639907836914s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.6129207611083984s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.3055269718170166s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.733030557632446s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.409278392791748s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 43.93374490737915s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.385775089263916s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.6068689823150635s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.884162664413452s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.3311312198638916s
Security | Sign check for Spanish Linguistic Datasets took 0.3081381320953369s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 10.7276451587677s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.4604630470275879s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.021319866180419922s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.4332275390625e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 2.384185791015625e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 1.0251998901367188e-05s
INFO | --- Analysis for spanish-linguistic-datasets took 416.86158537864685s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.06383085250854492s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.3088655471801758s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.02146434783935547s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 5.3882598876953125e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 1.239776611328125e-05s
INFO | --- Analysis for sparql-endpoint-status took 2.9364161491394043s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 8.797645568847656e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.3148970603942871s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.020503520965576172s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 9.465217590332031e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 1.0967254638671875e-05s
INFO | --- Analysis for springernaturescigraph took 3.4489030838012695s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.38690185546875e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0008058547973632812s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.3406646251678467s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.021267175674438477s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.3828277587890625e-05s
INFO | --- Analysis for srcmf took 7.170072793960571s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.3704824447631836s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0006461143493652344s
Extra | Recovery of all triples for Lexicon of Syntactic and Semantic Framework took 1.3949840068817139s
Performance | Total latancy measurement for Lexicon of Syntactic and Semantic Framework took 0.8398683071136475s
Amount of data | Number of triples check for Lexicon of Syntactic and Semantic Framework took 0.16832661628723145s
Interoperability | New terms check for Lexicon of Syntactic and Semantic Framework took 1.296372890472412s
Versatility | Languages check for Lexicon of Syntactic and Semantic Framework took 0.17269110679626465s
Interpretability | Number of blank nodes check for Lexicon of Syntactic and Semantic Framework took 0.16860556602478027s
Security | Check HTTPS for Lexicon of Syntactic and Semantic Framework took 0.10188722610473633s
Interpretability | RDF structures check for Lexicon of Syntactic and Semantic Framework took 0.17095041275024414s
Versatility | Serialization formats check for Lexicon of Syntactic and Semantic Framework took 0.17310428619384766s
Availability | RDF dump link check for Lexicon of Syntactic and Semantic Framework took 0.16768145561218262s
License | MR license check for Lexicon of Syntactic and Semantic Framework took 0.17125725746154785s
License | HR license check for Lexicon of Syntactic and Semantic Framework took 0.16892337799072266s
Amount of data | Number of property check for Lexicon of Syntactic and Semantic Framework took 0.1710972785949707s
Understandability | Number of label check for Lexicon of Syntactic and Semantic Framework took 0.17612123489379883s
Understandability | URI regex check for Lexicon of Syntactic and Semantic Framework took 0.34244585037231445s
Understandability | Vocabs check for Lexicon of Syntactic and Semantic Framework took 0.16809630393981934s
Verifiability | Authors check for Lexicon of Syntactic and Semantic Framework took 0.16992759704589844s
Verifiability | Publishers check for Lexicon of Syntactic and Semantic Framework took 0.16784119606018066s
Performance | Throughput check for Lexicon of Syntactic and Semantic Framework took 10.12188196182251s
Amount of data | Check the number of entities for Lexicon of Syntactic and Semantic Framework took 6.389617919921875e-05s
Verifiability | Contribs. check for Lexicon of Syntactic and Semantic Framework took 0.16823053359985352s
Interlinking | sameAs chians check for Lexicon of Syntactic and Semantic Framework took 0.16807293891906738s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.1706688404083252s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.1697986125946045s
Timeliness | dataset update frequency check for Lexicon of Syntactic and Semantic Framework took 0.17235851287841797s
Currency | Creation date check for Lexicon of Syntactic and Semantic Framework took 0.3423624038696289s
Currency | Modification date check for Lexicon of Syntactic and Semantic Framework took 0.3391895294189453s
Rep.Conc. | URIs length for Lexicon of Syntactic and Semantic Framework took 0.5313267707824707s
Interoperability | New vocabularies check for Lexicon of Syntactic and Semantic Framework took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Lexicon of Syntactic and Semantic Framework took 0.16800761222839355s
Accuracy | Check Functional Property for Lexicon of Syntactic and Semantic Framework took 0.16762948036193848s
Accuracy | Check Inverse Functional Property for Lexicon of Syntactic and Semantic Framework took 0.16776061058044434s
Accuracy | Check Empty annotation labels for Lexicon of Syntactic and Semantic Framework took 0.1779487133026123s
Accuracy | Check White space in annotation for Lexicon of Syntactic and Semantic Framework took 0.0003104209899902344s
Accuracy | Check Datatype consistency for Lexicon of Syntactic and Semantic Framework took 0.03469514846801758s
Consistency | Disjoint class check for Lexicon of Syntactic and Semantic Framework took 0.17420172691345215s
Consistency | Check Misplaced properties for Lexicon of Syntactic and Semantic Framework took 0.34087419509887695s
Consistency | Misplaced classes for Lexicon of Syntactic and Semantic Framework took 0.22184419631958008s
Consistency | Check Ontology hijacking for Lexicon of Syntactic and Semantic Framework took 1.382802963256836s
Consistency | Check Invalid usage of undefined classes for Lexicon of Syntactic and Semantic Framework took 1.158339262008667s
Consistency | Check Invalid usage of undefined properties for Lexicon of Syntactic and Semantic Framework took 1.3466956615447998s
Conciseness | Check Extensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.022786617279052734s
Conciseness | Check Intensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.16885709762573242s
Security | Sign check for Lexicon of Syntactic and Semantic Framework took 0.16932177543640137s
Availability | Check URIs Dereferenciability for Lexicon of Syntactic and Semantic Framework took 278.7090380191803s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.42385292053222656s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.021231889724731445s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 6.0558319091796875e-05s
Interoperability | Check the re-using of existing vocabs for Lexicon of Syntactic and Semantic Framework took 1.430511474609375e-06s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 2.3126602172851562e-05s
INFO | --- Analysis for ssf took 319.952353477478s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.267692565917969e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.3143343925476074s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.02100825309753418s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.838539123535156e-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.2527217864990234s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 8.225440979003906e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.31414055824279785s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020900249481201172s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.4809112548828125e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 8.821487426757812e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 3.6046998500823975s
Availability | SPARQL endpoint availability check for Stammbuch took 8.296966552734375e-05s
Availability | VoID file availability check for Stammbuch took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.3103806972503662s
Reputation | Calculation of the PageRank for Stammbuch took 0.020687103271484375s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 3.0040740966796875e-05s
Believability | Calculation of trust value for Stammbuch took 1.0728836059570312e-05s
INFO | --- Analysis for Stammbuch took 2.8398191928863525s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.2805583477020264s
Availability | VoID file availability check for statistics.data.gov.uk took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.28989720344543457s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010848045349121094s
Believability | Calculation of trust value for statistics.data.gov.uk took 8.106231689453125e-06s
INFO | --- Analysis for statistics-data-gov-uk took 4.338559150695801s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 8.296966552734375e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.3603489398956299s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.022166013717651367s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.0001068115234375s
Believability | Calculation of trust value for statusnet-1w6-org took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-1w6-org took 3.777338981628418s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 8.797645568847656e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.3089761734008789s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.021049022674560547s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.413459777832031e-05s
Believability | Calculation of trust value for statusnet-20100-org took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-20100-org took 2.97969388961792s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 5.340576171875e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.29531359672546387s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.02123284339904785s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 7.104873657226562e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-alexandrefranke-com took 3.2501132488250732s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 9.72747802734375e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.3166942596435547s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.02132868766784668s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 7.891654968261719e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.8788626194000244s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.30776286125183105s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.021207571029663086s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.632110595703125e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-belfalas-org took 3.033726453781128s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 8.058547973632812e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.34463024139404297s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.02237677574157715s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00010776519775390625s
Believability | Calculation of trust value for statusnet-bka-li took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-bka-li took 13.003190040588379s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.31818556785583496s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02263951301574707s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.600120544433594e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.846055269241333s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 8.344650268554688e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.31631946563720703s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.553794860839844e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-ced117-net took 4.3870532512664795s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 8.177757263183594e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.3143336772918701s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 4.982948303222656e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-chickenkiller-com took 3.0501179695129395s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 0.00013136863708496094s
Availability | VoID file availability check for statusnet-chromic-org took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.3073091506958008s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.02237415313720703s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.000110626220703125s
Believability | Calculation of trust value for statusnet-chromic-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-chromic-org took 3.091383695602417s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 8.416175842285156e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.29523444175720215s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020917177200317383s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 7.677078247070312e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-cooleysekula-net took 6.437986850738525s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 8.249282836914062e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.3107919692993164s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.021057605743408203s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.91278076171875e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-coreyavis-com took 2.930206537246704s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 0.00010061264038085938s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.31000852584838867s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.022254467010498047s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 7.05718994140625e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.5812788009643555s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 8.368492126464844e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.3102560043334961s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.020845890045166016s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010180473327636719s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 3.042304039001465s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.30737996101379395s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.021541595458984375s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.318092346191406e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.921893835067749s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.3135702610015869s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.02090620994567871s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.1975250244140625e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-doomicile-de took 4.48884129524231s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 9.870529174804688e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.2929701805114746s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020908355712890625s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.532669067382812e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-dtdns-net took 22.829278230667114s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.3126258850097656s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020977258682250977s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.4332275390625e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.841602087020874s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 8.320808410644531e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.30820512771606445s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.021134138107299805s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.510185241699219e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-exdc-net took 2.922872304916382s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 8.249282836914062e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.30936217308044434s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.022845745086669922s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.655952453613281e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-fcac-com took 3.2337417602539062s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 8.535385131835938e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0010645389556884766s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.3132307529449463s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.0209658145904541s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.435943603515625e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-fcestrada-com took 3.614962577819824s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 9.131431579589844e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.31144285202026367s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020377159118652344s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00018358230590820312s
Believability | Calculation of trust value for statusnet-fragdev-com took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-fragdev-com took 3.741746664047241s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.2892608642578125s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.0210421085357666s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.414817810058594e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-freelish-us took 2.9056358337402344s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 8.630752563476562e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.31961727142333984s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010919570922851562s
Believability | Calculation of trust value for statusnet-gegeweb-org took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-gegeweb-org took 3.000236988067627s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.3152759075164795s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.021366357803344727s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 7.033348083496094e-05s
Believability | Calculation of trust value for statusnet-glou-org took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-glou-org took 2.912419557571411s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.30925822257995605s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020996809005737305s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00012564659118652344s
Believability | Calculation of trust value for statusnet-gomertronic-com took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-gomertronic-com took 2.9113106727600098s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 8.559226989746094e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.31015658378601074s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.02171802520751953s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010633468627929688s
Believability | Calculation of trust value for statusnet-hackerposse-com took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-hackerposse-com took 3.3740124702453613s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 0.00014138221740722656s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.30953526496887207s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020825862884521484s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.839897155761719e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-hii-co-il took 4.245619297027588s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 8.487701416015625e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.3130156993865967s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.020795822143554688s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 0.00010776519775390625s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 13.061948776245117s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 9.989738464355469e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.3146250247955322s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.021981477737426758s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 5.698204040527344e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-imirhil-fr took 2.965022325515747s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 8.678436279296875e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.001146554946899414s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.3408031463623047s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 3.695487976074219e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-integralblue-com took 3.086348295211792s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.31252408027648926s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.0205991268157959s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.412101745605469e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.852980375289917s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 8.702278137207031e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.310344934463501s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.020766258239746094s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011372566223144531s
Believability | Calculation of trust value for statusnet-jonkman-ca took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-jonkman-ca took 3.805762529373169s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.31917810440063477s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.584426879882812e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-kaimi-cc took 2.9873547554016113s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.2936367988586426s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.02243971824645996s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 4.982948303222656e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-kathryl-fr took 2.84162974357605s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 8.559226989746094e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.3379538059234619s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.020990610122680664s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.814697265625e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-kenzoid-com took 3.756782054901123s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.31087613105773926s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.021175861358642578s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.319450378417969e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-keuser-fr took 2.8742642402648926s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 8.368492126464844e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.33433008193969727s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.020966053009033203s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.839897155761719e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.977055311203003s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 8.416175842285156e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.31049203872680664s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.021023273468017578s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 6.890296936035156e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 7.081031799316406e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-lebsanft-org took 3.0619564056396484s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 7.390975952148438e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.30768656730651855s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020966291427612305s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.822845458984375e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 3.036897897720337s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.3346705436706543s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.022397756576538086s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011777877807617188s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.863090753555298s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.3079826831817627s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.0209352970123291s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.650520324707031e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-ludost-net took 4.260329484939575s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 0.00012803077697753906s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.3363027572631836s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.023229598999023438s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.870529174804688e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.911503791809082s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 8.249282836914062e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.31067323684692383s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.022330284118652344s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.245208740234375e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.804896831512451s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.3097050189971924s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020722389221191406s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00015306472778320312s
Believability | Calculation of trust value for statusnet-macno-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-macno-org took 2.92228364944458s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.3085927963256836s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.021378755569458008s
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.0007171630859375s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.67572021484375e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.8867082595825195s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.37401676177978516s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.0210573673248291s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.082389831542969e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-maymay-net took 62.44973921775818s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 8.559226989746094e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.3084523677825928s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.0216214656829834s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00016117095947265625s
Believability | Calculation of trust value for statusnet-morphtown-de took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.9054572582244873s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 0.0001270771026611328s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.30785107612609863s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.020809650421142578s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 0.00010156631469726562s
Believability | Calculation of trust value for statusnet-mrblog-nl took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-mrblog-nl took 2.935245990753174s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 8.416175842285156e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.3132927417755127s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020650863647460938s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.4836273193359375e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-mulestable-net took 2.885930061340332s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 8.487701416015625e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.3103067874908447s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.021042585372924805s
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.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.3882598876953125e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-my-status-tk took 3.1077020168304443s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.30855655670166016s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.021329402923583984s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00011205673217773438s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.8844738006591797s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.30642271041870117s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.7220458984375e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-orangeseeds-org took 3.0038697719573975s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.2902684211730957s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.02279496192932129s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.532669067382812e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-otbm-fr took 2.9840664863586426s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 8.368492126464844e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.3372926712036133s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.487701416015625e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.8945300579071045s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 0.00010538101196289062s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.317976713180542s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.021033287048339844s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 5.078315734863281e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-panda-id-au took 3.661999225616455s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 9.751319885253906e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.3363828659057617s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.021166086196899414s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.751319885253906e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-piana-eu took 2.949511766433716s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 9.250640869140625e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.31126952171325684s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.02107691764831543s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.700920104980469e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-planet-libre-org took 2.891528367996216s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.3125956058502197s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.0002295970916748047s
Believability | Calculation of trust value for statusnet-postblue-info took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-postblue-info took 3.1702680587768555s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.3090689182281494s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.021005630493164062s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.67572021484375e-05s
Believability | Calculation of trust value for statusnet-progval-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-progval-net took 2.9535090923309326s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 8.654594421386719e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.3086569309234619s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.021276235580444336s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00011444091796875s
Believability | Calculation of trust value for statusnet-qdnx-org took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-qdnx-org took 3.4219210147857666s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 8.368492126464844e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.3085205554962158s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.02092742919921875s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.270408630371094e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-qth-fr took 3.9024012088775635s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.3081026077270508s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.02106952667236328s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.0002186298370361328s
Believability | Calculation of trust value for statusnet-quitter-se took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-quitter-se took 5.8942975997924805s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.3090367317199707s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.022663354873657227s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010776519775390625s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 3.0216784477233887s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.3349623680114746s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.02324056625366211s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.745887756347656e-05s
Believability | Calculation of trust value for statusnet-recit-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-recit-org took 5.9035561084747314s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 8.249282836914062e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.314100980758667s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.022209882736206055s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.0001506805419921875s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-russwurm-org took 3.6922993659973145s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.3140370845794678s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020917177200317383s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.177757263183594e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-samnoble-org took 5.240641832351685s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 5.364418029785156e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.2958505153656006s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020972728729248047s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.296966552734375e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-schiessle-org took 3.0059092044830322s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.3136165142059326s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.02102375030517578s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 0.0001010894775390625s
Believability | Calculation of trust value for statusnet-scoffoni-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-scoffoni-net took 2.9264566898345947s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 8.392333984375e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.3423771858215332s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020957469940185547s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.4849853515625e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.876598596572876s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 8.893013000488281e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.31662797927856445s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020906686782836914s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.176399230957031e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 8.85729169845581s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 8.916854858398438e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.31119799613952637s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.022049903869628906s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.0002090930938720703s
Believability | Calculation of trust value for statusnet-skilledtests-com took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 3.3201169967651367s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 9.1552734375e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.33903074264526367s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.02170085906982422s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010633468627929688s
Believability | Calculation of trust value for statusnet-somsants-net took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-somsants-net took 2.92826247215271s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 8.893013000488281e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.30845069885253906s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.0210416316986084s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.0001373291015625s
Believability | Calculation of trust value for statusnet-soucy-cc took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-soucy-cc took 4.53342604637146s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.3148765563964844s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.02079939842224121s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.127357482910156e-05s
Believability | Calculation of trust value for statusnet-spip-org took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-spip-org took 4.239408493041992s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 8.58306884765625e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0007538795471191406s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.32746362686157227s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020844459533691406s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.723403930664062e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-spraci-org took 5.755384683609009s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 8.58306884765625e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.3185868263244629s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.021036624908447266s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00011134147644042969s
Believability | Calculation of trust value for statusnet-ssweeny-net took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-ssweeny-net took 5.777420520782471s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.3176109790802002s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020834684371948242s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00022554397583007812s
Believability | Calculation of trust value for statusnet-status-net took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-status-net took 4.047350883483887s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 7.510185241699219e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.31453466415405273s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.020646333694458008s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.5789947509765625e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.8633203506469727s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 8.463859558105469e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.30858659744262695s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.02123713493347168s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.393692016601562e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-tekk-com-ar took 3.389859914779663s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.3149833679199219s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00012636184692382812s
Believability | Calculation of trust value for statusnet-thelovebug-org took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 3.0455942153930664s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 6.198883056640625e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.30876827239990234s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.022244930267333984s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.319450378417969e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-thornton2-com took 7.575899362564087s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 8.463859558105469e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.30653834342956543s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020796775817871094s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00010919570922851562s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-timttmy-co-uk took 3.143587350845337s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 8.130073547363281e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.30951595306396484s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020869970321655273s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 3.910064697265625e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-tl1n-com took 3.98293399810791s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 9.202957153320312e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.3078629970550537s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.02120804786682129s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.842613220214844e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 3.1263325214385986s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.33803772926330566s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020963191986083984s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.7670135498046875e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-uni-siegen-de took 3.868486166000366s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 9.894371032714844e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.33788347244262695s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.021007061004638672s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 9.775161743164062e-06s
INFO | --- Analysis for steak took 3.2282040119171143s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 8.344650268554688e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.31824469566345215s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.02100205421447754s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.435943603515625e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 9.775161743164062e-06s
INFO | --- Analysis for stitch-rameau took 4.625417232513428s
Availability | SPARQL endpoint availability check for Stone Tech Square took 1.0063848495483398s
Availability | VoID file availability check for Stone Tech Square took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.30481433868408203s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.02252650260925293s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.239776611328125e-05s
Believability | Calculation of trust value for Stone Tech Square took 1.049041748046875e-05s
INFO | --- Analysis for stone-tech-square-data took 5.982438564300537s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.4639160633087158s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0006039142608642578s
Extra | Recovery of all triples for STW Thesaurus for Economics took 13.785541772842407s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.291733741760254s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.6644396781921387s
Interoperability | New terms check for STW Thesaurus for Economics took 1.4453785419464111s
Versatility | Languages check for STW Thesaurus for Economics took 1.6594982147216797s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.5586752891540527s
Security | Check HTTPS for STW Thesaurus for Economics took 0.14891648292541504s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.26180100440979004s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.272904634475708s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.2688744068145752s
License | MR license check for STW Thesaurus for Economics took 0.26967620849609375s
License | HR license check for STW Thesaurus for Economics took 3.5693464279174805s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.27451634407043457s
Understandability | Number of label check for STW Thesaurus for Economics took 1.1714215278625488s
Understandability | URI regex check for STW Thesaurus for Economics took 0.5534882545471191s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.25978827476501465s
Verifiability | Authors check for STW Thesaurus for Economics took 0.2846798896789551s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.25621676445007324s
Performance | Throughput check for STW Thesaurus for Economics took 11.49286937713623s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7268109321594238s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.2793853282928467s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.2743337154388428s
Interlinking | skos check for STW Thesaurus for Economics took 0.8082106113433838s
Interlinking | skos check for STW Thesaurus for Economics took 0.7479910850524902s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.276883602142334s
Currency | Creation date check for STW Thesaurus for Economics took 0.5904839038848877s
Currency | Modification date check for STW Thesaurus for Economics took 0.5153634548187256s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 18.80916929244995s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.2885091304779053s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.25675201416015625s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.24930596351623535s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 7.662767171859741s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0483896732330322s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.3392205238342285s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.2721982002258301s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.4741952419281006s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 1.6898114681243896s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.1627917289733887s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.2819254398345947s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6241042613983154s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.2588944435119629s
Security | Sign check for STW Thesaurus for Economics took 0.2565431594848633s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 2135.2376680374146s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.7551114559173584s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.021179676055908203s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 6.127357482910156e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00012421607971191406s
Believability | Calculation of trust value for STW Thesaurus for Economics took 1.0967254638671875e-05s
INFO | --- Analysis for stw-thesaurus-for-economics took 2242.7230727672577s
Availability | SPARQL endpoint availability check for SudershanTech took 4.3392181396484375e-05s
Availability | VoID file availability check for SudershanTech took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.31099557876586914s
Reputation | Calculation of the PageRank for SudershanTech took 0.020784854888916016s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.0279159545898438e-05s
Believability | Calculation of trust value for SudershanTech took 1.0728836059570312e-05s
INFO | --- Analysis for SudershanTech took 2.883293390274048s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.864192008972168s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.31103515625s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.020984411239624023s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.76837158203125e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 1.1205673217773438e-05s
INFO | --- Analysis for sudocfr took 7.94298529624939s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 1.1244370937347412s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0007295608520507812s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 21.1330828666687s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.632481813430786s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.7111432552337646s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 2.7847626209259033s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 3.528287649154663s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.16068696975708s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5618112087249756s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.565345048904419s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5042343139648438s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5297548770904541s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 9.391884803771973s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.57314133644104s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.6617753505706787s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.060723066329956s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5514922142028809s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5300295352935791s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5478396415710449s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.538795948028564s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 0.00011157989501953125s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5501549243927002s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5471856594085693s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5894486904144287s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5704793930053711s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5684423446655273s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.0886030197143555s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.0687320232391357s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 40.903071880340576s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5729241371154785s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5438046455383301s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.4972546100616455s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 3.0146963596343994s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.3800363540649414s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.5535640716552734s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 31.710735082626343s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.382134914398193s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.44215655326843s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 22.347449779510498s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.9985246658325195s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.560070514678955s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5431027412414551s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4520.583220481873s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.7970161437988281s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.02164745330810547s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 6.222724914550781e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 9.1552734375e-05s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 1.0728836059570312e-05s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 8217.614036083221s
Availability | SPARQL endpoint availability check for Surge Radio took 4.076957702636719e-05s
Availability | VoID file availability check for Surge Radio took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.310194730758667s
Reputation | Calculation of the PageRank for Surge Radio took 0.021045207977294922s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.869171142578125e-05s
Believability | Calculation of trust value for Surge Radio took 1.0013580322265625e-05s
INFO | --- Analysis for surge-radio took 3.970867395401001s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 4.315376281738281e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.3382244110107422s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.021949052810668945s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.695487976074219e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 1.1205673217773438e-05s
INFO | --- Analysis for SWAT took 95.46111488342285s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.458427429199219e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.4480867385864258s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.3146071434020996s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.02097773551940918s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.937980651855469e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 1.1920928955078125e-05s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.379518747329712s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.0846431255340576s
Availability | VoID file availability check for SweFN-RDF took 0.001232147216796875s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.3424835205078125s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.02158355712890625s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.3855438232421875e-05s
Believability | Calculation of trust value for SweFN-RDF took 1.2636184692382812e-05s
INFO | --- Analysis for swefn-rdf took 6.363305568695068s
Availability | SPARQL endpoint availability check for SwetoDblp took 8.153915405273438e-05s
Availability | VoID file availability check for SwetoDblp took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.3325350284576416s
Reputation | Calculation of the PageRank for SwetoDblp took 0.020745515823364258s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.933906555175781e-05s
Believability | Calculation of trust value for SwetoDblp took 6.67572021484375e-06s
INFO | --- Analysis for sweto-dblp took 23.230791807174683s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.5418212413787842s
Availability | VoID file availability check for Swift Vocabulary took 0.0012135505676269531s
Extra | Recovery of all triples for Swift Vocabulary took 2.436276912689209s
Performance | Total latancy measurement for Swift Vocabulary took 1.130730390548706s
Amount of data | Number of triples check for Swift Vocabulary took 0.22649335861206055s
Interoperability | New terms check for Swift Vocabulary took 1.335256814956665s
Versatility | Languages check for Swift Vocabulary took 0.18421363830566406s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.18783926963806152s
Interpretability | RDF structures check for Swift Vocabulary took 0.19001364707946777s
Versatility | Serialization formats check for Swift Vocabulary took 0.1885056495666504s
Availability | RDF dump link check for Swift Vocabulary took 0.18753314018249512s
License | MR license check for Swift Vocabulary took 0.1891312599182129s
License | HR license check for Swift Vocabulary took 0.19096899032592773s
Amount of data | Number of property check for Swift Vocabulary took 0.1868743896484375s
Understandability | Number of label check for Swift Vocabulary took 0.23598408699035645s
Understandability | URI regex check for Swift Vocabulary took 0.45288777351379395s
Understandability | Vocabs check for Swift Vocabulary took 0.2298586368560791s
Verifiability | Authors check for Swift Vocabulary took 0.23079204559326172s
Verifiability | Publishers check for Swift Vocabulary took 0.25038886070251465s
Performance | Throughput check for Swift Vocabulary took 11.2081937789917s
Amount of data | Check the number of entities for Swift Vocabulary took 0.00010561943054199219s
Verifiability | Contribs. check for Swift Vocabulary took 0.22780394554138184s
Interlinking | sameAs chians check for Swift Vocabulary took 0.22618722915649414s
Interlinking | skos check for Swift Vocabulary took 0.22424602508544922s
Interlinking | skos check for Swift Vocabulary took 0.22289013862609863s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.2249438762664795s
Currency | Creation date check for Swift Vocabulary took 0.4507293701171875s
Currency | Modification date check for Swift Vocabulary took 0.452836275100708s
Rep.Conc. | URIs length for Swift Vocabulary took 0.8695387840270996s
Interoperability | New vocabularies check for Swift Vocabulary took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.22437500953674316s
Accuracy | Check Functional Property for Swift Vocabulary took 0.22374725341796875s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.2240743637084961s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.36959028244018555s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.0019783973693847656s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.03539586067199707s
Consistency | Disjoint class check for Swift Vocabulary took 0.22449445724487305s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.49443578720092773s
Consistency | Misplaced classes for Swift Vocabulary took 0.29558348655700684s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.4227080345153809s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.1588683128356934s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.3388404846191406s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.025813817977905273s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.18486714363098145s
Security | Sign check for Swift Vocabulary took 0.18184351921081543s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 969.7157294750214s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.7837235927581787s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.021211624145507812s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 6.079673767089844e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 8.559226989746094e-05s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 1.430511474609375e-06s
Believability | Calculation of trust value for Swift Vocabulary took 1.4066696166992188e-05s
INFO | --- Analysis for Swift took 1018.1904606819153s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 4.1484832763671875e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.3278920650482178s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020572185516357422s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 2.8133392333984375e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 1.1205673217773438e-05s
INFO | --- Analysis for symptoms-in-chinese took 53.04373860359192s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.42705368995666504s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0007250308990478516s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.534557580947876s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.963367223739624s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 7.42835259437561s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 19.976197481155396s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.1921381950378418s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 3.196951389312744s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.11962032318115234s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.5851492881774902s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.7473118305206299s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.19279813766479492s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.3068516254425049s
License | HR license check for National Digital Data Archive of Hungary (partial) took 54.788007974624634s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.42407703399658203s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 34.16732311248779s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3884434700012207s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.19493460655212402s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.3222665786743164s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.6924433708190918s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.947827577590942s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 7.700920104980469e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.8673300743103027s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 2.0497491359710693s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.7667198181152344s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.6941118240356445s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.6490862369537354s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 3.214643955230713s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 3.038966178894043s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 66.36809968948364s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.19867873191833496s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.195023775100708s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.19431304931640625s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.2500743865966797s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0024602413177490234s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0015032291412353516s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.20881366729736328s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 44.05812406539917s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.28462791442871094s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.4747507572174072s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.1747753620147705s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 44.812618255615234s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.0021343231201171875s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.30658626556396484s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.20364618301391602s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 9.912413835525513s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.41111159324645996s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.021486997604370117s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 8.130073547363281e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.9073486328125e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 1.049041748046875e-05s
INFO | --- Analysis for sztaki-lod took 496.29224824905396s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.00010633468627929688s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.31001830101013184s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.021178245544433594s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.53131103515625e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 1.049041748046875e-05s
INFO | --- Analysis for t4gm-info took 2.99605131149292s
Availability | SPARQL endpoint availability check for tags2con delicious took 9.083747863769531e-05s
Availability | VoID file availability check for tags2con delicious took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.3177909851074219s
Reputation | Calculation of the PageRank for tags2con delicious took 0.0209958553314209s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.172325134277344e-05s
Believability | Calculation of trust value for tags2con delicious took 1.0013580322265625e-05s
INFO | --- Analysis for tags2con-delicious took 45.08918499946594s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 263.71242475509644s
Availability | VoID file availability check for Taiwan geographic names took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.3912045955657959s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.02296137809753418s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0008578300476074219s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 6.389617919921875e-05s
Believability | Calculation of trust value for Taiwan geographic names took 1.239776611328125e-05s
INFO | --- Analysis for taiwan-geographic-names took 667.7762312889099s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 8.273124694824219e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.3388843536376953s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.021576881408691406s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.393692016601562e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 1.0967254638671875e-05s
INFO | --- Analysis for talis-openlibrary took 4.4604332447052s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 1.1215777397155762s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.3241546154022217s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020935773849487305s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.0001220703125s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 1.2636184692382812e-05s
INFO | --- Analysis for taxonconcept took 16.050462245941162s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.363059997558594e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.2928121089935303s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.022736549377441406s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.320808410644531e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.3113021850585938e-05s
INFO | --- Analysis for taxonconcept-assets took 3.2039382457733154s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.2438507080078125e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.36995959281921387s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.02152109146118164s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.364418029785156e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 1.0013580322265625e-05s
INFO | --- Analysis for taxonconcept-occurences took 3.3525807857513428s
Availability | SPARQL endpoint availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 21.1532244682312s
Availability | VoID file availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 2.1152384281158447s
Reputation | Calculation of the PageRank for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.021462678909301758s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 5.9604644775390625e-05s
Believability | Calculation of trust value for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.33514404296875e-05s
INFO | --- Analysis for taxref-ld took 80.76770114898682s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 263.0768597126007s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.36207032203674316s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.022233963012695312s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 3.886222839355469e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.2159347534179688e-05s
INFO | --- Analysis for tcga took 542.4917709827423s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.4290425777435303s
Availability | VoID file availability check for TCGA Roadmap took 0.0008530616760253906s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.29738903045654297s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.021383047103881836s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.867813110351562e-05s
Believability | Calculation of trust value for TCGA Roadmap took 1.0728836059570312e-05s
INFO | --- Analysis for tcga-roadmap took 6.137712478637695s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.2441458702087402s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.3477439880371094s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00010752677917480469s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for tcmgenedit_dataset took 137.8150177001953s
Availability | SPARQL endpoint availability check for TDS took 8.440017700195312e-05s
Availability | VoID file availability check for TDS took 0.0007507801055908203s
Completeness | Calculation of interlinking completeness for TDS took 0.31946897506713867s
Reputation | Calculation of the PageRank for TDS took 0.022577762603759766s
Interlinking | Calculation of Degree of Connection for TDS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for TDS took 4.029273986816406e-05s
Believability | Calculation of trust value for TDS took 1.0967254638671875e-05s
INFO | --- Analysis for tds took 5.392435550689697s
Availability | SPARQL endpoint availability check for TEKORD took 8.749961853027344e-05s
Availability | VoID file availability check for TEKORD took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for TEKORD took 0.3147156238555908s
Reputation | Calculation of the PageRank for TEKORD took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.57763671875e-05s
Believability | Calculation of trust value for TEKORD took 1.0251998901367188e-05s
INFO | --- Analysis for tekord took 5.7500505447387695s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 1.872645616531372s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0007398128509521484s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.37048959732055664s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.02156233787536621s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00012087821960449219s
Believability | Calculation of trust value for Telegraphis Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for telegraphis took 8.457419395446777s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 8.296966552734375e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.3189578056335449s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.02083754539489746s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.009506225585938e-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.3408682346344s
Availability | SPARQL endpoint availability check for Ontology took 8.320808410644531e-05s
Availability | VoID file availability check for Ontology took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Ontology took 0.3137075901031494s
Reputation | Calculation of the PageRank for Ontology took 0.02097940444946289s
Interlinking | Calculation of Degree of Connection for Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for Terrorist_attack took 3.3701608180999756s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 8.344650268554688e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.2902073860168457s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.022103309631347656s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.6716461181640625e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 1.0967254638671875e-05s
INFO | --- Analysis for Terrorist_Attack_1 took 2.8341662883758545s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 8.416175842285156e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.30794548988342285s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.020580768585205078s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.075599670410156e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.1920928955078125e-05s
INFO | --- Analysis for Tesla_Deaths took 4.114869594573975s
Availability | SPARQL endpoint availability check for test took 8.988380432128906e-05s
Availability | VoID file availability check for test took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for test took 0.31765222549438477s
Reputation | Calculation of the PageRank for test took 0.020732641220092773s
Interlinking | Calculation of Degree of Connection for test took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for test took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for test took 3.24249267578125e-05s
Believability | Calculation of trust value for test took 1.0967254638671875e-05s
INFO | --- Analysis for test took 2.838690757751465s
Availability | SPARQL endpoint availability check for Test took 4.410743713378906e-05s
Availability | VoID file availability check for Test took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Test took 0.31076717376708984s
Reputation | Calculation of the PageRank for Test took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for Test took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Test took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Test took 3.0279159545898438e-05s
Believability | Calculation of trust value for Test took 1.0251998901367188e-05s
INFO | --- Analysis for Test took 2.8800625801086426s
Availability | SPARQL endpoint availability check for test-svu took 20.204741954803467s
Availability | VoID file availability check for test-svu took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for test-svu took 0.3142080307006836s
Reputation | Calculation of the PageRank for test-svu took 0.021724462509155273s
Interlinking | Calculation of Degree of Connection for test-svu took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.123283386230469e-05s
Believability | Calculation of trust value for test-svu took 1.0967254638671875e-05s
INFO | --- Analysis for test-svu took 53.102684020996094s
Availability | SPARQL endpoint availability check for Test took 4.1961669921875e-05s
Availability | VoID file availability check for Test took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Test took 0.3030881881713867s
Reputation | Calculation of the PageRank for Test took 0.021857500076293945s
Interlinking | Calculation of Degree of Connection for Test took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Test took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Test took 3.0279159545898438e-05s
Believability | Calculation of trust value for Test took 1.049041748046875e-05s
INFO | --- Analysis for Test_ took 2.884103775024414s
Availability | SPARQL endpoint availability check for xxxxx took 261.44842529296875s
Availability | VoID file availability check for xxxxx took 0.0008091926574707031s
Completeness | Calculation of interlinking completeness for xxxxx took 0.46809840202331543s
Reputation | Calculation of the PageRank for xxxxx took 0.0218813419342041s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for xxxxx took 5.030632019042969e-05s
Believability | Calculation of trust value for xxxxx took 1.2874603271484375e-05s
INFO | --- Analysis for testee took 798.632527589798s
Availability | SPARQL endpoint availability check for tharawat magazine took 0.00010633468627929688s
Availability | VoID file availability check for tharawat magazine took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.29430079460144043s
Reputation | Calculation of the PageRank for tharawat magazine took 0.02079939842224121s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00010251998901367188s
Believability | Calculation of trust value for tharawat magazine took 1.1205673217773438e-05s
INFO | --- Analysis for tharawat-magazine-com took 3.5539610385894775s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 1.4030225276947021s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.28730249404907227s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.020677566528320312s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.0279159545898438e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 1.239776611328125e-05s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 7.982200860977173s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 3.3307719230651855s
Availability | VoID file availability check for The European Library Open Dataset took 0.0007305145263671875s
Extra | Recovery of all triples for The European Library Open Dataset took 6.259569406509399s
Performance | Total latancy measurement for The European Library Open Dataset took 15.959872722625732s
Amount of data | Number of triples check for The European Library Open Dataset took 64.1840705871582s
Interoperability | New terms check for The European Library Open Dataset took 61.08030390739441s
Versatility | Languages check for The European Library Open Dataset took 3.1785130500793457s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 3.2047884464263916s
Interpretability | RDF structures check for The European Library Open Dataset took 3.201817750930786s
Versatility | Serialization formats check for The European Library Open Dataset took 3.1993203163146973s
Availability | RDF dump link check for The European Library Open Dataset took 3.2046210765838623s
License | MR license check for The European Library Open Dataset took 3.197364330291748s
License | HR license check for The European Library Open Dataset took 3.2027714252471924s
Amount of data | Number of property check for The European Library Open Dataset took 3.200617551803589s
Understandability | Number of label check for The European Library Open Dataset took 3.821525812149048s
Understandability | URI regex check for The European Library Open Dataset took 6.413045883178711s
Understandability | Vocabs check for The European Library Open Dataset took 3.202146291732788s
Verifiability | Authors check for The European Library Open Dataset took 3.2053186893463135s
Verifiability | Publishers check for The European Library Open Dataset took 3.1984927654266357s
Performance | Throughput check for The European Library Open Dataset took 31.997992515563965s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.295608520507812e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 3.2032463550567627s
Interlinking | sameAs chians check for The European Library Open Dataset took 3.3547465801239014s
Interlinking | skos check for The European Library Open Dataset took 3.2504241466522217s
Interlinking | skos check for The European Library Open Dataset took 3.258883237838745s
Timeliness | dataset update frequency check for The European Library Open Dataset took 3.2228434085845947s
Currency | Creation date check for The European Library Open Dataset took 6.401982069015503s
Currency | Modification date check for The European Library Open Dataset took 6.397960901260376s
Rep.Conc. | URIs length for The European Library Open Dataset took 124.44145560264587s
Interoperability | New vocabularies check for The European Library Open Dataset took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 3.2079873085021973s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 3.4966416358947754s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.02636432647705078s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02816033363342285s
Consistency | Disjoint class check for The European Library Open Dataset took 3.197216510772705s
Consistency | Check Misplaced properties for The European Library Open Dataset took 67.82791876792908s
Consistency | Misplaced classes for The European Library Open Dataset took 3.306069850921631s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 4.76857328414917s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.1825644969940186s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 65.88235878944397s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03369593620300293s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 3.21598219871521s
Security | Sign check for The European Library Open Dataset took 3.1922428607940674s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 11.057281970977783s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.5224177837371826s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.02284836769104004s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 7.05718994140625e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 2.384185791015625e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 1.2636184692382812e-05s
INFO | --- Analysis for the-european-library-open-dataset took 921.5129041671753s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 0.8409128189086914s
Availability | VoID file availability check for The Eurostat Linked Data took 0.12966609001159668s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.3154182434082031s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.020942211151123047s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00010585784912109375s
Believability | Calculation of trust value for The Eurostat Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for the-eurostat-linked-data took 5.004968643188477s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 8.869171142578125e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.00036025047302246094s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.4237058162689209s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.02085137367248535s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.390975952148438e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 1.0967254638671875e-05s
INFO | --- Analysis for the-living-lod-cloud took 46.94255304336548s
Availability | SPARQL endpoint availability check for The View From took 0.1893618106842041s
Availability | VoID file availability check for The View From took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for The View From took 0.31409502029418945s
Reputation | Calculation of the PageRank for The View From took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for The View From took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The View From took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for The View From took 8.225440979003906e-05s
Believability | Calculation of trust value for The View From took 1.1444091796875e-05s
INFO | --- Analysis for the-view-from took 2.9455084800720215s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.446165561676025s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.3337099552154541s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020645618438720703s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007102489471435547s
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 6.198883056640625e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 73.33352041244507s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.064119338989258s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.33466386795043945s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020857810974121094s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.814697265625e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.0728836059570312e-05s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 103.14161610603333s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.363059997558594e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.2984781265258789s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.021224021911621094s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00011372566223144531s
Believability | Calculation of trust value for The Content Wrangler took 1.049041748046875e-05s
INFO | --- Analysis for thecontentwrangler-com took 3.390307903289795s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 8.630752563476562e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.27793121337890625s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.075599670410156e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 1.239776611328125e-05s
INFO | --- Analysis for thesaurus-datenwissen took 2.8690927028656006s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.5961189270019531s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.3224976062774658s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.022329092025756836s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 8.392333984375e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 1.239776611328125e-05s
INFO | --- Analysis for thesaurus-w took 4.137631893157959s
Availability | SPARQL endpoint availability check for theses.fr took 4.267692565917969e-05s
Availability | VoID file availability check for theses.fr took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for theses.fr took 0.301440954208374s
Reputation | Calculation of the PageRank for theses.fr took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.76837158203125e-05s
Believability | Calculation of trust value for theses.fr took 1.1205673217773438e-05s
INFO | --- Analysis for thesesfr took 4.455173492431641s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 5.4836273193359375e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.3018772602081299s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.020965099334716797s
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.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.457069396972656e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.0251998901367188e-05s
INFO | --- Analysis for Thinkphile took 2.620504856109619s
Availability | SPARQL endpoint availability check for ThIST took 265.38677525520325s
Availability | VoID file availability check for ThIST took 0.0008089542388916016s
Completeness | Calculation of interlinking completeness for ThIST took 0.35753941535949707s
Reputation | Calculation of the PageRank for ThIST took 0.0213315486907959s
Interlinking | Calculation of Degree of Connection for ThIST took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for ThIST took 8.678436279296875e-05s
Believability | Calculation of trust value for ThIST took 1.0013580322265625e-05s
INFO | --- Analysis for thist took 569.0596120357513s
Availability | SPARQL endpoint availability check for TIP took 40.04037809371948s
Availability | VoID file availability check for TIP took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for TIP took 0.2790851593017578s
Reputation | Calculation of the PageRank for TIP took 0.023626327514648438s
Interlinking | Calculation of Degree of Connection for TIP took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00011301040649414062s
Believability | Calculation of trust value for TIP took 1.0251998901367188e-05s
INFO | --- Analysis for tip took 102.90725803375244s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 9.1552734375e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.29464149475097656s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.020693302154541016s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 2.8371810913085938e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 7.3909759521484375e-06s
INFO | --- Analysis for TOPMODEL took 27.457661628723145s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.4389100074768066s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.28254032135009766s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.020678043365478516s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.218650817871094e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 8.344650268554688e-06s
INFO | --- Analysis for TP-data took 7.577545404434204s
Availability | SPARQL endpoint availability check for Trackloaded Artist Profiles took 11.500864744186401s
Availability | VoID file availability check for Trackloaded Artist Profiles took 0.00038361549377441406s
Extra | Recovery of all triples for Trackloaded Artist Profiles took 6.7460618019104s
Performance | Total latancy measurement for Trackloaded Artist Profiles took 36.51765155792236s
Amount of data | Number of triples check for Trackloaded Artist Profiles took 1.622236728668213s
Interoperability | New terms check for Trackloaded Artist Profiles took 3.27429461479187s
Versatility | Languages check for Trackloaded Artist Profiles took 3.00915789604187s
Interpretability | Number of blank nodes check for Trackloaded Artist Profiles took 1.243837833404541s
Interpretability | RDF structures check for Trackloaded Artist Profiles took 1.5405950546264648s
Versatility | Serialization formats check for Trackloaded Artist Profiles took 1.1212530136108398s
Availability | RDF dump link check for Trackloaded Artist Profiles took 2.0690486431121826s
License | MR license check for Trackloaded Artist Profiles took 2.294874906539917s
License | HR license check for Trackloaded Artist Profiles took 1.896106243133545s
Amount of data | Number of property check for Trackloaded Artist Profiles took 3.7728235721588135s
Understandability | Number of label check for Trackloaded Artist Profiles took 5.507632255554199s
Understandability | URI regex check for Trackloaded Artist Profiles took 6.909297466278076s
Understandability | Vocabs check for Trackloaded Artist Profiles took 1.2865760326385498s
Verifiability | Authors check for Trackloaded Artist Profiles took 1.4431188106536865s
Verifiability | Publishers check for Trackloaded Artist Profiles took 1.3125436305999756s
Performance | Throughput check for Trackloaded Artist Profiles took 22.658042907714844s
Amount of data | Check the number of entities for Trackloaded Artist Profiles took 6.4849853515625e-05s
Verifiability | Contribs. check for Trackloaded Artist Profiles took 1.8952834606170654s
Interlinking | sameAs chians check for Trackloaded Artist Profiles took 2.5099258422851562s
Interlinking | skos check for Trackloaded Artist Profiles took 2.088190793991089s
Interlinking | skos check for Trackloaded Artist Profiles took 2.783745765686035s
Timeliness | dataset update frequency check for Trackloaded Artist Profiles took 4.594515323638916s
Currency | Creation date check for Trackloaded Artist Profiles took 13.116509437561035s
Currency | Modification date check for Trackloaded Artist Profiles took 4.992462396621704s
Rep.Conc. | URIs length for Trackloaded Artist Profiles took 3.3164637088775635s
Interoperability | New vocabularies check for Trackloaded Artist Profiles took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Trackloaded Artist Profiles took 1.4208283424377441s
Consistency | Disjoint class check for Trackloaded Artist Profiles took 1.9427714347839355s
Consistency | Check Misplaced properties for Trackloaded Artist Profiles took 2.391124725341797s
Consistency | Misplaced classes for Trackloaded Artist Profiles took 1.168452501296997s
Consistency | Check Ontology hijacking for Trackloaded Artist Profiles took 2.256723642349243s
Consistency | Check Invalid usage of undefined classes for Trackloaded Artist Profiles took 1.134143590927124s
Consistency | Check Invalid usage of undefined properties for Trackloaded Artist Profiles took 3.0650172233581543s
Conciseness | Check Extensional conciseness for Trackloaded Artist Profiles took 0.00020170211791992188s
Security | Sign check for Trackloaded Artist Profiles took 1.8888373374938965s
Availability | Check URIs Dereferenciability for Trackloaded Artist Profiles took 1.4156394004821777s
Completeness | Calculation of interlinking completeness for Trackloaded Artist Profiles took 0.38774704933166504s
Reputation | Calculation of the PageRank for Trackloaded Artist Profiles took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for Trackloaded Artist Profiles took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Trackloaded Artist Profiles took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Trackloaded Artist Profiles took 3.0040740966796875e-05s
Interoperability | Check the re-using of existing vocabs for Trackloaded Artist Profiles took 1.1920928955078125e-06s
Believability | Calculation of trust value for Trackloaded Artist Profiles took 1.239776611328125e-05s
INFO | --- Analysis for trackloaded took 262.82159209251404s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.3512134552001953s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.31209897994995117s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.0206601619720459s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.3392181396484375e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for traditional-korean-medicine took 3.655844211578369s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.23319792747497559s
Availability | VoID file availability check for Traffic Scotland took 0.0010800361633300781s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.33507227897644043s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.218650817871094e-05s
Believability | Calculation of trust value for Traffic Scotland took 9.059906005859375e-06s
INFO | --- Analysis for traffic-scotland took 3.2113780975341797s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.12139201164245605s
Availability | VoID file availability check for Transparency International Linked Data took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.2857940196990967s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.02152228355407715s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010251998901367188s
Believability | Calculation of trust value for Transparency International Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for transparency-linked-data took 2.9422571659088135s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.6731894016265869s
Availability | VoID file availability check for transport.data.gov.uk took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.2888298034667969s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020738601684570312s
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.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.965896606445312e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 8.58306884765625e-06s
INFO | --- Analysis for transport-data-gov-uk took 4.314609050750732s
Availability | SPARQL endpoint availability check for Trelios took 6.699562072753906e-05s
Availability | VoID file availability check for Trelios took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Trelios took 0.27854037284851074s
Reputation | Calculation of the PageRank for Trelios took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for Trelios took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.1205673217773438e-05s
Believability | Calculation of trust value for Trelios took 1.239776611328125e-05s
INFO | --- Analysis for Trelios took 2.6761367321014404s
Availability | SPARQL endpoint availability check for Twarql took 10.543621301651001s
Availability | VoID file availability check for Twarql took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Twarql took 0.2855522632598877s
Reputation | Calculation of the PageRank for Twarql took 0.02042531967163086s
Interlinking | Calculation of Degree of Connection for Twarql took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.771087646484375e-05s
Believability | Calculation of trust value for Twarql took 1.2636184692382812e-05s
INFO | --- Analysis for twarql took 13.350029945373535s
Availability | SPARQL endpoint availability check for TWC Data-gov took 4.2438507080078125e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.30097436904907227s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.020707130432128906s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.3855438232421875e-05s
Believability | Calculation of trust value for TWC Data-gov took 9.059906005859375e-06s
INFO | --- Analysis for twc-data-gov took 13.057319402694702s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.15691184997558594s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.00034809112548828125s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.2833859920501709s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.020560741424560547s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 2.8133392333984375e-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.974524974822998s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.246130466461182s
Availability | VoID file availability check for Instance Hub (all) took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.30143046379089355s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 6.771087646484375e-05s
Believability | Calculation of trust value for Instance Hub (all) took 7.62939453125e-06s
INFO | --- Analysis for twc-hub took 76.62892508506775s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.1362144947052002s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.4687643051147461s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00010848045349121094s
Believability | Calculation of trust value for IEEE VIS Source Data took 5.7220458984375e-06s
INFO | --- Analysis for twc-ieeevis took 106.6720130443573s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 0.00011873245239257812s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.2764418125152588s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.02112865447998047s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 9.202957153320312e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 9.298324584960938e-06s
INFO | --- Analysis for twc-logd took 2.8147034645080566s
Availability | SPARQL endpoint availability check for twc-opendap took 0.1306314468383789s
Availability | VoID file availability check for twc-opendap took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.2925379276275635s
Reputation | Calculation of the PageRank for twc-opendap took 0.021069765090942383s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0008077621459960938s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 8.416175842285156e-05s
Believability | Calculation of trust value for twc-opendap took 1.1920928955078125e-05s
INFO | --- Analysis for twc-opendap took 69.59739303588867s
Availability | SPARQL endpoint availability check for typepad took 4.315376281738281e-05s
Availability | VoID file availability check for typepad took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for typepad took 0.2991189956665039s
Reputation | Calculation of the PageRank for typepad took 0.021071910858154297s
Interlinking | Calculation of Degree of Connection for typepad took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for typepad took 5.14984130859375e-05s
Believability | Calculation of trust value for typepad took 1.1682510375976562e-05s
INFO | --- Analysis for typepad took 3.3128435611724854s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 2.621387004852295s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.29390954971313477s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.021915912628173828s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.001107931137084961s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.792213439941406e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.1682510375976562e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 6.6801605224609375s
Availability | SPARQL endpoint availability check for Uberblic.org took 3.3233723640441895s
Availability | VoID file availability check for Uberblic.org took 0.0011327266693115234s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.31766247749328613s
Reputation | Calculation of the PageRank for Uberblic.org took 0.021167278289794922s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0010476112365722656s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.0001614093780517578s
Believability | Calculation of trust value for Uberblic.org took 1.2874603271484375e-05s
INFO | --- Analysis for uberblic took 8.654381275177002s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.6918511390686035s
Availability | VoID file availability check for UDante in LiLa took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.30782127380371094s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.020984172821044922s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 5.364418029785156e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for UDante took 4.685019254684448s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 0.9846048355102539s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.32090067863464355s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.02136826515197754s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 2.86102294921875e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for ufo took 4.927478075027466s
Availability | SPARQL endpoint availability check for Uganda Disasters took 4.315376281738281e-05s
Availability | VoID file availability check for Uganda Disasters took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.3399975299835205s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.023063182830810547s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 5.555152893066406e-05s
Believability | Calculation of trust value for Uganda Disasters took 1.3828277587890625e-05s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.868178367614746s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.05161118507385254s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.277172327041626s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.022742271423339844s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.00012159347534179688s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for uis-linked-data took 2.809321641921997s
Availability | SPARQL endpoint availability check for UK Legislation took 3.933906555175781e-05s
Availability | VoID file availability check for UK Legislation took 0.0006253719329833984s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.2748837471008301s
Reputation | Calculation of the PageRank for UK Legislation took 0.020660877227783203s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.7738037109375e-05s
Believability | Calculation of trust value for UK Legislation took 8.344650268554688e-06s
INFO | --- Analysis for uk-legislation-api took 3.730567693710327s
Availability | SPARQL endpoint availability check for UK Postcodes took 8.392333984375e-05s
Availability | VoID file availability check for UK Postcodes took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.32290029525756836s
Reputation | Calculation of the PageRank for UK Postcodes took 0.0212552547454834s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 6.008148193359375e-05s
Believability | Calculation of trust value for UK Postcodes took 1.2159347534179688e-05s
INFO | --- Analysis for uk-postcodes took 22.757237195968628s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 4.3392181396484375e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.28281593322753906s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.021643400192260742s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0001251697540283203s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.239776611328125e-05s
INFO | --- Analysis for umbel took 7.48805046081543s
Availability | SPARQL endpoint availability check for German environmental thesaurus UMTHES took 6.127357482910156e-05s
Availability | VoID file availability check for German environmental thesaurus UMTHES took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for German environmental thesaurus UMTHES took 0.31653308868408203s
Reputation | Calculation of the PageRank for German environmental thesaurus UMTHES took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for German environmental thesaurus UMTHES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for German environmental thesaurus UMTHES took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for German environmental thesaurus UMTHES took 4.1484832763671875e-05s
Believability | Calculation of trust value for German environmental thesaurus UMTHES took 8.58306884765625e-06s
INFO | --- Analysis for umthes took 3.6237282752990723s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 1.5101642608642578s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0008273124694824219s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.27285051345825195s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.020952463150024414s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.170967102050781e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 1.0251998901367188e-05s
INFO | --- Analysis for un-hazardous-numbers took 10.184797048568726s
Availability | SPARQL endpoint availability check for UniProt took 3.505040168762207s
Availability | VoID file availability check for UniProt took 0.0007393360137939453s
Extra | Recovery of all triples for UniProt took 17.61947536468506s
Performance | Total latancy measurement for UniProt took 6.364459991455078s
Amount of data | Number of triples check for UniProt took 0.5902960300445557s
Interoperability | New terms check for UniProt took 1.676220417022705s
Versatility | Languages check for UniProt took 1.9039390087127686s
Interpretability | Number of blank nodes check for UniProt took 3.3484222888946533s
Interpretability | RDF structures check for UniProt took 1.7421014308929443s
Versatility | Serialization formats check for UniProt took 3.013004779815674s
Availability | RDF dump link check for UniProt took 0.2986626625061035s
License | MR license check for UniProt took 1.227574348449707s
License | HR license check for UniProt took 300.0817801952362s
Amount of data | Number of property check for UniProt took 0.4768223762512207s
Understandability | Number of label check for UniProt took 55.74974250793457s
Understandability | URI regex check for UniProt took 1.0363309383392334s
Understandability | Vocabs check for UniProt took 0.9890480041503906s
Verifiability | Authors check for UniProt took 1.375458002090454s
Verifiability | Publishers check for UniProt took 1.1960530281066895s
Performance | Throughput check for UniProt took 29.91755700111389s
Amount of data | Check the number of entities for UniProt took 7.176399230957031e-05s
Verifiability | Contribs. check for UniProt took 0.7418005466461182s
Interlinking | sameAs chians check for UniProt took 0.5199470520019531s
Interlinking | skos check for UniProt took 1.5811495780944824s
Interlinking | skos check for UniProt took 0.07597851753234863s
Timeliness | dataset update frequency check for UniProt took 1.3389453887939453s
Currency | Creation date check for UniProt took 1.7203643321990967s
Currency | Modification date check for UniProt took 1.648465633392334s
Rep.Conc. | URIs length for UniProt took 118.25005197525024s
Interoperability | New vocabularies check for UniProt took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for UniProt took 0.6338958740234375s
Accuracy | Check Functional Property for UniProt took 0.3479421138763428s
Accuracy | Check Inverse Functional Property for UniProt took 0.3591163158416748s
Accuracy | Check Empty annotation labels for UniProt took 17.215455293655396s
Accuracy | Check White space in annotation for UniProt took 2.4996001720428467s
Accuracy | Check Datatype consistency for UniProt took 7.101353883743286s
Consistency | Disjoint class check for UniProt took 0.36343979835510254s
Consistency | Check Misplaced properties for UniProt took 2.72405743598938s
Consistency | Check Ontology hijacking for UniProt took 7.692367315292358s
Consistency | Check Invalid usage of undefined classes for UniProt took 18375.536796331406s
Consistency | Check Invalid usage of undefined properties for UniProt took 2.491417169570923s
Conciseness | Check Extensional conciseness for UniProt took 2.9348793029785156s
Conciseness | Check Intensional conciseness for UniProt took 0.83402419090271s
Security | Sign check for UniProt took 1.1047449111938477s
Availability | Check URIs Dereferenciability for UniProt took 4.658267974853516s
Completeness | Calculation of interlinking completeness for UniProt took 0.88993239402771s
Reputation | Calculation of the PageRank for UniProt took 0.02350330352783203s
Interlinking | Calculation of Degree of Connection for UniProt took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for UniProt took 0.00011396408081054688s
Interoperability | Check the re-using of existing vocabs for UniProt took 1.9073486328125e-06s
Believability | Calculation of trust value for UniProt took 1.1205673217773438e-05s
INFO | --- Analysis for UniProt took 19500.02432823181s
Availability | SPARQL endpoint availability check for UniProt took 3.649493455886841s
Availability | VoID file availability check for UniProt took 0.0006186962127685547s
Extra | Recovery of all triples for UniProt took 16.938207387924194s
Performance | Total latancy measurement for UniProt took 7.651240110397339s
Amount of data | Number of triples check for UniProt took 0.7598166465759277s
Versatility | Languages check for UniProt took 1.8074219226837158s
Interpretability | Number of blank nodes check for UniProt took 3.3856706619262695s
Security | Check HTTPS for UniProt took 3.0321619510650635s
Interpretability | RDF structures check for UniProt took 0.20655155181884766s
Versatility | Serialization formats check for UniProt took 0.17124056816101074s
Availability | RDF dump link check for UniProt took 0.17174005508422852s
License | MR license check for UniProt took 0.18972468376159668s
License | HR license check for UniProt took 0.1816730499267578s
Amount of data | Number of property check for UniProt took 0.19095396995544434s
Understandability | Number of label check for UniProt took 0.18692517280578613s
Understandability | URI regex check for UniProt took 0.3633720874786377s
Understandability | Vocabs check for UniProt took 0.18207240104675293s
Verifiability | Authors check for UniProt took 0.19632220268249512s
Verifiability | Publishers check for UniProt took 0.18532514572143555s
Performance | Throughput check for UniProt took 36.91636848449707s
Amount of data | Check the number of entities for UniProt took 0.000148773193359375s
Verifiability | Contribs. check for UniProt took 0.18201017379760742s
Interlinking | sameAs chians check for UniProt took 0.16355562210083008s
Interlinking | skos check for UniProt took 0.16834807395935059s
Interlinking | skos check for UniProt took 0.13841557502746582s
Timeliness | dataset update frequency check for UniProt took 0.1717071533203125s
Currency | Creation date check for UniProt took 0.36530423164367676s
Currency | Modification date check for UniProt took 0.36475205421447754s
Rep.Conc. | URIs length for UniProt took 119.64593982696533s
Interoperability | New vocabularies check for UniProt took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.1902177333831787s
Accuracy | Check Datatype consistency for UniProt took 6.995817184448242s
Consistency | Disjoint class check for UniProt took 0.16208410263061523s
Consistency | Check Ontology hijacking for UniProt took 0.16272997856140137s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.8504259586334229s
Conciseness | Check Extensional conciseness for UniProt took 2.67227840423584s
Security | Sign check for UniProt took 0.18552803993225098s
Availability | Check URIs Dereferenciability for UniProt took 4.030220031738281s
Completeness | Calculation of interlinking completeness for UniProt took 0.44190287590026855s
Reputation | Calculation of the PageRank for UniProt took 0.02305436134338379s
Interlinking | Calculation of Degree of Connection for UniProt took 8.535385131835938e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for UniProt took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 9.5367431640625e-07s
Believability | Calculation of trust value for UniProt took 1.1682510375976562e-05s
INFO | --- Analysis for uniprot took 759.2593488693237s
Availability | SPARQL endpoint availability check for uniprot-metadata took 9.131431579589844e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.3152649402618408s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.020886898040771484s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 5.888938903808594e-05s
Believability | Calculation of trust value for uniprot-metadata took 5.7220458984375e-06s
INFO | --- Analysis for uniprot-metadata took 3.9794559478759766s
Availability | SPARQL endpoint availability check for UniProtKB took 3.7653965950012207s
Availability | VoID file availability check for UniProtKB took 0.0006649494171142578s
Extra | Recovery of all triples for UniProtKB took 17.353846549987793s
Performance | Total latancy measurement for UniProtKB took 6.8643810749053955s
Amount of data | Number of triples check for UniProtKB took 0.6606848239898682s
Interoperability | New terms check for UniProtKB took 1.6757245063781738s
Versatility | Languages check for UniProtKB took 1.528686285018921s
Interpretability | Number of blank nodes check for UniProtKB took 3.618041515350342s
Interpretability | RDF structures check for UniProtKB took 2.09272837638855s
Versatility | Serialization formats check for UniProtKB took 2.8239595890045166s
Availability | RDF dump link check for UniProtKB took 0.3636784553527832s
License | MR license check for UniProtKB took 1.2939879894256592s
License | HR license check for UniProtKB took 300.09197664260864s
Amount of data | Number of property check for UniProtKB took 0.08253192901611328s
Understandability | Number of label check for UniProtKB took 55.126383543014526s
Understandability | URI regex check for UniProtKB took 0.9938433170318604s
Understandability | Vocabs check for UniProtKB took 0.8146343231201172s
Verifiability | Authors check for UniProtKB took 1.7893834114074707s
Verifiability | Publishers check for UniProtKB took 1.5360898971557617s
Performance | Throughput check for UniProtKB took 37.50030994415283s
Amount of data | Check the number of entities for UniProtKB took 6.747245788574219e-05s
Verifiability | Contribs. check for UniProtKB took 0.8851094245910645s
Interlinking | sameAs chians check for UniProtKB took 0.6793422698974609s
Interlinking | skos check for UniProtKB took 1.7788722515106201s
Interlinking | skos check for UniProtKB took 1.328887939453125s
Timeliness | dataset update frequency check for UniProtKB took 1.6637966632843018s
Currency | Creation date check for UniProtKB took 1.7784011363983154s
Currency | Modification date check for UniProtKB took 2.0211784839630127s
Rep.Conc. | URIs length for UniProtKB took 114.66330456733704s
Interoperability | New vocabularies check for UniProtKB took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.4016854763031006s
Accuracy | Check Functional Property for UniProtKB took 0.3532376289367676s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.36264610290527344s
Accuracy | Check Empty annotation labels for UniProtKB took 11.387485265731812s
Accuracy | Check White space in annotation for UniProtKB took 2.5159971714019775s
Accuracy | Check Datatype consistency for UniProtKB took 7.117293834686279s
Consistency | Disjoint class check for UniProtKB took 0.3997018337249756s
Consistency | Check Misplaced properties for UniProtKB took 2.0637853145599365s
Consistency | Check Ontology hijacking for UniProtKB took 7.544798135757446s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 20451.577167510986s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 2.1663167476654053s
Conciseness | Check Extensional conciseness for UniProtKB took 2.6836092472076416s
Conciseness | Check Intensional conciseness for UniProtKB took 0.7907552719116211s
Security | Sign check for UniProtKB took 1.2837169170379639s
Availability | Check URIs Dereferenciability for UniProtKB took 4.5387866497039795s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.8311812877655029s
Reputation | Calculation of the PageRank for UniProtKB took 0.021426677703857422s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 6.985664367675781e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 2.384185791015625e-06s
Believability | Calculation of trust value for UniProtKB took 1.2159347534179688e-05s
INFO | --- Analysis for uniprotkb took 21485.314640045166s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 4.76837158203125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0007152557373046875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.3106398582458496s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.021300077438354492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 13.896883010864258s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 8.463859558105469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.00041103363037109375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.29895758628845215s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.02089238166809082s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 4.018930435180664s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 8.58306884765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.31950831413269043s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.022109031677246094s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.525625705718994s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.000701904296875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.31903505325317383s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.021218299865722656s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.565963745117188s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.28780651092529297s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.02107834815979004s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 13.516730308532715s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 8.416175842285156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.28464341163635254s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.020798921585083008s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 13.48865270614624s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 8.511543273925781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.2861604690551758s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.022205829620361328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 4.134841203689575s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 8.535385131835938e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.29753684997558594s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 5.7220458984375e-06s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.410135507583618s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0007462501525878906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.28321409225463867s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.021449565887451172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.570654153823853s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0007405281066894531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.2652122974395752s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.021091222763061523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.453798770904541s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 9.5367431640625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.306765079498291s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.021753549575805664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 13.284563064575195s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0008039474487304688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.30036449432373047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.021759510040283203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.839897155761719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 13.367952585220337s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 8.320808410644531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.31061768531799316s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.02101588249206543s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-danish took 4.48912787437439s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.601478576660156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0007169246673583984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.32112669944763184s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.020876407623291016s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.453173875808716s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 8.296966552734375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.3157625198364258s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.020872831344604492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 13.36855673789978s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 8.797645568847656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0007817745208740234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.407437801361084s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.02175617218017578s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 1.4543533325195312e-05s
INFO | --- Analysis for universal-dependencies-treebank-english took 13.696415662765503s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 8.797645568847656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0007686614990234375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.2795701026916504s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.022459983825683594s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.6253204345703125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.304521322250366s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 8.225440979003906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.2839772701263428s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.02079153060913086s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 13.218193769454956s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 8.535385131835938e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.2759552001953125s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.02235579490661621s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0008256435394287109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 13.461445569992065s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 8.273124694824219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.298900842666626s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020977258682250977s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 4.162253379821777s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 4.553794860839844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.277022123336792s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.021181344985961914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 13.284604549407959s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.30300140380859375s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.020769596099853516s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.453043937683105s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.33349037170410156s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.02318859100341797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 3.62396240234375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.605252265930176s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 8.296966552734375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.31169557571411133s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.020582914352416992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 3.9754350185394287s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 8.416175842285156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.315840482711792s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-german took 4.193748712539673s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 8.249282836914062e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.26390957832336426s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.02242136001586914s
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.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 4.249661922454834s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.32651543617248535s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.02204298973083496s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-greek took 3.9769163131713867s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 8.368492126464844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.30515503883361816s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.021333694458007812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.781583547592163s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 6.723403930664062e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.2756919860839844s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 3.743171691894531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.48195219039917s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 0.00012159347534179688s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.2904834747314453s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 4.380950927734375s
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.0006630420684814453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.2873258590698242s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.02169013023376465s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.440731763839722s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 0.000133514404296875s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.2975587844848633s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-irish took 4.313560962677002s
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.0006406307220458984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.3049900531768799s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.02157425880432129s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-italian took 13.608025550842285s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.2756154537200928s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 3.647804260253906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.361591100692749s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 0.00010895729064941406s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.3169384002685547s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 3.8418326377868652s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 8.463859558105469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0008242130279541016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.29065656661987305s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.3392181396484375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 13.435335159301758s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 5.5789947509765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.299701452255249s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.021162986755371094s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin took 4.096048355102539s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.29106974601745605s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.02080535888671875s
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.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 13.214048385620117s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 8.344650268554688e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.2847275733947754s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.02066326141357422s
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.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 3.719329833984375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 13.253354787826538s
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.0005624294281005859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.31160569190979004s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.021994829177856445s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.57334041595459s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 8.130073547363281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.3072071075439453s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.024286985397338867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0011186599731445312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 5.698204040527344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 13.286221265792847s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 8.630752563476562e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0008144378662109375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.30329251289367676s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.0213015079498291s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.446672677993774s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 5.91278076171875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.3268263339996338s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.022980928421020508s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0008707046508789062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.57763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-persian took 4.161895275115967s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0007357597351074219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.3019859790802002s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.020901918411254883s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.428255796432495s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 8.344650268554688e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.33831000328063965s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.021353483200073242s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 13.430912256240845s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 8.440017700195312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0007331371307373047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.29251694679260254s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020978689193725586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 5.14984130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 9.298324584960938e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 13.338165044784546s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 0.00010371208190917969s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.2824366092681885s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.021900177001953125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 4.00543212890625e-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.516332149505615s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 8.225440979003906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.2736854553222656s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.02107691764831543s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.491360664367676s
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.0006289482116699219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.30591511726379395s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.021833181381225586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.359262704849243s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 8.702278137207031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0007691383361816406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.3468441963195801s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.023055553436279297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 4.3502960205078125s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 5.793571472167969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.000732421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.3278515338897705s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.021095752716064453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.44272255897522s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 8.058547973632812e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0006883144378662109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.3181571960449219s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.02103114128112793s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 6.723403930664062e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.514561176300049s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 0.00010275840759277344s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.2879772186279297s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.020827770233154297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.507413148880005s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.29286670684814453s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.021091699600219727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 13.351440668106079s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 5.507469177246094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.28411173820495605s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.020933866500854492s
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.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 13.810949325561523s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.2923929691314697s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.020880699157714844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 13.381023406982422s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 9.870529174804688e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.27587890625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.020865201950073242s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 4.353120803833008s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.3148503303527832s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.022790193557739258s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 3.856093168258667s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 4.673004150390625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.28925466537475586s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.021524906158447266s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0011775493621826172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 13.533095359802246s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 8.726119995117188e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.29806971549987793s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020681142807006836s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.363412141799927s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 8.749961853027344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.3177056312561035s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.02045416831970215s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.559389352798462s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.57763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.3257603645324707s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 13.413028955459595s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 6.341934204101562e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.29920172691345215s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.02078843116760254s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 13.542734146118164s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 8.797645568847656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.3259711265563965s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.45674729347229s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 4.220008850097656e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.2761833667755127s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.021266460418701172s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.651878356933594e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 1.1444091796875e-05s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 7.264579772949219s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 8.678436279296875e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.2822883129119873s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.02054619789123535s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 5.340576171875e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.1205673217773438e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 3.2846689224243164s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 8.487701416015625e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.28333497047424316s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.0212862491607666s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0010292530059814453s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 4.57763671875e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 1.3113021850585938e-05s
INFO | --- Analysis for university-sussex-reading-lists took 3.0598361492156982s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 6.234256744384766s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.2793431282043457s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.022556066513061523s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 7.557868957519531e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 1.0728836059570312e-05s
INFO | --- Analysis for unodc took 16.152148723602295s
Availability | SPARQL endpoint availability check for Super Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Super Ontology took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.32562875747680664s
Reputation | Calculation of the PageRank for Super Ontology took 0.020677566528320312s
Interlinking | Calculation of Degree of Connection for Super Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 9.369850158691406e-05s
Believability | Calculation of trust value for Super Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for upper-ontology took 3.6675944328308105s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 1.1791174411773682s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.29377245903015137s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.021091222763061523s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for Upper_Ontology took 4.870106220245361s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 8.440017700195312e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.2668952941894531s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.022394895553588867s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 3.0994415283203125e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 1.1920928955078125e-05s
INFO | --- Analysis for Urban_Atlas_ took 2.67995023727417s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 1.0843067169189453s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.29294443130493164s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.0211179256439209s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 3.123283386230469e-05s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 6.198883056640625e-06s
INFO | --- Analysis for Urban_Atlas_Dataset took 4.356961250305176s
Availability | SPARQL endpoint availability check for URIBurner took 1.945357084274292s
Availability | VoID file availability check for URIBurner took 0.0004742145538330078s
Extra | Recovery of all triples for URIBurner took 123.14911890029907s
Performance | Total latancy measurement for URIBurner took 3.6313982009887695s
Amount of data | Number of triples check for URIBurner took 3.5659539699554443s
Interoperability | New terms check for URIBurner took 37.96613526344299s
Versatility | Languages check for URIBurner took 122.99003624916077s
Interpretability | Number of blank nodes check for URIBurner took 2.14633846282959s
Security | Check HTTPS for URIBurner took 1.182197093963623s
Interpretability | RDF structures check for URIBurner took 3.473792791366577s
Versatility | Serialization formats check for URIBurner took 7.06020450592041s
Availability | RDF dump link check for URIBurner took 50.804890632629395s
License | MR license check for URIBurner took 1.4456028938293457s
License | HR license check for URIBurner took 122.38274335861206s
Amount of data | Number of property check for URIBurner took 0.9700744152069092s
Understandability | Number of label check for URIBurner took 4.225483179092407s
Understandability | URI regex check for URIBurner took 1.7054264545440674s
Understandability | Vocabs check for URIBurner took 0.8292160034179688s
Verifiability | Authors check for URIBurner took 0.8906505107879639s
Verifiability | Publishers check for URIBurner took 0.8275783061981201s
Performance | Throughput check for URIBurner took 14.572266101837158s
Amount of data | Check the number of entities for URIBurner took 8.797645568847656e-05s
Verifiability | Contribs. check for URIBurner took 0.7959661483764648s
Interlinking | sameAs chians check for URIBurner took 1.0700414180755615s
Interlinking | skos check for URIBurner took 1.0814697742462158s
Interlinking | skos check for URIBurner took 0.7136197090148926s
Timeliness | dataset update frequency check for URIBurner took 1.2987909317016602s
Currency | Creation date check for URIBurner took 3.7983434200286865s
Currency | Modification date check for URIBurner took 0.8771989345550537s
Rep.Conc. | URIs length for URIBurner took 126.58982038497925s
Interoperability | New vocabularies check for URIBurner took 21.73724389076233s
Consistency | Deprecated classes/propertiers check for URIBurner took 0.767711877822876s
Accuracy | Check Functional Property for URIBurner took 0.795419454574585s
Accuracy | Check Inverse Functional Property for URIBurner took 0.7199897766113281s
Accuracy | Check Empty annotation labels for URIBurner took 57.09562015533447s
Accuracy | Check White space in annotation for URIBurner took 0.1800532341003418s
Consistency | Disjoint class check for URIBurner took 0.7993021011352539s
Consistency | Check Misplaced properties for URIBurner took 305.50108432769775s
Consistency | Misplaced classes for URIBurner took 58.40940546989441s
Consistency | Check Ontology hijacking for URIBurner took 59.45673751831055s
Consistency | Check Invalid usage of undefined properties for URIBurner took 59.648154735565186s
Conciseness | Check Extensional conciseness for URIBurner took 0.0001666545867919922s
Conciseness | Check Intensional conciseness for URIBurner took 111.85917782783508s
Security | Sign check for URIBurner took 1.022414207458496s
Completeness | Calculation of interlinking completeness for URIBurner took 0.5035386085510254s
Reputation | Calculation of the PageRank for URIBurner took 0.02123093605041504s
Interlinking | Calculation of Degree of Connection for URIBurner took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for URIBurner took 9.465217590332031e-05s
Interoperability | Check the re-using of existing vocabs for URIBurner took 23.90904140472412s
Believability | Calculation of trust value for URIBurner took 1.3113021850585938e-05s
INFO | --- Analysis for uriburner took 11774.800755739212s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.363059997558594e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.2887442111968994s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.021228790283203125s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 6.031990051269531e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.86102294921875e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 7.3909759521484375e-06s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 2.7808258533477783s
Availability | SPARQL endpoint availability check for Legija Stranaca took 0.00010347366333007812s
Availability | VoID file availability check for Legija Stranaca took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.3202781677246094s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.022444963455200195s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 2.8848648071289062e-05s
Believability | Calculation of trust value for Legija Stranaca took 1.2159347534179688e-05s
INFO | --- Analysis for Uros_Legija_Susa took 2.726046085357666s
Availability | SPARQL endpoint availability check for Legija took 8.7738037109375e-05s
Availability | VoID file availability check for Legija took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Legija took 0.28547191619873047s
Reputation | Calculation of the PageRank for Legija took 0.022068262100219727s
Interlinking | Calculation of Degree of Connection for Legija took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Legija took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Legija took 2.7894973754882812e-05s
Believability | Calculation of trust value for Legija took 1.0013580322265625e-05s
INFO | --- Analysis for Uros_Susa took 2.754225492477417s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.36464357376098633s
Availability | VoID file availability check for USAGE review corpus took 0.0012500286102294922s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.3205115795135498s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.021120548248291016s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.0040740966796875e-05s
Believability | Calculation of trust value for USAGE review corpus took 8.344650268554688e-06s
INFO | --- Analysis for usage-review-corpus took 3.8328399658203125s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 5.556670665740967s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0003502368927001953s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.30506324768066406s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.02077031135559082s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.367134094238281e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 1.239776611328125e-05s
INFO | --- Analysis for utpl-lod took 10.877047061920166s
Availability | SPARQL endpoint availability check for terrorist attack took 4.172325134277344e-05s
Availability | VoID file availability check for terrorist attack took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.3075435161590576s
Reputation | Calculation of the PageRank for terrorist attack took 0.02171778678894043s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 3.552436828613281e-05s
Believability | Calculation of trust value for terrorist attack took 1.0967254638671875e-05s
INFO | --- Analysis for varsha took 4.519496202468872s
Availability | SPARQL endpoint availability check for VA took 8.988380432128906e-05s
Availability | VoID file availability check for VA took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for VA took 0.29213762283325195s
Reputation | Calculation of the PageRank for VA took 0.021144628524780273s
Interlinking | Calculation of Degree of Connection for VA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VA took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for VA took 3.147125244140625e-05s
Believability | Calculation of trust value for VA took 1.0251998901367188e-05s
INFO | --- Analysis for Vehicule_Autonome took 2.978297233581543s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 0.7079756259918213s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.28066205978393555s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.02233409881591797s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 4.4345855712890625e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 1.0013580322265625e-05s
INFO | --- Analysis for VelezIndexTotiusArtis took 4.445223331451416s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 6.568280935287476s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0007748603820800781s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.2938413619995117s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 9.036064147949219e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 1.2874603271484375e-05s
INFO | --- Analysis for verrijktkoninkrijk took 15.716557502746582s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 8.368492126464844e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.31313443183898926s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.02098369598388672s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00016999244689941406s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.049041748046875e-05s
INFO | --- Analysis for viaf took 20.65662693977356s
Availability | SPARQL endpoint availability check for Vihar Exports took 8.654594421386719e-05s
Availability | VoID file availability check for Vihar Exports took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.305387020111084s
Reputation | Calculation of the PageRank for Vihar Exports took 0.02134561538696289s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 3.075599670410156e-05s
Believability | Calculation of trust value for Vihar Exports took 1.2636184692382812e-05s
INFO | --- Analysis for Vihar_Exports took 2.7641477584838867s
Availability | SPARQL endpoint availability check for VIVO took 8.153915405273438e-05s
Availability | VoID file availability check for VIVO took 0.0006425380706787109s
Completeness | Calculation of interlinking completeness for VIVO took 0.27557873725891113s
Reputation | Calculation of the PageRank for VIVO took 0.021004915237426758s
Interlinking | Calculation of Degree of Connection for VIVO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for VIVO took 7.033348083496094e-05s
Believability | Calculation of trust value for VIVO took 1.1682510375976562e-05s
INFO | --- Analysis for vivo took 5.168891191482544s
Availability | SPARQL endpoint availability check for VIVO Cornell took 4.3392181396484375e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.2970771789550781s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.020823240280151367s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.678436279296875e-05s
Believability | Calculation of trust value for VIVO Cornell took 1.1682510375976562e-05s
INFO | --- Analysis for vivo-cornell-university took 6.332197427749634s
Availability | SPARQL endpoint availability check for VIVO Indiana took 4.38690185546875e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.3028993606567383s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.02082037925720215s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 8.273124694824219e-05s
Believability | Calculation of trust value for VIVO Indiana took 1.1205673217773438e-05s
INFO | --- Analysis for vivo-indiana-university took 3.33817720413208s
Availability | SPARQL endpoint availability check for VIVO Ponce took 8.869171142578125e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.28624892234802246s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.020798206329345703s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.4332275390625e-05s
Believability | Calculation of trust value for VIVO Ponce took 1.1205673217773438e-05s
INFO | --- Analysis for vivo-ponce took 3.1543526649475098s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 4.1961669921875e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.3000977039337158s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.02072310447692871s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.552436828613281e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 1.1444091796875e-05s
INFO | --- Analysis for vivo-scripps-research-institute took 3.1827638149261475s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 8.392333984375e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.29729413986206055s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.02268671989440918s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.34600830078125e-05s
Believability | Calculation of trust value for VIVO University of Florida took 1.049041748046875e-05s
INFO | --- Analysis for vivo-university-of-florida took 2.8989779949188232s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 9.274482727050781e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.3036932945251465s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.020992517471313477s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.838539123535156e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 5.0067901611328125e-06s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 3.140947103500366s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 8.320808410644531e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.2722146511077881s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.62396240234375e-05s
Believability | Calculation of trust value for VIVO WUSTL took 1.049041748046875e-05s
INFO | --- Analysis for vivo-wustl took 3.1003878116607666s
Availability | SPARQL endpoint availability check for vivo2doi took 8.487701416015625e-05s
Availability | VoID file availability check for vivo2doi took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.28579139709472656s
Reputation | Calculation of the PageRank for vivo2doi took 0.02107858657836914s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.696846008300781e-05s
Believability | Calculation of trust value for vivo2doi took 1.0251998901367188e-05s
INFO | --- Analysis for vivo2doi took 25.701220273971558s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 4.38690185546875e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.29813599586486816s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.021240234375s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.67572021484375e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 1.0728836059570312e-05s
INFO | --- Analysis for vu-wordnet took 14.7210693359375s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.15947556495666504s
Availability | VoID file availability check for vulnerapedia took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.2964515686035156s
Reputation | Calculation of the PageRank for vulnerapedia took 0.02082514762878418s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 6.580352783203125e-05s
Believability | Calculation of trust value for vulnerapedia took 1.0251998901367188e-05s
INFO | --- Analysis for vulnerapedia took 3.379621744155884s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 8.392333984375e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.2617614269256592s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.02139592170715332s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.239776611328125e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.049041748046875e-05s
INFO | --- Analysis for VVASIAK took 2.5862741470336914s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 4.2438507080078125e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.3233513832092285s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.021032094955444336s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.0994415283203125e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 1.0013580322265625e-05s
INFO | --- Analysis for Vyvasta took 2.6698522567749023s
Availability | SPARQL endpoint availability check for W3C took 8.654594421386719e-05s
Availability | VoID file availability check for W3C took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for W3C took 0.30197715759277344s
Reputation | Calculation of the PageRank for W3C took 0.021172046661376953s
Interlinking | Calculation of Degree of Connection for W3C took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for W3C took 0.00013875961303710938s
Believability | Calculation of trust value for W3C took 1.049041748046875e-05s
INFO | --- Analysis for w3c took 2.9120800495147705s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 8.440017700195312e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.3151881694793701s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.02074432373046875s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.0001347064971923828s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 1.1205673217773438e-05s
INFO | --- Analysis for w3c-wordnet took 3.6286323070526123s
Availability | SPARQL endpoint availability check for WarSampo took 0.3526909351348877s
Availability | VoID file availability check for WarSampo took 0.0006732940673828125s
Extra | Recovery of all triples for WarSampo took 23.479061365127563s
Performance | Total latancy measurement for WarSampo took 0.8135557174682617s
Amount of data | Number of triples check for WarSampo took 18.183500289916992s
Interoperability | New terms check for WarSampo took 3.7348058223724365s
Versatility | Languages check for WarSampo took 50.75842571258545s
Interpretability | Number of blank nodes check for WarSampo took 17.44177770614624s
Security | Check HTTPS for WarSampo took 0.3970344066619873s
Interpretability | RDF structures check for WarSampo took 0.19214344024658203s
Versatility | Serialization formats check for WarSampo took 0.1885981559753418s
Availability | RDF dump link check for WarSampo took 1.61769437789917s
License | MR license check for WarSampo took 1.2439496517181396s
License | HR license check for WarSampo took 44.685914039611816s
Amount of data | Number of property check for WarSampo took 0.2079935073852539s
Understandability | Number of label check for WarSampo took 8.775994062423706s
Understandability | URI regex check for WarSampo took 0.34252023696899414s
Understandability | Vocabs check for WarSampo took 0.16158032417297363s
Verifiability | Authors check for WarSampo took 0.18913722038269043s
Verifiability | Publishers check for WarSampo took 0.18126368522644043s
Performance | Throughput check for WarSampo took 10.964959144592285s
Amount of data | Check the number of entities for WarSampo took 15.426368474960327s
Verifiability | Contribs. check for WarSampo took 0.1903395652770996s
Interlinking | sameAs chians check for WarSampo took 0.19882965087890625s
Interlinking | skos check for WarSampo took 0.20630335807800293s
Interlinking | skos check for WarSampo took 0.15653204917907715s
Timeliness | dataset update frequency check for WarSampo took 0.16987109184265137s
Currency | Creation date check for WarSampo took 0.3519251346588135s
Currency | Modification date check for WarSampo took 0.35050058364868164s
Rep.Conc. | URIs length for WarSampo took 48.68415570259094s
Interoperability | New vocabularies check for WarSampo took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.1879568099975586s
Accuracy | Check Functional Property for WarSampo took 0.18813753128051758s
Accuracy | Check Inverse Functional Property for WarSampo took 0.1600325107574463s
Accuracy | Check Empty annotation labels for WarSampo took 10.589042663574219s
Accuracy | Check White space in annotation for WarSampo took 2.1767330169677734s
Accuracy | Check Datatype consistency for WarSampo took 5.334875106811523s
Consistency | Disjoint class check for WarSampo took 0.20284390449523926s
Consistency | Check Misplaced properties for WarSampo took 19.834683179855347s
Consistency | Check Ontology hijacking for WarSampo took 18.559211492538452s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.3936927318572998s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.6210427284240723s
Conciseness | Check Extensional conciseness for WarSampo took 2.826582908630371s
Conciseness | Check Intensional conciseness for WarSampo took 0.27022886276245117s
Security | Sign check for WarSampo took 0.16070771217346191s
Availability | Check URIs Dereferenciability for WarSampo took 2.568096160888672s
Completeness | Calculation of interlinking completeness for WarSampo took 0.46523284912109375s
Reputation | Calculation of the PageRank for WarSampo took 0.021305561065673828s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for WarSampo took 8.630752563476562e-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 851.9008762836456s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.60492253303528s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.29849767684936523s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.025110960006713867s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 8.749961853027344e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 1.1205673217773438e-05s
INFO | --- Analysis for wasabi took 55.13398480415344s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 60.06157469749451s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.2764279842376709s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.021174907684326172s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 3.814697265625e-05s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 9.775161743164062e-06s
INFO | --- Analysis for Water_Areas_Classification took 122.81600546836853s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 60.04835820198059s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.27425527572631836s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.02087688446044922s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 2.9802322387695312e-05s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 5.245208740234375e-06s
INFO | --- Analysis for Water_Buffer took 122.80150127410889s
Availability | SPARQL endpoint availability check for WebIsALOD took 30.245120763778687s
Availability | VoID file availability check for WebIsALOD took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.32295894622802734s
Reputation | Calculation of the PageRank for WebIsALOD took 0.022641897201538086s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 8.368492126464844e-05s
Believability | Calculation of trust value for WebIsALOD took 1.3113021850585938e-05s
INFO | --- Analysis for webisalod took 67.79703426361084s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 9.72747802734375e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.2891960144042969s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.020727872848510742s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 3.5762786865234375e-05s
Believability | Calculation of trust value for webnmasunotraveler took 1.2636184692382812e-05s
INFO | --- Analysis for webnmasunotraveler took 8.868710994720459s
Availability | SPARQL endpoint availability check for Whisky Circle took 8.654594421386719e-05s
Availability | VoID file availability check for Whisky Circle took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.3234751224517822s
Reputation | Calculation of the PageRank for Whisky Circle took 0.020640850067138672s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00011372566223144531s
Believability | Calculation of trust value for Whisky Circle took 1.239776611328125e-05s
INFO | --- Analysis for whisky-circle-info took 3.3148016929626465s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 15.454798460006714s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.31450366973876953s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.023450136184692383s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0010652542114257812s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 4.982948303222656e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 1.239776611328125e-05s
INFO | --- Analysis for WHOnto took 36.24036169052124s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0008039474487304688s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.2782280445098877s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.02104663848876953s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 3.361701965332031e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 1.239776611328125e-05s
INFO | --- Analysis for whonto took 8.71901535987854s
Availability | SPARQL endpoint availability check for Wikidata took 1.0205631256103516s
Availability | VoID file availability check for Wikidata took 0.0007920265197753906s
Extra | Recovery of all triples for Wikidata took 24.705447912216187s
Performance | Total latancy measurement for Wikidata took 1.5590054988861084s
Amount of data | Number of triples check for Wikidata took 65.15475344657898s
Interoperability | New terms check for Wikidata took 1.8999576568603516s
Versatility | Languages check for Wikidata took 65.15988445281982s
Interpretability | Number of blank nodes check for Wikidata took 65.32502865791321s
Interpretability | RDF structures check for Wikidata took 0.4889094829559326s
Versatility | Serialization formats check for Wikidata took 0.19636321067810059s
Availability | RDF dump link check for Wikidata took 0.3045237064361572s
License | MR license check for Wikidata took 0.18549251556396484s
License | HR license check for Wikidata took 65.18435645103455s
Amount of data | Number of property check for Wikidata took 0.6027936935424805s
Understandability | Number of label check for Wikidata took 65.16719365119934s
Understandability | URI regex check for Wikidata took 0.36835789680480957s
Understandability | Vocabs check for Wikidata took 0.19726896286010742s
Verifiability | Authors check for Wikidata took 0.48125386238098145s
Verifiability | Publishers check for Wikidata took 0.1830275058746338s
Performance | Throughput check for Wikidata took 11.118749380111694s
Amount of data | Check the number of entities for Wikidata took 6.866455078125e-05s
Verifiability | Contribs. check for Wikidata took 0.17090678215026855s
Interlinking | sameAs chians check for Wikidata took 17.475959300994873s
Interlinking | skos check for Wikidata took 0.20721006393432617s
Interlinking | skos check for Wikidata took 0.5802764892578125s
Timeliness | dataset update frequency check for Wikidata took 0.1721184253692627s
Currency | Creation date check for Wikidata took 0.37981176376342773s
Currency | Modification date check for Wikidata took 0.3707163333892822s
Rep.Conc. | URIs length for Wikidata took 26.355172872543335s
Interoperability | New vocabularies check for Wikidata took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Wikidata took 0.1813807487487793s
Accuracy | Check Empty annotation labels for Wikidata took 19.66081690788269s
Accuracy | Check White space in annotation for Wikidata took 2.632328748703003s
Accuracy | Check Datatype consistency for Wikidata took 4.636366844177246s
Consistency | Disjoint class check for Wikidata took 0.17937541007995605s
Consistency | Check Misplaced properties for Wikidata took 25.36724042892456s
Consistency | Misplaced classes for Wikidata took 8.850430250167847s
Consistency | Check Ontology hijacking for Wikidata took 17.402463912963867s
Consistency | Check Invalid usage of undefined classes for Wikidata took 1.3059134483337402s
Consistency | Check Invalid usage of undefined properties for Wikidata took 8.186236143112183s
Conciseness | Check Extensional conciseness for Wikidata took 2.7823448181152344s
Conciseness | Check Intensional conciseness for Wikidata took 1.5989954471588135s
Security | Sign check for Wikidata took 0.1723465919494629s
Availability | Check URIs Dereferenciability for Wikidata took 8.996651887893677s
Completeness | Calculation of interlinking completeness for Wikidata took 0.5688621997833252s
Reputation | Calculation of the PageRank for Wikidata took 0.021645545959472656s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.00029754638671875s
Interoperability | Check the re-using of existing vocabs for Wikidata took 2.384185791015625e-06s
Believability | Calculation of trust value for Wikidata took 5.4836273193359375e-06s
INFO | --- Analysis for wikidata took 962.8861298561096s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 9.34600830078125e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.278425931930542s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.021128177642822266s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 7.510185241699219e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 1.049041748046875e-05s
INFO | --- Analysis for wikilinks-rdf-nif took 2.7853989601135254s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.2894856929779053s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.29450035095214844s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.02139902114868164s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.487701416015625e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 1.1920928955078125e-05s
INFO | --- Analysis for wiktionary-dbpedia-org took 4.5892653465271s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2188611030578613s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.299379825592041s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.021288633346557617s
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.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.075599670410156e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 1.1205673217773438e-05s
INFO | --- Analysis for wl-kg took 4.2181665897369385s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 7.224082946777344e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.33895301818847656s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 6.818771362304688e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 1.0013580322265625e-05s
INFO | --- Analysis for wn-wiki-instances took 3.574418306350708s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.1366863250732422s
Availability | VoID file availability check for World Loanword Database took 0.0004267692565917969s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.3277559280395508s
Reputation | Calculation of the PageRank for World Loanword Database took 0.021132469177246094s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 7.081031799316406e-05s
Believability | Calculation of trust value for World Loanword Database took 1.0251998901367188e-05s
INFO | --- Analysis for wold took 2.9710769653320312s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 8.511543273925781e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.2687711715698242s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.022630929946899414s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 3.266334533691406e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.239776611328125e-05s
INFO | --- Analysis for woodtrick took 3.266822099685669s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 0.5874722003936768s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.0004012584686279297s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.2737398147583008s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.022618532180786133s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 4.4345855712890625e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 1.0967254638671875e-05s
INFO | --- Analysis for WordFormationLatin took 4.326073408126831s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 8.821487426757812e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.2971477508544922s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.021094560623168945s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.00010776519775390625s
Believability | Calculation of trust value for WordLift Blog EN took 1.0251998901367188e-05s
INFO | --- Analysis for wordlift-io-blog-en took 3.197158098220825s
Availability | SPARQL endpoint availability check for WordLift IT took 4.291534423828125e-05s
Availability | VoID file availability check for WordLift IT took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.26465678215026855s
Reputation | Calculation of the PageRank for WordLift IT took 0.02146148681640625s
Interlinking | Calculation of Degree of Connection for WordLift IT took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WordLift IT took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00010704994201660156s
Believability | Calculation of trust value for WordLift IT took 1.1205673217773438e-05s
INFO | --- Analysis for wordlift-io-blog-it took 3.44405198097229s
Availability | SPARQL endpoint availability check for WordNet-RDF took 8.487701416015625e-05s
Availability | VoID file availability check for WordNet-RDF took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.2847921848297119s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.021986007690429688s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.393692016601562e-05s
Believability | Calculation of trust value for WordNet-RDF took 1.049041748046875e-05s
INFO | --- Analysis for wordnet-rdf took 2.6265101432800293s
Availability | SPARQL endpoint availability check for wordpress took 8.559226989746094e-05s
Availability | VoID file availability check for wordpress took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for wordpress took 0.26570892333984375s
Reputation | Calculation of the PageRank for wordpress took 0.023020029067993164s
Interlinking | Calculation of Degree of Connection for wordpress took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for wordpress took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.702278137207031e-05s
Believability | Calculation of trust value for wordpress took 1.049041748046875e-05s
INFO | --- Analysis for wordpress took 3.1405420303344727s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 0.11051392555236816s
Availability | VoID file availability check for World Bank Linked Data took 0.0004246234893798828s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.3023808002471924s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.023093223571777344s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00012493133544921875s
Believability | Calculation of trust value for World Bank Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for world-bank-linked-data took 2.876304864883423s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 1.1116340160369873s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.3048989772796631s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.02106618881225586s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.630752563476562e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 1.0013580322265625e-05s
INFO | --- Analysis for world-factbook-fu-berlin took 5.509625434875488s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 8.487701416015625e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.28812289237976074s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.02074742317199707s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.511543273925781e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 1.0251998901367188e-05s
INFO | --- Analysis for world-wide-web-foundation took 5.886361598968506s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.1847515106201172s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0010142326354980469s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 3.0220916271209717s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.8124408721923828s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.24336457252502441s
Interoperability | New terms check for World War 1 as Linked Open Data took 2.543839931488037s
Versatility | Languages check for World War 1 as Linked Open Data took 0.36698365211486816s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.23352861404418945s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.40277099609375s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.43247413635253906s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.26581478118896484s
Availability | RDF dump link check for World War 1 as Linked Open Data took 6.736528396606445s
License | MR license check for World War 1 as Linked Open Data took 0.19221806526184082s
License | HR license check for World War 1 as Linked Open Data took 1.904228925704956s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.18666481971740723s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.3654813766479492s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.3723762035369873s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.23906445503234863s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.1791229248046875s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.19533538818359375s
Performance | Throughput check for World War 1 as Linked Open Data took 10.951303005218506s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.07235336303710938s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.19461321830749512s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.2378990650177002s
Interlinking | skos check for World War 1 as Linked Open Data took 0.18934202194213867s
Interlinking | skos check for World War 1 as Linked Open Data took 0.15740394592285156s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.1938767433166504s
Currency | Creation date check for World War 1 as Linked Open Data took 0.37322449684143066s
Currency | Modification date check for World War 1 as Linked Open Data took 0.1887221336364746s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 2.015902519226074s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 5.870140314102173s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.25661325454711914s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.19598984718322754s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.1618211269378662s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.2081053256988525s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.050755977630615234s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.31969785690307617s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.18981003761291504s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.5988147258758545s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 1.9643466472625732s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.2641706466674805s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.5103917121887207s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.18966913223266602s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 1.0133028030395508s
Security | Sign check for World War 1 as Linked Open Data took 0.16710138320922852s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1516.1279923915863s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.7494025230407715s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.02151012420654297s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 6.4849853515625e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 9.584426879882812e-05s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 5.1563427448272705s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 1.430511474609375e-05s
INFO | --- Analysis for ww1lod took 1597.2378089427948s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.356489896774292s
Availability | VoID file availability check for xLiD-Lexica took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.2760803699493408s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.02190566062927246s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 7.033348083496094e-05s
Believability | Calculation of trust value for xLiD-Lexica took 1.0251998901367188e-05s
INFO | --- Analysis for xlid-lexica took 4.475670576095581s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 9.012222290039062e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.29126548767089844s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.021515369415283203s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.933906555175781e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 1.0013580322265625e-05s
INFO | --- Analysis for xwn took 2.898446559906006s
Availability | SPARQL endpoint availability check for xxx took 8.392333984375e-05s
Availability | VoID file availability check for xxx took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for xxx took 0.29535603523254395s
Reputation | Calculation of the PageRank for xxx took 0.021270036697387695s
Interlinking | Calculation of Degree of Connection for xxx took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for xxx took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for xxx took 3.0279159545898438e-05s
Believability | Calculation of trust value for xxx took 1.0013580322265625e-05s
INFO | --- Analysis for xx took 2.6636950969696045s
Availability | SPARQL endpoint availability check for YAGO took 4.601478576660156e-05s
Availability | VoID file availability check for YAGO took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for YAGO took 0.28231191635131836s
Reputation | Calculation of the PageRank for YAGO took 0.020807266235351562s
Interlinking | Calculation of Degree of Connection for YAGO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.00012946128845214844s
Believability | Calculation of trust value for YAGO took 9.775161743164062e-06s
INFO | --- Analysis for yago took 4.430954217910767s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 2.5910627841949463s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.2907674312591553s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.02151346206665039s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 7.05718994140625e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 7.915496826171875e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 1.2159347534179688e-05s
INFO | --- Analysis for yahoo_geoplanet took 60.90475034713745s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.1659390926361084s
Availability | VoID file availability check for Yale Senselab took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.2791330814361572s
Reputation | Calculation of the PageRank for Yale Senselab took 0.020783424377441406s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 3.0994415283203125e-05s
Believability | Calculation of trust value for Yale Senselab took 1.2159347534179688e-05s
INFO | --- Analysis for yale_senselab took 11.238993406295776s
Availability | SPARQL endpoint availability check for test-dapp-2 took 8.845329284667969e-05s
Availability | VoID file availability check for test-dapp-2 took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.29970836639404297s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.021155834197998047s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 3.24249267578125e-05s
Believability | Calculation of trust value for test-dapp-2 took 1.0728836059570312e-05s
INFO | --- Analysis for yordhis took 2.6554644107818604s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 0.9085836410522461s
Availability | VoID file availability check for Yovisto - academic video search took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.26485657691955566s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.02081131935119629s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.723403930664062e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 9.298324584960938e-06s
INFO | --- Analysis for yovisto took 23.485509395599365s
Availability | SPARQL endpoint availability check for YSA - General Finnish Thesaurus took 7.295608520507812e-05s
Availability | VoID file availability check for YSA - General Finnish Thesaurus took 0.0007822513580322266s
Completeness | Calculation of interlinking completeness for YSA - General Finnish Thesaurus took 0.2939767837524414s
Reputation | Calculation of the PageRank for YSA - General Finnish Thesaurus took 0.02227044105529785s
Interlinking | Calculation of Degree of Connection for YSA - General Finnish Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for YSA - General Finnish Thesaurus took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for YSA - General Finnish Thesaurus took 3.24249267578125e-05s
Believability | Calculation of trust value for YSA - General Finnish Thesaurus took 1.0251998901367188e-05s
INFO | --- Analysis for ysa took 4.991004705429077s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.31575942039489746s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.316734313964844e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 5.7220458984375e-06s
INFO | --- Analysis for yso took 5.4278037548065186s
Availability | SPARQL endpoint availability check for yso-fi-allars took 4.1484832763671875e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.3496997356414795s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.022783756256103516s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.504753112792969e-05s
Believability | Calculation of trust value for yso-fi-allars took 1.1444091796875e-05s
INFO | --- Analysis for yso-fi-allars took 3.6345858573913574s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 8.702278137207031e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.27815771102905273s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.022304773330688477s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.719329833984375e-05s
Believability | Calculation of trust value for yso-fi-ysa took 1.1682510375976562e-05s
INFO | --- Analysis for yso-fi-ysa took 3.6112091541290283s
Availability | SPARQL endpoint availability check for YSO places took 0.7691202163696289s
Availability | VoID file availability check for YSO places took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for YSO places took 0.29225707054138184s
Reputation | Calculation of the PageRank for YSO places took 0.020986557006835938s
Interlinking | Calculation of Degree of Connection for YSO places took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for YSO places took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for YSO places took 3.1948089599609375e-05s
Believability | Calculation of trust value for YSO places took 1.1682510375976562e-05s
INFO | --- Analysis for yso-paikat took 4.517123460769653s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 8.249282836914062e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.33892273902893066s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.022244691848754883s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.457069396972656e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 9.059906005859375e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 6.135014772415161s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 8.678436279296875e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.32621169090270996s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.02113652229309082s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.361701965332031e-05s
Believability | Calculation of trust value for zaragoza_turruta took 5.936622619628906e-05s
INFO | --- Analysis for zaragoza_turruta took 2.8422329425811768s
Availability | SPARQL endpoint availability check for ZBW Labs took 8.630752563476562e-05s
Availability | VoID file availability check for ZBW Labs took 0.0006649494171142578s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.32611823081970215s
Reputation | Calculation of the PageRank for ZBW Labs took 0.022777318954467773s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 6.890296936035156e-05s
Believability | Calculation of trust value for ZBW Labs took 1.1920928955078125e-05s
INFO | --- Analysis for zbw-labs took 3.66426157951355s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.17149758338928223s
Availability | VoID file availability check for 20th Century Press Archives took 0.0006134510040283203s
Extra | Recovery of all triples for 20th Century Press Archives took 25.962992191314697s
Performance | Total latancy measurement for 20th Century Press Archives took 0.7587902545928955s
Amount of data | Number of triples check for 20th Century Press Archives took 2.2224647998809814s
Interoperability | New terms check for 20th Century Press Archives took 1.8121087551116943s
Versatility | Languages check for 20th Century Press Archives took 7.165931701660156s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.897169828414917s
Interpretability | RDF structures check for 20th Century Press Archives took 0.13276886940002441s
Versatility | Serialization formats check for 20th Century Press Archives took 0.13035964965820312s
Availability | RDF dump link check for 20th Century Press Archives took 0.14255309104919434s
License | MR license check for 20th Century Press Archives took 0.14461302757263184s
License | HR license check for 20th Century Press Archives took 5.598419189453125s
Amount of data | Number of property check for 20th Century Press Archives took 0.18515920639038086s
Understandability | Number of label check for 20th Century Press Archives took 0.6441709995269775s
Understandability | URI regex check for 20th Century Press Archives took 0.3493845462799072s
Understandability | Vocabs check for 20th Century Press Archives took 0.1841585636138916s
Verifiability | Authors check for 20th Century Press Archives took 0.1302938461303711s
Verifiability | Publishers check for 20th Century Press Archives took 0.12943172454833984s
Performance | Throughput check for 20th Century Press Archives took 10.931627988815308s
Amount of data | Check the number of entities for 20th Century Press Archives took 6.818771362304688e-05s
Verifiability | Contribs. check for 20th Century Press Archives took 0.1632699966430664s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.14948654174804688s
Interlinking | skos check for 20th Century Press Archives took 0.17693305015563965s
Interlinking | skos check for 20th Century Press Archives took 0.19394350051879883s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.15212082862854004s
Currency | Creation date check for 20th Century Press Archives took 0.3471262454986572s
Currency | Modification date check for 20th Century Press Archives took 0.31035757064819336s
Rep.Conc. | URIs length for 20th Century Press Archives took 14.99324917793274s
Interoperability | New vocabularies check for 20th Century Press Archives took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.1500411033630371s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.14332079887390137s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.13768649101257324s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 4.7917563915252686s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.887927770614624s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.072697401046753s
Consistency | Disjoint class check for 20th Century Press Archives took 0.1705317497253418s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.366464376449585s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.4813311100006104s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 6.871587514877319s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.4829745292663574s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.738521099090576s
Security | Sign check for 20th Century Press Archives took 0.16193127632141113s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 1028.8814952373505s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.4175591468811035s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.021368741989135742s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 6.318092346191406e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.0001163482666015625s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 1.430511474609375e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 6.4373016357421875e-06s
INFO | --- Analysis for zbw-pressemappe20 took 1152.8619456291199s
Availability | SPARQL endpoint availability check for zhishi.lemon took 4.267692565917969e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.27428531646728516s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.020935535430908203s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 4.7206878662109375e-05s
Believability | Calculation of trust value for zhishi.lemon took 8.106231689453125e-06s
INFO | --- Analysis for zhishi-lemon took 25.523434162139893s
Availability | SPARQL endpoint availability check for Zhishi.me took 10.65339708328247s
Availability | VoID file availability check for Zhishi.me took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.29837632179260254s
Reputation | Calculation of the PageRank for Zhishi.me took 0.020706653594970703s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 6.651878356933594e-05s
Believability | Calculation of trust value for Zhishi.me took 1.1205673217773438e-05s
INFO | --- Analysis for zhishi-me took 15.909299373626709s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 0.00010156631469726562s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.324782133102417s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 5.888938903808594e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 1.1444091796875e-05s
INFO | --- Analysis for zitgist-musicbrainz took 3.2162716388702393s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 8.726119995117188e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.27701830863952637s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.021042823791503906s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 3.075599670410156e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 1.049041748046875e-05s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 3.009641408920288s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.3019561767578125s
Availability | VoID file availability check for performing-arts.ch took 0.0005195140838623047s
Extra | Recovery of all triples for performing-arts.ch took 15.366584300994873s
Performance | Total latancy measurement for performing-arts.ch took 0.759894609451294s
Amount of data | Number of triples check for performing-arts.ch took 32.83392405509949s
Interoperability | New terms check for performing-arts.ch took 1.5263376235961914s
Versatility | Languages check for performing-arts.ch took 60.16248536109924s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.151938676834106s
Interpretability | RDF structures check for performing-arts.ch took 0.16198062896728516s
Versatility | Serialization formats check for performing-arts.ch took 0.16126394271850586s
Availability | RDF dump link check for performing-arts.ch took 0.1662461757659912s
License | MR license check for performing-arts.ch took 0.1352536678314209s
License | HR license check for performing-arts.ch took 57.61522197723389s
Amount of data | Number of property check for performing-arts.ch took 0.19661283493041992s
Understandability | Number of label check for performing-arts.ch took 3.345118999481201s
Understandability | URI regex check for performing-arts.ch took 0.3183133602142334s
Understandability | Vocabs check for performing-arts.ch took 0.14595603942871094s
Verifiability | Authors check for performing-arts.ch took 0.15060949325561523s
Verifiability | Publishers check for performing-arts.ch took 0.16069722175598145s
Performance | Throughput check for performing-arts.ch took 10.939341306686401s
Amount of data | Check the number of entities for performing-arts.ch took 7.62939453125e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.17604637145996094s
Interlinking | sameAs chians check for performing-arts.ch took 0.5519108772277832s
Interlinking | skos check for performing-arts.ch took 0.18759655952453613s
Interlinking | skos check for performing-arts.ch took 0.1676936149597168s
Timeliness | dataset update frequency check for performing-arts.ch took 0.1817333698272705s
Currency | Creation date check for performing-arts.ch took 0.3235170841217041s
Currency | Modification date check for performing-arts.ch took 0.37418413162231445s
Rep.Conc. | URIs length for performing-arts.ch took 22.34297227859497s
Interoperability | New vocabularies check for performing-arts.ch took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.15500092506408691s
Accuracy | Check Functional Property for performing-arts.ch took 0.13827896118164062s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.1391298770904541s
Accuracy | Check Empty annotation labels for performing-arts.ch took 10.963584184646606s
Accuracy | Check White space in annotation for performing-arts.ch took 2.507575511932373s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.7765727043151855s
Consistency | Disjoint class check for performing-arts.ch took 0.14418649673461914s
Consistency | Check Misplaced properties for performing-arts.ch took 0.3469250202178955s
Consistency | Misplaced classes for performing-arts.ch took 8.373299360275269s
Consistency | Check Ontology hijacking for performing-arts.ch took 48.0104124546051s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 15320.531836032867s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.7864840030670166s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.85713791847229s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.39471888542175293s
Security | Sign check for performing-arts.ch took 0.14529204368591309s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.3802053928375244s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.8959641456604004s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.02132105827331543s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0006847381591796875s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.6450881958007812e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 1.9073486328125e-06s
Believability | Calculation of trust value for performing-arts.ch took 1.0728836059570312e-05s
INFO | --- Analysis for performing-arts.ch took 16008.58960556984s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.89286208152771s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.29854917526245117s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.02147698402404785s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.52587890625e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.8358230590820312e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 1.0967254638671875e-05s
INFO | --- Analysis for The-AA-Thesaurus took 8.637286186218262s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.6902098655700684s
Availability | VoID file availability check for MiMoTextBase took 0.00039887428283691406s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.27206921577453613s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.02099776268005371s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.239776611328125e-05s
Believability | Calculation of trust value for MiMoTextBase took 1.1205673217773438e-05s
INFO | --- Analysis for MiMoTextBase took 6.656019449234009s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.48572874069213867s
Availability | VoID file availability check for National Library of Sweden took 0.0005536079406738281s
Extra | Recovery of all triples for National Library of Sweden took 5.556021451950073s
Performance | Total latancy measurement for National Library of Sweden took 1.008803367614746s
Amount of data | Number of triples check for National Library of Sweden took 25.94325351715088s
Interoperability | New terms check for National Library of Sweden took 15.090639114379883s
Versatility | Languages check for National Library of Sweden took 0.21495318412780762s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.1520984172821s
Interpretability | RDF structures check for National Library of Sweden took 0.26580286026000977s
Versatility | Serialization formats check for National Library of Sweden took 0.22636747360229492s
Availability | RDF dump link check for National Library of Sweden took 0.20603537559509277s
License | MR license check for National Library of Sweden took 0.2086639404296875s
License | HR license check for National Library of Sweden took 0.2213151454925537s
Amount of data | Number of property check for National Library of Sweden took 0.21060729026794434s
Understandability | Number of label check for National Library of Sweden took 0.23009324073791504s
Understandability | URI regex check for National Library of Sweden took 0.38791990280151367s
Understandability | Vocabs check for National Library of Sweden took 0.21940851211547852s
Verifiability | Authors check for National Library of Sweden took 0.21119308471679688s
Verifiability | Publishers check for National Library of Sweden took 0.21827435493469238s
Performance | Throughput check for National Library of Sweden took 10.487423181533813s
Amount of data | Check the number of entities for National Library of Sweden took 7.104873657226562e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.20661616325378418s
Interlinking | sameAs chians check for National Library of Sweden took 0.2101452350616455s
Interlinking | skos check for National Library of Sweden took 0.21027851104736328s
Interlinking | skos check for National Library of Sweden took 0.2055661678314209s
Timeliness | dataset update frequency check for National Library of Sweden took 0.2065262794494629s
Currency | Creation date check for National Library of Sweden took 0.437777042388916s
Currency | Modification date check for National Library of Sweden took 0.42415904998779297s
Rep.Conc. | URIs length for National Library of Sweden took 81.47344636917114s
Interoperability | New vocabularies check for National Library of Sweden took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.21845459938049316s
Accuracy | Check Functional Property for National Library of Sweden took 0.21595263481140137s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.20589208602905273s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.2731821537017822s
Consistency | Disjoint class check for National Library of Sweden took 0.19225406646728516s
Consistency | Check Misplaced properties for National Library of Sweden took 60.553565979003906s
Consistency | Misplaced classes for National Library of Sweden took 1.1180975437164307s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.228604555130005s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.2651574611663818s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 61.63893175125122s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.281339168548584s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.3705480098724365s
Security | Sign check for National Library of Sweden took 0.20566534996032715s
Availability | Check URIs Dereferenciability for National Library of Sweden took 10.35034990310669s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.42420220375061035s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.020919084548950195s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.9311904907226562e-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 1.1682510375976562e-05s
INFO | --- Analysis for NLS took 1368.364987373352s
Availability | SPARQL endpoint availability check for Japan Search took 1.7136731147766113s
Availability | VoID file availability check for Japan Search took 0.0006406307220458984s
Extra | Recovery of all triples for Japan Search took 3.944812774658203s
Performance | Total latancy measurement for Japan Search took 2.592661142349243s
Amount of data | Number of triples check for Japan Search took 9.06135869026184s
Interoperability | New terms check for Japan Search took 4.158748388290405s
Versatility | Languages check for Japan Search took 0.2591226100921631s
Interpretability | Number of blank nodes check for Japan Search took 11.932005882263184s
Interpretability | RDF structures check for Japan Search took 0.8550879955291748s
Versatility | Serialization formats check for Japan Search took 0.8442234992980957s
Availability | RDF dump link check for Japan Search took 0.3100619316101074s
License | MR license check for Japan Search took 1.231297254562378s
License | HR license check for Japan Search took 12.06981372833252s
Amount of data | Number of property check for Japan Search took 0.3043994903564453s
Understandability | Number of label check for Japan Search took 14.155075550079346s
Understandability | URI regex check for Japan Search took 1.0079240798950195s
Understandability | Vocabs check for Japan Search took 0.2865176200866699s
Verifiability | Authors check for Japan Search took 0.8098948001861572s
Verifiability | Publishers check for Japan Search took 0.29756808280944824s
Performance | Throughput check for Japan Search took 11.16264533996582s
Amount of data | Check the number of entities for Japan Search took 6.961822509765625e-05s
Verifiability | Contribs. check for Japan Search took 0.3125722408294678s
Interlinking | sameAs chians check for Japan Search took 0.2756514549255371s
Interlinking | skos check for Japan Search took 0.44833922386169434s
Interlinking | skos check for Japan Search took 0.2832925319671631s
Timeliness | dataset update frequency check for Japan Search took 0.33429884910583496s
Currency | Creation date check for Japan Search took 0.6753346920013428s
Currency | Modification date check for Japan Search took 0.604069709777832s
Rep.Conc. | URIs length for Japan Search took 15.946717262268066s
Interoperability | New vocabularies check for Japan Search took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.07406044006347656s
Accuracy | Check Datatype consistency for Japan Search took 0.03274822235107422s
Consistency | Disjoint class check for Japan Search took 0.030713558197021484s
Consistency | Check Ontology hijacking for Japan Search took 0.07464909553527832s
Consistency | Check Invalid usage of undefined properties for Japan Search took 1.344552755355835s
Conciseness | Check Extensional conciseness for Japan Search took 0.037041664123535156s
Security | Sign check for Japan Search took 0.07275032997131348s
Availability | Check URIs Dereferenciability for Japan Search took 8.97058892250061s
Completeness | Calculation of interlinking completeness for Japan Search took 0.35321855545043945s
Reputation | Calculation of the PageRank for Japan Search took 0.021184921264648438s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Japan Search took 1.2159347534179688e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 1.1920928955078125e-06s
Believability | Calculation of trust value for Japan Search took 6.67572021484375e-06s
INFO | --- Analysis for Japan-Search took 347.5046489238739s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.1796271800994873s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.37578248977661133s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.023267507553100586s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.2874603271484375e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.239776611328125e-05s
INFO | --- Analysis for Rijksmuseum took 5.223579406738281s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 1.088968276977539s
Availability | VoID file availability check for Finnish Public Libraries took 0.0007431507110595703s
Extra | Recovery of all triples for Finnish Public Libraries took 13.324008464813232s
Performance | Total latancy measurement for Finnish Public Libraries took 1.4598169326782227s
Amount of data | Number of triples check for Finnish Public Libraries took 51.33456015586853s
Interoperability | New terms check for Finnish Public Libraries took 12.91494107246399s
Versatility | Languages check for Finnish Public Libraries took 60.11681532859802s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 52.71952700614929s
Interpretability | RDF structures check for Finnish Public Libraries took 0.3271939754486084s
Versatility | Serialization formats check for Finnish Public Libraries took 0.16633319854736328s
Availability | RDF dump link check for Finnish Public Libraries took 0.12325882911682129s
License | MR license check for Finnish Public Libraries took 0.299741268157959s
License | HR license check for Finnish Public Libraries took 35.602280139923096s
Amount of data | Number of property check for Finnish Public Libraries took 0.30472302436828613s
Understandability | Number of label check for Finnish Public Libraries took 11.661355257034302s
Understandability | URI regex check for Finnish Public Libraries took 0.5534827709197998s
Understandability | Vocabs check for Finnish Public Libraries took 0.27686166763305664s
Verifiability | Authors check for Finnish Public Libraries took 0.3423442840576172s
Verifiability | Publishers check for Finnish Public Libraries took 0.29705047607421875s
Performance | Throughput check for Finnish Public Libraries took 10.879716873168945s
Amount of data | Check the number of entities for Finnish Public Libraries took 6.818771362304688e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.13375282287597656s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.431934118270874s
Interlinking | skos check for Finnish Public Libraries took 0.14152264595031738s
Interlinking | skos check for Finnish Public Libraries took 0.1259610652923584s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.27366209030151367s
Currency | Creation date check for Finnish Public Libraries took 0.3756992816925049s
Currency | Modification date check for Finnish Public Libraries took 0.3943009376525879s
Rep.Conc. | URIs length for Finnish Public Libraries took 80.95348715782166s
Interoperability | New vocabularies check for Finnish Public Libraries took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.4940652847290039s
Accuracy | Check Functional Property for Finnish Public Libraries took 0.29546070098876953s
Accuracy | Check Inverse Functional Property for Finnish Public Libraries took 0.33448243141174316s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 7.803175926208496s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.184805154800415s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.397917032241821s
Consistency | Disjoint class check for Finnish Public Libraries took 0.27059340476989746s
Consistency | Check Misplaced properties for Finnish Public Libraries took 52.49029517173767s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 14.644731521606445s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.5685880184173584s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 54.75214672088623s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.7336134910583496s
Security | Sign check for Finnish Public Libraries took 0.2796285152435303s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 0.9178433418273926s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.4379916191101074s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.021032333374023438s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 2.2172927856445312e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 1.6689300537109375e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 7.152557373046875e-06s
INFO | --- Analysis for FI-Library took 665.7644119262695s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 2.6416547298431396s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0005340576171875s
Extra | Recovery of all triples for Shanghai Library Open Data Platform took 8.975455522537231s
Performance | Total latancy measurement for Shanghai Library Open Data Platform took 3.586176872253418s
Amount of data | Number of triples check for Shanghai Library Open Data Platform took 1.119349718093872s
Interoperability | New terms check for Shanghai Library Open Data Platform took 4.920575380325317s
Versatility | Languages check for Shanghai Library Open Data Platform took 60.723873138427734s
Interpretability | Number of blank nodes check for Shanghai Library Open Data Platform took 16.51509380340576s
Interpretability | RDF structures check for Shanghai Library Open Data Platform took 1.1210296154022217s
Versatility | Serialization formats check for Shanghai Library Open Data Platform took 0.8570940494537354s
Availability | RDF dump link check for Shanghai Library Open Data Platform took 0.7754316329956055s
License | MR license check for Shanghai Library Open Data Platform took 1.0884418487548828s
License | HR license check for Shanghai Library Open Data Platform took 35.615856647491455s
Amount of data | Number of property check for Shanghai Library Open Data Platform took 0.7590136528015137s
Understandability | Number of label check for Shanghai Library Open Data Platform took 1.4244520664215088s
Understandability | URI regex check for Shanghai Library Open Data Platform took 1.5823285579681396s
Understandability | Vocabs check for Shanghai Library Open Data Platform took 0.7769126892089844s
Verifiability | Authors check for Shanghai Library Open Data Platform took 0.8410110473632812s
Verifiability | Publishers check for Shanghai Library Open Data Platform took 0.7900137901306152s
Performance | Throughput check for Shanghai Library Open Data Platform took 14.291523218154907s
Amount of data | Check the number of entities for Shanghai Library Open Data Platform took 7.176399230957031e-05s
Verifiability | Contribs. check for Shanghai Library Open Data Platform took 0.7566335201263428s
Interlinking | sameAs chians check for Shanghai Library Open Data Platform took 0.7504208087921143s
Interlinking | skos check for Shanghai Library Open Data Platform took 1.0641472339630127s
Interlinking | skos check for Shanghai Library Open Data Platform took 0.7051882743835449s
Timeliness | dataset update frequency check for Shanghai Library Open Data Platform took 0.8453991413116455s
Currency | Creation date check for Shanghai Library Open Data Platform took 1.5584001541137695s
Currency | Modification date check for Shanghai Library Open Data Platform took 1.565267562866211s
Rep.Conc. | URIs length for Shanghai Library Open Data Platform took 11.796761512756348s
Interoperability | New vocabularies check for Shanghai Library Open Data Platform took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for Shanghai Library Open Data Platform took 0.7236518859863281s
Accuracy | Check Functional Property for Shanghai Library Open Data Platform took 0.7414512634277344s
Accuracy | Check Inverse Functional Property for Shanghai Library Open Data Platform took 0.7349073886871338s
Accuracy | Check Empty annotation labels for Shanghai Library Open Data Platform took 3.2526187896728516s
Accuracy | Check White space in annotation for Shanghai Library Open Data Platform took 0.15346050262451172s
Accuracy | Check Datatype consistency for Shanghai Library Open Data Platform took 0.135817289352417s
Consistency | Disjoint class check for Shanghai Library Open Data Platform took 0.8798627853393555s
Consistency | Check Misplaced properties for Shanghai Library Open Data Platform took 6.354933023452759s
Consistency | Misplaced classes for Shanghai Library Open Data Platform took 1.3351852893829346s
Consistency | Check Ontology hijacking for Shanghai Library Open Data Platform took 4.683985948562622s
Consistency | Check Invalid usage of undefined classes for Shanghai Library Open Data Platform took 1.532336950302124s
Consistency | Check Invalid usage of undefined properties for Shanghai Library Open Data Platform took 7.121361494064331s
Conciseness | Check Extensional conciseness for Shanghai Library Open Data Platform took 0.15464186668395996s
Conciseness | Check Intensional conciseness for Shanghai Library Open Data Platform took 1.1548030376434326s
Security | Sign check for Shanghai Library Open Data Platform took 0.9633364677429199s
Availability | Check URIs Dereferenciability for Shanghai Library Open Data Platform took 9.525509595870972s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.399503231048584s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.021301984786987305s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 2.0265579223632812e-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.0251998901367188e-05s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 337.6295883655548s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.476963996887207s
Availability | VoID file availability check for National Library Netherlands took 0.00046443939208984375s
Extra | Recovery of all triples for National Library Netherlands took 0.6465721130371094s
Performance | Total latancy measurement for National Library Netherlands took 0.8910801410675049s
Amount of data | Number of triples check for National Library Netherlands took 0.15024542808532715s
Interoperability | New terms check for National Library Netherlands took 1.436006784439087s
Versatility | Languages check for National Library Netherlands took 58.14752984046936s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.16036772727966309s
Interpretability | RDF structures check for National Library Netherlands took 0.16218996047973633s
Versatility | Serialization formats check for National Library Netherlands took 0.1733694076538086s
Availability | RDF dump link check for National Library Netherlands took 0.16176891326904297s
License | MR license check for National Library Netherlands took 0.21381163597106934s
License | HR license check for National Library Netherlands took 0.19736504554748535s
Amount of data | Number of property check for National Library Netherlands took 0.15788578987121582s
Understandability | Number of label check for National Library Netherlands took 0.1648883819580078s
Understandability | URI regex check for National Library Netherlands took 0.3438382148742676s
Understandability | Vocabs check for National Library Netherlands took 0.1538841724395752s
Verifiability | Authors check for National Library Netherlands took 0.1647021770477295s
Verifiability | Publishers check for National Library Netherlands took 0.16080713272094727s
Performance | Throughput check for National Library Netherlands took 11.101563930511475s
Amount of data | Check the number of entities for National Library Netherlands took 0.00014066696166992188s
Verifiability | Contribs. check for National Library Netherlands took 0.16111421585083008s
Interlinking | sameAs chians check for National Library Netherlands took 0.1640763282775879s
Interlinking | skos check for National Library Netherlands took 0.1596980094909668s
Interlinking | skos check for National Library Netherlands took 0.1706373691558838s
Timeliness | dataset update frequency check for National Library Netherlands took 0.16076278686523438s
Currency | Creation date check for National Library Netherlands took 0.3619232177734375s
Currency | Modification date check for National Library Netherlands took 0.31188035011291504s
Rep.Conc. | URIs length for National Library Netherlands took 0.706514835357666s
Interoperability | New vocabularies check for National Library Netherlands took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.17371535301208496s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.44243288040161133s
Accuracy | Check White space in annotation for National Library Netherlands took 0.027095794677734375s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.027049779891967773s
Consistency | Disjoint class check for National Library Netherlands took 0.15297794342041016s
Consistency | Check Misplaced properties for National Library Netherlands took 0.33634400367736816s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.6614680290222168s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 1.3213684558868408s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.4874696731567383s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.028519630432128906s
Security | Sign check for National Library Netherlands took 0.18834424018859863s
Availability | Check URIs Dereferenciability for National Library Netherlands took 6.447571754455566s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.28899407386779785s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.022047996520996094s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007243156433105469s
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.9073486328125e-06s
Believability | Calculation of trust value for National Library Netherlands took 1.0728836059570312e-05s
INFO | --- Analysis for National-Library-Netherlands took 170.93534803390503s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 31.522454977035522s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.3062756061553955s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.021412134170532227s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.8835067749023438e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.049041748046875e-05s
INFO | --- Analysis for Antique-Renaissance took 49.250120401382446s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 6.842783451080322s
Availability | VoID file availability check for ARTSDATA.CA took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.32945799827575684s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.020787477493286133s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.3113021850585938e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 1.049041748046875e-05s
INFO | --- Analysis for ARTSDATA-CA took 12.379211902618408s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.21103310585021973s
Availability | VoID file availability check for Architecture of Knowledge took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.2782447338104248s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.020979642868041992s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.2636184692382812e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 1.0728836059570312e-05s
INFO | --- Analysis for ArCo took 3.899573802947998s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.3608865737915039s
Availability | VoID file availability check for ConfermentSampo took 0.0004911422729492188s
Extra | Recovery of all triples for ConfermentSampo took 65.61071395874023s
Performance | Total latancy measurement for ConfermentSampo took 0.8138313293457031s
Amount of data | Number of triples check for ConfermentSampo took 10.602972507476807s
Interoperability | New terms check for ConfermentSampo took 2.5300097465515137s
Versatility | Languages check for ConfermentSampo took 31.358622789382935s
Interpretability | Number of blank nodes check for ConfermentSampo took 8.76195764541626s
Security | Check HTTPS for ConfermentSampo took 0.4081554412841797s
Interpretability | RDF structures check for ConfermentSampo took 0.21136808395385742s
Versatility | Serialization formats check for ConfermentSampo took 0.20766520500183105s
Availability | RDF dump link check for ConfermentSampo took 3.069636106491089s
License | MR license check for ConfermentSampo took 0.18916773796081543s
License | HR license check for ConfermentSampo took 0.21997928619384766s
Amount of data | Number of property check for ConfermentSampo took 0.18973684310913086s
Understandability | Number of label check for ConfermentSampo took 5.673710107803345s
Understandability | URI regex check for ConfermentSampo took 0.36362767219543457s
Understandability | Vocabs check for ConfermentSampo took 0.1679365634918213s
Verifiability | Authors check for ConfermentSampo took 0.1955888271331787s
Verifiability | Publishers check for ConfermentSampo took 0.2011857032775879s
Performance | Throughput check for ConfermentSampo took 11.100918292999268s
Amount of data | Check the number of entities for ConfermentSampo took 3.88834810256958s
Verifiability | Contribs. check for ConfermentSampo took 0.17508459091186523s
Interlinking | sameAs chians check for ConfermentSampo took 0.4714515209197998s
Interlinking | skos check for ConfermentSampo took 0.1787712574005127s
Interlinking | skos check for ConfermentSampo took 0.1488790512084961s
Timeliness | dataset update frequency check for ConfermentSampo took 0.17295217514038086s
Currency | Creation date check for ConfermentSampo took 0.35313892364501953s
Currency | Modification date check for ConfermentSampo took 0.3570747375488281s
Rep.Conc. | URIs length for ConfermentSampo took 34.8239312171936s
Interoperability | New vocabularies check for ConfermentSampo took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.1866133213043213s
Accuracy | Check Functional Property for ConfermentSampo took 0.1923656463623047s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.15737032890319824s
Accuracy | Check Empty annotation labels for ConfermentSampo took 14.870718717575073s
Accuracy | Check White space in annotation for ConfermentSampo took 2.9879095554351807s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.112567186355591s
Consistency | Disjoint class check for ConfermentSampo took 0.17086434364318848s
Consistency | Check Misplaced properties for ConfermentSampo took 6.563855409622192s
Consistency | Check Ontology hijacking for ConfermentSampo took 15.306426048278809s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.4009935855865479s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.5187222957611084s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.7998247146606445s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.1912703514099121s
Security | Sign check for ConfermentSampo took 0.16825318336486816s
Availability | Check URIs Dereferenciability for ConfermentSampo took 2.404756784439087s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.4918687343597412s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.02104663848876953s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0006732940673828125s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 2.002716064453125e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 2.1457672119140625e-06s
Believability | Calculation of trust value for ConfermentSampo took 1.2159347534179688e-05s
INFO | --- Analysis for ConfermentSampo took 372.31902623176575s
Availability | SPARQL endpoint availability check for Museum Finland took 0.27936553955078125s
Availability | VoID file availability check for Museum Finland took 0.00031280517578125s
Extra | Recovery of all triples for Museum Finland took 7.40497612953186s
Performance | Total latancy measurement for Museum Finland took 0.8062839508056641s
Amount of data | Number of triples check for Museum Finland took 0.3465261459350586s
Interoperability | New terms check for Museum Finland took 1.6902360916137695s
Versatility | Languages check for Museum Finland took 0.7022769451141357s
Interpretability | Number of blank nodes check for Museum Finland took 0.3126084804534912s
Security | Check HTTPS for Museum Finland took 0.24197697639465332s
Interpretability | RDF structures check for Museum Finland took 0.31179189682006836s
Versatility | Serialization formats check for Museum Finland took 0.19592595100402832s
Availability | RDF dump link check for Museum Finland took 0.16833090782165527s
License | MR license check for Museum Finland took 0.19576144218444824s
License | HR license check for Museum Finland took 0.37579345703125s
Amount of data | Number of property check for Museum Finland took 0.19445490837097168s
Understandability | Number of label check for Museum Finland took 0.30983448028564453s
Understandability | URI regex check for Museum Finland took 0.3124349117279053s
Understandability | Vocabs check for Museum Finland took 0.15945863723754883s
Verifiability | Authors check for Museum Finland took 0.16208291053771973s
Verifiability | Publishers check for Museum Finland took 0.15901947021484375s
Performance | Throughput check for Museum Finland took 11.025955438613892s
Amount of data | Check the number of entities for Museum Finland took 6.866455078125e-05s
Verifiability | Contribs. check for Museum Finland took 0.1679677963256836s
Interlinking | sameAs chians check for Museum Finland took 0.21844124794006348s
Interlinking | skos check for Museum Finland took 0.15925192832946777s
Interlinking | skos check for Museum Finland took 0.1485610008239746s
Timeliness | dataset update frequency check for Museum Finland took 0.15955066680908203s
Currency | Creation date check for Museum Finland took 0.3890721797943115s
Currency | Modification date check for Museum Finland took 0.35663414001464844s
Rep.Conc. | URIs length for Museum Finland took 3.705071449279785s
Interoperability | New vocabularies check for Museum Finland took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.18770527839660645s
Accuracy | Check Functional Property for Museum Finland took 0.1601548194885254s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.15308022499084473s
Accuracy | Check Empty annotation labels for Museum Finland took 1.0282914638519287s
Accuracy | Check White space in annotation for Museum Finland took 0.06158614158630371s
Accuracy | Check Datatype consistency for Museum Finland took 0.9621872901916504s
Consistency | Disjoint class check for Museum Finland took 0.15586066246032715s
Consistency | Check Misplaced properties for Museum Finland took 0.6393797397613525s
Consistency | Check Ontology hijacking for Museum Finland took 2.1960644721984863s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.4690744876861572s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.6544325351715088s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6470112800598145s
Conciseness | Check Intensional conciseness for Museum Finland took 0.6989891529083252s
Security | Sign check for Museum Finland took 0.15940093994140625s
Availability | Check URIs Dereferenciability for Museum Finland took 3237.1872828006744s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.6259200572967529s
Reputation | Calculation of the PageRank for Museum Finland took 0.022756338119506836s
Interlinking | Calculation of Degree of Connection for Museum Finland took 7.414817810058594e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 2.002716064453125e-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 1.2874603271484375e-05s
INFO | --- Analysis for FI-Museum took 3295.6246180534363s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.19866490364074707s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0005903244018554688s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 16.49107003211975s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 1.4023897647857666s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 32.02546763420105s
Interoperability | New terms check for Mapping Manuscript Migrations took 4.93854832649231s
Versatility | Languages check for Mapping Manuscript Migrations took 77.11170673370361s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 29.859318256378174s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.42100000381469727s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.2008066177368164s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.20153403282165527s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.17116665840148926s
License | MR license check for Mapping Manuscript Migrations took 0.20096230506896973s
License | HR license check for Mapping Manuscript Migrations took 1.7925214767456055s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.20070481300354004s
Understandability | Number of label check for Mapping Manuscript Migrations took 8.832910776138306s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.43947744369506836s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.1813499927520752s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.23822593688964844s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.20020532608032227s
Performance | Throughput check for Mapping Manuscript Migrations took 10.658411979675293s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.0198664665222168s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.3888535499572754s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 1.5640645027160645s
Interlinking | skos check for Mapping Manuscript Migrations took 0.254213809967041s
Interlinking | skos check for Mapping Manuscript Migrations took 0.25973963737487793s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 1.424971342086792s
Currency | Creation date check for Mapping Manuscript Migrations took 0.9463627338409424s
Currency | Modification date check for Mapping Manuscript Migrations took 0.21969890594482422s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 65.3616406917572s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.20066499710083008s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.16728591918945312s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.16817641258239746s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 10.888182401657104s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.4066712856292725s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.7027246952056885s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.19846630096435547s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 23.869178295135498s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 16.94605016708374s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.5789625644683838s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.5904521942138672s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.824810266494751s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.20560431480407715s
Security | Sign check for Mapping Manuscript Migrations took 0.18474435806274414s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1703.4757256507874s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.842628002166748s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.022202014923095703s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 7.009506225585938e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.4066696166992188e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 4.291534423828125e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 1.3113021850585938e-05s
INFO | --- Analysis for MMM took 2136.581379175186s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.2655630111694336s
Availability | VoID file availability check for Semantic Kalevala took 0.0004994869232177734s
Extra | Recovery of all triples for Semantic Kalevala took 8.458092451095581s
Performance | Total latancy measurement for Semantic Kalevala took 0.8614015579223633s
Amount of data | Number of triples check for Semantic Kalevala took 0.4287388324737549s
Interoperability | New terms check for Semantic Kalevala took 1.972877025604248s
Versatility | Languages check for Semantic Kalevala took 0.9790945053100586s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.40550994873046875s
Security | Check HTTPS for Semantic Kalevala took 0.41875624656677246s
Interpretability | RDF structures check for Semantic Kalevala took 0.28696703910827637s
Versatility | Serialization formats check for Semantic Kalevala took 0.20000648498535156s
Availability | RDF dump link check for Semantic Kalevala took 0.16917204856872559s
License | MR license check for Semantic Kalevala took 0.23137736320495605s
License | HR license check for Semantic Kalevala took 1.040388822555542s
Amount of data | Number of property check for Semantic Kalevala took 0.19808030128479004s
Understandability | Number of label check for Semantic Kalevala took 0.4157137870788574s
Understandability | URI regex check for Semantic Kalevala took 0.3410024642944336s
Understandability | Vocabs check for Semantic Kalevala took 0.16824007034301758s
Verifiability | Authors check for Semantic Kalevala took 0.16877198219299316s
Verifiability | Publishers check for Semantic Kalevala took 0.16948771476745605s
Performance | Throughput check for Semantic Kalevala took 10.961040496826172s
Amount of data | Check the number of entities for Semantic Kalevala took 6.961822509765625e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.18287134170532227s
Interlinking | sameAs chians check for Semantic Kalevala took 0.19854187965393066s
Interlinking | skos check for Semantic Kalevala took 0.2961745262145996s
Interlinking | skos check for Semantic Kalevala took 0.16487956047058105s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.18068432807922363s
Currency | Creation date check for Semantic Kalevala took 0.3723423480987549s
Currency | Modification date check for Semantic Kalevala took 0.3673274517059326s
Rep.Conc. | URIs length for Semantic Kalevala took 5.287710189819336s
Interoperability | New vocabularies check for Semantic Kalevala took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.2398991584777832s
Accuracy | Check Functional Property for Semantic Kalevala took 0.20157504081726074s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.16730117797851562s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.896179437637329s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.2953948974609375s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.398317575454712s
Consistency | Disjoint class check for Semantic Kalevala took 0.16748523712158203s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.8198354244232178s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.397874355316162s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.4424047470092773s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.6516497135162354s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.8953049182891846s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.23818159103393555s
Security | Sign check for Semantic Kalevala took 0.19085264205932617s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 3381.6585400104523s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.6515824794769287s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.021329402923583984s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.2636184692382812e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 3.0994415283203125e-06s
Believability | Calculation of trust value for Semantic Kalevala took 1.049041748046875e-05s
INFO | --- Analysis for Semantic-Kalevala took 3447.7772088050842s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 1.11698579788208s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0005638599395751953s
Extra | Recovery of all triples for Smithsonian American Art Museum took 288.52381014823914s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.3925347328186035s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.6006455421447754s
Interoperability | New terms check for Smithsonian American Art Museum took 4.307475566864014s
Versatility | Languages check for Smithsonian American Art Museum took 31.845364093780518s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.6007089614868164s
Security | Check HTTPS for Smithsonian American Art Museum took 0.38279247283935547s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.7108731269836426s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.6514849662780762s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.607365608215332s
License | MR license check for Smithsonian American Art Museum took 0.6370246410369873s
License | HR license check for Smithsonian American Art Museum took 20.66261315345764s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.6048591136932373s
Understandability | Number of label check for Smithsonian American Art Museum took 0.6030197143554688s
Understandability | URI regex check for Smithsonian American Art Museum took 1.2431530952453613s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.636023759841919s
Verifiability | Authors check for Smithsonian American Art Museum took 0.6245255470275879s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.6286900043487549s
Performance | Throughput check for Smithsonian American Art Museum took 12.249417304992676s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 7.176399230957031e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.6176176071166992s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.6102473735809326s
Interlinking | skos check for Smithsonian American Art Museum took 0.6022305488586426s
Interlinking | skos check for Smithsonian American Art Museum took 0.6083617210388184s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.6165378093719482s
Currency | Creation date check for Smithsonian American Art Museum took 1.3534519672393799s
Currency | Modification date check for Smithsonian American Art Museum took 1.2902729511260986s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 109.4420473575592s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.6075587272644043s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 20.619075298309326s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.49254655838012695s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.159898996353149s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.6037695407867432s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 5.01120662689209s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 98.4978723526001s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.5609056949615479s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 4.8754682540893555s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.8834781646728516s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.7192115783691406s
Security | Sign check for Smithsonian American Art Museum took 0.6085343360900879s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.564849615097046s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.6870124340057373s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.021440982818603516s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.4781951904296875e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 3.5762786865234375e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 1.3113021850585938e-05s
INFO | --- Analysis for Smithsonian took 726.3467671871185s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.2154693603515625s
Availability | VoID file availability check for Zeri Photo Archive took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.33835721015930176s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.020638227462768555s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.33514404296875e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 1.3113021850585938e-05s
INFO | --- Analysis for Zeri-Photo-Archive took 6.671568870544434s
Availability | SPARQL endpoint availability check for Archives Hub took 20.490190029144287s
Availability | VoID file availability check for Archives Hub took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.34795498847961426s
Reputation | Calculation of the PageRank for Archives Hub took 0.021149873733520508s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.2159347534179688e-05s
Believability | Calculation of trust value for Archives Hub took 1.239776611328125e-05s
INFO | --- Analysis for Archives-Hub took 54.28897547721863s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.5804564952850342s
Availability | VoID file availability check for Yale centre of British Art took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.3478052616119385s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.02279973030090332s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.1444091796875e-05s
Believability | Calculation of trust value for Yale centre of British Art took 1.239776611328125e-05s
INFO | --- Analysis for Yale took 5.264056444168091s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 261.7439739704132s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.39930224418640137s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.0222170352935791s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.8596649169921875e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 1.0967254638671875e-05s
INFO | --- Analysis for ADL took 536.852044582367s
Availability | SPARQL endpoint availability check for MusicKG took 0.7792556285858154s
Availability | VoID file availability check for MusicKG took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for MusicKG took 0.31142377853393555s
Reputation | Calculation of the PageRank for MusicKG took 0.020863056182861328s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.6927719116210938e-05s
Believability | Calculation of trust value for MusicKG took 7.62939453125e-06s
INFO | --- Analysis for MusicKG took 4.6773927211761475s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.9542965888977051s
Availability | VoID file availability check for CIDOC-CRM took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.31363630294799805s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.021099328994750977s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.1682510375976562e-05s
Believability | Calculation of trust value for CIDOC-CRM took 1.1682510375976562e-05s
INFO | --- Analysis for CIDOC-CRM took 4.8124494552612305s
Availability | SPARQL endpoint availability check for Mondis took 0.3584933280944824s
Availability | VoID file availability check for Mondis took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Mondis took 0.34217381477355957s
Reputation | Calculation of the PageRank for Mondis took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for Mondis took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.0967254638671875e-05s
Believability | Calculation of trust value for Mondis took 1.2874603271484375e-05s
INFO | --- Analysis for Mondis took 3.983062267303467s
Availability | SPARQL endpoint availability check for DigitalNZ took 3.5956051349639893s
Availability | VoID file availability check for DigitalNZ took 0.0003712177276611328s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.30113792419433594s
Reputation | Calculation of the PageRank for DigitalNZ took 0.02064800262451172s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.1920928955078125e-05s
Believability | Calculation of trust value for DigitalNZ took 7.62939453125e-06s
INFO | --- Analysis for DigitalNZ took 8.206282138824463s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.17650175094604492s
Availability | VoID file availability check for Fondazione Zeri took 0.0003197193145751953s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.3055133819580078s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.1205673217773438e-05s
Believability | Calculation of trust value for Fondazione Zeri took 7.3909759521484375e-06s
INFO | --- Analysis for Fondazione-Zeri took 3.921811819076538s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.21322226524353027s
Availability | VoID file availability check for Digital Public Library of America took 0.0003714561462402344s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.3100273609161377s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.02078533172607422s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 3.1948089599609375e-05s
Believability | Calculation of trust value for Digital Public Library of America took 7.152557373046875e-06s
INFO | --- Analysis for Library-of-America took 4.684169292449951s
Availability | SPARQL endpoint availability check for Auckland Museum took 1.990856647491455s
Availability | VoID file availability check for Auckland Museum took 0.0003650188446044922s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.3395719528198242s
Reputation | Calculation of the PageRank for Auckland Museum took 0.02101588249206543s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0008752346038818359s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.1920928955078125e-05s
Believability | Calculation of trust value for Auckland Museum took 7.867813110351562e-06s
INFO | --- Analysis for Auckland-Museum took 7.46690559387207s
Availability | SPARQL endpoint availability check for National Library of Spain took 1.9348084926605225s
Availability | VoID file availability check for National Library of Spain took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.335906982421875s
Reputation | Calculation of the PageRank for National Library of Spain took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007030963897705078s
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 6.9141387939453125e-06s
INFO | --- Analysis for BNE took 5.5095508098602295s
Availability | SPARQL endpoint availability check for National Library of Korea took 1.638716697692871s
Availability | VoID file availability check for National Library of Korea took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.3052816390991211s
Reputation | Calculation of the PageRank for National Library of Korea took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.1682510375976562e-05s
Believability | Calculation of trust value for National Library of Korea took 5.9604644775390625e-06s
INFO | --- Analysis for Korea-Library took 5.172295331954956s
Availability | SPARQL endpoint availability check for The State Russian Museum took 1.2879419326782227s
Availability | VoID file availability check for The State Russian Museum took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.3348095417022705s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.1920928955078125e-05s
Believability | Calculation of trust value for The State Russian Museum took 6.4373016357421875e-06s
INFO | --- Analysis for Russian-Museum took 4.808380365371704s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.9579286575317383s
Availability | VoID file availability check for National Library of Scotland took 0.0003364086151123047s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.33242034912109375s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.1920928955078125e-05s
Believability | Calculation of trust value for National Library of Scotland took 7.152557373046875e-06s
INFO | --- Analysis for National-Library-of-Scotland took 8.212291717529297s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.355771541595459s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.33646392822265625s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.1920928955078125e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 5.245208740234375e-06s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 4.089025974273682s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.2098066806793213s
Availability | VoID file availability check for OntoComedySources took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.3135838508605957s
Reputation | Calculation of the PageRank for OntoComedySources took 0.020895957946777344s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.1920928955078125e-05s
Believability | Calculation of trust value for OntoComedySources took 6.9141387939453125e-06s
INFO | --- Analysis for OntoComedySources took 4.501204252243042s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.21070623397827148s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0003542900085449219s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.3331756591796875s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.1682510375976562e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 6.67572021484375e-06s
INFO | --- Analysis for OntoCeramic-2.0 took 4.992948293685913s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.2115776538848877s
Availability | VoID file availability check for SaintGall Ontology took 0.000217437744140625s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.331620454788208s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.020693302154541016s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.1920928955078125e-05s
Believability | Calculation of trust value for SaintGall Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for SaintGall-Ontology took 3.8256454467773438s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.8186023235321045s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.307481050491333s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.020425081253051758s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.3828277587890625e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 4.613117218017578s
Availability | SPARQL endpoint availability check for ICON took 0.3157649040222168s
Availability | VoID file availability check for ICON took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for ICON took 0.3193089962005615s
Reputation | Calculation of the PageRank for ICON took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for ICON took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for ICON took 1.0251998901367188e-05s
Believability | Calculation of trust value for ICON took 1.0251998901367188e-05s
INFO | --- Analysis for ICON took 4.8926379680633545s
Availability | SPARQL endpoint availability check for Polifonia took 0.30643606185913086s
Availability | VoID file availability check for Polifonia took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for Polifonia took 0.35768556594848633s
Reputation | Calculation of the PageRank for Polifonia took 0.020324230194091797s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.1682510375976562e-05s
Believability | Calculation of trust value for Polifonia took 6.9141387939453125e-06s
INFO | --- Analysis for Polifonia took 5.080722332000732s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.3359827995300293s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0003857612609863281s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.3031797409057617s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.020856142044067383s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.2159347534179688e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 5.7220458984375e-06s
INFO | --- Analysis for Atlas-of-Paths took 4.567542552947998s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.21636176109313965s
Availability | VoID file availability check for Music Note Ontology took 0.0003075599670410156s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.33397698402404785s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 2.1457672119140625e-05s
Believability | Calculation of trust value for Music Note Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for Music-Note-Ontology took 10.607574224472046s
Availability | SPARQL endpoint availability check for HaMSE took 0.21050620079040527s
Availability | VoID file availability check for HaMSE took 0.00032639503479003906s
Completeness | Calculation of interlinking completeness for HaMSE took 0.30228233337402344s
Reputation | Calculation of the PageRank for HaMSE took 0.020364046096801758s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.0728836059570312e-05s
Believability | Calculation of trust value for HaMSE took 6.9141387939453125e-06s
INFO | --- Analysis for HaMSE took 5.569714546203613s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.28436875343322754s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.33023524284362793s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.020778417587280273s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.1444091796875e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 7.152557373046875e-06s
INFO | --- Analysis for FOod took 5.784579038619995s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.6826701164245605s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.00038743019104003906s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.3029158115386963s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.02029728889465332s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.2159347534179688e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 6.9141387939453125e-06s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 5.938854932785034s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.9398694038391113s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.337451696395874s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.020817041397094727s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.1682510375976562e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 5.0067901611328125e-06s
INFO | --- Analysis for ARIADNE took 6.967155456542969s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.3704037666320801s
Availability | VoID file availability check for Odeuropa Ontology took 0.00022220611572265625s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.33409643173217773s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.021189451217651367s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.1682510375976562e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 5.7220458984375e-06s
INFO | --- Analysis for Odeuropa took 3.912151575088501s

--- Total time for analysis:460844.12299370766s ---
--- Total time for analysis:128.012256387141 hours ---