Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.000102996826171875s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.40561747550964355s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.5868842601776123s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.0004258155822753906s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 7.867813110351562e-06s
INFO | --- Analysis for 0080-3626 took 5.8148534297943115s
Availability | SPARQL endpoint availability check for 土地利用图 took 5.364418029785156e-05s
Availability | VoID file availability check for 土地利用图 took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.3877260684967041s
Reputation | Calculation of the PageRank for 土地利用图 took 0.02119588851928711s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 3.337860107421875e-05s
Believability | Calculation of trust value for 土地利用图 took 8.344650268554688e-06s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 2.9467804431915283s
Availability | SPARQL endpoint availability check for 113322 took 5.14984130859375e-05s
Availability | VoID file availability check for 113322 took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for 113322 took 0.41599035263061523s
Reputation | Calculation of the PageRank for 113322 took 0.02104353904724121s
Interlinking | Calculation of Degree of Connection for 113322 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for 113322 took 3.4332275390625e-05s
Believability | Calculation of trust value for 113322 took 1.2159347534179688e-05s
INFO | --- Analysis for 11 took 5.253373384475708s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 5.7697296142578125e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.31737422943115234s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.02075982093811035s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.147125244140625e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.4066696166992188e-05s
INFO | --- Analysis for 12323 took 2.8946480751037598s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.05969572067260742s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.5121235847473145s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.022821903228759766s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 9.298324584960938e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.239776611328125e-05s
INFO | --- Analysis for 2000-us-census-rdf took 3.3025143146514893s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.5433375835418701s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.35433459281921387s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.023784637451171875s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.001054525375366211s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 5.078315734863281e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 9.775161743164062e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 6.494828224182129s
Availability | SPARQL endpoint availability check for Open Data Web took 12.069616079330444s
Availability | VoID file availability check for Open Data Web took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.32651209831237793s
Reputation | Calculation of the PageRank for Open Data Web took 0.020869731903076172s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.504753112792969e-05s
Believability | Calculation of trust value for Open Data Web took 1.3828277587890625e-05s
INFO | --- Analysis for _data.odw.tw took 20.3515305519104s
Availability | SPARQL endpoint availability check for 土地利用 took 6.580352783203125e-05s
Availability | VoID file availability check for 土地利用 took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.33328747749328613s
Reputation | Calculation of the PageRank for 土地利用 took 0.0212252140045166s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.2901763916015625e-05s
Believability | Calculation of trust value for 土地利用 took 1.3589859008789062e-05s
INFO | --- Analysis for _data1.odw.tw took 3.0406789779663086s
Availability | SPARQL endpoint availability check for 土地利用模型 took 0.00010132789611816406s
Availability | VoID file availability check for 土地利用模型 took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.2880542278289795s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.03173255920410156s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0016903877258300781s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 5.1021575927734375e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.3828277587890625e-05s
INFO | --- Analysis for _data2.odw.tw took 6.74474024772644s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.0001609325408935547s
Availability | VoID file availability check for Indian Biodiversity took 0.0008001327514648438s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3465914726257324s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02644205093383789s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0015459060668945312s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 4.9114227294921875e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.239776611328125e-05s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 4.356865882873535s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 5.412101745605469e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.3281376361846924s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.023925304412841797s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0011928081512451172s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 4.410743713378906e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.2636184692382812e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 3.8982272148132324s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 0.00010251998901367188s
Availability | VoID file availability check for ITS TEST DATASET took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.3222494125366211s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.02087688446044922s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.457069396972656e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 1.0251998901367188e-05s
INFO | --- Analysis for A1 took 3.847198247909546s
Availability | SPARQL endpoint availability check for SummerOlympics took 1.8057968616485596s
Availability | VoID file availability check for SummerOlympics took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.3227066993713379s
Reputation | Calculation of the PageRank for SummerOlympics took 0.02124929428100586s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.961822509765625e-05s
Believability | Calculation of trust value for SummerOlympics took 1.3113021850585938e-05s
INFO | --- Analysis for abc took 8.724900007247925s
Availability | SPARQL endpoint availability check for Test_m took 5.4836273193359375e-05s
Availability | VoID file availability check for Test_m took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for Test_m took 0.34433746337890625s
Reputation | Calculation of the PageRank for Test_m took 0.02308821678161621s
Interlinking | Calculation of Degree of Connection for Test_m took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0016834735870361328s
Interlinking | Calculation of Clustering coefficient for Test_m took 5.030632019042969e-05s
Believability | Calculation of trust value for Test_m took 1.1444091796875e-05s
INFO | --- Analysis for ABC took 2.948974132537842s
Availability | SPARQL endpoint availability check for my intro took 9.822845458984375e-05s
Availability | VoID file availability check for my intro took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for my intro took 0.35488414764404297s
Reputation | Calculation of the PageRank for my intro took 0.02133941650390625s
Interlinking | Calculation of Degree of Connection for my intro took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for my intro took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for my intro took 3.552436828613281e-05s
Believability | Calculation of trust value for my intro took 1.239776611328125e-05s
INFO | --- Analysis for abhay_intro took 3.009516954421997s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.23065710067749023s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.3598635196685791s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.021351099014282227s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.00083160400390625s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010991096496582031s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.33514404296875e-05s
INFO | --- Analysis for abs-linked-data took 3.1383423805236816s
Availability | SPARQL endpoint availability check for AcadOnto took 0.00018835067749023438s
Availability | VoID file availability check for AcadOnto took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.31940579414367676s
Reputation | Calculation of the PageRank for AcadOnto took 0.020990371704101562s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.266334533691406e-05s
Believability | Calculation of trust value for AcadOnto took 1.2636184692382812e-05s
INFO | --- Analysis for acadonto took 3.8190817832946777s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 8.959319353103638s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.35626697540283203s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.021292448043823242s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.3392181396484375e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 6.4373016357421875e-06s
INFO | --- Analysis for acorn-sat took 35.984352111816406s
Availability | SPARQL endpoint availability check for Addgene took 0.00010418891906738281s
Availability | VoID file availability check for Addgene took 0.0007989406585693359s
Completeness | Calculation of interlinking completeness for Addgene took 0.29997801780700684s
Reputation | Calculation of the PageRank for Addgene took 0.02109551429748535s
Interlinking | Calculation of Degree of Connection for Addgene took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.7670135498046875e-05s
Believability | Calculation of trust value for Addgene took 1.2636184692382812e-05s
INFO | --- Analysis for addgene took 15.905675172805786s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 0.00010371208190917969s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0008475780487060547s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.37995195388793945s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020818233489990234s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.393692016601562e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.2159347534179688e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 9.324734210968018s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.3999598026275635s
Availability | VoID file availability check for AEMET metereological dataset took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.4488706588745117s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020957469940185547s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 4.172325134277344e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 1.3589859008789062e-05s
INFO | --- Analysis for aemet took 5.5749192237854s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.029384851455688477s
Availability | VoID file availability check for AgriNepalData took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.3315551280975342s
Reputation | Calculation of the PageRank for AgriNepalData took 0.022235393524169922s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0012850761413574219s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 9.584426879882812e-05s
Believability | Calculation of trust value for AgriNepalData took 1.4066696166992188e-05s
INFO | --- Analysis for agrinepaldata took 3.0302860736846924s
Availability | SPARQL endpoint availability check for AGRIS took 262.1169648170471s
Availability | VoID file availability check for AGRIS took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for AGRIS took 0.49591898918151855s
Reputation | Calculation of the PageRank for AGRIS took 0.021658658981323242s
Interlinking | Calculation of Degree of Connection for AGRIS took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for AGRIS took 8.20159912109375e-05s
Believability | Calculation of trust value for AGRIS took 1.049041748046875e-05s
INFO | --- Analysis for agris took 575.9344527721405s
Availability | SPARQL endpoint availability check for AGROVOC took 0.20064973831176758s
Availability | VoID file availability check for AGROVOC took 0.0006458759307861328s
Extra | Recovery of all triples for AGROVOC took 272.1924955844879s
Performance | Total latancy measurement for AGROVOC took 0.46605896949768066s
Amount of data | Number of triples check for AGROVOC took 46.1493558883667s
Interoperability | New terms check for AGROVOC took 3.5407822132110596s
Versatility | Languages check for AGROVOC took 300.0969271659851s
Interpretability | Number of blank nodes check for AGROVOC took 300.1197576522827s
Interpretability | RDF structures check for AGROVOC took 0.09775996208190918s
Versatility | Serialization formats check for AGROVOC took 0.09050703048706055s
Availability | RDF dump link check for AGROVOC took 0.09855198860168457s
License | MR license check for AGROVOC took 0.17692875862121582s
License | HR license check for AGROVOC took 2.080491304397583s
Amount of data | Number of property check for AGROVOC took 0.14863133430480957s
Understandability | Number of label check for AGROVOC took 300.09048318862915s
Understandability | URI regex check for AGROVOC took 0.2139279842376709s
Understandability | Vocabs check for AGROVOC took 0.09642362594604492s
Verifiability | Authors check for AGROVOC took 0.08009672164916992s
Verifiability | Publishers check for AGROVOC took 0.09121966361999512s
Performance | Throughput check for AGROVOC took 10.554283618927002s
Amount of data | Check the number of entities for AGROVOC took 8.20159912109375e-05s
Verifiability | Contribs. check for AGROVOC took 0.08098912239074707s
Interlinking | sameAs chians check for AGROVOC took 0.0898895263671875s
Interlinking | skos check for AGROVOC took 11.108895540237427s
Interlinking | skos check for AGROVOC took 7.713916778564453s
Timeliness | dataset update frequency check for AGROVOC took 0.08933234214782715s
Currency | Creation date check for AGROVOC took 0.1858658790588379s
Currency | Modification date check for AGROVOC took 0.1761302947998047s
Rep.Conc. | URIs length for AGROVOC took 127.1503963470459s
Interoperability | New vocabularies check for AGROVOC took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.08930420875549316s
Accuracy | Check Functional Property for AGROVOC took 0.0897526741027832s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.08874702453613281s
Accuracy | Check Empty annotation labels for AGROVOC took 26.833983659744263s
Accuracy | Check White space in annotation for AGROVOC took 3.033823251724243s
Accuracy | Check Datatype consistency for AGROVOC took 4.578343868255615s
Consistency | Disjoint class check for AGROVOC took 0.07607674598693848s
Consistency | Check Misplaced properties for AGROVOC took 23.081533432006836s
Consistency | Check Ontology hijacking for AGROVOC took 208.18647146224976s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 2.144388437271118s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 22.031352996826172s
Conciseness | Check Extensional conciseness for AGROVOC took 2.695347309112549s
Conciseness | Check Intensional conciseness for AGROVOC took 0.10351347923278809s
Security | Sign check for AGROVOC took 0.08774089813232422s
Availability | Check URIs Dereferenciability for AGROVOC took 3.513657569885254s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.5695877075195312s
Reputation | Calculation of the PageRank for AGROVOC took 0.03680014610290527s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00012111663818359375s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 2.1457672119140625e-06s
Believability | Calculation of trust value for AGROVOC took 1.2636184692382812e-05s
INFO | --- Analysis for agrovoc took 2296.22540807724s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.5841970443725586s
Availability | VoID file availability check for Analytics India Magazine took 0.0003407001495361328s
Extra | Recovery of all triples for Analytics India Magazine took 2.303619384765625s
Performance | Total latancy measurement for Analytics India Magazine took 2.7976298332214355s
Amount of data | Number of triples check for Analytics India Magazine took 1.3250682353973389s
Versatility | Languages check for Analytics India Magazine took 1.1467607021331787s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.8219923973083496s
Interpretability | RDF structures check for Analytics India Magazine took 1.8525798320770264s
Versatility | Serialization formats check for Analytics India Magazine took 1.2096350193023682s
Availability | RDF dump link check for Analytics India Magazine took 1.2300403118133545s
License | MR license check for Analytics India Magazine took 1.3559677600860596s
License | HR license check for Analytics India Magazine took 1.2325961589813232s
Amount of data | Number of property check for Analytics India Magazine took 1.2793264389038086s
Understandability | Number of label check for Analytics India Magazine took 1.879572868347168s
Understandability | URI regex check for Analytics India Magazine took 2.282949447631836s
Understandability | Vocabs check for Analytics India Magazine took 1.3929939270019531s
Verifiability | Authors check for Analytics India Magazine took 1.3623089790344238s
Verifiability | Publishers check for Analytics India Magazine took 1.411025047302246s
Performance | Throughput check for Analytics India Magazine took 19.723845958709717s
Amount of data | Check the number of entities for Analytics India Magazine took 0.00018978118896484375s
Verifiability | Contribs. check for Analytics India Magazine took 1.7294979095458984s
Interlinking | sameAs chians check for Analytics India Magazine took 1.5893609523773193s
Interlinking | skos check for Analytics India Magazine took 1.2760615348815918s
Interlinking | skos check for Analytics India Magazine took 0.16377043724060059s
Timeliness | dataset update frequency check for Analytics India Magazine took 1.1256041526794434s
Currency | Creation date check for Analytics India Magazine took 2.7082037925720215s
Currency | Modification date check for Analytics India Magazine took 3.0955002307891846s
Rep.Conc. | URIs length for Analytics India Magazine took 3.578622579574585s
Interoperability | New vocabularies check for Analytics India Magazine took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 1.361053228378296s
Consistency | Disjoint class check for Analytics India Magazine took 1.9068396091461182s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.509333610534668s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 3.5280940532684326s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.00017118453979492188s
Security | Sign check for Analytics India Magazine took 1.1284730434417725s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.36017537117004395s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.409385681152344e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 1.6689300537109375e-06s
Believability | Calculation of trust value for Analytics India Magazine took 1.2874603271484375e-05s
INFO | --- Analysis for AIM took 107.9693295955658s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 0.0001773834228515625s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0008103847503662109s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.3412775993347168s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.021146774291992188s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.24249267578125e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.3113021850585938e-05s
INFO | --- Analysis for AISHE took 3.3158469200134277s
Availability | SPARQL endpoint availability check for  equipment ontology took 0.0001766681671142578s
Availability | VoID file availability check for  equipment ontology took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.4039115905761719s
Reputation | Calculation of the PageRank for  equipment ontology took 0.02167820930480957s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.600120544433594e-05s
Believability | Calculation of trust value for  equipment ontology took 1.3589859008789062e-05s
INFO | --- Analysis for akash took 2.983748435974121s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 261.80794072151184s
Availability | VoID file availability check for aliada-scanbit-net took 0.0009951591491699219s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.41948795318603516s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.02289271354675293s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00013828277587890625s
Believability | Calculation of trust value for aliada-scanbit-net took 1.3589859008789062e-05s
INFO | --- Analysis for aliada-scanbit-net took 1453.3292622566223s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.7852444648742676s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0007853507995605469s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 136.2472767829895s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.8159244060516357s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.3703296184539795s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.720529317855835s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.10537028312683s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.812365770339966s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8734261989593506s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.6142334938049316s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.6983153820037842s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5968735218048096s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.567514181137085s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 32.01230239868164s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.587026834487915s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.7792119979858398s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1377372741699219s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.5736002922058105s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6199085712432861s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.6657209396362305s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.888556480407715s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 4.839897155761719e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5550897121429443s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5830793380737305s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5821890830993652s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.566364049911499s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.594982385635376s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.218010663986206s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1726834774017334s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 55.031691789627075s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 10.727602243423462s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5809757709503174s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6737558841705322s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.5593953132629395s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 36.7417414188385s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.1053593158721924s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.8270998001098633s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.6365954875946045s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.421616554260254s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 9.169496536254883s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 32.626421213150024s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.5753288269042969s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.487401723861694s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.871136426925659s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8608248233795166s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5503339767456055s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 13851.817231178284s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.7311983108520508s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.022860288619995117s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 8.344650268554688e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 5.229490280151367s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.2636184692382812e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 14615.067059278488s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.30201077461242676s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.3327958583831787s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.023231029510498047s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.001064300537109375s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 5.054473876953125e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.2159347534179688e-05s
INFO | --- Analysis for alpino-rdf took 4.516552448272705s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.76837158203125e-05s
Availability | VoID file availability check for AAT-atawil took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.34253406524658203s
Reputation | Calculation of the PageRank for AAT-atawil took 0.02114105224609375s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.24249267578125e-05s
Believability | Calculation of trust value for AAT-atawil took 1.3113021850585938e-05s
INFO | --- Analysis for Altawil took 2.9741837978363037s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.9591064453125e-05s
Availability | VoID file availability check for Amer Nejma took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.29790616035461426s
Reputation | Calculation of the PageRank for Amer Nejma took 0.021477699279785156s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0008614063262939453s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.123283386230469e-05s
Believability | Calculation of trust value for Amer Nejma took 1.239776611328125e-05s
INFO | --- Analysis for Amer_Nejma took 3.2835538387298584s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.6880085468292236s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.33205556869506836s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.021207094192504883s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007317066192626953s
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.3828277587890625e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 4.849118232727051s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.935264587402344e-05s
Availability | VoID file availability check for Anime Dataset took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.29254937171936035s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020981788635253906s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.3855438232421875e-05s
Believability | Calculation of trust value for Anime Dataset took 1.33514404296875e-05s
INFO | --- Analysis for Anime took 4.551174879074097s
Availability | SPARQL endpoint availability check for ANNO took 8.368492126464844e-05s
Availability | VoID file availability check for ANNO took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for ANNO took 0.2735178470611572s
Reputation | Calculation of the PageRank for ANNO took 0.02113485336303711s
Interlinking | Calculation of Degree of Connection for ANNO took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.886222839355469e-05s
Believability | Calculation of trust value for ANNO took 1.3113021850585938e-05s
INFO | --- Analysis for anno took 8.301106929779053s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.935264587402344e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.34130382537841797s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020939111709594727s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.796287536621094e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 1.2636184692382812e-05s
INFO | --- Analysis for AntiqueCarsCollection took 3.8090579509735107s
Availability | SPARQL endpoint availability check for apache took 4.887580871582031e-05s
Availability | VoID file availability check for apache took 0.0009324550628662109s
Completeness | Calculation of interlinking completeness for apache took 0.3578946590423584s
Reputation | Calculation of the PageRank for apache took 0.02857208251953125s
Interlinking | Calculation of Degree of Connection for apache took 3.9577484130859375e-05s
Interlinking | Calculation of Centrality for apache took 0.0013971328735351562s
Interlinking | Calculation of Clustering coefficient for apache took 0.00010848045349121094s
Believability | Calculation of trust value for apache took 1.3113021850585938e-05s
INFO | --- Analysis for apache took 4.314159154891968s
Availability | SPARQL endpoint availability check for Apertium RDF took 5.3882598876953125e-05s
Availability | VoID file availability check for Apertium RDF took 0.0007612705230712891s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.33749938011169434s
Reputation | Calculation of the PageRank for Apertium RDF took 0.029143810272216797s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0014748573303222656s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 7.915496826171875e-05s
Believability | Calculation of trust value for Apertium RDF took 1.5020370483398438e-05s
INFO | --- Analysis for apertium-rdf took 7.217718124389648s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 5.459785461425781e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0007727146148681641s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.3267090320587158s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.022031307220458984s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 6.4246861934661865s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.792213439941406e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.3333568572998047s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 6.212013483047485s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 0.00010156631469726562s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0007131099700927734s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.9176807403564453s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.022333860397338867s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.76837158203125e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-en-es took 6.895073175430298s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 5.1975250244140625e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.3262052536010742s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.021898269653320312s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 6.336272478103638s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 9.822845458984375e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.4207906723022461s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.021498680114746094s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.673004150390625e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 6.2678773403167725s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 9.965896606445312e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0007297992706298828s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.3403301239013672s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02090001106262207s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.4066696166992188e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 6.0341362953186035s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.935264587402344e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.374530553817749s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.027727842330932617s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0012941360473632812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 5.8650970458984375e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 6.947593450546265s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 9.965896606445312e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.36649465560913086s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.021747827529907227s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 5.0067901611328125e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 6.2333292961120605s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 0.00010204315185546875s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0007517337799072266s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2952556610107422s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.02813267707824707s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0014057159423828125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 7.319450378417969e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.4781951904296875e-05s
INFO | --- Analysis for apertium-rdf-es-an took 6.209592819213867s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 8.320808410644531e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006430149078369141s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.3111090660095215s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020812273025512695s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.4066696166992188e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 6.2791242599487305s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 5.888938903808594e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0008006095886230469s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.3168914318084717s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.02841782569885254s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0014810562133789062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 7.796287536621094e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.4781951904296875e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 15.505915641784668s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 0.00010728836059570312s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.32681727409362793s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.028208255767822266s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0016908645629882812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 8.416175842285156e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.621246337890625e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 6.331875801086426s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 5.4836273193359375e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.3434929847717285s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.028351306915283203s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0015513896942138672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 8.273124694824219e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.5735626220703125e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 6.214229583740234s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 5.173683166503906e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0007529258728027344s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.4410123825073242s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02769303321838379s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0014765262603759766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 7.724761962890625e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.3828277587890625e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 6.2430548667907715s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 7.987022399902344e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.30278706550598145s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02161860466003418s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.8160552978515625e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 6.082301139831543s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 5.054473876953125e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0007741451263427734s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.3675980567932129s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.021223783493041992s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 5.435943603515625e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 0.0002040863037109375s
INFO | --- Analysis for apertium-rdf-eu-es took 6.33669114112854s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 0.00011110305786132812s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0017156600952148438s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.3368699550628662s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.028156042098999023s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0015711784362792969s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 8.440017700195312e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.430511474609375e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 6.551506757736206s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 5.4836273193359375e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0007541179656982422s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.3214080333709717s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.028374910354614258s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0015919208526611328s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 8.535385131835938e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.4543533325195312e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 6.46275782585144s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 9.870529174804688e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0007007122039794922s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.3672971725463867s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02099776268005371s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 5.1021575927734375e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 6.2886271476745605s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 8.487701416015625e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.3663167953491211s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.022690534591674805s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.8160552978515625e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 6.323781490325928s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 0.00012946128845214844s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.47264885902404785s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02110886573791504s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.673004150390625e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 6.281580209732056s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 5.0067901611328125e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.3270909786224365s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.021122217178344727s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 0.0002090930938720703s
INFO | --- Analysis for apertium-rdf-pt-gl took 7.218579053878784s
Availability | SPARQL endpoint availability check for AragoDBpedia - aragon open data took 0.6665918827056885s
Availability | VoID file availability check for AragoDBpedia - aragon open data took 0.0007214546203613281s
Extra | Recovery of all triples for AragoDBpedia - aragon open data took 2.984429359436035s
Performance | Total latancy measurement for AragoDBpedia - aragon open data took 1.694448709487915s
Amount of data | Number of triples check for AragoDBpedia - aragon open data took 0.7716672420501709s
Interoperability | New terms check for AragoDBpedia - aragon open data took 2.2185182571411133s
Versatility | Languages check for AragoDBpedia - aragon open data took 60.463189363479614s
Interpretability | Number of blank nodes check for AragoDBpedia - aragon open data took 4.302473783493042s
Security | Check HTTPS for AragoDBpedia - aragon open data took 0.19460296630859375s
Interpretability | RDF structures check for AragoDBpedia - aragon open data took 0.76003098487854s
Versatility | Serialization formats check for AragoDBpedia - aragon open data took 0.9144301414489746s
Availability | RDF dump link check for AragoDBpedia - aragon open data took 0.37301087379455566s
License | MR license check for AragoDBpedia - aragon open data took 0.6406233310699463s
License | HR license check for AragoDBpedia - aragon open data took 6.09212851524353s
Amount of data | Number of property check for AragoDBpedia - aragon open data took 0.39244651794433594s
Understandability | Number of label check for AragoDBpedia - aragon open data took 0.5529537200927734s
Understandability | URI regex check for AragoDBpedia - aragon open data took 0.839214563369751s
Understandability | Vocabs check for AragoDBpedia - aragon open data took 0.4209752082824707s
Verifiability | Authors check for AragoDBpedia - aragon open data took 0.47839951515197754s
Verifiability | Publishers check for AragoDBpedia - aragon open data took 0.39097046852111816s
Performance | Throughput check for AragoDBpedia - aragon open data took 11.496867895126343s
Amount of data | Check the number of entities for AragoDBpedia - aragon open data took 7.557868957519531e-05s
Verifiability | Contribs. check for AragoDBpedia - aragon open data took 0.4703702926635742s
Interlinking | sameAs chians check for AragoDBpedia - aragon open data took 0.3983192443847656s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.7263596057891846s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.31174516677856445s
Timeliness | dataset update frequency check for AragoDBpedia - aragon open data took 0.516364336013794s
Currency | Creation date check for AragoDBpedia - aragon open data took 1.1187520027160645s
Currency | Modification date check for AragoDBpedia - aragon open data took 0.37119507789611816s
Rep.Conc. | URIs length for AragoDBpedia - aragon open data took 5.772226333618164s
Interoperability | New vocabularies check for AragoDBpedia - aragon open data took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for AragoDBpedia - aragon open data took 0.3749575614929199s
Accuracy | Check Functional Property for AragoDBpedia - aragon open data took 0.4776620864868164s
Accuracy | Check Inverse Functional Property for AragoDBpedia - aragon open data took 0.4792366027832031s
Accuracy | Check Empty annotation labels for AragoDBpedia - aragon open data took 1.1743152141571045s
Accuracy | Check White space in annotation for AragoDBpedia - aragon open data took 0.03029155731201172s
Accuracy | Check Datatype consistency for AragoDBpedia - aragon open data took 0.029870986938476562s
Consistency | Disjoint class check for AragoDBpedia - aragon open data took 0.39971470832824707s
Consistency | Check Misplaced properties for AragoDBpedia - aragon open data took 4.330812215805054s
Consistency | Misplaced classes for AragoDBpedia - aragon open data took 0.6269071102142334s
Consistency | Check Ontology hijacking for AragoDBpedia - aragon open data took 2.5332391262054443s
Consistency | Check Invalid usage of undefined classes for AragoDBpedia - aragon open data took 1.4852232933044434s
Consistency | Check Invalid usage of undefined properties for AragoDBpedia - aragon open data took 5.1954851150512695s
Conciseness | Check Extensional conciseness for AragoDBpedia - aragon open data took 0.03490877151489258s
Conciseness | Check Intensional conciseness for AragoDBpedia - aragon open data took 0.5342051982879639s
Security | Sign check for AragoDBpedia - aragon open data took 0.6463682651519775s
Availability | Check URIs Dereferenciability for AragoDBpedia - aragon open data took 3335.5128371715546s
Completeness | Calculation of interlinking completeness for AragoDBpedia - aragon open data took 0.7204797267913818s
Reputation | Calculation of the PageRank for AragoDBpedia - aragon open data took 0.022628068923950195s
Interlinking | Calculation of Degree of Connection for AragoDBpedia - aragon open data took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for AragoDBpedia - aragon open data took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for AragoDBpedia - aragon open data took 9.083747863769531e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBpedia - aragon open data took 1.430511474609375e-06s
Believability | Calculation of trust value for AragoDBpedia - aragon open data took 1.049041748046875e-05s
INFO | --- Analysis for aragodbpedia took 3606.697158575058s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.343249082565308s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0008342266082763672s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.34364819526672363s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020982742309570312s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.269050598144531e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.3828277587890625e-05s
INFO | --- Analysis for archiveshub-linkeddata took 83.72319626808167s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 7.309972286224365s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.2963685989379883s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.021955251693725586s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.552436828613281e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 1.3113021850585938e-05s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 24.31457018852234s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.8775980472564697s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0008599758148193359s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.33705639839172363s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.02924370765686035s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.00140380859375s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 6.556510925292969e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.4781951904296875e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 18.102606534957886s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.965896606445312e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.3645358085632324s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.029071331024169922s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0013701915740966797s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00015687942504882812s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.52587890625e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 7.635796546936035s
Availability | SPARQL endpoint availability check for Arthroscopy community took 0.00010752677917480469s
Availability | VoID file availability check for Arthroscopy community took 0.0007905960083007812s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.33444833755493164s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.021500587463378906s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0008895397186279297s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00012135505676269531s
Believability | Calculation of trust value for Arthroscopy community took 1.2636184692382812e-05s
INFO | --- Analysis for arthroscopy took 11.848361492156982s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.8717718124389648s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0007486343383789062s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 35.72027397155762s
Performance | Total latancy measurement for Wikidata entry for Art × Science International took 1.3709585666656494s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 65.17119407653809s
Interoperability | New terms check for Wikidata entry for Art × Science International took 2.3123645782470703s
Versatility | Languages check for Wikidata entry for Art × Science International took 65.16597771644592s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 65.1815836429596s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.2304551601409912s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.19621062278747559s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.427323579788208s
License | MR license check for Wikidata entry for Art × Science International took 0.1806011199951172s
License | HR license check for Wikidata entry for Art × Science International took 65.17184615135193s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 1.0838494300842285s
Understandability | Number of label check for Wikidata entry for Art × Science International took 65.17174935340881s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.545903205871582s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.22039246559143066s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.21146249771118164s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.18189430236816406s
Performance | Throughput check for Wikidata entry for Art × Science International took 11.295215845108032s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 7.724761962890625e-05s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.21872353553771973s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 28.702372550964355s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.1589524745941162s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.1955854892730713s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.175095796585083s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.3440687656402588s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.4448730945587158s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 4.043720245361328s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.3241398334503174s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.862756967544556s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.1872575283050537s
Consistency | Check Misplaced properties for Wikidata entry for Art × Science International took 20.851962566375732s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 0.16907334327697754s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 13.978039026260376s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.981834888458252s
Conciseness | Check Intensional conciseness for Wikidata entry for Art × Science International took 1.5667309761047363s
Security | Sign check for Wikidata entry for Art × Science International took 0.3053014278411865s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 8.849887609481812s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.4082932472229004s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.024464130401611328s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 2.2172927856445312e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 1.430511474609375e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 1.3589859008789062e-05s
INFO | --- Analysis for artxscienceinternational-wikidata took 782.9903094768524s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.2121775150299072s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.3450319766998291s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.534027099609375e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.33514404296875e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 12.49099612236023s
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.15873646736145s
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.0006101131439208984s
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.3403444290161133s
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.020938873291015625s
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.1682510375976562e-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.0007584095001220703s
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.106231689453125e-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.2636184692382812e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 11.044348001480103s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.1634292602539062s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.3140828609466553s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.02225971221923828s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.1552734375e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.2159347534179688e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 11.957595825195312s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.192194700241089s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.00041937828063964844s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.3371400833129883s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.03226017951965332s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0012412071228027344s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 6.4849853515625e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.2874603271484375e-05s
INFO | --- Analysis for ASCDC-CRB took 13.888476610183716s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.1715543270111084s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0008876323699951172s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.4311256408691406s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.02106952667236328s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.72747802734375e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.2636184692382812e-05s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 11.736500024795532s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.1527411937713623s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.33827996253967285s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020873308181762695s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.600120544433594e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.430511474609375e-05s
INFO | --- Analysis for ASCDC-DQOT took 12.426276206970215s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.1666085720062256s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.3336150646209717s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.02286243438720703s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.225440979003906e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.2874603271484375e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.554971933364868s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 2.8771724700927734s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.3465597629547119s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.022543668746948242s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.20159912109375e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.2874603271484375e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 14.582722187042236s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.15863037109375s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.31093573570251465s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.021982192993164062s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 6.604194641113281e-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.239776611328125e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 11.404709100723267s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.16843318939209s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.34288787841796875s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.021365642547607422s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.6743621826171875e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 11.306071519851685s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.561044216156006s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0004093647003173828s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.29876160621643066s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.02119731903076172s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.935264587402344e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.3113021850585938e-05s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 15.337292671203613s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.184450387954712s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.3598470687866211s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020934343338012695s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.775161743164062e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 11.06285285949707s
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.1898510456085205s
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.0006039142608642578s
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.3074502944946289s
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.020949602127075195s
Interlinking | Calculation of Degree of Connection for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 8.225440979003906e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.420623540878296s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.1586523056030273s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.29232287406921387s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020917177200317383s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0008015632629394531s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.696846008300781e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 1.4781951904296875e-05s
INFO | --- Analysis for ASCDC_-_DNB took 10.732152462005615s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.9591064453125e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0006642341613769531s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.30649280548095703s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.0209500789642334s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 7.009506225585938e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.33514404296875e-05s
INFO | --- Analysis for asit took 8.724549770355225s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.863739013671875e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0004067420959472656s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.3555455207824707s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 4.076957702636719e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 7.867813110351562e-06s
INFO | --- Analysis for asjp took 5.246235370635986s
Availability | SPARQL endpoint availability check for ASN:US took 2.54044771194458s
Availability | VoID file availability check for ASN:US took 0.0002982616424560547s
Completeness | Calculation of interlinking completeness for ASN:US took 0.3247532844543457s
Reputation | Calculation of the PageRank for ASN:US took 0.022029399871826172s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for ASN:US took 7.033348083496094e-05s
Believability | Calculation of trust value for ASN:US took 1.049041748046875e-05s
INFO | --- Analysis for asn-us took 14.301964521408081s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 6.031990051269531e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.31302952766418457s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.020940303802490234s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.218650817871094e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 9.059906005859375e-06s
INFO | --- Analysis for aspire-mmu took 4.98569130897522s
Availability | SPARQL endpoint availability check for associations took 7.605552673339844e-05s
Availability | VoID file availability check for associations took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for associations took 0.3206348419189453s
Reputation | Calculation of the PageRank for associations took 0.02105236053466797s
Interlinking | Calculation of Degree of Connection for associations took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for associations took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for associations took 8.034706115722656e-05s
Believability | Calculation of trust value for associations took 8.106231689453125e-06s
INFO | --- Analysis for associations took 73.70584440231323s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 9.1552734375e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.3057398796081543s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020857810974121094s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 9.799003601074219e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.3828277587890625e-05s
INFO | --- Analysis for athelia-rfid took 6.528294086456299s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.572180986404419s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0006773471832275391s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.3415846824645996s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.02092909812927246s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.054473876953125e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for AugustiniConfessiones took 4.558031797409058s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.4936504364013672s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.3400154113769531s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02064061164855957s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.1552734375e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.239776611328125e-05s
INFO | --- Analysis for austrian_ski_racers took 4.148095369338989s
Availability | SPARQL endpoint availability check for AVsOnto took 4.9114227294921875e-05s
Availability | VoID file availability check for AVsOnto took 0.0003590583801269531s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.5925102233886719s
Reputation | Calculation of the PageRank for AVsOnto took 0.021579742431640625s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.457069396972656e-05s
Believability | Calculation of trust value for AVsOnto took 7.62939453125e-06s
INFO | --- Analysis for AVsOnto took 4.017067909240723s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.21469426155090332s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0006074905395507812s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 179.91454005241394s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5104525089263916s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.09748935699463s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 212.88342714309692s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.07894682884216s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.01881551742554s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.33521151542663574s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2502284049987793s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.25601696968078613s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14957857131958008s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 45.369340658187866s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10311913490295s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.18218088150024414s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0318834781647s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2743721008300781s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1212759017944336s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11430907249450684s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10919833183288574s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.497562170028687s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.082389831542969e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11272668838500977s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.05769896507263s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.19865798950195312s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13714265823364258s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1536083221435547s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24225306510925293s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.34003329277038574s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1103.2721180915833s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20098447799682617s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 11.300138711929321s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.2713406085968018s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.989204168319702s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1534266471862793s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.20147919654846s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 176.66894435882568s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.3972086906433105s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.81913924217224s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.955272912979126s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3726646900177002s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.1085338592529297s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.44809889793395996s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0226590633392334s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.296966552734375e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.337860107421875e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.049041748046875e-05s
INFO | --- Analysis for b3kat took 4643.238012075424s
Availability | SPARQL endpoint availability check for BabelNet took 4.673004150390625e-05s
Availability | VoID file availability check for BabelNet took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for BabelNet took 0.25568294525146484s
Reputation | Calculation of the PageRank for BabelNet took 0.02153491973876953s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001647472381591797s
Believability | Calculation of trust value for BabelNet took 1.2636184692382812e-05s
INFO | --- Analysis for babelnet took 1.9651060104370117s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.8160552978515625e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.1277012825012207s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.021162986755371094s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.337860107421875e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.3828277587890625e-05s
INFO | --- Analysis for Bacevicius.lt took 1.7901103496551514s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 9.822845458984375e-05s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.00041413307189941406s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.1873478889465332s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.021158695220947266s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.863739013671875e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.2636184692382812e-05s
INFO | --- Analysis for bag took 1.6116702556610107s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 9.608268737792969e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.11517047882080078s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.021713972091674805s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.337860107421875e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.3589859008789062e-05s
INFO | --- Analysis for baixue took 1.7236363887786865s
Availability | SPARQL endpoint availability check for baixue composer took 4.9114227294921875e-05s
Availability | VoID file availability check for baixue composer took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for baixue composer took 0.1699354648590088s
Reputation | Calculation of the PageRank for baixue composer took 0.021390676498413086s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.218650817871094e-05s
Believability | Calculation of trust value for baixue composer took 1.3828277587890625e-05s
INFO | --- Analysis for baixue_composer took 1.7274680137634277s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 9.441375732421875e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.16042804718017578s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.021940231323242188s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.1948089599609375e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 6.9141387939453125e-06s
INFO | --- Analysis for baixue_imagery took 2.0526092052459717s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.887580871582031e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.14346575736999512s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.021031618118286133s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.8623809814453125e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.239776611328125e-05s
INFO | --- Analysis for baixue_imagery1 took 1.8304076194763184s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 9.369850158691406e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.15360331535339355s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.021694183349609375s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.410743713378906e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.2636184692382812e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 1.5880846977233887s
Availability | SPARQL endpoint availability check for BBC Music took 0.4083747863769531s
Availability | VoID file availability check for BBC Music took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for BBC Music took 0.13192033767700195s
Reputation | Calculation of the PageRank for BBC Music took 0.02118539810180664s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00013709068298339844s
Believability | Calculation of trust value for BBC Music took 1.3113021850585938e-05s
INFO | --- Analysis for bbc-music took 2.114576816558838s
Availability | SPARQL endpoint availability check for BBC Programmes took 6.198883056640625e-05s
Availability | VoID file availability check for BBC Programmes took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.1555166244506836s
Reputation | Calculation of the PageRank for BBC Programmes took 0.021054983139038086s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010514259338378906s
Believability | Calculation of trust value for BBC Programmes took 1.239776611328125e-05s
INFO | --- Analysis for bbc-programmes took 1.887092113494873s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.3081650733947754s
Availability | VoID file availability check for BBC Wildlife Finder took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.15672659873962402s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.02116107940673828s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010967254638671875s
Believability | Calculation of trust value for BBC Wildlife Finder took 8.344650268554688e-06s
INFO | --- Analysis for bbc-wildlife-finder took 2.4434900283813477s
Availability | SPARQL endpoint availability check for BBOP took 5.173683166503906e-05s
Availability | VoID file availability check for BBOP took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for BBOP took 0.1778886318206787s
Reputation | Calculation of the PageRank for BBOP took 0.028018712997436523s
Interlinking | Calculation of Degree of Connection for BBOP took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0014576911926269531s
Interlinking | Calculation of Clustering coefficient for BBOP took 6.198883056640625e-05s
Believability | Calculation of trust value for BBOP took 8.821487426757812e-06s
INFO | --- Analysis for bbop-selected took 1.6147875785827637s
Availability | SPARQL endpoint availability check for Bdgp took 9.608268737792969e-05s
Availability | VoID file availability check for Bdgp took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Bdgp took 0.17980527877807617s
Reputation | Calculation of the PageRank for Bdgp took 0.021341800689697266s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.457069396972656e-05s
Believability | Calculation of trust value for Bdgp took 1.2636184692382812e-05s
INFO | --- Analysis for bdgp took 2.117980718612671s
Availability | SPARQL endpoint availability check for Bendev Junior took 9.989738464355469e-05s
Availability | VoID file availability check for Bendev Junior took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.15854501724243164s
Reputation | Calculation of the PageRank for Bendev Junior took 0.02104043960571289s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.218650817871094e-05s
Believability | Calculation of trust value for Bendev Junior took 1.3828277587890625e-05s
INFO | --- Analysis for bendevoficial took 1.8635101318359375s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 9.584426879882812e-05s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.15211915969848633s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.021001100540161133s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.128715515136719e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 8.344650268554688e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 1.9371259212493896s
Availability | SPARQL endpoint availability check for berlios took 9.584426879882812e-05s
Availability | VoID file availability check for berlios took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for berlios took 0.15988516807556152s
Reputation | Calculation of the PageRank for berlios took 0.021127700805664062s
Interlinking | Calculation of Degree of Connection for berlios took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for berlios took 9.322166442871094e-05s
Believability | Calculation of trust value for berlios took 1.430511474609375e-05s
INFO | --- Analysis for berlios took 1.6991112232208252s
Availability | SPARQL endpoint availability check for Between Our Worlds took 5.030632019042969e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.2291872501373291s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.02179861068725586s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 7.128715515136719e-05s
Believability | Calculation of trust value for Between Our Worlds took 8.106231689453125e-06s
INFO | --- Analysis for betweenourworlds took 1.8969874382019043s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 4.792213439941406e-05s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.12941193580627441s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.02205061912536621s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.00010013580322265625s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.0728836059570312e-05s
INFO | --- Analysis for bfs-linked-data took 1.6496076583862305s
Availability | SPARQL endpoint availability check for BibBase took 9.560585021972656e-05s
Availability | VoID file availability check for BibBase took 0.00039887428283691406s
Completeness | Calculation of interlinking completeness for BibBase took 0.11589670181274414s
Reputation | Calculation of the PageRank for BibBase took 0.021075010299682617s
Interlinking | Calculation of Degree of Connection for BibBase took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.632110595703125e-05s
Believability | Calculation of trust value for BibBase took 7.867813110351562e-06s
INFO | --- Analysis for bibbase took 2.1286165714263916s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.673004150390625e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.14080405235290527s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.021073579788208008s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.0001010894775390625s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.33514404296875e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 1.6152653694152832s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 9.918212890625e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.00030112266540527344s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.11597609519958496s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.02129220962524414s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010156631469726562s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 6.9141387939453125e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 1.7187767028808594s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.00010395050048828125s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.00021696090698242188s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.11550784111022949s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.022446393966674805s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0008141994476318359s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.910064697265625e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.1920928955078125e-05s
INFO | --- Analysis for BibSonomy took 1.5816285610198975s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 9.417533874511719e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.000400543212890625s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.14890694618225098s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.021271228790283203s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.314018249511719e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.1682510375976562e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 1.7061686515808105s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 5.0067901611328125e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.1337144374847412s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.02122807502746582s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.147125244140625e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.3589859008789062e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 1.5593857765197754s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 4.458427429199219e-05s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.1105198860168457s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.02259683609008789s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.703636169433594e-05s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1.556901216506958s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 4.839897155761719e-05s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.21300959587097168s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.021349668502807617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0008127689361572266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011324882507324219s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1.8334088325500488s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 9.72747802734375e-05s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.17975473403930664s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.0210726261138916s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.000408172607421875s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1.9603805541992188s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.1362307071685791s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.021453142166137695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.8650970458984375e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 3.457069396972656e-05s
INFO | --- Analysis for bio2rdf-chembl took 1.54878830909729s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 9.679794311523438e-05s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.13609981536865234s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.02164912223815918s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 4.8160552978515625e-05s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1.6861786842346191s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 9.322166442871094e-05s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.11596369743347168s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.022107601165771484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 8.440017700195312e-05s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-ctd took 1.5755441188812256s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 9.202957153320312e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.11448502540588379s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.02138066291809082s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 4.935264587402344e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-dataset took 1.5703792572021484s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 5.269050598144531e-05s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.2644658088684082s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.021231889724731445s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 6.198883056640625e-05s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 1.977015733718872s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 9.799003601074219e-05s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.16523122787475586s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.02233123779296875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00010466575622558594s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-drugbank took 1.5943262577056885s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 4.673004150390625e-05s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.11673712730407715s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.021387577056884766s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.3882598876953125e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-genage took 1.5944159030914307s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 9.489059448242188e-05s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.1648273468017578s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.021022796630859375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.316734313964844e-05s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-gendr took 1.856018304824829s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 4.553794860839844e-05s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.38174915313720703s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.021276235580444336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 5.936622619628906e-05s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-goa took 1.722794532775879s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 9.250640869140625e-05s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.00042724609375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.18202519416809082s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.022095918655395508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011897087097167969s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-hgnc took 2.1116254329681396s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 4.8160552978515625e-05s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0002994537353515625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.13178467750549316s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.02112579345703125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.221366882324219e-05s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-homologene took 1.5852010250091553s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 4.839897155761719e-05s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.13989710807800293s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.023439645767211914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010132789611816406s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-interpro took 1.654975414276123s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.000118255615234375s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.13783597946166992s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.021173477172851562s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 0.00010991096496582031s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-iproclass took 2.0461807250976562s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 9.560585021972656e-05s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.16370058059692383s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.02133464813232422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.177757263183594e-05s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1.7057116031646729s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.0001621246337890625s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.15254878997802734s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.021257877349853516s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.337860107421875e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 9.775161743164062e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 1.7294275760650635s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 4.458427429199219e-05s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.16893768310546875s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.0214691162109375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 4.38690185546875e-05s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-lsr took 1.81874418258667s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 4.506111145019531e-05s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.00022530555725097656s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.10757255554199219s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.02127671241760254s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.05718994140625e-05s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-mesh took 1.3194680213928223s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 4.696846008300781e-05s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.11994576454162598s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.022771835327148438s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.298324584960938e-05s
Believability | Calculation of trust value for Bio2RDF::Mgi took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-mgi took 1.7438058853149414s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 7.748603820800781e-05s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.13502001762390137s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.022438526153564453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00011134147644042969s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 2.1594045162200928s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.00018858909606933594s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.1668994426727295s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.021553754806518555s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.57763671875e-05s
Believability | Calculation of trust value for Bio2RDF::Ndc took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-ndc took 1.7192065715789795s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 5.364418029785156e-05s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.10483646392822266s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.022851228713989258s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.147125244140625e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-nextprot took 1.6805627346038818s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.00018548965454101562s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.13082456588745117s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.021015644073486328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00012636184692382812s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-omim took 1.511629343032837s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 0.00017642974853515625s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.13016796112060547s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.02139449119567871s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.3392181396484375e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 1.5532457828521729s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 9.799003601074219e-05s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.1709902286529541s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02133631706237793s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.034706115722656e-05s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-orphanet took 2.1276681423187256s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 9.512901306152344e-05s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0002167224884033203s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.15590238571166992s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.021127700805664062s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.266334533691406e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-pathwaycommons took 1.8251948356628418s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 9.918212890625e-05s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.1564624309539795s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.021090984344482422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.271766662597656e-05s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 1.8501501083374023s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 4.673004150390625e-05s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.14832234382629395s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.021500110626220703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00013327598571777344s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1.5036089420318604s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 9.632110595703125e-05s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.16365742683410645s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.021929025650024414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.796287536621094e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-sabiork took 1.6527972221374512s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 6.29425048828125e-05s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.11346602439880371s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.02149057388305664s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010395050048828125s
Believability | Calculation of trust value for Bio2RDF::Sgd took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-sgd took 1.6105811595916748s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.6253204345703125e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.13364863395690918s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.02118825912475586s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.719329833984375e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 1.5111515522003174s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 4.76837158203125e-05s
Availability | VoID file availability check for Bio2RDF::Sider took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.1483781337738037s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.0210268497467041s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 3.9577484130859375e-05s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.4066696166992188e-05s
INFO | --- Analysis for bio2rdf-sider took 1.535944938659668s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 9.751319885253906e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.14856863021850586s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.021329164505004883s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.410743713378906e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-taxon took 1.5513460636138916s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 9.751319885253906e-05s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.13660788536071777s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.021064281463623047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010013580322265625s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 1.5671348571777344s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 4.673004150390625e-05s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.15701818466186523s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.021275758743286133s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 1.8808338642120361s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 9.608268737792969e-05s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.00039887428283691406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.11520934104919434s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.02136063575744629s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.106231689453125e-05s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-wormbase took 1.696434497833252s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 4.744529724121094e-05s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.13005781173706055s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.023514986038208008s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.535385131835938e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 1.4066696166992188e-05s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 1.6324312686920166s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 9.584426879882812e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0004076957702636719s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.16643333435058594s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.021514177322387695s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.38690185546875e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.4066696166992188e-05s
INFO | --- Analysis for biolod-pdb took 1.5327987670898438s
Availability | SPARQL endpoint availability check for BioModels RDF took 9.322166442871094e-05s
Availability | VoID file availability check for BioModels RDF took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.13596200942993164s
Reputation | Calculation of the PageRank for BioModels RDF took 0.021471500396728516s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 4.00543212890625e-05s
Believability | Calculation of trust value for BioModels RDF took 1.2636184692382812e-05s
INFO | --- Analysis for biomodels-rdf took 1.560863971710205s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.744529724121094e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.14377856254577637s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.021837949752807617s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.314018249511719e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 8.106231689453125e-06s
INFO | --- Analysis for Biop took 2.2649362087249756s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.00011682510375976562s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.3309903144836426s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.021338224411010742s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.743171691894531e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.2636184692382812e-05s
INFO | --- Analysis for Bioportal took 3.524953842163086s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.9591064453125e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.3241300582885742s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.021132946014404297s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006351470947265625s
Believability | Calculation of trust value for Amphibian gross anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-aao took 3.3295698165893555s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 5.6743621826171875e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.32704710960388184s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.021824121475219727s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0011768341064453125s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00041556358337402344s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-aba took 3.2933926582336426s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 0.0001239776611328125s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.3242759704589844s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.02151346206665039s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015025138854980469s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-acgt took 3.319932699203491s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.887580871582031e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.29601120948791504s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.021384000778198242s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.00032329559326171875s
Believability | Calculation of trust value for Animal natural history and life history took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-adw took 3.014270544052124s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 0.00016880035400390625s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.28684473037719727s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.021152257919311523s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004813671112060547s
Believability | Calculation of trust value for Anatomical Entity Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-aeo took 3.1588568687438965s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 0.00010275840759277344s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.3315720558166504s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.02147078514099121s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009777545928955078s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-aero took 3.517274856567383s
Availability | SPARQL endpoint availability check for AI/RHEUM took 9.942054748535156e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.3407740592956543s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.02126932144165039s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.00040912628173828125s
Believability | Calculation of trust value for AI/RHEUM took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-air took 3.1378228664398193s
Availability | SPARQL endpoint availability check for Amino Acid took 5.030632019042969e-05s
Availability | VoID file availability check for Amino Acid took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.34497737884521484s
Reputation | Calculation of the PageRank for Amino Acid took 0.02152395248413086s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00025725364685058594s
Believability | Calculation of trust value for Amino Acid took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-amino-acid took 3.1549875736236572s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 5.078315734863281e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.32457637786865234s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.021146297454833984s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.00028967857360839844s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-apo took 3.0002689361572266s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 0.00010609626770019531s
Availability | VoID file availability check for African Traditional Medicine took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.3002281188964844s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020937681198120117s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00026798248291015625s
Believability | Calculation of trust value for African Traditional Medicine took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-atmo took 3.1895172595977783s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 5.125999450683594e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.301039457321167s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.02120494842529297s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.369850158691406e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ato took 3.0550537109375s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 0.00011038780212402344s
Availability | VoID file availability check for BioAssay Ontology took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.2747223377227783s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.02113819122314453s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013170242309570312s
Believability | Calculation of trust value for BioAssay Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bao took 3.1730971336364746s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 0.0001049041748046875s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.3002755641937256s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.02229142189025879s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003826618194580078s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 3.497548818588257s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 0.00017380714416503906s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.5185844898223877s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.021350383758544922s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003216266632080078s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bcgo took 3.4164950847625732s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 0.000110626220703125s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.3001384735107422s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.021155118942260742s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0013566017150878906s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bdo took 3.372028350830078s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 0.00010728836059570312s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.3132030963897705s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.021591901779174805s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005002021789550781s
Believability | Calculation of trust value for Basic Formal Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bfo took 3.143348217010498s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 0.00017714500427246094s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.3341944217681885s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.021193504333496094s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007753372192382812s
Believability | Calculation of trust value for Bleeding History Phenotype took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-bho took 3.0961039066314697s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 5.0067901611328125e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.34095144271850586s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.022770404815673828s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004863739013671875s
Believability | Calculation of trust value for Bilateria anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bila took 3.1115610599517822s
Availability | SPARQL endpoint availability check for BIRNLex took 9.679794311523438e-05s
Availability | VoID file availability check for BIRNLex took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.3480713367462158s
Reputation | Calculation of the PageRank for BIRNLex took 0.02191329002380371s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014910697937011719s
Believability | Calculation of trust value for BIRNLex took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-birnlex took 3.084439277648926s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 9.822845458984375e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.49802160263061523s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02211141586303711s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007824897766113281s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-bootstrep took 3.2568488121032715s
Availability | SPARQL endpoint availability check for BioPAX took 4.982948303222656e-05s
Availability | VoID file availability check for BioPAX took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for BioPAX took 0.3367464542388916s
Reputation | Calculation of the PageRank for BioPAX took 0.02153491973876953s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.00010180473327636719s
Believability | Calculation of trust value for BioPAX took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bp took 3.211214780807495s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 5.054473876953125e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.30396461486816406s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.0222322940826416s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0009868144989013672s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0004355907440185547s
Believability | Calculation of trust value for Biomedical Resource Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-bro_x1 took 3.225959539413452s
Availability | SPARQL endpoint availability check for Spatial Ontology took 0.00016260147094726562s
Availability | VoID file availability check for Spatial Ontology took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.30698084831237793s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020842552185058594s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00021791458129882812s
Believability | Calculation of trust value for Spatial Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bspo took 3.113354444503784s
Availability | SPARQL endpoint availability check for BioTop took 0.00010037422180175781s
Availability | VoID file availability check for BioTop took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for BioTop took 0.3350191116333008s
Reputation | Calculation of the PageRank for BioTop took 0.02137136459350586s
Interlinking | Calculation of Degree of Connection for BioTop took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006515979766845703s
Believability | Calculation of trust value for BioTop took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bt took 3.1480939388275146s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.9114227294921875e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.2920808792114258s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.02113175392150879s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008747577667236328s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-bto took 3.0479726791381836s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 0.00010418891906738281s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3750629425048828s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.021205425262451172s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0017840862274169922s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-canco took 3.71962571144104s
Availability | SPARQL endpoint availability check for CAO took 9.870529174804688e-05s
Availability | VoID file availability check for CAO took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for CAO took 0.2962155342102051s
Reputation | Calculation of the PageRank for CAO took 0.028197050094604492s
Interlinking | Calculation of Degree of Connection for CAO took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for CAO took 0.0012443065643310547s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0007367134094238281s
Believability | Calculation of trust value for CAO took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-cao took 3.4655280113220215s
Availability | SPARQL endpoint availability check for CareLex took 5.1021575927734375e-05s
Availability | VoID file availability check for CareLex took 0.0007631778717041016s
Completeness | Calculation of interlinking completeness for CareLex took 0.293529748916626s
Reputation | Calculation of the PageRank for CareLex took 0.021405935287475586s
Interlinking | Calculation of Degree of Connection for CareLex took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.2928924560546875e-05s
Believability | Calculation of trust value for CareLex took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-carelex took 3.4644742012023926s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 5.078315734863281e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.32825303077697754s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.02106189727783203s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0008115768432617188s
Believability | Calculation of trust value for Cell Cycle Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cco took 3.1585566997528076s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 0.00013494491577148438s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.31830573081970215s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020898818969726562s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0002598762512207031s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-cdao took 3.1151416301727295s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 5.030632019042969e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.39787888526916504s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020772933959960938s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0008940696716308594s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008058547973632812s
Believability | Calculation of trust value for Chemical entities of biological interest took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-chebi took 3.3024308681488037s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.696846008300781e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.5296115875244141s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.021243810653686523s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002703666687011719s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-chem2bio2owl took 3.3519675731658936s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 0.0001876354217529297s
Availability | VoID file availability check for Chemical Information Ontology took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.28305912017822266s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.02120065689086914s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007810592651367188s
Believability | Calculation of trust value for Chemical Information Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cheminf took 3.010145664215088s
Availability | SPARQL endpoint availability check for Cell type took 0.0002384185791015625s
Availability | VoID file availability check for Cell type took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for Cell type took 0.3390185832977295s
Reputation | Calculation of the PageRank for Cell type took 0.02147674560546875s
Interlinking | Calculation of Degree of Connection for Cell type took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cell type took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003821849822998047s
Believability | Calculation of trust value for Cell type took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-cl took 3.3475818634033203s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 0.00016689300537109375s
Availability | VoID file availability check for Cell Line Ontology took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.3024258613586426s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.022530317306518555s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008018016815185547s
Believability | Calculation of trust value for Cell Line Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-clo took 3.139608860015869s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 0.00017905235290527344s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.2768673896789551s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020909786224365234s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00017523765563964844s
Believability | Calculation of trust value for Clinical Measurement Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cmo took 3.2380692958831787s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 6.699562072753906e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.31874608993530273s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.021877765655517578s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.000217437744140625s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-cno took 3.4840352535247803s
Availability | SPARQL endpoint availability check for Wheat trait took 5.340576171875e-05s
Availability | VoID file availability check for Wheat trait took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.3176994323730469s
Reputation | Calculation of the PageRank for Wheat trait took 0.021563291549682617s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.602836608886719e-05s
Believability | Calculation of trust value for Wheat trait took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-co_wheat took 3.5726099014282227s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 5.459785461425781e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.2809872627258301s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020969629287719727s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.00034618377685546875s
Believability | Calculation of trust value for Cognitive Atlas took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-cogat took 3.323225736618042s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 6.222724914550781e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.00030303001403808594s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.33381199836730957s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.02086949348449707s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007545948028564453s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cogpo took 3.118931293487549s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 0.00010156631469726562s
Availability | VoID file availability check for Current Procedural Terminology took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.2856619358062744s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.022502899169921875s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004582405090332031s
Believability | Calculation of trust value for Current Procedural Terminology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-cpt took 3.0627849102020264s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 0.00010395050048828125s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.35358285903930664s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.021376609802246094s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017604827880859375s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-csp took 3.868537664413452s
Availability | SPARQL endpoint availability check for COSTART took 0.00015044212341308594s
Availability | VoID file availability check for COSTART took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for COSTART took 0.37180614471435547s
Reputation | Calculation of the PageRank for COSTART took 0.02123713493347168s
Interlinking | Calculation of Degree of Connection for COSTART took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009663105010986328s
Believability | Calculation of trust value for COSTART took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cst took 3.577371835708618s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 0.00010371208190917969s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.2845885753631592s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.022017955780029297s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.00119781494140625s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0006542205810546875s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-ctcae took 3.2045834064483643s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 0.0001957416534423828s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.33391523361206055s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.02110004425048828s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0008409023284912109s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004458427429199219s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ctx took 3.169987916946411s
Availability | SPARQL endpoint availability check for Dendritic cell took 0.00020742416381835938s
Availability | VoID file availability check for Dendritic cell took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.34789180755615234s
Reputation | Calculation of the PageRank for Dendritic cell took 0.021310091018676758s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00028896331787109375s
Believability | Calculation of trust value for Dendritic cell took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-dc_cl took 3.158019781112671s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.7206878662109375e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.3318145275115967s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02149796485900879s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 9.179115295410156e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ddanat took 3.2395403385162354s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 0.00010347366333007812s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.2638719081878662s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.021081209182739258s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009777545928955078s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ddi took 3.2174975872039795s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 0.0001857280731201172s
Availability | VoID file availability check for Diagnostic Ontology took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.32646799087524414s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.021013259887695312s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.654594421386719e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-diagnosticont took 3.059774398803711s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 0.00016379356384277344s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.28728461265563965s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.021342754364013672s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.0001614093780517578s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-dikb-evidence took 3.1905789375305176s
Availability | SPARQL endpoint availability check for Human disease ontology took 7.891654968261719e-05s
Availability | VoID file availability check for Human disease ontology took 0.0008678436279296875s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2993009090423584s
Reputation | Calculation of the PageRank for Human disease ontology took 0.0213775634765625s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006778240203857422s
Believability | Calculation of trust value for Human disease ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-doid took 3.033919334411621s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 0.0001010894775390625s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.353564977645874s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.02104926109313965s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008161067962646484s
Believability | Calculation of trust value for Electrocardiography Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ecg took 3.035543918609619s
Availability | SPARQL endpoint availability check for Evidence codes took 4.863739013671875e-05s
Availability | VoID file availability check for Evidence codes took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.4813880920410156s
Reputation | Calculation of the PageRank for Evidence codes took 0.021176815032958984s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0008177757263183594s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.695487976074219e-05s
Believability | Calculation of trust value for Evidence codes took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-eco took 3.187032699584961s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 0.0001785755157470703s
Availability | VoID file availability check for Experimental Factor Ontology took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3747272491455078s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.02124762535095215s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017304420471191406s
Believability | Calculation of trust value for Experimental Factor Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-efo took 3.6026976108551025s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 6.508827209472656e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.2737600803375244s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020743370056152344s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011425018310546875s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ehda took 3.099905490875244s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 5.245208740234375e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.33099889755249023s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.021294832229614258s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0008215904235839844s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007450580596923828s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ehdaa took 3.3695530891418457s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.9591064453125e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0008001327514648438s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.30678582191467285s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.023879051208496094s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.001440286636352539s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0006940364837646484s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ehdaa2 took 3.111001491546631s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 0.00010204315185546875s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.33400988578796387s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.021269559860229492s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.2901763916015625e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-emap took 3.208156108856201s
Availability | SPARQL endpoint availability check for Environment Ontology took 6.389617919921875e-05s
Availability | VoID file availability check for Environment Ontology took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.3287224769592285s
Reputation | Calculation of the PageRank for Environment Ontology took 0.02129507064819336s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0004048347473144531s
Believability | Calculation of trust value for Environment Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-envo took 3.3881585597991943s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 0.00010204315185546875s
Availability | VoID file availability check for Plant environmental conditions took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.322676420211792s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.021042585372924805s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0002956390380859375s
Believability | Calculation of trust value for Plant environmental conditions took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-eo took 3.1994454860687256s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 9.894371032714844e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.31879734992980957s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.021146535873413086s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.001249551773071289s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ep took 3.08561372756958s
Availability | SPARQL endpoint availability check for Epilepsy took 9.775161743164062e-05s
Availability | VoID file availability check for Epilepsy took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.3211226463317871s
Reputation | Calculation of the PageRank for Epilepsy took 0.021620512008666992s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001277923583984375s
Believability | Calculation of trust value for Epilepsy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-epileponto took 3.1872270107269287s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 0.00011396408081054688s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.36378979682922363s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.02110004425048828s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.001169443130493164s
Believability | Calculation of trust value for eagle-i research resource ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ero took 3.3085670471191406s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 5.054473876953125e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.36398887634277344s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.021296262741088867s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011429786682128906s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ev took 3.2898128032684326s
Availability | SPARQL endpoint availability check for ExO took 9.751319885253906e-05s
Availability | VoID file availability check for ExO took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for ExO took 0.3327178955078125s
Reputation | Calculation of the PageRank for ExO took 0.021405696868896484s
Interlinking | Calculation of Degree of Connection for ExO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00025343894958496094s
Believability | Calculation of trust value for ExO took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-exo took 3.4305739402770996s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 0.00015592575073242188s
Availability | VoID file availability check for Fungal gross anatomy took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.44798827171325684s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.02117013931274414s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011348724365234375s
Believability | Calculation of trust value for Fungal gross anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-fao took 3.207413911819458s
Availability | SPARQL endpoint availability check for Biological imaging methods took 5.030632019042969e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.35358381271362305s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.021344423294067383s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.0002014636993408203s
Believability | Calculation of trust value for Biological imaging methods took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-fbbi took 3.4192163944244385s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 0.0001049041748046875s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.29328250885009766s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.02185511589050293s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006694793701171875s
Believability | Calculation of trust value for Drosophila gross anatomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-fbbt took 3.772033452987671s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 0.00012564659118652344s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.35289931297302246s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.022791624069213867s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004184246063232422s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-fbcv took 3.272277593612671s
Availability | SPARQL endpoint availability check for Drosophila development took 0.00010228157043457031s
Availability | VoID file availability check for Drosophila development took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.5208585262298584s
Reputation | Calculation of the PageRank for Drosophila development took 0.022572040557861328s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.76837158203125e-05s
Believability | Calculation of trust value for Drosophila development took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-fbdv took 3.4063637256622314s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.863739013671875e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.3155834674835205s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.022552490234375s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0004010200500488281s
Believability | Calculation of trust value for Fly taxonomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-fbsp took 3.3980138301849365s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 0.00011086463928222656s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.29421305656433105s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.022732257843017578s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0009262561798095703s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00023126602172851562s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 3.138876438140869s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 0.00010633468627929688s
Availability | VoID file availability check for Family Health History Ontology took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.3034536838531494s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.021430253982543945s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0003952980041503906s
Believability | Calculation of trust value for Family Health History Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-fhho took 3.3697080612182617s
Availability | SPARQL endpoint availability check for Influenza Ontology took 0.00010991096496582031s
Availability | VoID file availability check for Influenza Ontology took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.33484315872192383s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.02218484878540039s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.001081705093383789s
Believability | Calculation of trust value for Influenza Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-flu took 3.2102954387664795s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 0.00011396408081054688s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.3022880554199219s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020944833755493164s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.508827209472656e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-fma took 3.071397304534912s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 0.00010085105895996094s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.3341670036315918s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.02114415168762207s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00013947486877441406s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-fypo took 3.1662073135375977s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 0.00010204315185546875s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.30654168128967285s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.02200460433959961s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.001026153564453125s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 0.0001285076141357422s
Believability | Calculation of trust value for GeoSpecies Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-geospecies took 3.1693825721740723s
Availability | SPARQL endpoint availability check for General Formal Ontology took 0.00010418891906738281s
Availability | VoID file availability check for General Formal Ontology took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.3224942684173584s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.021182775497436523s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016450881958007812s
Believability | Calculation of trust value for General Formal Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gfo took 3.1087474822998047s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.8160552978515625e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.2897830009460449s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020892858505249023s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006186962127685547s
Believability | Calculation of trust value for General Formal Ontology: Biology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-gfo-bio took 3.3129944801330566s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 0.0001163482666015625s
Availability | VoID file availability check for Gene Ontology Extension took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.32588648796081543s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.02272772789001465s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0009582042694091797s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0009429454803466797s
Believability | Calculation of trust value for Gene Ontology Extension took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-go_x1 took 3.3194072246551514s
Availability | SPARQL endpoint availability check for Gene Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Gene Ontology took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.3611583709716797s
Reputation | Calculation of the PageRank for Gene Ontology took 0.02189350128173828s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008635520935058594s
Believability | Calculation of trust value for Gene Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-go_x2 took 3.4699416160583496s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 0.00010180473327636719s
Availability | VoID file availability check for Cereal Plant Development took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.29794740676879883s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.021027803421020508s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.1948089599609375e-05s
Believability | Calculation of trust value for Cereal Plant Development took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-gro took 3.22855281829834s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 0.00015997886657714844s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.2879190444946289s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.02127861976623535s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004627704620361328s
Believability | Calculation of trust value for Cereal plant gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-gro_x1 took 3.4904568195343018s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 0.00010275840759277344s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.3150355815887451s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02107858657836914s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007853507995605469s
Believability | Calculation of trust value for Gene Regulation Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-gro_x2 took 3.344233751296997s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 0.00010085105895996094s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.3323328495025635s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020903825759887695s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005764961242675781s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-hao took 3.4573755264282227s
Availability | SPARQL endpoint availability check for HCPCS took 5.364418029785156e-05s
Availability | VoID file availability check for HCPCS took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for HCPCS took 0.3152482509613037s
Reputation | Calculation of the PageRank for HCPCS took 0.02215409278869629s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00023889541625976562s
Believability | Calculation of trust value for HCPCS took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-hcpcs took 3.3471381664276123s
Availability | SPARQL endpoint availability check for Health Level Seven took 5.340576171875e-05s
Availability | VoID file availability check for Health Level Seven took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.341141939163208s
Reputation | Calculation of the PageRank for Health Level Seven took 0.021198511123657227s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0013432502746582031s
Believability | Calculation of trust value for Health Level Seven took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-hl7 took 3.464353322982788s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 0.00010061264038085938s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.26349401473999023s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.02124309539794922s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00034689903259277344s
Believability | Calculation of trust value for HEALTH_INDICATORS took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-hlth_indics took 3.226386070251465s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 0.00010013580322265625s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.3351311683654785s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.0228421688079834s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 3.0279159545898438e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.001294851303100586s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 4.839897155761719e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-hom took 3.237351655960083s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 5.555152893066406e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.3049280643463135s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.021584272384643555s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.552436828613281e-05s
Believability | Calculation of trust value for HOM-HARVARD took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-hom_harvard took 3.15675687789917s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 0.00011038780212402344s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.3603348731994629s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.021475553512573242s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006473064422607422s
Believability | Calculation of trust value for Human Phenotype Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-hp_x1 took 3.2740836143493652s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 5.245208740234375e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.34778261184692383s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.021218538284301758s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010678768157958984s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-hpio took 3.1810691356658936s
Availability | SPARQL endpoint availability check for HUGO took 0.00010633468627929688s
Availability | VoID file availability check for HUGO took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for HUGO took 0.3339111804962158s
Reputation | Calculation of the PageRank for HUGO took 0.02136850357055664s
Interlinking | Calculation of Degree of Connection for HUGO took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for HUGO took 8.034706115722656e-05s
Believability | Calculation of trust value for HUGO took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-hugo took 3.3069796562194824s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 9.751319885253906e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.32977843284606934s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.02104926109313965s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006439685821533203s
Believability | Calculation of trust value for Information Artifact Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-iao took 3.431765079498291s
Availability | SPARQL endpoint availability check for ICD10 took 0.00010132789611816406s
Availability | VoID file availability check for ICD10 took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for ICD10 took 0.29204511642456055s
Reputation | Calculation of the PageRank for ICD10 took 0.022057056427001953s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0007898807525634766s
Believability | Calculation of trust value for ICD10 took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-icd10 took 3.048100709915161s
Availability | SPARQL endpoint availability check for ICD10CM took 5.078315734863281e-05s
Availability | VoID file availability check for ICD10CM took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.5845589637756348s
Reputation | Calculation of the PageRank for ICD10CM took 0.021197080612182617s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0005881786346435547s
Believability | Calculation of trust value for ICD10CM took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-icd10cm took 3.544877290725708s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 0.00015664100646972656s
Availability | VoID file availability check for ICD-10-PCS took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.29363036155700684s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.021088838577270508s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00015974044799804688s
Believability | Calculation of trust value for ICD-10-PCS took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-icd10pcs took 3.435534954071045s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 9.655952453613281e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.3048884868621826s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.021540164947509766s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0007257461547851562s
Believability | Calculation of trust value for International Classification of Diseases took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-icd9cm took 3.2497355937957764s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 9.965896606445312e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.33546018600463867s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.021642208099365234s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.00046944618225097656s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-icf_x1 took 3.1683905124664307s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 0.00010156631469726562s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.32868123054504395s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.021050214767456055s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012238025665283203s
Believability | Calculation of trust value for International Classification for Nursing Practice took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-icnp took 3.227783679962158s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 0.00010180473327636719s
Availability | VoID file availability check for International Classification of Primary Care took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.3622722625732422s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.0211029052734375s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.000980377197265625s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.00045228004455566406s
Believability | Calculation of trust value for International Classification of Primary Care took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-icpc took 3.351475954055786s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 0.00011849403381347656s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.3067922592163086s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.02107071876525879s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.000858306884765625s
Believability | Calculation of trust value for ICPC-2 PLUS took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-icpc2p took 3.411098003387451s
Availability | SPARQL endpoint availability check for ICPS Network took 9.775161743164062e-05s
Availability | VoID file availability check for ICPS Network took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.5429511070251465s
Reputation | Calculation of the PageRank for ICPS Network took 0.0212552547454834s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00023555755615234375s
Believability | Calculation of trust value for ICPS Network took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-icps took 3.3147149085998535s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 0.00010943412780761719s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.30437207221984863s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.021012544631958008s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008487701416015625s
Believability | Calculation of trust value for Infectious Disease Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ido took 3.1086859703063965s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 0.00010323524475097656s
Availability | VoID file availability check for Brucellosis Ontology took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2904951572418213s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.02234673500061035s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0010981559753417969s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0013551712036132812s
Believability | Calculation of trust value for Brucellosis Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-idobru took 3.2496535778045654s
Availability | SPARQL endpoint availability check for Malaria Ontology took 0.00010275840759277344s
Availability | VoID file availability check for Malaria Ontology took 0.0009093284606933594s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.29976868629455566s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.02117443084716797s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.001260995864868164s
Believability | Calculation of trust value for Malaria Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-idomal took 3.5125906467437744s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 0.00011682510375976562s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.2750387191772461s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.02252340316772461s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003910064697265625s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-iev took 3.235957145690918s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 0.0001289844512939453s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.321209192276001s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.021196842193603516s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0009598731994628906s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00022172927856445312s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-imgt took 3.1798934936523438s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.649162292480469e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.3434157371520996s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.0213010311126709s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005316734313964844s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-imr took 3.2961654663085938s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 0.00011515617370605469s
Availability | VoID file availability check for Interaction Network Ontology took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.32761716842651367s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.021013736724853516s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0008676052093505859s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007963180541992188s
Believability | Calculation of trust value for Interaction Network Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ino took 3.1435658931732178s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.935264587402344e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2982351779937744s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.021992921829223633s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 6.365776062011719e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-invertebrata took 3.069796085357666s
Availability | SPARQL endpoint availability check for IxnO took 9.918212890625e-05s
Availability | VoID file availability check for IxnO took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for IxnO took 0.33933424949645996s
Reputation | Calculation of the PageRank for IxnO took 0.02136826515197754s
Interlinking | Calculation of Degree of Connection for IxnO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.000194549560546875s
Believability | Calculation of trust value for IxnO took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ixno took 3.1151983737945557s
Availability | SPARQL endpoint availability check for SysMO-JERM took 0.00011396408081054688s
Availability | VoID file availability check for SysMO-JERM took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.30236077308654785s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.022100210189819336s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.00038909912109375s
Believability | Calculation of trust value for SysMO-JERM took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-jerm took 2.9976587295532227s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 5.245208740234375e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.311281681060791s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.021704912185668945s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.62396240234375e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-kisao took 3.145921468734741s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 9.560585021972656e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.30013275146484375s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.021893024444580078s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00019621849060058594s
Believability | Calculation of trust value for Loggerhead nesting took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-lhn took 3.1033499240875244s
Availability | SPARQL endpoint availability check for Lipid Ontology took 0.00010085105895996094s
Availability | VoID file availability check for Lipid Ontology took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.3200056552886963s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.022023439407348633s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00019598007202148438s
Believability | Calculation of trust value for Lipid Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-lipro took 3.6062474250793457s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 9.870529174804688e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.3754863739013672s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.02102971076965332s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.001834869384765625s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-lnc took 3.4690802097320557s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 9.846687316894531e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.28738927841186523s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.021114826202392578s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006463527679443359s
Believability | Calculation of trust value for Mouse adult gross anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ma took 3.0387463569641113s
Availability | SPARQL endpoint availability check for Multiple alignment took 0.00010228157043457031s
Availability | VoID file availability check for Multiple alignment took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.3727874755859375s
Reputation | Calculation of the PageRank for Multiple alignment took 0.021187782287597656s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00020742416381835938s
Believability | Calculation of trust value for Multiple alignment took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mao took 3.328922986984253s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 0.00010395050048828125s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2893178462982178s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020814180374145508s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006926059722900391s
Believability | Calculation of trust value for Minimal anatomical terminology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mat took 3.080873727798462s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 9.679794311523438e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.343289852142334s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020972490310668945s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.00042557716369628906s
Believability | Calculation of trust value for Breast tissue cell lines took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mcbcc took 3.0178940296173096s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.9114227294921875e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.5232877731323242s
Reputation | Calculation of the PageRank for Cell line ontology took 0.021207332611083984s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007548332214355469s
Believability | Calculation of trust value for Cell line ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mccl took 3.9241976737976074s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Cell line ontology took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2846810817718506s
Reputation | Calculation of the PageRank for Cell line ontology took 0.021608352661132812s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0013856887817382812s
Believability | Calculation of trust value for Cell line ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 3.143951892852783s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 5.2928924560546875e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.370455265045166s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.021083593368530273s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002613067626953125s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mcv took 3.239877939224243s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 0.00010085105895996094s
Availability | VoID file availability check for Master Drug Data Base took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.35816144943237305s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.022748470306396484s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00020265579223632812s
Believability | Calculation of trust value for Master Drug Data Base took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mddb took 3.0514578819274902s
Availability | SPARQL endpoint availability check for MedDRA took 4.982948303222656e-05s
Availability | VoID file availability check for MedDRA took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for MedDRA took 0.5460319519042969s
Reputation | Calculation of the PageRank for MedDRA took 0.02068614959716797s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011065006256103516s
Believability | Calculation of trust value for MedDRA took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mdr took 3.473452568054199s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 9.799003601074219e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.32411623001098633s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.021936893463134766s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008733272552490234s
Believability | Calculation of trust value for MedlinePlus Health Topics took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-medlineplus took 3.173818349838257s
Availability | SPARQL endpoint availability check for MeGO took 0.00012135505676269531s
Availability | VoID file availability check for MeGO took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for MeGO took 0.28566837310791016s
Reputation | Calculation of the PageRank for MeGO took 0.02122354507446289s
Interlinking | Calculation of Degree of Connection for MeGO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.0001437664031982422s
Believability | Calculation of trust value for MeGO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mego took 3.2022995948791504s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 0.0001533031463623047s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0007691383361816406s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.3636465072631836s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.02184605598449707s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018198490142822266s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-mesh-owl took 3.67260479927063s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 5.435943603515625e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.29428935050964355s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.02112579345703125s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006198883056640625s
Believability | Calculation of trust value for Mental Functioning Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mf took 3.0403549671173096s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 0.00015807151794433594s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.29732728004455566s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.021637439727783203s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005393028259277344s
Believability | Calculation of trust value for Medaka fish anatomy and development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mfo took 3.2076523303985596s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.887580871582031e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.29557347297668457s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.036603689193725586s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 2.574920654296875e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.002223968505859375s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0010068416595458984s
Believability | Calculation of trust value for Emotion Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mfoem took 3.003648519515991s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.9591064453125e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.3467569351196289s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.021398067474365234s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00011444091796875s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-mhc took 3.7849926948547363s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 5.125999450683594e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.29555201530456543s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020870447158813477s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006740093231201172s
Believability | Calculation of trust value for Protein-protein interaction took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mi took 3.1132280826568604s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 0.00016546249389648438s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.39626073837280273s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.021316051483154297s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007174015045166016s
Believability | Calculation of trust value for Mosquito insecticide resistance took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-miro took 3.1729469299316406s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 0.000118255615234375s
Availability | VoID file availability check for Measurement Method Ontology took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.31394028663635254s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020984411239624023s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00014495849609375s
Believability | Calculation of trust value for Measurement Method Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mmo took 3.1332333087921143s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.76837158203125e-05s
Availability | VoID file availability check for MGED Ontology took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.4612727165222168s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020929574966430664s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003936290740966797s
Believability | Calculation of trust value for MGED Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-mo took 3.4653046131134033s
Availability | SPARQL endpoint availability check for Protein modification took 9.942054748535156e-05s
Availability | VoID file availability check for Protein modification took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for Protein modification took 0.34051036834716797s
Reputation | Calculation of the PageRank for Protein modification took 0.02130889892578125s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002300739288330078s
Believability | Calculation of trust value for Protein modification took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-mod took 3.0151619911193848s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 5.1021575927734375e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.3675556182861328s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.02093791961669922s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006515979766845703s
Believability | Calculation of trust value for Mammalian phenotype took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mp took 3.058997869491577s
Availability | SPARQL endpoint availability check for Mouse pathology took 0.00010395050048828125s
Availability | VoID file availability check for Mouse pathology took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.3282790184020996s
Reputation | Calculation of the PageRank for Mouse pathology took 0.021042823791503906s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.00047016143798828125s
Believability | Calculation of trust value for Mouse pathology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mpath took 3.1493563652038574s
Availability | SPARQL endpoint availability check for Mass spectrometry took 0.00010776519775390625s
Availability | VoID file availability check for Mass spectrometry took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.3443892002105713s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.02392721176147461s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0012578964233398438s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0005002021789550781s
Believability | Calculation of trust value for Mass spectrometry took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ms took 3.332927942276001s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 9.72747802734375e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.3682386875152588s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.02288222312927246s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018525123596191406s
Believability | Calculation of trust value for Medical Subject Headings took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-msh took 3.890289783477783s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 0.00015997886657714844s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2709369659423828s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.02114725112915039s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00018024444580078125s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-mthch took 3.1292002201080322s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.37066102027893066s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.022234439849853516s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007836818695068359s
Believability | Calculation of trust value for Natural Products Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-natpro took 3.441149950027466s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.935264587402344e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2900710105895996s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.02116680145263672s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.00081634521484375s
Believability | Calculation of trust value for NCBI organismal classification took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 3.268930673599243s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 0.00010251998901367188s
Availability | VoID file availability check for NCI Thesaurus took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.3673553466796875s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.002035856246948242s
Believability | Calculation of trust value for NCI Thesaurus took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ncit took 3.5375449657440186s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.887580871582031e-05s
Availability | VoID file availability check for National Drug Data File took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.30225133895874023s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02109670639038086s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006067752838134766s
Believability | Calculation of trust value for National Drug Data File took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-nddf took 3.147371292114258s
Availability | SPARQL endpoint availability check for National Drug File took 9.655952453613281e-05s
Availability | VoID file availability check for National Drug File took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for National Drug File took 0.3432180881500244s
Reputation | Calculation of the PageRank for National Drug File took 0.02175617218017578s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012755393981933594s
Believability | Calculation of trust value for National Drug File took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ndfrt took 3.2383129596710205s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 9.775161743164062e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.3354651927947998s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.021024703979492188s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011646747589111328s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 3.219302177429199s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 0.0001068115234375s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.30751800537109375s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.021549224853515625s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006763935089111328s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-neomark took 3.184161901473999s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.935264587402344e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.2973926067352295s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.021001338958740234s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00012135505676269531s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-neomarkontology took 3.1281237602233887s
Availability | SPARQL endpoint availability check for NIFSTD took 4.982948303222656e-05s
Availability | VoID file availability check for NIFSTD took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.38033604621887207s
Reputation | Calculation of the PageRank for NIFSTD took 0.0212862491607666s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0019071102142333984s
Believability | Calculation of trust value for NIFSTD took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nif took 3.66497540473938s
Availability | SPARQL endpoint availability check for NIF Cell took 4.744529724121094e-05s
Availability | VoID file availability check for NIF Cell took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.31542444229125977s
Reputation | Calculation of the PageRank for NIF Cell took 0.021895885467529297s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.001325368881225586s
Believability | Calculation of trust value for NIF Cell took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-nif_cell took 3.2095184326171875s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 9.72747802734375e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.3268156051635742s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.021218538284301758s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0008533000946044922s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.001436471939086914s
Believability | Calculation of trust value for NIF Dysfunction took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-nif_dysfunction took 3.366480827331543s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 9.799003601074219e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.29640674591064453s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.022345542907714844s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0006062984466552734s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nigo took 3.304771661758423s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 9.655952453613281e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.30490565299987793s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.021374225616455078s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005519390106201172s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nmr took 2.996129035949707s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 9.799003601074219e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.5064883232116699s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.021383047103881836s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00010895729064941406s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-nonrctontology took 3.336207628250122s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 9.512901306152344e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.26549696922302246s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.021107196807861328s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011780261993408203s
Believability | Calculation of trust value for NanoParticle Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-npo took 2.962470054626465s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.696846008300781e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.3283505439758301s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.02132868766784668s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007417201995849609s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-oae took 3.019637107849121s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 0.00010538101196289062s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.3222019672393799s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.021524906158447266s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.001497507095336914s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 2.0503997802734375e-05s
INFO | --- Analysis for bioportal-obi took 3.122873544692993s
Availability | SPARQL endpoint availability check for OBOE took 0.00010347366333007812s
Availability | VoID file availability check for OBOE took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for OBOE took 0.31724977493286133s
Reputation | Calculation of the PageRank for OBOE took 0.021234512329101562s
Interlinking | Calculation of Degree of Connection for OBOE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011420249938964844s
Believability | Calculation of trust value for OBOE took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-oboe took 3.3132870197296143s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.887580871582031e-05s
Availability | VoID file availability check for OBOE SBC took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.3472287654876709s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020809412002563477s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007796287536621094s
Believability | Calculation of trust value for OBOE SBC took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 3.275189161300659s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.6253204345703125e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.3457224369049072s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.02185511589050293s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005702972412109375s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ocre took 3.1567156314849854s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.863739013671875e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.30324530601501465s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.021227598190307617s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008461475372314453s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-odgi took 3.526127338409424s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.9114227294921875e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.35056352615356445s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020890235900878906s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008804798126220703s
Believability | Calculation of trust value for Ontology for Genetic Interval took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ogi took 3.1297781467437744s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 0.00010037422180175781s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.3402388095855713s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020925521850585938s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0002923011779785156s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ogmd took 3.0873568058013916s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 0.00010275840759277344s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.33762311935424805s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.021233320236206055s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006642341613769531s
Believability | Calculation of trust value for Ontology for General Medical Science took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ogms took 3.6132254600524902s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 0.00012421607971191406s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.630476713180542s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.0215299129486084s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011255741119384766s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-omim took 3.3567450046539307s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 9.870529174804688e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.31583309173583984s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.021028518676757812s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003745555877685547s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-omit took 3.5390427112579346s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.935264587402344e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.30925774574279785s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020932674407958984s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005922317504882812s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-omrse took 3.019270896911621s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 9.918212890625e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.3082084655761719s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.021111249923706055s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0008001327514648438s
Believability | Calculation of trust value for Ontology of Data Mining took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ontodm took 3.089489459991455s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 5.459785461425781e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.28153204917907715s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.029252290725708008s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0015506744384765625s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0004253387451171875s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-ontodt took 3.0630948543548584s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 5.5789947509765625e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.34302759170532227s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.021070003509521484s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.000598907470703125s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ontoorpha took 3.06050181388855s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 0.00010251998901367188s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.33623647689819336s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.02143073081970215s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009641647338867188s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-opl took 3.192094087600708s
Availability | SPARQL endpoint availability check for Phenotypic quality took 0.00016880035400390625s
Availability | VoID file availability check for Phenotypic quality took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.3661823272705078s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.021463871002197266s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0009171962738037109s
Believability | Calculation of trust value for Phenotypic quality took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-pato took 3.2039575576782227s
Availability | SPARQL endpoint availability check for Physician Data Query took 0.0001780986785888672s
Availability | VoID file availability check for Physician Data Query took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.32073140144348145s
Reputation | Calculation of the PageRank for Physician Data Query took 0.02205371856689453s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008490085601806641s
Believability | Calculation of trust value for Physician Data Query took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-pdq took 3.205501079559326s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 0.00016617774963378906s
Availability | VoID file availability check for Pediatric Terminology took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.3118865489959717s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.021016359329223633s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008003711700439453s
Believability | Calculation of trust value for Pediatric Terminology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-pedterm took 3.207554340362549s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 9.894371032714844e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.3425443172454834s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.021451473236083984s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00023245811462402344s
Believability | Calculation of trust value for Parasite Experiment Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-peo took 3.283155679702759s
Availability | SPARQL endpoint availability check for PHARE took 9.822845458984375e-05s
Availability | VoID file availability check for PHARE took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for PHARE took 0.2928922176361084s
Reputation | Calculation of the PageRank for PHARE took 0.021199464797973633s
Interlinking | Calculation of Degree of Connection for PHARE took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006425380706787109s
Believability | Calculation of trust value for PHARE took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-phare took 3.459129571914673s
Availability | SPARQL endpoint availability check for PKO_Re took 9.846687316894531e-05s
Availability | VoID file availability check for PKO_Re took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.3854546546936035s
Reputation | Calculation of the PageRank for PKO_Re took 0.021490812301635742s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00018858909606933594s
Believability | Calculation of trust value for PKO_Re took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-pko took 3.257915496826172s
Availability | SPARQL endpoint availability check for PMA 2010 took 0.00011014938354492188s
Availability | VoID file availability check for PMA 2010 took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.4487638473510742s
Reputation | Calculation of the PageRank for PMA 2010 took 0.022161483764648438s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009381771087646484s
Believability | Calculation of trust value for PMA 2010 took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-pma took 3.167426824569702s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 0.000102996826171875s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.31340932846069336s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.021370887756347656s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00017213821411132812s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-pmr took 3.2055718898773193s
Availability | SPARQL endpoint availability check for Plant Anatomy took 5.14984130859375e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.32222461700439453s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.023038387298583984s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.000396728515625s
Believability | Calculation of trust value for Plant Anatomy took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-po took 3.1057310104370117s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 0.00010895729064941406s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2740049362182617s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.02107095718383789s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 7.557868957519531e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-po_x1 took 3.07916522026062s
Availability | SPARQL endpoint availability check for Plant Ontology took 9.846687316894531e-05s
Availability | VoID file availability check for Plant Ontology took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.35744237899780273s
Reputation | Calculation of the PageRank for Plant Ontology took 0.02098536491394043s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.00044274330139160156s
Believability | Calculation of trust value for Plant Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-po_x2 took 3.6405506134033203s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 5.030632019042969e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.33299827575683594s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.021069049835205078s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006551742553710938s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-pr took 3.2059009075164795s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.696846008300781e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.3262772560119629s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.022065162658691406s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002579689025878906s
Believability | Calculation of trust value for Proteomics data and process provenance took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-propreo took 3.233628511428833s
Availability | SPARQL endpoint availability check for Pathway ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Pathway ontology took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.3184621334075928s
Reputation | Calculation of the PageRank for Pathway ontology took 0.022901296615600586s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.0001308917999267578s
Believability | Calculation of trust value for Pathway ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-pw took 3.2543373107910156s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 0.0001571178436279297s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.3369574546813965s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.021771669387817383s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-qibo took 3.2621243000030518s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 6.222724914550781e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3846266269683838s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02282571792602539s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017604827880859375s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-rcd took 3.9431097507476807s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.9591064453125e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.40181922912597656s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02264237403869629s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00013566017150878906s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-rctontology took 3.2270467281341553s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.863739013671875e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.2764251232147217s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.0212099552154541s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.751319885253906e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-repo took 3.060154914855957s
Availability | SPARQL endpoint availability check for Physico-chemical process took 9.369850158691406e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.3488461971282959s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.021471023559570312s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00019478797912597656s
Believability | Calculation of trust value for Physico-chemical process took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-rex took 3.0465471744537354s
Availability | SPARQL endpoint availability check for RadLex took 0.00010013580322265625s
Availability | VoID file availability check for RadLex took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for RadLex took 0.33499884605407715s
Reputation | Calculation of the PageRank for RadLex took 0.02162003517150879s
Interlinking | Calculation of Degree of Connection for RadLex took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015735626220703125s
Believability | Calculation of trust value for RadLex took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-rid took 3.441267490386963s
Availability | SPARQL endpoint availability check for RNA ontology took 4.935264587402344e-05s
Availability | VoID file availability check for RNA ontology took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2956736087799072s
Reputation | Calculation of the PageRank for RNA ontology took 0.02094554901123047s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.00055694580078125s
Believability | Calculation of trust value for RNA ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-rnao took 3.0075573921203613s
Availability | SPARQL endpoint availability check for Role Ontology took 5.316734313964844e-05s
Availability | VoID file availability check for Role Ontology took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.33370018005371094s
Reputation | Calculation of the PageRank for Role Ontology took 0.02820420265197754s
Interlinking | Calculation of Degree of Connection for Role Ontology took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0014202594757080078s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.0002970695495605469s
Believability | Calculation of trust value for Role Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-roleo took 3.1348249912261963s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.863739013671875e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.3342020511627197s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020969390869140625s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00018286705017089844s
Believability | Calculation of trust value for Rat Strain Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-rs took 3.2968270778656006s
Availability | SPARQL endpoint availability check for RxNORM took 5.0067901611328125e-05s
Availability | VoID file availability check for RxNORM took 0.0006425380706787109s
Completeness | Calculation of interlinking completeness for RxNORM took 0.34025025367736816s
Reputation | Calculation of the PageRank for RxNORM took 0.021015167236328125s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006232261657714844s
Believability | Calculation of trust value for RxNORM took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-rxnorm took 3.202019691467285s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 0.000102996826171875s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.5636155605316162s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.021146535873413086s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010235309600830078s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sao took 3.793471336364746s
Availability | SPARQL endpoint availability check for Systems Biology took 5.793571472167969e-05s
Availability | VoID file availability check for Systems Biology took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.3631017208099365s
Reputation | Calculation of the PageRank for Systems Biology took 0.021040678024291992s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004756450653076172s
Believability | Calculation of trust value for Systems Biology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sbo took 3.274506092071533s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 9.632110595703125e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.5183026790618896s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.020959854125976562s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00011658668518066406s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sbro took 3.443079710006714s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 0.00011038780212402344s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.316133975982666s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.021156787872314453s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013768672943115234s
Believability | Calculation of trust value for Sleep Domain Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-sdo took 3.2703139781951904s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 5.125999450683594e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2983667850494385s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.021222829818725586s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00035309791564941406s
Believability | Calculation of trust value for Sample processing and separation techniques took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sep took 3.8548412322998047s
Availability | SPARQL endpoint availability check for Student Health Record took 4.982948303222656e-05s
Availability | VoID file availability check for Student Health Record took 0.0003814697265625s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.3376035690307617s
Reputation | Calculation of the PageRank for Student Health Record took 0.021616697311401367s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004718303680419922s
Believability | Calculation of trust value for Student Health Record took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-shr took 3.3565218448638916s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 9.465217590332031e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0007529258728027344s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.4995079040527344s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.021105051040649414s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012140274047851562s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-sio took 4.438398838043213s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 7.152557373046875e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.00031113624572753906s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.2908756732940674s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.022381305694580078s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00020837783813476562s
Believability | Calculation of trust value for Situation-Based Access Control took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-sitbac took 3.452460765838623s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 7.534027099609375e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3445718288421631s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.02122974395751953s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0009338855743408203s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.001917123794555664s
Believability | Calculation of trust value for SNOMED Clinical Terms took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-snomedct took 3.4173834323883057s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.935264587402344e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.3286292552947998s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.022571802139282227s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0008182525634765625s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0007455348968505859s
Believability | Calculation of trust value for SNP-Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-snpo took 3.0795440673828125s
Availability | SPARQL endpoint availability check for Sequence types and features took 0.0001747608184814453s
Availability | VoID file availability check for Sequence types and features took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.3256402015686035s
Reputation | Calculation of the PageRank for Sequence types and features took 0.021198034286499023s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0006349086761474609s
Believability | Calculation of trust value for Sequence types and features took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-so_x1 took 3.906276226043701s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 0.00017189979553222656s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.3839237689971924s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.021796703338623047s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015933513641357422s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-sopharm took 3.6573779582977295s
Availability | SPARQL endpoint availability check for SoyOntology took 4.863739013671875e-05s
Availability | VoID file availability check for SoyOntology took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.28438472747802734s
Reputation | Calculation of the PageRank for SoyOntology took 0.023337602615356445s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001513957977294922s
Believability | Calculation of trust value for SoyOntology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-soy took 3.2688918113708496s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.9114227294921875e-05s
Availability | VoID file availability check for Spider Ontology took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.2898991107940674s
Reputation | Calculation of the PageRank for Spider Ontology took 0.021048545837402344s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003209114074707031s
Believability | Calculation of trust value for Spider Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-spd took 3.0989716053009033s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.76837158203125e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.3180429935455322s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.02203202247619629s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0002689361572265625s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-spto took 3.3542518615722656s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.744529724121094e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.31910133361816406s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.021048307418823242s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004475116729736328s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sso took 3.112865924835205s
Availability | SPARQL endpoint availability check for Software Ontology took 9.989738464355469e-05s
Availability | VoID file availability check for Software Ontology took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.33167171478271484s
Reputation | Calculation of the PageRank for Software Ontology took 0.021036863327026367s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0003998279571533203s
Believability | Calculation of trust value for Software Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-swo took 2.9815046787261963s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 0.00010204315185546875s
Availability | VoID file availability check for Tick gross anatomy took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.29782867431640625s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.021000146865844727s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00023508071899414062s
Believability | Calculation of trust value for Tick gross anatomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-tads took 3.17681884765625s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 0.00014209747314453125s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.2800877094268799s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.020918607711791992s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0009412765502929688s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0010693073272705078s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-tao took 3.060058355331421s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 0.000102996826171875s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.2929420471191406s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.02131795883178711s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.940696716308594e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-taxrank took 3.2705442905426025s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.863739013671875e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.3172342777252197s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.152557373046875e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-teddy took 3.134481906890869s
Availability | SPARQL endpoint availability check for Time Event Ontology took 5.14984130859375e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.466249942779541s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.021508216857910156s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008187294006347656s
Believability | Calculation of trust value for Time Event Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-teo took 3.328094959259033s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 0.00010418891906738281s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.29990506172180176s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.021785736083984375s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0004546642303466797s
Believability | Calculation of trust value for Mosquito gross anatomy took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-tgma took 2.973073720932007s
Availability | SPARQL endpoint availability check for thesaurus took 0.00010275840759277344s
Availability | VoID file availability check for thesaurus took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for thesaurus took 0.30162715911865234s
Reputation | Calculation of the PageRank for thesaurus took 0.021352767944335938s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.628036499023438e-05s
Believability | Calculation of trust value for thesaurus took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-thesaurus took 3.1218349933624268s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 8.797645568847656e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.2962646484375s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.02135157585144043s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003402233123779297s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 3.2121100425720215s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 0.00011754035949707031s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.9690773487091064s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.021063804626464844s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008370876312255859s
Believability | Calculation of trust value for Translational Medicine Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-tmo took 4.189326286315918s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 0.00010323524475097656s
Availability | VoID file availability check for Plant Trait Ontology took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.34829139709472656s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.02142333984375s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015616416931152344s
Believability | Calculation of trust value for Plant Trait Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-to took 3.1976547241210938s
Availability | SPARQL endpoint availability check for TOK_Ontology took 9.703636169433594e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.3327353000640869s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00017642974853515625s
Believability | Calculation of trust value for TOK_Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-tok took 3.596571683883667s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.935264587402344e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.3095245361328125s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.021091461181640625s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.0002009868621826172s
Believability | Calculation of trust value for Teleost taxonomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-tto took 3.277947187423706s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 9.965896606445312e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.33060288429260254s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.021108388900756836s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010406970977783203s
Believability | Calculation of trust value for Uber anatomy ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-uberon took 3.336721897125244s
Availability | SPARQL endpoint availability check for Units Ontology took 0.00010538101196289062s
Availability | VoID file availability check for Units Ontology took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.3782470226287842s
Reputation | Calculation of the PageRank for Units Ontology took 0.028957128524780273s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0014705657958984375s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0003561973571777344s
Believability | Calculation of trust value for Units Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-unitsontology took 3.28389048576355s
Availability | SPARQL endpoint availability check for Units of measurement took 4.76837158203125e-05s
Availability | VoID file availability check for Units of measurement took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.27369093894958496s
Reputation | Calculation of the PageRank for Units of measurement took 0.021230697631835938s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00027871131896972656s
Believability | Calculation of trust value for Units of measurement took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-uo took 3.2401156425476074s
Availability | SPARQL endpoint availability check for VANDF took 9.918212890625e-05s
Availability | VoID file availability check for VANDF took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for VANDF took 0.3370857238769531s
Reputation | Calculation of the PageRank for VANDF took 0.021720170974731445s
Interlinking | Calculation of Degree of Connection for VANDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for VANDF took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007231235504150391s
Believability | Calculation of trust value for VANDF took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-vandf took 3.275522232055664s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 9.751319885253906e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2886545658111572s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.02122807502746582s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00043272972106933594s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-vao took 3.0635976791381836s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 0.00010943412780761719s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.3474874496459961s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.021261930465698242s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006320476531982422s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-vhog took 3.609112024307251s
Availability | SPARQL endpoint availability check for VIVO took 5.316734313964844e-05s
Availability | VoID file availability check for VIVO took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for VIVO took 0.3177790641784668s
Reputation | Calculation of the PageRank for VIVO took 0.02172374725341797s
Interlinking | Calculation of Degree of Connection for VIVO took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0004315376281738281s
Believability | Calculation of trust value for VIVO took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-vivo took 3.107518196105957s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.887580871582031e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.3428013324737549s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.022525787353515625s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.001287221908569336s
Believability | Calculation of trust value for Vaccine Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-vo took 3.21870493888855s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 9.822845458984375e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.328519344329834s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020964384078979492s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020766258239746094s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-vt took 3.0927867889404297s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 0.00010275840759277344s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0007297992706298828s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.2972729206085205s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.02102828025817871s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0004937648773193359s
Believability | Calculation of trust value for C. elegans gross anatomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-wbbt took 3.4331977367401123s
Availability | SPARQL endpoint availability check for C. elegans development took 8.869171142578125e-05s
Availability | VoID file availability check for C. elegans development took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.30766773223876953s
Reputation | Calculation of the PageRank for C. elegans development took 0.021098852157592773s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.839897155761719e-05s
Believability | Calculation of trust value for C. elegans development took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-wbls took 3.1181583404541016s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 0.0001010894775390625s
Availability | VoID file availability check for C. elegans phenotype took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.30155110359191895s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.02128124237060547s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.630752563476562e-05s
Believability | Calculation of trust value for C. elegans phenotype took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-wbphenotype took 3.4390571117401123s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.839897155761719e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.31172871589660645s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020985126495361328s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.000579833984375s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-who took 3.1650028228759766s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 5.14984130859375e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.30643367767333984s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.02104973793029785s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006818771362304688s
Believability | Calculation of trust value for Xenopus anatomy and development took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-xao took 3.4826438426971436s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 9.703636169433594e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.34080982208251953s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.021475791931152344s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.0002543926239013672s
Believability | Calculation of trust value for Experimental Conditions Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-xco took 3.2121057510375977s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.839897155761719e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0003528594970703125s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.5680227279663086s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.021326303482055664s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002753734588623047s
Believability | Calculation of trust value for Yeast phenotypes took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-ypo took 3.91055965423584s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 0.00011014938354492188s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.370164155960083s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.02101874351501465s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.00077056884765625s
Believability | Calculation of trust value for Zebrafish anatomy and development took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-zfa took 3.346815347671509s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 9.799003601074219e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0008161067962646484s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.3692591190338135s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.021123409271240234s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 3.314018249511719e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.3589859008789062e-05s
INFO | --- Analysis for Bioportal_link took 4.83568000793457s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.5135500431060791s
Availability | VoID file availability check for BioSamples RDF took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.36013054847717285s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.029608488082885742s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0014028549194335938s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 8.654594421386719e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.049041748046875e-05s
INFO | --- Analysis for biosamples-rdf took 4.155039310455322s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.09776473045349121s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.33426523208618164s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.021416902542114258s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011777877807617188s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for bis-linked-data took 3.1671574115753174s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 5.0067901611328125e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0003592967987060547s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.29662466049194336s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.021347761154174805s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.1961669921875e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.33514404296875e-05s
INFO | --- Analysis for bll-thesaurus took 4.120080232620239s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 0.9848079681396484s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.31409525871276855s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.021117687225341797s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.628036499023438e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.239776611328125e-05s
INFO | --- Analysis for bluk-bnb took 15.34589695930481s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.22259902954101562s
Availability | VoID file availability check for Thesaurus BNCF took 0.0007672309875488281s
Extra | Recovery of all triples for Thesaurus BNCF took 44.29095458984375s
Performance | Total latancy measurement for Thesaurus BNCF took 0.5822947025299072s
Amount of data | Number of triples check for Thesaurus BNCF took 0.5919716358184814s
Interoperability | New terms check for Thesaurus BNCF took 1.6446478366851807s
Versatility | Languages check for Thesaurus BNCF took 6.908546209335327s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.7909696102142334s
Security | Check HTTPS for Thesaurus BNCF took 0.0924525260925293s
Interpretability | RDF structures check for Thesaurus BNCF took 0.13009309768676758s
Versatility | Serialization formats check for Thesaurus BNCF took 0.133331298828125s
Availability | RDF dump link check for Thesaurus BNCF took 0.11809444427490234s
License | MR license check for Thesaurus BNCF took 0.11982583999633789s
License | HR license check for Thesaurus BNCF took 0.19234776496887207s
Amount of data | Number of property check for Thesaurus BNCF took 0.14036226272583008s
Understandability | Number of label check for Thesaurus BNCF took 0.3465151786804199s
Understandability | URI regex check for Thesaurus BNCF took 0.26775050163269043s
Understandability | Vocabs check for Thesaurus BNCF took 0.12564730644226074s
Verifiability | Authors check for Thesaurus BNCF took 0.12563276290893555s
Verifiability | Publishers check for Thesaurus BNCF took 0.12397122383117676s
Performance | Throughput check for Thesaurus BNCF took 10.603470802307129s
Amount of data | Check the number of entities for Thesaurus BNCF took 3.695487976074219e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.13039541244506836s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.14184117317199707s
Interlinking | skos check for Thesaurus BNCF took 0.16533541679382324s
Interlinking | skos check for Thesaurus BNCF took 0.145538330078125s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.13545894622802734s
Currency | Creation date check for Thesaurus BNCF took 0.2544283866882324s
Currency | Modification date check for Thesaurus BNCF took 0.2615664005279541s
Rep.Conc. | URIs length for Thesaurus BNCF took 27.642163276672363s
Interoperability | New vocabularies check for Thesaurus BNCF took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.14455461502075195s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.12266182899475098s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.1319284439086914s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 14.557385444641113s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.4906799793243408s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 4.010026216506958s
Consistency | Disjoint class check for Thesaurus BNCF took 0.12095999717712402s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.8694887161254883s
Consistency | Misplaced classes for Thesaurus BNCF took 6.865981340408325s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 9.192098140716553s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.7129058837890625s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.447199821472168s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.4838225841522217s
Security | Sign check for Thesaurus BNCF took 0.1635599136352539s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 20.87687039375305s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.34255003929138184s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.021212339401245117s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 8.177757263183594e-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.3113021850585938e-05s
INFO | --- Analysis for bncf-ns took 191.79450726509094s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6158449649810791s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006952285766601562s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.4984235763549805s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.7871437072753906s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.4927656650543213s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.586606740951538s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.250365257263184s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.641509532928467s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.32872653007507324s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.40488362312316895s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.41896510124206543s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3186607360839844s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.43587613105773926s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 58.20217204093933s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38623571395874023s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5806474685668945s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7474551200866699s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4418342113494873s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3937547206878662s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3761465549468994s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.828346014022827s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.963180541992188e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.41460490226745605s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.40792250633239746s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4043123722076416s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4002959728240967s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.38562488555908203s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7518489360809326s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.373981237411499s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.904683113098145s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3461153507232666s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4234755039215088s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4419832229614258s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7567079067230225s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.023949384689331055s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.033391714096069336s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36045312881469727s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.664201498031616s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4948132038116455s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.7689406871795654s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.1154232025146484s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.691937685012817s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.035195112228393555s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.42923784255981445s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.39191293716430664s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.815330266952515s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.42139434814453125s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02184152603149414s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.3882598876953125e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.430511474609375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.821487426757812e-06s
INFO | --- Analysis for bpr took 397.0855915546417s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.935264587402344e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.3231041431427002s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.02147531509399414s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 8.249282836914062e-05s
Believability | Calculation of trust value for Brazilian Politicians took 9.775161743164062e-06s
INFO | --- Analysis for brazilian-politicians took 3.2490110397338867s
Availability | SPARQL endpoint availability check for Bricklink took 4.688791751861572s
Availability | VoID file availability check for Bricklink took 0.00040268898010253906s
Completeness | Calculation of interlinking completeness for Bricklink took 0.36434030532836914s
Reputation | Calculation of the PageRank for Bricklink took 0.02184605598449707s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Bricklink took 7.367134094238281e-05s
Believability | Calculation of trust value for Bricklink took 1.4781951904296875e-05s
INFO | --- Analysis for bricklink took 19.42322325706482s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.311174154281616s
Availability | VoID file availability check for British Museum Collection took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.45592665672302246s
Reputation | Calculation of the PageRank for British Museum Collection took 0.02131962776184082s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.314018249511719e-05s
Believability | Calculation of trust value for British Museum Collection took 1.33514404296875e-05s
INFO | --- Analysis for british-museum-collection took 73.52585506439209s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 6.270408630371094e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.3128678798675537s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.02132725715637207s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.267692565917969e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.33514404296875e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.899534225463867s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2456037998199463s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006885528564453125s
Extra | Recovery of all triples for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 16.76541018486023s
Performance | Total latancy measurement for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.6353178024291992s
Amount of data | Number of triples check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.5385544300079346s
Interoperability | New terms check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.9764251708984375s
Versatility | Languages check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.926307916641235s
Interpretability | Number of blank nodes check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.9589180946350098s
Interpretability | RDF structures check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12737655639648438s
Versatility | Serialization formats check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13232159614562988s
Availability | RDF dump link check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12224912643432617s
License | MR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11652302742004395s
License | HR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 21.98259925842285s
Amount of data | Number of property check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1315295696258545s
Understandability | Number of label check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.17792034149169922s
Understandability | URI regex check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24728083610534668s
Understandability | Vocabs check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1233832836151123s
Verifiability | Authors check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12421941757202148s
Verifiability | Publishers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12431740760803223s
Performance | Throughput check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.95917558670044s
Amount of data | Check the number of entities for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 8.58306884765625e-05s
Verifiability | Contribs. check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12420058250427246s
Interlinking | sameAs chians check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13074803352355957s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12393760681152344s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12441658973693848s
Timeliness | dataset update frequency check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13132524490356445s
Currency | Creation date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.25654149055480957s
Currency | Modification date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2539355754852295s
Rep.Conc. | URIs length for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 11.296679973602295s
Interoperability | New vocabularies check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12562179565429688s
Accuracy | Check Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12264251708984375s
Accuracy | Check Inverse Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1299145221710205s
Accuracy | Check Empty annotation labels for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.396019458770752s
Accuracy | Check White space in annotation for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24654865264892578s
Accuracy | Check Datatype consistency for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.766972303390503s
Consistency | Disjoint class check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12354207038879395s
Consistency | Check Misplaced properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.1522388458251953s
Consistency | Check Ontology hijacking for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.537735223770142s
Consistency | Check Invalid usage of undefined classes for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3900606632232666s
Consistency | Check Invalid usage of undefined properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.5498571395874023s
Conciseness | Check Extensional conciseness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.8354015350341797s
Security | Sign check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11563634872436523s
Availability | Check URIs Dereferenciability for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10321.234041929245s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.7587220668792725s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.027852773666381836s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.719329833984375e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.001344919204711914s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.9087066650390625e-05s
Interoperability | Check the re-using of existing vocabs for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.3909759521484375e-06s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.723403930664062e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 10449.857744693756s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.1814732551574707s
Availability | VoID file availability check for business.data.gov.uk took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.33382105827331543s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.02830982208251953s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0015285015106201172s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 9.584426879882812e-05s
Believability | Calculation of trust value for business.data.gov.uk took 7.62939453125e-06s
INFO | --- Analysis for business-data-gov-uk took 3.5553715229034424s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.4835491180419922s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.000560760498046875s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 1.851853847503662s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.4748954772949219s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.3818497657775879s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.9721429347991943s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 40.077552795410156s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.33272504806518555s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.16910147666931152s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.4055593013763428s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.3165907859802246s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.2850170135498047s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.350543737411499s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 19.13766598701477s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.3583853244781494s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.5856881141662598s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.5920414924621582s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.3031044006347656s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.38607144355773926s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.32068657875061035s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.989111423492432s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 3.2901763916015625e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.31280517578125s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.3029963970184326s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3785989284515381s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3197464942932129s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.29926252365112305s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.6479692459106445s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.6353683471679688s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 3.0640130043029785s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.29065752029418945s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.43656444549560547s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.43895888328552246s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 0.989391565322876s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03558492660522461s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.03197216987609863s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.35357093811035156s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.4291021823883057s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.395967960357666s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.4817919731140137s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.5953214168548584s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.723343849182129s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03632712364196777s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.29575204849243164s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.3084735870361328s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1273.4904890060425s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.4544699192047119s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.02626657485961914s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.412101745605469e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.239776611328125e-05s
INFO | --- Analysis for BVMC took 1402.40403008461s
Availability | SPARQL endpoint availability check for cablegate took 1.5828356742858887s
Availability | VoID file availability check for cablegate took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for cablegate took 0.349531888961792s
Reputation | Calculation of the PageRank for cablegate took 0.0292508602142334s
Interlinking | Calculation of Degree of Connection for cablegate took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0016179084777832031s
Interlinking | Calculation of Clustering coefficient for cablegate took 0.0001697540283203125s
Believability | Calculation of trust value for cablegate took 9.5367431640625e-06s
INFO | --- Analysis for cablegate took 17.918938636779785s
Availability | SPARQL endpoint availability check for Calames took 5.507469177246094e-05s
Availability | VoID file availability check for Calames took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Calames took 0.3841989040374756s
Reputation | Calculation of the PageRank for Calames took 0.028861045837402344s
Interlinking | Calculation of Degree of Connection for Calames took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Calames took 0.0013663768768310547s
Interlinking | Calculation of Clustering coefficient for Calames took 6.389617919921875e-05s
Believability | Calculation of trust value for Calames took 1.049041748046875e-05s
INFO | --- Analysis for calames took 5.142884731292725s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.4172067642211914s
Availability | VoID file availability check for CaLiGraph took 0.0007770061492919922s
Extra | Recovery of all triples for CaLiGraph took 1.8350152969360352s
Performance | Total latancy measurement for CaLiGraph took 1.1432702541351318s
Amount of data | Number of triples check for CaLiGraph took 13.565114259719849s
Interoperability | New terms check for CaLiGraph took 2.2956347465515137s
Versatility | Languages check for CaLiGraph took 60.30888915061951s
Interpretability | Number of blank nodes check for CaLiGraph took 0.28423452377319336s
Security | Check HTTPS for CaLiGraph took 0.15102577209472656s
Interpretability | RDF structures check for CaLiGraph took 0.4545013904571533s
Versatility | Serialization formats check for CaLiGraph took 0.32898926734924316s
Availability | RDF dump link check for CaLiGraph took 0.28244566917419434s
License | MR license check for CaLiGraph took 0.40744996070861816s
License | HR license check for CaLiGraph took 60.291380405426025s
Amount of data | Number of property check for CaLiGraph took 0.26119089126586914s
Understandability | Number of label check for CaLiGraph took 4.750791311264038s
Understandability | URI regex check for CaLiGraph took 0.5541577339172363s
Understandability | Vocabs check for CaLiGraph took 0.2971920967102051s
Verifiability | Authors check for CaLiGraph took 0.3042440414428711s
Verifiability | Publishers check for CaLiGraph took 0.2553894519805908s
Performance | Throughput check for CaLiGraph took 11.390501976013184s
Amount of data | Check the number of entities for CaLiGraph took 0.018088340759277344s
Verifiability | Contribs. check for CaLiGraph took 0.2609267234802246s
Interlinking | sameAs chians check for CaLiGraph took 0.7061514854431152s
Interlinking | skos check for CaLiGraph took 0.42271876335144043s
Interlinking | skos check for CaLiGraph took 0.23367762565612793s
Timeliness | dataset update frequency check for CaLiGraph took 0.34222936630249023s
Currency | Creation date check for CaLiGraph took 0.6406848430633545s
Currency | Modification date check for CaLiGraph took 0.596172571182251s
Rep.Conc. | URIs length for CaLiGraph took 61.01717162132263s
Interoperability | New vocabularies check for CaLiGraph took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.27170872688293457s
Accuracy | Check Functional Property for CaLiGraph took 0.3043694496154785s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.32335782051086426s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5536119937896729s
Accuracy | Check White space in annotation for CaLiGraph took 0.027738094329833984s
Accuracy | Check Datatype consistency for CaLiGraph took 0.054212331771850586s
Consistency | Disjoint class check for CaLiGraph took 0.3429222106933594s
Consistency | Check Misplaced properties for CaLiGraph took 60.929516077041626s
Consistency | Misplaced classes for CaLiGraph took 0.5033414363861084s
Consistency | Check Ontology hijacking for CaLiGraph took 2.3380961418151855s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.5962176322937012s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.879502296447754s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03841233253479004s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4764876365661621s
Security | Sign check for CaLiGraph took 0.4411177635192871s
Availability | Check URIs Dereferenciability for CaLiGraph took 9.796236753463745s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.5345444679260254s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02922844886779785s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0015463829040527344s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 9.1552734375e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 3.337860107421875e-06s
Believability | Calculation of trust value for CaLiGraph took 1.4781951904296875e-05s
INFO | --- Analysis for CaLiGraph took 1453.9202694892883s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.2811579704284668s
Availability | VoID file availability check for CaLiGraph took 0.000469207763671875s
Extra | Recovery of all triples for CaLiGraph took 1.1908464431762695s
Performance | Total latancy measurement for CaLiGraph took 1.147949457168579s
Amount of data | Number of triples check for CaLiGraph took 13.557352304458618s
Interoperability | New terms check for CaLiGraph took 2.0316033363342285s
Versatility | Languages check for CaLiGraph took 60.28317856788635s
Interpretability | Number of blank nodes check for CaLiGraph took 0.25546765327453613s
Security | Check HTTPS for CaLiGraph took 0.15113353729248047s
Interpretability | RDF structures check for CaLiGraph took 0.28835511207580566s
Versatility | Serialization formats check for CaLiGraph took 0.2617347240447998s
Availability | RDF dump link check for CaLiGraph took 0.26806044578552246s
License | MR license check for CaLiGraph took 0.2548024654388428s
License | HR license check for CaLiGraph took 60.29627084732056s
Amount of data | Number of property check for CaLiGraph took 0.25650811195373535s
Understandability | Number of label check for CaLiGraph took 3.2707974910736084s
Understandability | URI regex check for CaLiGraph took 0.5228092670440674s
Understandability | Vocabs check for CaLiGraph took 0.25133585929870605s
Verifiability | Authors check for CaLiGraph took 0.26535844802856445s
Verifiability | Publishers check for CaLiGraph took 0.2635073661804199s
Performance | Throughput check for CaLiGraph took 11.469144582748413s
Amount of data | Check the number of entities for CaLiGraph took 0.014876127243041992s
Verifiability | Contribs. check for CaLiGraph took 0.2673799991607666s
Interlinking | sameAs chians check for CaLiGraph took 0.687821626663208s
Interlinking | skos check for CaLiGraph took 0.26418137550354004s
Interlinking | skos check for CaLiGraph took 0.22348594665527344s
Timeliness | dataset update frequency check for CaLiGraph took 0.2634851932525635s
Currency | Creation date check for CaLiGraph took 0.5267951488494873s
Currency | Modification date check for CaLiGraph took 0.5119023323059082s
Rep.Conc. | URIs length for CaLiGraph took 61.00864005088806s
Interoperability | New vocabularies check for CaLiGraph took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2645268440246582s
Accuracy | Check Functional Property for CaLiGraph took 0.27904248237609863s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2570326328277588s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.6064941883087158s
Accuracy | Check White space in annotation for CaLiGraph took 0.026306629180908203s
Accuracy | Check Datatype consistency for CaLiGraph took 0.05105018615722656s
Consistency | Disjoint class check for CaLiGraph took 0.26043701171875s
Consistency | Check Misplaced properties for CaLiGraph took 60.909106492996216s
Consistency | Misplaced classes for CaLiGraph took 0.6345775127410889s
Consistency | Check Ontology hijacking for CaLiGraph took 2.1637423038482666s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.4168083667755127s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.73361897468567s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.0307004451751709s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4747755527496338s
Security | Sign check for CaLiGraph took 0.27129244804382324s
Availability | Check URIs Dereferenciability for CaLiGraph took 11.171067237854004s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.38520359992980957s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02302408218383789s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.796287536621094e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 1.2874603271484375e-05s
INFO | --- Analysis for caligraph took 1450.4298822879791s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.0670022964477539s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.35259127616882324s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.02167963981628418s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.457069396972656e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.1682510375976562e-05s
INFO | --- Analysis for cap-italy-rdf took 3.091758966445923s
Availability | SPARQL endpoint availability check for person took 5.221366882324219e-05s
Availability | VoID file availability check for person took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for person took 0.2972090244293213s
Reputation | Calculation of the PageRank for person took 0.021455049514770508s
Interlinking | Calculation of Degree of Connection for person took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for person took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for person took 6.151199340820312e-05s
Believability | Calculation of trust value for person took 8.106231689453125e-06s
INFO | --- Analysis for card took 2.8959622383117676s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.839897155761719e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.3210177421569824s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.021265745162963867s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 4.3392181396484375e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 8.344650268554688e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 4.0624778270721436s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.5454626083374023s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0004968643188476562s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 102.87810158729553s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 0.9369866847991943s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 9.310997247695923s
Interoperability | New terms check for Norway catch records dataset @PSNC took 14.22170615196228s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.2567913532257s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 2.3712711334228516s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.35946226119995117s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 9.263009786605835s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.36568760871887207s
License | MR license check for Norway catch records dataset @PSNC took 0.9492337703704834s
License | HR license check for Norway catch records dataset @PSNC took 300.20728945732117s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.19550657272338867s
Understandability | Number of label check for Norway catch records dataset @PSNC took 3.0823442935943604s
Understandability | URI regex check for Norway catch records dataset @PSNC took 1.1580703258514404s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.6239807605743408s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.22188687324523926s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.26703834533691406s
Performance | Throughput check for Norway catch records dataset @PSNC took 10.912056684494019s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 6.937980651855469e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.1881110668182373s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.21672606468200684s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.47815585136413574s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.48587560653686523s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 5.74407172203064s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.4977836608886719s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.25890445709228516s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 147.21574234962463s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.20102477073669434s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.45977783203125s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.4849982261657715s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 39.72602701187134s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.7265710830688477s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.787097454071045s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.1984081268310547s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 85.80848479270935s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.721107482910156s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 33.97947716712952s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.5309007167816162s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 87.79185104370117s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 3.0878283977508545s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.578214168548584s
Security | Sign check for Norway catch records dataset @PSNC took 1.6516623497009277s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 21.431138277053833s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.4230356216430664s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.02213001251220703s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.792213439941406e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 4.291534423828125e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 3093.6675786972046s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00011301040649414062s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007245540618896484s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.3380410671234131s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.029151439666748047s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0013625621795654297s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00018739700317382812s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.1920928955078125e-05s
INFO | --- Analysis for ce4r took 18.45582866668701s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.39586806297302246s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005390644073486328s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.0306921005249023s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.760216474533081s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21164774894714355s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.8511457443237305s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 21.047539472579956s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17418742179870605s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 58.17137551307678s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1962871551513672s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.163773775100708s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4572474956512451s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.22659850120544434s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15813899040222168s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3766748905181885s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3543965816497803s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17807269096374512s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.23669147491455078s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.31276965141296387s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.961413621902466s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 8.487701416015625e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24051856994628906s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16889595985412598s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.611546516418457s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20137310028076172s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18123412132263184s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.46260952949523926s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.33332347869873047s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 1.403667688369751s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19532418251037598s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.312941312789917s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.3376038074493408s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6664249897003174s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.029356956481933594s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.030242443084716797s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.31166791915893555s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 0.7369136810302734s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.159911870956421s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.58907151222229s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.8843157291412354s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03253817558288574s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.2026350498199463s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16498422622680664s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2918.128798007965s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.41721034049987793s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.021317720413208008s
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.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.430511474609375e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.1920928955078125e-05s
INFO | --- Analysis for ceo took 3062.872457265854s
Availability | SPARQL endpoint availability check for Chat Game corpus took 8.320808410644531e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0008318424224853516s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.3646211624145508s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.02154827117919922s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.647804260253906e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.2874603271484375e-05s
INFO | --- Analysis for chat-game-corpus took 13.671646356582642s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 0.00010585784912109375s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0008516311645507812s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.38446664810180664s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.698204040527344e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.0967254638671875e-05s
INFO | --- Analysis for chem2bio2rdf took 135.12851929664612s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.5643885135650635s
Availability | VoID file availability check for ChEMBL RDF took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.37809062004089355s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.021576404571533203s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.269050598144531e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.239776611328125e-05s
INFO | --- Analysis for chembl-rdf took 4.733330488204956s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.0547308921813965s
Availability | VoID file availability check for chemdb  dataset took 0.0011038780212402344s
Extra | Recovery of all triples for chemdb  dataset took 5.3053483963012695s
Performance | Total latancy measurement for chemdb  dataset took 2.693298816680908s
Amount of data | Number of triples check for chemdb  dataset took 0.5845232009887695s
Interoperability | New terms check for chemdb  dataset took 3.7579753398895264s
Versatility | Languages check for chemdb  dataset took 23.59635639190674s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5727388858795166s
Interpretability | RDF structures check for chemdb  dataset took 0.6258261203765869s
Versatility | Serialization formats check for chemdb  dataset took 0.562567949295044s
Availability | RDF dump link check for chemdb  dataset took 0.5458147525787354s
License | MR license check for chemdb  dataset took 0.5586793422698975s
License | HR license check for chemdb  dataset took 3.149186849594116s
Amount of data | Number of property check for chemdb  dataset took 0.5687541961669922s
Understandability | Number of label check for chemdb  dataset took 0.5718507766723633s
Understandability | URI regex check for chemdb  dataset took 1.0584018230438232s
Understandability | Vocabs check for chemdb  dataset took 0.5288450717926025s
Verifiability | Authors check for chemdb  dataset took 0.5372772216796875s
Verifiability | Publishers check for chemdb  dataset took 0.5347225666046143s
Performance | Throughput check for chemdb  dataset took 10.72597861289978s
Amount of data | Check the number of entities for chemdb  dataset took 7.581710815429688e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.5201625823974609s
Interlinking | sameAs chians check for chemdb  dataset took 0.5597612857818604s
Interlinking | skos check for chemdb  dataset took 0.5215306282043457s
Interlinking | skos check for chemdb  dataset took 0.5289223194122314s
Timeliness | dataset update frequency check for chemdb  dataset took 0.5285141468048096s
Currency | Creation date check for chemdb  dataset took 1.096813678741455s
Currency | Modification date check for chemdb  dataset took 1.0879721641540527s
Rep.Conc. | URIs length for chemdb  dataset took 3.1673858165740967s
Interoperability | New vocabularies check for chemdb  dataset took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5697555541992188s
Accuracy | Check Functional Property for chemdb  dataset took 0.5739684104919434s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.5494129657745361s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.2933809757232666s
Accuracy | Check White space in annotation for chemdb  dataset took 0.030219078063964844s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.034366607666015625s
Consistency | Disjoint class check for chemdb  dataset took 0.5283553600311279s
Consistency | Check Misplaced properties for chemdb  dataset took 1.3132054805755615s
Consistency | Misplaced classes for chemdb  dataset took 0.6524124145507812s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.685227632522583s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.4150607585906982s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 2.1481211185455322s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.03339028358459473s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5539696216583252s
Security | Sign check for chemdb  dataset took 0.5967636108398438s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2702.696343421936s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.6221418380737305s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.021770238876342773s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.128715515136719e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb  dataset took 1.1205673217773438e-05s
INFO | --- Analysis for chemdb-basicInfo took 7475.436172485352s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5760335922241211s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0005490779876708984s
Extra | Recovery of all triples for chemdb estimated properties dataset took 5.322469472885132s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.721167802810669s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5815515518188477s
Interoperability | New terms check for chemdb estimated properties dataset took 3.730407476425171s
Versatility | Languages check for chemdb estimated properties dataset took 22.570183992385864s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5796811580657959s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.576941967010498s
Versatility | Serialization formats check for chemdb estimated properties dataset took 0.5812070369720459s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.534492015838623s
License | MR license check for chemdb estimated properties dataset took 0.5448782444000244s
License | HR license check for chemdb estimated properties dataset took 3.1749114990234375s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5711872577667236s
Understandability | Number of label check for chemdb estimated properties dataset took 0.5787971019744873s
Understandability | URI regex check for chemdb estimated properties dataset took 1.0620427131652832s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.5438954830169678s
Verifiability | Authors check for chemdb estimated properties dataset took 0.5314004421234131s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.5505740642547607s
Performance | Throughput check for chemdb estimated properties dataset took 10.814956188201904s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 7.176399230957031e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.5296447277069092s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 0.5978691577911377s
Interlinking | skos check for chemdb estimated properties dataset took 0.530221700668335s
Interlinking | skos check for chemdb estimated properties dataset took 0.5442929267883301s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 0.5505163669586182s
Currency | Creation date check for chemdb estimated properties dataset took 1.1251728534698486s
Currency | Modification date check for chemdb estimated properties dataset took 1.1213324069976807s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 3.3035225868225098s
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.5385689735412598s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.5600430965423584s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.5330202579498291s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 2.2925546169281006s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.0304415225982666s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03506803512573242s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.528583288192749s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.300621509552002s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.6824872493743896s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 3.6964633464813232s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.4187674522399902s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 2.1658620834350586s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03474307060241699s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.5651068687438965s
Security | Sign check for chemdb estimated properties dataset took 0.5501465797424316s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2975.4055013656616s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.56076979637146s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.026451587677001953s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 6.0558319091796875e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.33514404296875e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 7449.217879533768s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5900928974151611s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0005004405975341797s
Extra | Recovery of all triples for chemdb phase transition dataset took 5.2532641887664795s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.786362409591675s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.6024208068847656s
Interoperability | New terms check for chemdb phase transition dataset took 3.7632954120635986s
Versatility | Languages check for chemdb phase transition dataset took 23.382178783416748s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5894467830657959s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.6002833843231201s
Versatility | Serialization formats check for chemdb phase transition dataset took 0.5909929275512695s
Availability | RDF dump link check for chemdb phase transition dataset took 0.5533373355865479s
License | MR license check for chemdb phase transition dataset took 0.5439989566802979s
License | HR license check for chemdb phase transition dataset took 3.1540865898132324s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5826742649078369s
Understandability | Number of label check for chemdb phase transition dataset took 0.5996055603027344s
Understandability | URI regex check for chemdb phase transition dataset took 1.099989414215088s
Understandability | Vocabs check for chemdb phase transition dataset took 0.5425233840942383s
Verifiability | Authors check for chemdb phase transition dataset took 0.5515575408935547s
Verifiability | Publishers check for chemdb phase transition dataset took 0.5653972625732422s
Performance | Throughput check for chemdb phase transition dataset took 11.019538164138794s
Amount of data | Check the number of entities for chemdb phase transition dataset took 8.20159912109375e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.548600435256958s
Interlinking | sameAs chians check for chemdb phase transition dataset took 0.5727438926696777s
Interlinking | skos check for chemdb phase transition dataset took 0.5498812198638916s
Interlinking | skos check for chemdb phase transition dataset took 0.5500025749206543s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 0.5441827774047852s
Currency | Creation date check for chemdb phase transition dataset took 1.1193623542785645s
Currency | Modification date check for chemdb phase transition dataset took 1.1382672786712646s
Rep.Conc. | URIs length for chemdb phase transition dataset took 3.1586360931396484s
Interoperability | New vocabularies check for chemdb phase transition dataset took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.5521361827850342s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.5776357650756836s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.5406637191772461s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 2.3273961544036865s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.030457735061645508s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03430819511413574s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.5478835105895996s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.3361237049102783s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6770167350769043s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 3.7162132263183594s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.4015233516693115s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 2.174811601638794s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.03394031524658203s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.6063835620880127s
Security | Sign check for chemdb phase transition dataset took 0.5585699081420898s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2788.8831403255463s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.5106589794158936s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.021401166915893555s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 2.288818359375e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 5.4836273193359375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 9.5367431640625e-07s
Believability | Calculation of trust value for chemdb phase transition dataset took 8.344650268554688e-06s
INFO | --- Analysis for chemdb-phaseTransition took 7297.825845241547s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5904076099395752s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0005011558532714844s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 5.3063318729400635s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.784989595413208s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.6128270626068115s
Interoperability | New terms check for chemdb thermochemistry dataset took 3.672363758087158s
Versatility | Languages check for chemdb thermochemistry dataset took 23.10554027557373s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5745081901550293s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.6083309650421143s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 0.5781688690185547s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.5463137626647949s
License | MR license check for chemdb thermochemistry dataset took 0.5610888004302979s
License | HR license check for chemdb thermochemistry dataset took 3.2398276329040527s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.6005744934082031s
Understandability | Number of label check for chemdb thermochemistry dataset took 0.600125789642334s
Understandability | URI regex check for chemdb thermochemistry dataset took 1.116842269897461s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.5612518787384033s
Verifiability | Authors check for chemdb thermochemistry dataset took 0.5624027252197266s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.5616855621337891s
Performance | Throughput check for chemdb thermochemistry dataset took 11.12350058555603s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 6.961822509765625e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.5461263656616211s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 0.5808064937591553s
Interlinking | skos check for chemdb thermochemistry dataset took 0.543046236038208s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5656485557556152s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 0.5610964298248291s
Currency | Creation date check for chemdb thermochemistry dataset took 1.1382434368133545s
Currency | Modification date check for chemdb thermochemistry dataset took 1.1256310939788818s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.195483922958374s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.5625150203704834s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.5777022838592529s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.5429596900939941s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 2.3489322662353516s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.030410051345825195s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03459429740905762s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.5424385070800781s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.3435142040252686s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6782033443450928s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 3.7137603759765625s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.3945693969726562s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 2.1651079654693604s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.03366994857788086s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5846419334411621s
Security | Sign check for chemdb thermochemistry dataset took 0.5471575260162354s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2796.0584614276886s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 10.186147212982178s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.03589892387390137s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 8.797645568847656e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 7.62939453125e-06s
INFO | --- Analysis for chemdb-thermochemistry took 7259.371997594833s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.482269287109375e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.3216729164123535s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.02214956283569336s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.2901763916015625e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.2159347534179688e-05s
INFO | --- Analysis for chempedia-rdf took 10.07137680053711s
Availability | SPARQL endpoint availability check for Chiman Maru took 0.00010228157043457031s
Availability | VoID file availability check for Chiman Maru took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.3446485996246338s
Reputation | Calculation of the PageRank for Chiman Maru took 0.021152019500732422s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.266334533691406e-05s
Believability | Calculation of trust value for Chiman Maru took 1.3589859008789062e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 3.1142942905426025s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 392.4984610080719s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.3422820568084717s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.0222780704498291s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 4.57763671875e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.239776611328125e-05s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 798.9118940830231s
Availability | SPARQL endpoint availability check for Chronicling America took 0.000274658203125s
Availability | VoID file availability check for Chronicling America took 0.0009455680847167969s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.37030959129333496s
Reputation | Calculation of the PageRank for Chronicling America took 0.021599292755126953s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00011277198791503906s
Believability | Calculation of trust value for Chronicling America took 1.239776611328125e-05s
INFO | --- Analysis for chronicling-america took 276.50953125953674s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.7670574188232422s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006606578826904297s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 96.31502485275269s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 2.045778751373291s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 1.4671416282653809s
Interoperability | New terms check for Cultural Heritage Thesaurus took 7.5041139125823975s
Versatility | Languages check for Cultural Heritage Thesaurus took 5.239368677139282s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 1.521618127822876s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3441016674041748s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.2930107116699219s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 6.682982683181763s
License | MR license check for Cultural Heritage Thesaurus took 0.3078773021697998s
License | HR license check for Cultural Heritage Thesaurus took 0.6507313251495361s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.36328554153442383s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.524418830871582s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.6021249294281006s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.3190948963165283s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.28072023391723633s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.27309608459472656s
Performance | Throughput check for Cultural Heritage Thesaurus took 12.00282883644104s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 8.416175842285156e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.2895689010620117s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.3120992183685303s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3300745487213135s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.30470919609069824s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.2996373176574707s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.95723557472229s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.5795648097991943s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 49.488184213638306s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 3.2517096996307373s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.2854588031768799s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.3336920738220215s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.2746708393096924s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 8.19204568862915s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22562670707702637s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.27733445167541504s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.853848934173584s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.32970428466796875s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 8.41464114189148s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.9091691970825195s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00017309188842773438s
Security | Sign check for Cultural Heritage Thesaurus took 0.30950140953063965s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 324.6550302505493s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 11.481248140335083s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.510368824005127s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0010933876037597656s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.021506309509277344s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.6009218692779541s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.7642974853515625e-05s
INFO | --- Analysis for cht took 602.2191889286041s
Availability | SPARQL endpoint availability check for ciard-ring took 0.00010585784912109375s
Availability | VoID file availability check for ciard-ring took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.2959718704223633s
Reputation | Calculation of the PageRank for ciard-ring took 0.021997451782226562s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.458427429199219e-05s
Believability | Calculation of trust value for ciard-ring took 1.52587890625e-05s
INFO | --- Analysis for ciard-ring took 6.159834146499634s
Availability | SPARQL endpoint availability check for Cine Figure took 9.775161743164062e-05s
Availability | VoID file availability check for Cine Figure took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.33603906631469727s
Reputation | Calculation of the PageRank for Cine Figure took 0.02047443389892578s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.4345855712890625e-05s
Believability | Calculation of trust value for Cine Figure took 1.5020370483398438e-05s
INFO | --- Analysis for Cine_Figure took 2.9839138984680176s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 1.8325965404510498s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.3391611576080322s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.02169966697692871s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0008409023284912109s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 5.125999450683594e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.7881393432617188e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 11.364678144454956s
Availability | SPARQL endpoint availability check for CIPFA took 5.698204040527344e-05s
Availability | VoID file availability check for CIPFA took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for CIPFA took 0.41696882247924805s
Reputation | Calculation of the PageRank for CIPFA took 0.021336793899536133s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.9577484130859375e-05s
Believability | Calculation of trust value for CIPFA took 6.67572021484375e-06s
INFO | --- Analysis for cipfa took 3.2110443115234375s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.05978274345398s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.4195830821990967s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.0214846134185791s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00043964385986328125s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 2.1457672119140625e-05s
INFO | --- Analysis for ckan took 347.20341324806213s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.635636568069458s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.39148521423339844s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020998001098632812s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.220008850097656e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.3589859008789062e-05s
INFO | --- Analysis for CLaSSES took 5.3454132080078125s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 0.00010395050048828125s
Availability | VoID file availability check for Temples of the Classical World took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.43929076194763184s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.2901763916015625e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.3113021850585938e-05s
INFO | --- Analysis for classical_temples took 6.453652381896973s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 0.9045307636260986s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.00035572052001953125s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.3403966426849365s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.02127814292907715s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 9.274482727050781e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 1.0251998901367188e-05s
INFO | --- Analysis for clean-energy-data-reegle took 5.66071343421936s
Availability | SPARQL endpoint availability check for CLLD-afbo took 0.00010609626770019531s
Availability | VoID file availability check for CLLD-afbo took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.3238682746887207s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.02328801155090332s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0009396076202392578s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 0.00010132789611816406s
Believability | Calculation of trust value for CLLD-afbo took 1.4066696166992188e-05s
INFO | --- Analysis for clld-afbo took 4.18379020690918s
Availability | SPARQL endpoint availability check for CLLD-APICS took 9.894371032714844e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0003933906555175781s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.31191492080688477s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.021364927291870117s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 8.58306884765625e-05s
Believability | Calculation of trust value for CLLD-APICS took 1.4781951904296875e-05s
INFO | --- Analysis for clld-apics took 4.384275197982788s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.9591064453125e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.31258487701416016s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.025392532348632812s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.001325845718383789s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 5.793571472167969e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 1.049041748046875e-05s
INFO | --- Analysis for clld-ewave took 4.887002229690552s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.887580871582031e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.4217338562011719s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.022026538848876953s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.0001087188720703125s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.4543533325195312e-05s
INFO | --- Analysis for clld-glottolog took 4.846875190734863s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.839897155761719e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.29016637802124023s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.021276235580444336s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.001135110855102539s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 0.00010037422180175781s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.4781951904296875e-05s
INFO | --- Analysis for clld-phoible took 4.790274620056152s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.9591064453125e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.3573296070098877s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.022263526916503906s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0010030269622802734s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 9.393692016601562e-05s
Believability | Calculation of trust value for CLLD-SAILS took 1.0251998901367188e-05s
INFO | --- Analysis for clld-sails took 4.090721607208252s
Availability | SPARQL endpoint availability check for CLLD-WALS took 9.465217590332031e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.31995701789855957s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020809173583984375s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.20159912109375e-05s
Believability | Calculation of trust value for CLLD-WALS took 9.298324584960938e-06s
INFO | --- Analysis for clld-wals took 4.142582416534424s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.6253204345703125e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.32077527046203613s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.02099895477294922s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.963180541992188e-05s
Believability | Calculation of trust value for CLLD-WOLD took 1.0251998901367188e-05s
INFO | --- Analysis for clld-wold took 4.616481304168701s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.1746845245361328s
Availability | VoID file availability check for Cooperation Databank took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.3145618438720703s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.552436828613281e-05s
Believability | Calculation of trust value for Cooperation Databank took 9.775161743164062e-06s
INFO | --- Analysis for CoDa took 3.190011501312256s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 1.1112196445465088s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.3167381286621094s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.020842552185058594s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.266334533691406e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 6.4373016357421875e-06s
INFO | --- Analysis for coins-openuplabs took 4.3559935092926025s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.776899814605713s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.3493828773498535s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.020977020263671875s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.654594421386719e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 1.4781951904296875e-05s
INFO | --- Analysis for CoLChina_sp2000 took 8.399406909942627s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.1882004737854004s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.5279214382171631s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.021021127700805664s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.814697265625e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 2.7894973754882812e-05s
INFO | --- Analysis for colinda took 3.5155601501464844s
Availability | SPARQL endpoint availability check for CN  2012 took 26.40983748435974s
Availability | VoID file availability check for CN  2012 took 0.000732421875s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.2983119487762451s
Reputation | Calculation of the PageRank for CN  2012 took 0.02225351333618164s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0008587837219238281s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.0531158447265625e-05s
Believability | Calculation of trust value for CN  2012 took 1.0013580322265625e-05s
INFO | --- Analysis for combined-nomenclature-2012 took 127.4247899055481s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.43184924125671387s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0008740425109863281s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.30617594718933105s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.030242443084716797s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0013148784637451172s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 6.151199340820312e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.1444091796875e-05s
INFO | --- Analysis for CompHistSem took 4.588631868362427s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 1.713458776473999s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.4414048194885254s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.020969152450561523s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0008535385131835938s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.910064697265625e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.430511474609375e-05s
INFO | --- Analysis for comsode-d3-2 took 8.224509716033936s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 0.00018525123596191406s
Availability | VoID file availability check for 2011 US Congress People took 0.0007791519165039062s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.34058356285095215s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020969152450561523s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.749961853027344e-05s
Believability | Calculation of trust value for 2011 US Congress People took 7.867813110351562e-06s
INFO | --- Analysis for congresspeople took 3.417078733444214s
Availability | SPARQL endpoint availability check for MIMO took 0.23636102676391602s
Availability | VoID file availability check for MIMO took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for MIMO took 0.40932393074035645s
Reputation | Calculation of the PageRank for MIMO took 0.02067089080810547s
Interlinking | Calculation of Degree of Connection for MIMO took 1.52587890625e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.33514404296875e-05s
Believability | Calculation of trust value for MIMO took 1.4066696166992188e-05s
INFO | --- Analysis for CONNECTED took 4.6397545337677s
Availability | SPARQL endpoint availability check for Copyright Free Music took 8.106231689453125e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.3284146785736084s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.02093958854675293s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.218650817871094e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.0251998901367188e-05s
INFO | --- Analysis for Copyright_Free_Music took 6.616149187088013s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 0.0001125335693359375s
Availability | VoID file availability check for CopyrightTermBank took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.31031227111816406s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.021507740020751953s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 8.630752563476562e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.430511474609375e-05s
INFO | --- Analysis for copyrighttermbank took 37.045490026474s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.8258769512176514s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.3170583248138428s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.021749019622802734s
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.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 4.029273986816406e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.4066696166992188e-05s
INFO | --- Analysis for core took 29.84533166885376s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.5084121227264404s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0002875328063964844s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 110.56333231925964s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.994213342666626s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 9.254266500473022s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.216055154800415s
Versatility | Languages check for Corine linked dataset @PSNC took 300.2284822463989s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 1.822195291519165s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.319840669631958s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 9.395539283752441s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.32826972007751465s
License | MR license check for Corine linked dataset @PSNC took 0.7423949241638184s
License | HR license check for Corine linked dataset @PSNC took 300.2026307582855s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.21872735023498535s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.9348373413085938s
Understandability | URI regex check for Corine linked dataset @PSNC took 1.1579773426055908s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.6288797855377197s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.2098701000213623s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.22741103172302246s
Performance | Throughput check for Corine linked dataset @PSNC took 11.584514379501343s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 6.270408630371094e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.21977949142456055s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.2208106517791748s
Interlinking | skos check for Corine linked dataset @PSNC took 0.48503708839416504s
Interlinking | skos check for Corine linked dataset @PSNC took 0.39632391929626465s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 6.672813415527344s
Currency | Creation date check for Corine linked dataset @PSNC took 0.5233416557312012s
Currency | Modification date check for Corine linked dataset @PSNC took 0.24529337882995605s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 155.54916644096375s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.19894146919250488s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.43209218978881836s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.43251967430114746s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 43.38743019104004s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.7007315158843994s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.6884419918060303s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.21654891967773438s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 86.0629243850708s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.283658981323242s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 44.12391805648804s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.5532896518707275s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 87.03000974655151s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.94334077835083s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.6116960048675537s
Security | Sign check for Corine linked dataset @PSNC took 1.0249483585357666s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 10.265701293945312s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 1.3300201892852783s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.021810293197631836s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0008344650268554688s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 4.315376281738281e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.5735626220703125e-05s
INFO | --- Analysis for Corine_linked_dataset took 2291.252338409424s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 0.00012564659118652344s
Availability | VoID file availability check for Cornetto1.2 took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.32233428955078125s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.022104263305664062s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 6.842613220214844e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.5020370483398438e-05s
INFO | --- Analysis for cornetto took 13.660126686096191s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.16997337341308594s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005497932434082031s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 208.1059021949768s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.5835647583007812s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 61.03443646430969s
Interoperability | New terms check for Corporate Body Named Authority List  took 55.6040244102478s
Versatility | Languages check for Corporate Body Named Authority List  took 300.03070545196533s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 16.284228801727295s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.3377852439880371s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.5777506828308105s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 4.344878435134888s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.24144649505615234s
License | MR license check for Corporate Body Named Authority List  took 0.39952635765075684s
License | HR license check for Corporate Body Named Authority List  took 300.105770111084s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.18418645858764648s
Understandability | Number of label check for Corporate Body Named Authority List  took 3.3406448364257812s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.3864924907684326s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.10823225975036621s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.21430397033691406s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.2415297031402588s
Performance | Throughput check for Corporate Body Named Authority List  took 10.543593406677246s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 9.274482727050781e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.1147456169128418s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 6.287256956100464s
Interlinking | skos check for Corporate Body Named Authority List  took 0.44744348526000977s
Interlinking | skos check for Corporate Body Named Authority List  took 0.3174879550933838s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.2656981945037842s
Currency | Creation date check for Corporate Body Named Authority List  took 0.4751269817352295s
Currency | Modification date check for Corporate Body Named Authority List  took 0.16223812103271484s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 415.28764843940735s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.17574620246887207s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.1771235466003418s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.17420625686645508s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 38.35381889343262s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.225595474243164s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.68534255027771s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.1574268341064453s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.5234034061432s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.659709215164185s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 68.08834457397461s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.9286115169525146s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.58463525772095s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.0885136127471924s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.48874616622924805s
Security | Sign check for Corporate Body Named Authority List  took 0.4791531562805176s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 10.998916864395142s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.41493797302246094s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.021735668182373047s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 5.459785461425781e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.430511474609375e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.5020370483398438e-05s
INFO | --- Analysis for corporate-body took 14908.742272377014s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.6044142246246338s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.3270697593688965s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.021481752395629883s
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.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 4.172325134277344e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.5020370483398438e-05s
INFO | --- Analysis for CorpusFibonacci took 20.71730899810791s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.1711423397064209s
Availability | VoID file availability check for Country Name Authority List took 0.0006413459777832031s
Extra | Recovery of all triples for Country Name Authority List took 192.17536425590515s
Performance | Total latancy measurement for Country Name Authority List took 0.5703039169311523s
Amount of data | Number of triples check for Country Name Authority List took 48.77795934677124s
Interoperability | New terms check for Country Name Authority List took 55.98319983482361s
Versatility | Languages check for Country Name Authority List took 300.0807147026062s
Interpretability | Number of blank nodes check for Country Name Authority List took 15.7946937084198s
Security | Check HTTPS for Country Name Authority List took 0.3752317428588867s
Interpretability | RDF structures check for Country Name Authority List took 0.2820169925689697s
Versatility | Serialization formats check for Country Name Authority List took 4.061778545379639s
Availability | RDF dump link check for Country Name Authority List took 0.25325632095336914s
License | MR license check for Country Name Authority List took 0.37275028228759766s
License | HR license check for Country Name Authority List took 300.0754864215851s
Amount of data | Number of property check for Country Name Authority List took 0.1934058666229248s
Understandability | Number of label check for Country Name Authority List took 1.955284833908081s
Understandability | URI regex check for Country Name Authority List took 0.41831088066101074s
Understandability | Vocabs check for Country Name Authority List took 0.09981465339660645s
Verifiability | Authors check for Country Name Authority List took 0.2655644416809082s
Verifiability | Publishers check for Country Name Authority List took 0.19804835319519043s
Performance | Throughput check for Country Name Authority List took 10.635857343673706s
Amount of data | Check the number of entities for Country Name Authority List took 0.00011587142944335938s
Verifiability | Contribs. check for Country Name Authority List took 0.11008358001708984s
Interlinking | sameAs chians check for Country Name Authority List took 8.149209022521973s
Interlinking | skos check for Country Name Authority List took 0.3788166046142578s
Interlinking | skos check for Country Name Authority List took 0.15752506256103516s
Timeliness | dataset update frequency check for Country Name Authority List took 0.30933284759521484s
Currency | Creation date check for Country Name Authority List took 0.4562103748321533s
Currency | Modification date check for Country Name Authority List took 0.14570236206054688s
Rep.Conc. | URIs length for Country Name Authority List took 405.071017742157s
Interoperability | New vocabularies check for Country Name Authority List took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.1830892562866211s
Accuracy | Check Functional Property for Country Name Authority List took 0.210496187210083s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.21140527725219727s
Accuracy | Check Empty annotation labels for Country Name Authority List took 39.20270586013794s
Accuracy | Check White space in annotation for Country Name Authority List took 3.2187161445617676s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.696547269821167s
Consistency | Disjoint class check for Country Name Authority List took 0.1575169563293457s
Consistency | Check Misplaced properties for Country Name Authority List took 300.45204043388367s
Consistency | Misplaced classes for Country Name Authority List took 8.597378253936768s
Consistency | Check Ontology hijacking for Country Name Authority List took 36.39011788368225s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.6617741584777832s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.6324324607849s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.0926191806793213s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.4582979679107666s
Security | Sign check for Country Name Authority List took 0.1262679100036621s
Availability | Check URIs Dereferenciability for Country Name Authority List took 10.80879545211792s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.8335955142974854s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.022218942642211914s
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.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 7.033348083496094e-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 1.1205673217773438e-05s
INFO | --- Analysis for country-authority-list took 14608.265587568283s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.08160400390625s
Availability | VoID file availability check for Courts thesaurus took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.641596794128418s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.021402835845947266s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 7.343292236328125e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.33514404296875e-05s
INFO | --- Analysis for courts-thesaurus took 3.731602668762207s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 20.459868669509888s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0008809566497802734s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.31143975257873535s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 9.107589721679688e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.5020370483398438e-05s
INFO | --- Analysis for Covid-on-the-Web took 55.59049582481384s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.798280477523804s
Availability | VoID file availability check for CPA 2008 took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.3309168815612793s
Reputation | Calculation of the PageRank for CPA 2008 took 0.02120065689086914s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.696846008300781e-05s
Believability | Calculation of trust value for CPA 2008 took 1.0728836059570312e-05s
INFO | --- Analysis for cpa-2008 took 125.64126253128052s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.36859774589538574s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0006146430969238281s
Extra | Recovery of all triples for Cooperative Patent Classification took 21.550055265426636s
Performance | Total latancy measurement for Cooperative Patent Classification took 0.8966312408447266s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.17954063415527s
Versatility | Languages check for Cooperative Patent Classification took 100.23812651634216s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.19243097305298s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.3205430507659912s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.27457571029663086s
Availability | RDF dump link check for Cooperative Patent Classification took 0.19141292572021484s
License | MR license check for Cooperative Patent Classification took 0.23789691925048828s
License | HR license check for Cooperative Patent Classification took 90.22387933731079s
Amount of data | Number of property check for Cooperative Patent Classification took 0.25191307067871094s
Understandability | Number of label check for Cooperative Patent Classification took 90.24612975120544s
Understandability | URI regex check for Cooperative Patent Classification took 0.504436731338501s
Understandability | Vocabs check for Cooperative Patent Classification took 0.201585054397583s
Verifiability | Authors check for Cooperative Patent Classification took 0.22474980354309082s
Verifiability | Publishers check for Cooperative Patent Classification took 0.24090099334716797s
Performance | Throughput check for Cooperative Patent Classification took 10.934906721115112s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.843971252441406e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.1907663345336914s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.18950581550598145s
Interlinking | skos check for Cooperative Patent Classification took 0.19987130165100098s
Interlinking | skos check for Cooperative Patent Classification took 0.17176175117492676s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.1806027889251709s
Currency | Creation date check for Cooperative Patent Classification took 0.38764142990112305s
Currency | Modification date check for Cooperative Patent Classification took 0.3725593090057373s
Rep.Conc. | URIs length for Cooperative Patent Classification took 130.88389229774475s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.19954442977905273s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 17.443294763565063s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.9999821186065674s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.915782690048218s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.19378876686096191s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 100.38363432884216s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 20.63222622871399s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.7338287830352783s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 101.75523972511292s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.867894411087036s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.3435232639312744s
Security | Sign check for Cooperative Patent Classification took 0.23018288612365723s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.6193630695343018s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.5500960350036621s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.02166604995727539s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0009324550628662109s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 1.6689300537109375e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.3828277587890625e-05s
INFO | --- Analysis for CPC took 1180.8449459075928s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.162172079086304s
Availability | VoID file availability check for CPC 2008 took 0.000985860824584961s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.3177633285522461s
Reputation | Calculation of the PageRank for CPC 2008 took 0.02281332015991211s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.863739013671875e-05s
Believability | Calculation of trust value for CPC 2008 took 1.1682510375976562e-05s
INFO | --- Analysis for cpc-2008 took 124.54251551628113s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.809741497039795s
Availability | VoID file availability check for CPV  2003 took 0.0009038448333740234s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.3903353214263916s
Reputation | Calculation of the PageRank for CPV  2003 took 0.022831201553344727s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.2438507080078125e-05s
Believability | Calculation of trust value for CPV  2003 took 1.1444091796875e-05s
INFO | --- Analysis for cpv-2003 took 115.33045673370361s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.529919147491455s
Availability | VoID file availability check for CPV 2008 took 0.0009062290191650391s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.3232760429382324s
Reputation | Calculation of the PageRank for CPV 2008 took 0.023273944854736328s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 5.888938903808594e-05s
Believability | Calculation of trust value for CPV 2008 took 1.2159347534179688e-05s
INFO | --- Analysis for cpv-2008 took 124.24145126342773s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 261.0988726615906s
Availability | VoID file availability check for crowdsourcing-fb took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.5574676990509033s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.02098870277404785s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.887580871582031e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.5974044799804688e-05s
INFO | --- Analysis for crowdsourcing-fb took 536.2047040462494s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.638416528701782s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.38313865661621094s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.02103590965270996s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 5.4836273193359375e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 7.62939453125e-06s
INFO | --- Analysis for ctic-public-dataset took 40.852317810058594s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 2.211305856704712s
Availability | VoID file availability check for CulturaLinkedData took 0.0006234645843505859s
Extra | Recovery of all triples for CulturaLinkedData took 121.56895995140076s
Performance | Total latancy measurement for CulturaLinkedData took 8.098817586898804s
Amount of data | Number of triples check for CulturaLinkedData took 0.8077561855316162s
Interoperability | New terms check for CulturaLinkedData took 2.3444879055023193s
Versatility | Languages check for CulturaLinkedData took 62.36337375640869s
Interpretability | Number of blank nodes check for CulturaLinkedData took 1.9256558418273926s
Interpretability | RDF structures check for CulturaLinkedData took 0.4958498477935791s
Versatility | Serialization formats check for CulturaLinkedData took 2.239806652069092s
Availability | RDF dump link check for CulturaLinkedData took 0.24084806442260742s
License | MR license check for CulturaLinkedData took 0.587134599685669s
License | HR license check for CulturaLinkedData took 61.707751512527466s
Amount of data | Number of property check for CulturaLinkedData took 2.0522854328155518s
Understandability | Number of label check for CulturaLinkedData took 2.790036916732788s
Understandability | URI regex check for CulturaLinkedData took 4.335729598999023s
Understandability | Vocabs check for CulturaLinkedData took 2.0559239387512207s
Verifiability | Authors check for CulturaLinkedData took 0.2808411121368408s
Verifiability | Publishers check for CulturaLinkedData took 2.0227835178375244s
Performance | Throughput check for CulturaLinkedData took 20.50281524658203s
Amount of data | Check the number of entities for CulturaLinkedData took 4.100799560546875e-05s
Verifiability | Contribs. check for CulturaLinkedData took 2.075366497039795s
Interlinking | sameAs chians check for CulturaLinkedData took 0.30298924446105957s
Interlinking | skos check for CulturaLinkedData took 2.271531581878662s
Interlinking | skos check for CulturaLinkedData took 2.0387978553771973s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.3088338375091553s
Currency | Creation date check for CulturaLinkedData took 2.2124576568603516s
Currency | Modification date check for CulturaLinkedData took 2.1585066318511963s
Rep.Conc. | URIs length for CulturaLinkedData took 53.08982181549072s
Interoperability | New vocabularies check for CulturaLinkedData took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.20283102989196777s
Accuracy | Check Functional Property for CulturaLinkedData took 0.18660688400268555s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 2.0303571224212646s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 36.86119246482849s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.619300127029419s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.3101916313171387s
Consistency | Disjoint class check for CulturaLinkedData took 0.25447845458984375s
Consistency | Check Misplaced properties for CulturaLinkedData took 10.539371967315674s
Consistency | Misplaced classes for CulturaLinkedData took 4.20181941986084s
Consistency | Check Ontology hijacking for CulturaLinkedData took 38.39309358596802s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.4087533950805664s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 12.225672245025635s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3817462921142578s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 2.0819406509399414s
Security | Sign check for CulturaLinkedData took 2.7089970111846924s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 10.339403867721558s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.6152117252349854s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.023993492126464844s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0011031627655029297s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 4.363059997558594e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 2.1457672119140625e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.2874603271484375e-05s
INFO | --- Analysis for culturalinkeddata took 598.0062544345856s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.4600808620452881s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.3162393569946289s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.021212339401245117s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.933906555175781e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 1.0728836059570312e-05s
INFO | --- Analysis for cz-ares-or took 3.6574997901916504s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.12028765678405762s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0009171962738037109s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.3469555377960205s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020946741104125977s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0009124279022216797s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.076957702636719e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.049041748046875e-05s
INFO | --- Analysis for cz-ares-rzp took 3.4797279834747314s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.1257021427154541s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.32909488677978516s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.021051645278930664s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.457069396972656e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 1.0251998901367188e-05s
INFO | --- Analysis for cz-cenia-irz-chemicals took 3.3820688724517822s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.11219143867492676s
Availability | VoID file availability check for Integrated pollution registry took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.3199455738067627s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.02256631851196289s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.9577484130859375e-05s
Believability | Calculation of trust value for Integrated pollution registry took 1.049041748046875e-05s
INFO | --- Analysis for cz-cenia-pollution took 3.424569845199585s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.11657953262329102s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0008158683776855469s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.34313178062438965s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02060413360595703s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 4.100799560546875e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 1.1682510375976562e-05s
INFO | --- Analysis for cz-contracts took 3.288271188735962s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.11755752563476562s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.5282418727874756s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.022658348083496094s
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.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.457069396972656e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 6.9141387939453125e-06s
INFO | --- Analysis for cz-ctia-bans took 11.294429063796997s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.11081981658935547s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.00039887428283691406s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.3469383716583252s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.0210113525390625s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.910064697265625e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
INFO | --- Analysis for cz-ctia-confiscations took 3.501356601715088s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11345338821411133s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.2935929298400879s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.023493051528930664s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0012357234954833984s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 4.673004150390625e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 1.1205673217773438e-05s
INFO | --- Analysis for cz-ctia-focus took 3.315615177154541s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.1181032657623291s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0008866786956787109s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.30770111083984375s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0008063316345214844s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 5.435943603515625e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
INFO | --- Analysis for cz-ctia-inspections took 3.422093391418457s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.11366915702819824s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.45236968994140625s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.021384000778198242s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0008683204650878906s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 4.100799560546875e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 1.049041748046875e-05s
INFO | --- Analysis for cz-ctia-sanctions took 10.591676950454712s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.21181750297546387s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0009028911590576172s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.3367149829864502s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020878076553344727s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0008835792541503906s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.1484832763671875e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 1.0728836059570312e-05s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 3.5026633739471436s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.10910224914550781s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0009365081787109375s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.3545253276824951s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.02115321159362793s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.8623809814453125e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 1.0967254638671875e-05s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 3.4202287197113037s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.6896657943725586s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.00032329559326171875s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.3234531879425049s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.0531158447265625e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-czso-average-salaries took 4.017486333847046s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.3670673370361328s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.3164687156677246s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.0531158447265625e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 1.049041748046875e-05s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.6673285961151123s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.33026552200317383s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.33246564865112305s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.020573139190673828s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 6.079673767089844e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0251998901367188e-05s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 4.41019082069397s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.35968685150146484s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.30614614486694336s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.021168947219848633s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.029273986816406e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 1.1920928955078125e-05s
INFO | --- Analysis for cz-czso-job-applicants took 3.9654035568237305s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.36574673652648926s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.2843294143676758s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.021075725555419922s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.410743713378906e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 1.2636184692382812e-05s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 4.0358428955078125s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3535454273223877s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0008928775787353516s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.31323909759521484s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.02084183692932129s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0008649826049804688s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.8623809814453125e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 1.2636184692382812e-05s
INFO | --- Analysis for cz-czso-regions took 3.4790217876434326s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3738417625427246s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.33275604248046875s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.02069711685180664s
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.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 6.4373016357421875e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.815305709838867s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.34038496017456055s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.3251321315765381s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020868539810180664s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.315376281738281e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.803072690963745s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.3575553894042969s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.3344149589538574s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020700693130493164s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 4.887580871582031e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 1.049041748046875e-05s
INFO | --- Analysis for cz-czso-unemployment-rate took 4.000175476074219s
Availability | SPARQL endpoint availability check for ATC groups took 0.11714720726013184s
Availability | VoID file availability check for ATC groups took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for ATC groups took 0.3329620361328125s
Reputation | Calculation of the PageRank for ATC groups took 0.021277189254760742s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0008206367492675781s
Interlinking | Calculation of Clustering coefficient for ATC groups took 8.296966552734375e-05s
Believability | Calculation of trust value for ATC groups took 1.5735626220703125e-05s
INFO | --- Analysis for cz-eh-1-atc took 3.4052622318267822s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.12039661407470703s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.36919212341308594s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020862579345703125s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007829666137695312s
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 1.1682510375976562e-05s
INFO | --- Analysis for cz-fulfillments took 3.3690083026885986s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.024086713790893555s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.4777534008026123s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.0208587646484375s
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.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.9114227294921875e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 1.0013580322265625e-05s
INFO | --- Analysis for cz-ic took 3.7970387935638428s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.12102198600769043s
Availability | VoID file availability check for List of Czech data boxes took 0.0006318092346191406s
Extra | Recovery of all triples for List of Czech data boxes took 137.21209931373596s
Performance | Total latancy measurement for List of Czech data boxes took 0.5745913982391357s
Amount of data | Number of triples check for List of Czech data boxes took 17.032346725463867s
Interoperability | New terms check for List of Czech data boxes took 11.251044988632202s
Versatility | Languages check for List of Czech data boxes took 300.1719882488251s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.3632032871246338s
Interpretability | RDF structures check for List of Czech data boxes took 0.36514902114868164s
Versatility | Serialization formats check for List of Czech data boxes took 0.2406299114227295s
Availability | RDF dump link check for List of Czech data boxes took 15.342383623123169s
License | MR license check for List of Czech data boxes took 0.6335952281951904s
License | HR license check for List of Czech data boxes took 53.19444799423218s
Amount of data | Number of property check for List of Czech data boxes took 0.11035823822021484s
Understandability | Number of label check for List of Czech data boxes took 2.0245442390441895s
Understandability | URI regex check for List of Czech data boxes took 0.5785930156707764s
Understandability | Vocabs check for List of Czech data boxes took 0.29518795013427734s
Verifiability | Authors check for List of Czech data boxes took 0.25878024101257324s
Verifiability | Publishers check for List of Czech data boxes took 0.10487103462219238s
Performance | Throughput check for List of Czech data boxes took 10.825369834899902s
Amount of data | Check the number of entities for List of Czech data boxes took 3.249887228012085s
Verifiability | Contribs. check for List of Czech data boxes took 0.18774771690368652s
Interlinking | sameAs chians check for List of Czech data boxes took 0.41484522819519043s
Interlinking | skos check for List of Czech data boxes took 0.24553632736206055s
Interlinking | skos check for List of Czech data boxes took 0.11432552337646484s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.220322847366333s
Currency | Creation date check for List of Czech data boxes took 0.5227267742156982s
Currency | Modification date check for List of Czech data boxes took 0.20964908599853516s
Rep.Conc. | URIs length for List of Czech data boxes took 110.65055274963379s
Interoperability | New vocabularies check for List of Czech data boxes took 64.24588084220886s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.37522029876708984s
Accuracy | Check Functional Property for List of Czech data boxes took 0.23023724555969238s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.17433691024780273s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 31.357873916625977s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.0749363899230957s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.645418167114258s
Consistency | Disjoint class check for List of Czech data boxes took 0.22132134437561035s
Consistency | Check Misplaced properties for List of Czech data boxes took 68.59375095367432s
Consistency | Misplaced classes for List of Czech data boxes took 7.600580215454102s
Consistency | Check Ontology hijacking for List of Czech data boxes took 31.45276713371277s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.5334579944610596s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 62.42798447608948s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.7201011180877686s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.3587625026702881s
Security | Sign check for List of Czech data boxes took 0.13981986045837402s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 379.4518768787384s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.6712102890014648s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.025190353393554688s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 9.441375732421875e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 58.66204833984375s
Believability | Calculation of trust value for List of Czech data boxes took 1.2159347534179688e-05s
INFO | --- Analysis for cz-list-of-databoxes took 1728.6104049682617s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12252449989318848s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006983280181884766s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 144.4492974281311s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6131017208099365s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.808610439300537s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.947998762130737s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.17223143577576s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.144301414489746s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12012863159179688s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1923668384552002s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 14.661706924438477s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11925172805786133s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 53.209049224853516s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12725353240966797s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3488359451293945s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.22447514533996582s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12024164199829102s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13190340995788574s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13761210441589355s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.709459781646729s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.4096150398254395s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13040614128112793s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.445634126663208s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12021732330322266s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10739946365356445s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.23428654670715332s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.27741146087646484s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10767936706542969s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 110.93911385536194s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 67.51809453964233s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3653733730316162s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11899876594543457s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10791158676147461s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 31.79209613800049s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0692527294158936s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.7283830642700195s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13551878929138184s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 68.35768961906433s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.64698338508606s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 33.71794080734253s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.5091185569763184s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 62.44461369514465s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.794128894805908s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3592658042907715s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12366294860839844s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 374.88798785209656s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3843116760253906s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.021881580352783203s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.1484832763671875e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 46.66441583633423s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.62939453125e-06s
INFO | --- Analysis for cz-nace took 1702.1611487865448s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.33312511444091797s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0006618499755859375s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.1 took 404.5440435409546s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.8038067817687988s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.47864413261413574s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.4566123485565186s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.1 took 232.42969822883606s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.2461483478546143s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.9104430675506592s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.1 took 6.415504455566406s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4134395122528076s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.9919075965881348s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.5666694641113281s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.17595553398132324s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.4572882652282715s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.544213056564331s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.248032808303833s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.5335369110107422s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2594456672668457s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.1 took 10.547544717788696s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.296966552734375e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.22749900817871094s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2326977252960205s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.567091703414917s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.19242072105407715s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.647552728652954s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.6356103420257568s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.454667329788208s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.1 took 92.62535166740417s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.16957402229309082s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.35345983505249023s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.35262632369995117s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.1 took 75.20185613632202s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.4146525859832764s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.7464990615844727s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2799346446990967s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 4.207333326339722s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.161274194717407s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.1 took 75.11311841011047s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.926438808441162s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.540456295013428s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.2078540325164795s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2527899742126465s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.8996951580047607s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.1 took 975.3413724899292s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.3110661506652832s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.02209186553955078s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.00011730194091796875s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.9073486328125e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.0728836059570312e-05s
INFO | --- Analysis for cz-nkod took 40309.08954501152s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.23050785064697266s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.32018041610717773s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.02094411849975586s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.6716461181640625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 1.0013580322265625e-05s
INFO | --- Analysis for cz-orders took 3.516036033630371s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.2080848217010498s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0005936622619628906s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 140.25464725494385s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.6283035278320312s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 9.921557903289795s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 10.7883460521698s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.1578767299652s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.341243028640747s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.12093329429626465s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.19951725006103516s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 15.493637084960938s
License | MR license check for Institutions of public power of the Czech Republic took 0.22452616691589355s
License | HR license check for Institutions of public power of the Czech Republic took 51.54162788391113s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.12338662147521973s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.4555387496948242s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.31986260414123535s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.12784242630004883s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.12956809997558594s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.11263108253479004s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.64045238494873s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.280280351638794s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.13300490379333496s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.4207010269165039s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.18422174453735352s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.11781573295593262s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.2165231704711914s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.24114251136779785s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.13944649696350098s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 111.81067180633545s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 56.660836935043335s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.3486366271972656s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.22517013549804688s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.21218395233154297s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 31.789541721343994s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.098161458969116s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.6623713970184326s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.13402843475341797s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 68.51805853843689s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.632401943206787s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 31.52256464958191s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.5045061111450195s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 62.778467416763306s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.6988210678100586s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.4084160327911377s
Security | Sign check for Institutions of public power of the Czech Republic took 0.14367175102233887s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 387.83956384658813s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.7692432403564453s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.027352571487426758s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 60.17140531539917s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 1.0967254638671875e-05s
INFO | --- Analysis for cz-ovm took 1715.8613204956055s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.10414934158325195s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.3552982807159424s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.022577762603759766s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 1.049041748046875e-05s
INFO | --- Analysis for cz-ovm-agendas took 3.809154510498047s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10179924964904785s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007596015930175781s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 59.67103624343872s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.5491750240325928s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 131.95568084716797s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 33.46328854560852s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.17412281036377s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.19208216667175293s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.45456814765930176s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.21003007888793945s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7870829105377197s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1519627571105957s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1465766429901123s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11617398262023926s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 5.267718553543091s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2415926456451416s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13467121124267578s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.17080473899841309s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.18662691116333008s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.615302801132202s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 3.552436828613281e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11466288566589355s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12621259689331055s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12711620330810547s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12474703788757324s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12198162078857422s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.23433637619018555s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13028192520141602s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 226.18639278411865s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10166168212890625s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13927102088928223s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12782526016235352s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 13.228997230529785s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.212085247039795s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.675016403198242s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12308835983276367s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 169.65296721458435s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.44185996055603s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 18.333163738250732s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.4442076683044434s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 170.91905236244202s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.95884370803833s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.35071802139282227s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10667967796325684s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.913363695144653s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6568114757537842s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.02416706085205078s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.249282836914062e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.6226043701171875e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0728836059570312e-05s
INFO | --- Analysis for cz-ruian took 1763.9211554527283s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7175838947296143s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.3135526180267334s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.02185654640197754s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 0.00012421607971191406s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 6.4373016357421875e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 4.211905479431152s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.4469871520996094s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.47342824935913086s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020931482315063477s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 4.1961669921875e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 1.049041748046875e-05s
INFO | --- Analysis for cz-sao-check-actions took 4.249439477920532s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.46251392364501953s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.34762072563171387s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.02143096923828125s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.504753112792969e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 1.4066696166992188e-05s
INFO | --- Analysis for cz-sao-check-actions-law took 4.011274099349976s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.11343264579772949s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.32386207580566406s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.02104496955871582s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.814697265625e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.5497207641601562e-05s
INFO | --- Analysis for cz-sidc-drug-ingredients took 3.5684430599212646s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.10883903503417969s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.3921332359313965s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.02126336097717285s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0009033679962158203s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.743171691894531e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 1.1444091796875e-05s
INFO | --- Analysis for cz-sidc-drug-prices took 3.828932762145996s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.15374326705932617s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.3573787212371826s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.021616458892822266s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 4.100799560546875e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.621246337890625e-05s
INFO | --- Analysis for cz-sidc-drugs took 3.6565775871276855s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.20414042472839355s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0006682872772216797s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 142.1408007144928s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5967814922332764s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 9.883155822753906s
Interoperability | New terms check for Summary types of Czech institutions of public power took 10.95866346359253s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.184344291687s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.3351497650146484s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.14047884941101074s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.2092905044555664s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 14.804105758666992s
License | MR license check for Summary types of Czech institutions of public power took 0.4777674674987793s
License | HR license check for Summary types of Czech institutions of public power took 53.082218408584595s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.11946845054626465s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.3196017742156982s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.4237654209136963s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.12466597557067871s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.12147116661071777s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.12476897239685059s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.832576274871826s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.2875993251800537s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.1341252326965332s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.41018033027648926s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.1966254711151123s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.11340713500976562s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.2523822784423828s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.24614644050598145s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.12085747718811035s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 110.42727565765381s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 42.45899820327759s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.4081134796142578s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.22478175163269043s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.1971902847290039s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 30.840797185897827s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.0662152767181396s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.627990484237671s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.1126089096069336s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 68.57851529121399s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.6882476806640625s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 31.018951892852783s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.4069807529449463s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 62.556861877441406s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.689175844192505s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.37693047523498535s
Security | Sign check for Summary types of Czech institutions of public power took 0.1647660732269287s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 378.62987637519836s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.819469690322876s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.02243494987487793s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.506111145019531e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 54.397565603256226s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 1.1205673217773438e-05s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 1688.1172378063202s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.10764503479003906s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0007529258728027344s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.383406400680542s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020879745483398438s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.695487976074219e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 1.049041748046875e-05s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 3.7095935344696045s
Availability | SPARQL endpoint availability check for State funding providers took 0.1122438907623291s
Availability | VoID file availability check for State funding providers took 0.0009725093841552734s
Completeness | Calculation of interlinking completeness for State funding providers took 0.4039125442504883s
Reputation | Calculation of the PageRank for State funding providers took 0.0207974910736084s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.3392181396484375e-05s
Believability | Calculation of trust value for State funding providers took 1.239776611328125e-05s
INFO | --- Analysis for cz-vavai-funding-providers took 3.5196993350982666s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.10907101631164551s
Availability | VoID file availability check for Organizations active in R&D took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.31859445571899414s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020474910736083984s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.220008850097656e-05s
Believability | Calculation of trust value for Organizations active in R&D took 8.344650268554688e-06s
INFO | --- Analysis for cz-vavai-organizations took 3.5163254737854004s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.11268472671508789s
Availability | VoID file availability check for R&D Programmes took 0.00072479248046875s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.28606677055358887s
Reputation | Calculation of the PageRank for R&D Programmes took 0.022823810577392578s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 3.9577484130859375e-05s
Believability | Calculation of trust value for R&D Programmes took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-programmes took 3.2474043369293213s
Availability | SPARQL endpoint availability check for R&D Projects took 0.11523842811584473s
Availability | VoID file availability check for R&D Projects took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.3644084930419922s
Reputation | Calculation of the PageRank for R&D Projects took 0.022925615310668945s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.1961669921875e-05s
Believability | Calculation of trust value for R&D Projects took 9.059906005859375e-06s
INFO | --- Analysis for cz-vavai-projects took 3.4035677909851074s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.11386799812316895s
Availability | VoID file availability check for Institutional research plans took 0.0008711814880371094s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.31139206886291504s
Reputation | Calculation of the PageRank for Institutional research plans took 0.022958040237426758s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0011436939239501953s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 5.412101745605469e-05s
Believability | Calculation of trust value for Institutional research plans took 1.0728836059570312e-05s
INFO | --- Analysis for cz-vavai-research-plans took 3.3488147258758545s
Availability | SPARQL endpoint availability check for Results of R&D took 0.11570024490356445s
Availability | VoID file availability check for Results of R&D took 0.0008766651153564453s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.32548022270202637s
Reputation | Calculation of the PageRank for Results of R&D took 0.021158933639526367s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.482269287109375e-05s
Believability | Calculation of trust value for Results of R&D took 1.0251998901367188e-05s
INFO | --- Analysis for cz-vavai-results took 3.458173990249634s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.11289811134338379s
Availability | VoID file availability check for Tenders in R&D took 0.0008831024169921875s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.30771565437316895s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.021064281463623047s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.00543212890625e-05s
Believability | Calculation of trust value for Tenders in R&D took 1.1682510375976562e-05s
INFO | --- Analysis for cz-vavai-tenders took 3.56611967086792s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 0.00016617774963378906s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.36923789978027344s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020827770233154297s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.552436828613281e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.4781951904296875e-05s
INFO | --- Analysis for czech_addresses took 4.998450040817261s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.5803501605987549s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.3237600326538086s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.021114826202392578s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 1.5735626220703125e-05s
INFO | --- Analysis for DanteLatinLoanwords took 4.522761344909668s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.37554073333740234s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0007908344268798828s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 145.11633133888245s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0186851024627686s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 15.011561155319214s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 6.7109715938568115s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 0.22858762741088867s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.2641897201538086s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.15400433540344238s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.4469571113586426s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.25009703636169434s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.2228543758392334s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.2559049129486084s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.31545925140381s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.25945544242858887s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 3.3236796855926514s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.5076782703399658s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.23978543281555176s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.5275871753692627s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.2485804557800293s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.401379346847534s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 9.560585021972656e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.23529601097106934s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 3.102048397064209s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.341796636581421s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.22594046592712402s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.2184000015258789s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 4.955055475234985s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 2.9379308223724365s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 100.01443386077881s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.23263001441955566s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.38550901412963867s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.3158292770385742s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 52.68092465400696s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.2642674446105957s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.6584014892578125s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.3349490165710449s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 34.440940618515015s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.52920413017273s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 68.00207281112671s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.5575411319732666s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 37.07746648788452s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.8684449195861816s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.41568732261657715s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.3183708190917969s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 9.130935430526733s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.43041229248046875s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.021814584732055664s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00015282630920410156s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.9073486328125e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.4781951904296875e-05s
INFO | --- Analysis for data-bnf-fr took 941.7135038375854s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.33289504051208496s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0007331371307373047s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.3436870574951172s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.020977020263671875s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0008034706115722656s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 7.486343383789062e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 1.0967254638671875e-05s
INFO | --- Analysis for data-cnr-it took 4.496323823928833s
Availability | SPARQL endpoint availability check for Data.gov took 1.9017045497894287s
Availability | VoID file availability check for Data.gov took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for Data.gov took 0.3776967525482178s
Reputation | Calculation of the PageRank for Data.gov took 0.021101713180541992s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.24249267578125e-05s
Believability | Calculation of trust value for Data.gov took 1.1205673217773438e-05s
INFO | --- Analysis for data-gov took 19.99651598930359s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.0833132266998291s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.3179042339324951s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020811796188354492s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.414817810058594e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 1.0251998901367188e-05s
INFO | --- Analysis for data-gov-ie took 3.2906906604766846s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 5.221366882324219e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.34842514991760254s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.02100992202758789s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.462501525878906e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 1.0728836059570312e-05s
INFO | --- Analysis for data-gov-uk-time-intervals took 3.073178768157959s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 22.269790410995483s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0007936954498291016s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.4195897579193115s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.020967721939086914s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.985664367675781e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 1.52587890625e-05s
INFO | --- Analysis for data-hnm-hu took 166.68424344062805s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.10582351684570312s
Availability | VoID file availability check for Climb Dataincubator took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.3179664611816406s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.023069381713867188s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.000835418701171875s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 8.630752563476562e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.430511474609375e-05s
INFO | --- Analysis for data-incubator-climb took 3.460749864578247s
Availability | SPARQL endpoint availability check for Discogs in RDF took 9.751319885253906e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.33663105964660645s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020914316177368164s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 0.00010395050048828125s
Believability | Calculation of trust value for Discogs in RDF took 1.4543533325195312e-05s
INFO | --- Analysis for data-incubator-discogs took 5.6902570724487305s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.04996490478515625s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.3300669193267822s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.021283864974975586s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.745887756347656e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 1.0013580322265625e-05s
INFO | --- Analysis for data-incubator-metoffice took 7.003567218780518s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.054300546646118164s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0008320808410644531s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.32004523277282715s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020733118057250977s
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.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 9.369850158691406e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 1.430511474609375e-05s
INFO | --- Analysis for data-incubator-moseley took 8.430537462234497s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.05221104621887207s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.3278825283050537s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.021249771118164062s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 9.202957153320312e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.430511474609375e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 3.2880845069885254s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.9623632431030273s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.31374573707580566s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.02164316177368164s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 9.608268737792969e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 1.1205673217773438e-05s
INFO | --- Analysis for data-incubator-nasa took 9.39612603187561s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.05376267433166504s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.33274292945861816s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.020978450775146484s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 8.058547973632812e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 1.4781951904296875e-05s
INFO | --- Analysis for data-incubator-our-airports took 2.8996524810791016s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.0556333065032959s
Availability | VoID file availability check for Pokedex data in RDF took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.3076636791229248s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.021229028701782227s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0008728504180908203s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 0.00010418891906738281s
Believability | Calculation of trust value for Pokedex data in RDF took 1.33514404296875e-05s
INFO | --- Analysis for data-incubator-pokedex took 3.758289098739624s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.050461530685424805s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.3167078495025635s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020747900009155273s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 9.298324584960938e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.52587890625e-05s
INFO | --- Analysis for data-incubator-smcjournals took 3.983989715576172s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.26813244819641113s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006663799285888672s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 16.277653217315674s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 0.5625436305999756s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 16.105814218521118s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.5545995235443115s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.149501085281372s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.14253282546997s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.19338703155517578s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.18288731575012207s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.3437209129333496s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.1309654712677002s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.22873950004577637s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.158860206604004s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.8279361724853516s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 30.14348816871643s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.30706238746643066s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.4333503246307373s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.2364943027496338s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.2267751693725586s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 11.032852172851562s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 8.130073547363281e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.20110511779785156s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.7079625129699707s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.22062230110168457s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.2831127643585205s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.29221391677856445s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.5788164138793945s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.54207444190979s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 30.45220422744751s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 315.13709783554077s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.1446998119354248s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.15033221244812012s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.135725736618042s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 11.069881439208984s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 3.007896900177002s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.292326927185059s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.1668856143951416s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.48656368255615234s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 8.016679048538208s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 8.588738679885864s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.4911673069000244s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.7450230121612549s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.928736925125122s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.3370046615600586s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.1379709243774414s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.11517000198364258s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.5294075012207031s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.020880699157714844s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 7.271766662597656e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 358.6029281616211s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 1.430511474609375e-05s
INFO | --- Analysis for data-open-ac-uk took 1140.681563615799s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.8149912357330322s
Availability | VoID file availability check for Persée in RDF took 0.0008220672607421875s
Extra | Recovery of all triples for Persée in RDF took 1.1544520854949951s
Performance | Total latancy measurement for Persée in RDF took 0.6636526584625244s
Amount of data | Number of triples check for Persée in RDF took 0.9386255741119385s
Interoperability | New terms check for Persée in RDF took 2.087587594985962s
Versatility | Languages check for Persée in RDF took 121.40694880485535s
Interpretability | Number of blank nodes check for Persée in RDF took 0.39468812942504883s
Interpretability | RDF structures check for Persée in RDF took 1.5921969413757324s
Versatility | Serialization formats check for Persée in RDF took 1.3048205375671387s
Availability | RDF dump link check for Persée in RDF took 0.3503086566925049s
License | MR license check for Persée in RDF took 2.3496835231781006s
License | HR license check for Persée in RDF took 40.58347272872925s
Amount of data | Number of property check for Persée in RDF took 0.13934755325317383s
Understandability | Number of label check for Persée in RDF took 2.095214366912842s
Understandability | URI regex check for Persée in RDF took 0.9897146224975586s
Understandability | Vocabs check for Persée in RDF took 0.4434022903442383s
Verifiability | Authors check for Persée in RDF took 0.6300008296966553s
Verifiability | Publishers check for Persée in RDF took 0.262209415435791s
Performance | Throughput check for Persée in RDF took 10.74461579322815s
Amount of data | Check the number of entities for Persée in RDF took 8.106231689453125e-05s
Verifiability | Contribs. check for Persée in RDF took 0.25390195846557617s
Interlinking | sameAs chians check for Persée in RDF took 0.1958012580871582s
Interlinking | skos check for Persée in RDF took 0.7387027740478516s
Interlinking | skos check for Persée in RDF took 0.1184394359588623s
Timeliness | dataset update frequency check for Persée in RDF took 0.7283523082733154s
Currency | Creation date check for Persée in RDF took 0.629709005355835s
Currency | Modification date check for Persée in RDF took 0.9675555229187012s
Rep.Conc. | URIs length for Persée in RDF took 3.451277017593384s
Interoperability | New vocabularies check for Persée in RDF took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.13885712623596191s
Accuracy | Check Functional Property for Persée in RDF took 0.13284802436828613s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.1457386016845703s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.794675350189209s
Accuracy | Check White space in annotation for Persée in RDF took 0.03962135314941406s
Accuracy | Check Datatype consistency for Persée in RDF took 0.028939008712768555s
Consistency | Disjoint class check for Persée in RDF took 0.33425068855285645s
Consistency | Check Misplaced properties for Persée in RDF took 2.6487388610839844s
Consistency | Misplaced classes for Persée in RDF took 0.2077486515045166s
Consistency | Check Ontology hijacking for Persée in RDF took 2.0175251960754395s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.5080997943878174s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 4.031423568725586s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.03261160850524902s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.1341707706451416s
Security | Sign check for Persée in RDF took 0.8306770324707031s
Availability | Check URIs Dereferenciability for Persée in RDF took 1330.1128659248352s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.6856222152709961s
Reputation | Calculation of the PageRank for Persée in RDF took 0.02386307716369629s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00011897087097167969s
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.5974044799804688e-05s
INFO | --- Analysis for data-persee-fr took 1579.4078705310822s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.1093409061431885s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.3552134037017822s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.022919893264770508s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00012063980102539062s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.4543533325195312e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 9.802427768707275s
Availability | SPARQL endpoint availability check for Open Data Web took 15.810604095458984s
Availability | VoID file availability check for Open Data Web took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.3344888687133789s
Reputation | Calculation of the PageRank for Open Data Web took 0.021546125411987305s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.0994415283203125e-05s
Believability | Calculation of trust value for Open Data Web took 1.3828277587890625e-05s
INFO | --- Analysis for data.odw.tw took 24.047346353530884s
Availability | SPARQL endpoint availability check for datahub took 5.14984130859375e-05s
Availability | VoID file availability check for datahub took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for datahub took 0.3234212398529053s
Reputation | Calculation of the PageRank for datahub took 0.020964622497558594s
Interlinking | Calculation of Degree of Connection for datahub took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for datahub took 4.863739013671875e-05s
Believability | Calculation of trust value for datahub took 9.298324584960938e-06s
INFO | --- Analysis for datahub took 5.133581638336182s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 31.63847327232361s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.3309757709503174s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.02200007438659668s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0009899139404296875s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.790855407714844e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 1.3589859008789062e-05s
INFO | --- Analysis for datahub-kr-datamap took 74.78182983398438s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3311009407043457s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007178783416748047s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3369412422180176s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.021798133850097656s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0008654594421386719s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 8.225440979003906e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.430511474609375e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.962380409240723s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.32777690887451s
Availability | VoID file availability check for datos-artium-org took 0.0008556842803955078s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.5127818584442139s
Reputation | Calculation of the PageRank for datos-artium-org took 0.02102828025817871s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00012993812561035156s
Believability | Calculation of trust value for datos-artium-org took 1.2159347534179688e-05s
INFO | --- Analysis for datos-artium-org took 165.73253059387207s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.7563927173614502s
Availability | VoID file availability check for Datos.bcn.cl took 0.0007610321044921875s
Extra | Recovery of all triples for Datos.bcn.cl took 22.216651439666748s
Performance | Total latancy measurement for Datos.bcn.cl took 6.005293846130371s
Amount of data | Number of triples check for Datos.bcn.cl took 4.52405047416687s
Interoperability | New terms check for Datos.bcn.cl took 3.8811564445495605s
Versatility | Languages check for Datos.bcn.cl took 284.818482875824s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.3185267448425293s
Security | Check HTTPS for Datos.bcn.cl took 0.7472357749938965s
Interpretability | RDF structures check for Datos.bcn.cl took 1.245755672454834s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2422754764556885s
Availability | RDF dump link check for Datos.bcn.cl took 1.2388935089111328s
License | MR license check for Datos.bcn.cl took 1.220238208770752s
License | HR license check for Datos.bcn.cl took 26.42572569847107s
Amount of data | Number of property check for Datos.bcn.cl took 1.2218754291534424s
Understandability | Number of label check for Datos.bcn.cl took 1.445666790008545s
Understandability | URI regex check for Datos.bcn.cl took 2.4217305183410645s
Understandability | Vocabs check for Datos.bcn.cl took 1.2456746101379395s
Verifiability | Authors check for Datos.bcn.cl took 1.1979777812957764s
Verifiability | Publishers check for Datos.bcn.cl took 1.2014188766479492s
Performance | Throughput check for Datos.bcn.cl took 12.04198956489563s
Amount of data | Check the number of entities for Datos.bcn.cl took 0.00011801719665527344s
Verifiability | Contribs. check for Datos.bcn.cl took 1.202681303024292s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.2267019748687744s
Interlinking | skos check for Datos.bcn.cl took 1.219430923461914s
Interlinking | skos check for Datos.bcn.cl took 1.2241857051849365s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.2350342273712158s
Currency | Creation date check for Datos.bcn.cl took 2.467390775680542s
Currency | Modification date check for Datos.bcn.cl took 1.1947450637817383s
Rep.Conc. | URIs length for Datos.bcn.cl took 30.26450514793396s
Interoperability | New vocabularies check for Datos.bcn.cl took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.2316334247589111s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.2491381168365479s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.2057178020477295s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 22.690069437026978s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.32764267921447754s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.2756383419036865s
Consistency | Disjoint class check for Datos.bcn.cl took 1.185621976852417s
Consistency | Check Misplaced properties for Datos.bcn.cl took 7.601323366165161s
Consistency | Misplaced classes for Datos.bcn.cl took 2.0651655197143555s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 16.58642816543579s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.4580731391906738s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 7.447526454925537s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.2998039722442627s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.4744417667388916s
Security | Sign check for Datos.bcn.cl took 1.2061922550201416s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 7418.181688547134s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.856837272644043s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.023021936416625977s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 0.0001323223114013672s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.6689300537109375e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 7.152557373046875e-06s
INFO | --- Analysis for datos-bcn-cl took 8509.536714076996s
Availability | SPARQL endpoint availability check for datos.bne.es took 2.5134174823760986s
Availability | VoID file availability check for datos.bne.es took 0.0004622936248779297s
Extra | Recovery of all triples for datos.bne.es took 134.41659998893738s
Performance | Total latancy measurement for datos.bne.es took 4.998654127120972s
Amount of data | Number of triples check for datos.bne.es took 2.726694345474243s
Interoperability | New terms check for datos.bne.es took 2.5143773555755615s
Versatility | Languages check for datos.bne.es took 65.08340573310852s
Interpretability | Number of blank nodes check for datos.bne.es took 2.030092477798462s
Security | Check HTTPS for datos.bne.es took 0.19429397583007812s
Interpretability | RDF structures check for datos.bne.es took 2.308881998062134s
Versatility | Serialization formats check for datos.bne.es took 0.5133678913116455s
Availability | RDF dump link check for datos.bne.es took 2.180265188217163s
License | MR license check for datos.bne.es took 0.6957745552062988s
License | HR license check for datos.bne.es took 61.37721824645996s
Amount of data | Number of property check for datos.bne.es took 2.2022807598114014s
Understandability | Number of label check for datos.bne.es took 1.1522374153137207s
Understandability | URI regex check for datos.bne.es took 0.8140158653259277s
Understandability | Vocabs check for datos.bne.es took 0.3773922920227051s
Verifiability | Authors check for datos.bne.es took 2.219454526901245s
Verifiability | Publishers check for datos.bne.es took 0.345308780670166s
Performance | Throughput check for datos.bne.es took 22.75969123840332s
Amount of data | Check the number of entities for datos.bne.es took 4.1484832763671875e-05s
Verifiability | Contribs. check for datos.bne.es took 0.37868809700012207s
Interlinking | sameAs chians check for datos.bne.es took 2.196256637573242s
Interlinking | skos check for datos.bne.es took 0.5866971015930176s
Interlinking | skos check for datos.bne.es took 2.140902519226074s
Timeliness | dataset update frequency check for datos.bne.es took 2.1866860389709473s
Currency | Creation date check for datos.bne.es took 4.339216470718384s
Currency | Modification date check for datos.bne.es took 0.6357731819152832s
Rep.Conc. | URIs length for datos.bne.es took 53.76894783973694s
Interoperability | New vocabularies check for datos.bne.es took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 0.3075284957885742s
Accuracy | Check Functional Property for datos.bne.es took 2.135993003845215s
Accuracy | Check Inverse Functional Property for datos.bne.es took 2.172163724899292s
Accuracy | Check Empty annotation labels for datos.bne.es took 45.20486235618591s
Accuracy | Check White space in annotation for datos.bne.es took 1.6221871376037598s
Accuracy | Check Datatype consistency for datos.bne.es took 1.3432936668395996s
Consistency | Disjoint class check for datos.bne.es took 2.1811349391937256s
Consistency | Check Misplaced properties for datos.bne.es took 11.346112251281738s
Consistency | Misplaced classes for datos.bne.es took 4.339059352874756s
Consistency | Check Ontology hijacking for datos.bne.es took 45.71204733848572s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.414536952972412s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 11.973358869552612s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.3986272811889648s
Conciseness | Check Intensional conciseness for datos.bne.es took 0.2952005863189697s
Security | Sign check for datos.bne.es took 0.9825141429901123s
Availability | Check URIs Dereferenciability for datos.bne.es took 10.10903263092041s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.4903414249420166s
Reputation | Calculation of the PageRank for datos.bne.es took 0.021870136260986328s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00012302398681640625s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 2.384185791015625e-06s
Believability | Calculation of trust value for datos.bne.es took 1.1682510375976562e-05s
INFO | --- Analysis for datos-bne-es took 655.875027179718s
Availability | SPARQL endpoint availability check for dbacademic took 0.05808615684509277s
Availability | VoID file availability check for dbacademic took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for dbacademic took 0.29187560081481934s
Reputation | Calculation of the PageRank for dbacademic took 0.020731210708618164s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.3855438232421875e-05s
Believability | Calculation of trust value for dbacademic took 1.0728836059570312e-05s
INFO | --- Analysis for dbacademic took 3.003025770187378s
Availability | SPARQL endpoint availability check for DBkWik took 0.20364999771118164s
Availability | VoID file availability check for DBkWik took 0.0006809234619140625s
Extra | Recovery of all triples for DBkWik took 1.5254566669464111s
Performance | Total latancy measurement for DBkWik took 0.46268749237060547s
Amount of data | Number of triples check for DBkWik took 5.528591632843018s
Interoperability | New terms check for DBkWik took 2.256350517272949s
Versatility | Languages check for DBkWik took 60.75890040397644s
Interpretability | Number of blank nodes check for DBkWik took 0.15616655349731445s
Interpretability | RDF structures check for DBkWik took 0.27224278450012207s
Versatility | Serialization formats check for DBkWik took 0.29703569412231445s
Availability | RDF dump link check for DBkWik took 2.6857080459594727s
License | MR license check for DBkWik took 0.35918378829956055s
License | HR license check for DBkWik took 61.497512102127075s
Amount of data | Number of property check for DBkWik took 0.1401817798614502s
Understandability | Number of label check for DBkWik took 2.0660347938537598s
Understandability | URI regex check for DBkWik took 0.3191087245941162s
Understandability | Vocabs check for DBkWik took 0.12894797325134277s
Verifiability | Authors check for DBkWik took 0.12401652336120605s
Verifiability | Publishers check for DBkWik took 0.10705280303955078s
Performance | Throughput check for DBkWik took 10.4415442943573s
Amount of data | Check the number of entities for DBkWik took 0.00011968612670898438s
Verifiability | Contribs. check for DBkWik took 0.12551641464233398s
Interlinking | sameAs chians check for DBkWik took 0.4239528179168701s
Interlinking | skos check for DBkWik took 0.5267059803009033s
Interlinking | skos check for DBkWik took 0.09393453598022461s
Timeliness | dataset update frequency check for DBkWik took 0.19771909713745117s
Currency | Creation date check for DBkWik took 0.4058854579925537s
Currency | Modification date check for DBkWik took 0.21332454681396484s
Rep.Conc. | URIs length for DBkWik took 11.266119003295898s
Interoperability | New vocabularies check for DBkWik took 15.980609893798828s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.12682127952575684s
Accuracy | Check Functional Property for DBkWik took 0.33463525772094727s
Accuracy | Check Inverse Functional Property for DBkWik took 0.26762962341308594s
Accuracy | Check Empty annotation labels for DBkWik took 1.2717530727386475s
Accuracy | Check White space in annotation for DBkWik took 0.023380517959594727s
Accuracy | Check Datatype consistency for DBkWik took 0.03803133964538574s
Consistency | Disjoint class check for DBkWik took 0.145003080368042s
Consistency | Check Misplaced properties for DBkWik took 12.273526668548584s
Consistency | Misplaced classes for DBkWik took 0.6220612525939941s
Consistency | Check Ontology hijacking for DBkWik took 1.9473206996917725s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.4045894145965576s
Consistency | Check Invalid usage of undefined properties for DBkWik took 12.035678625106812s
Conciseness | Check Extensional conciseness for DBkWik took 0.03316307067871094s
Conciseness | Check Intensional conciseness for DBkWik took 0.6572647094726562s
Security | Sign check for DBkWik took 0.2878837585449219s
Availability | Check URIs Dereferenciability for DBkWik took 9.444687604904175s
Completeness | Calculation of interlinking completeness for DBkWik took 0.45604467391967773s
Reputation | Calculation of the PageRank for DBkWik took 0.19048738479614258s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for DBkWik took 8.58306884765625e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 14.268148422241211s
Believability | Calculation of trust value for DBkWik took 1.5497207641601562e-05s
INFO | --- Analysis for dbkwik took 1445.2357122898102s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.00017571449279785156s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.2956852912902832s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.021241426467895508s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00011467933654785156s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.4066696166992188e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 5.3830342292785645s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.3704233169555664s
Availability | VoID file availability check for dblp Knowledge Graph took 0.00036525726318359375s
Extra | Recovery of all triples for dblp Knowledge Graph took 7.187762260437012s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.9270675182342529s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.1891770362854004s
Interoperability | New terms check for dblp Knowledge Graph took 1.9479217529296875s
Versatility | Languages check for dblp Knowledge Graph took 0.18758344650268555s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 7.20972466468811s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.1524052619934082s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.16206121444702148s
Availability | RDF dump link check for dblp Knowledge Graph took 0.16881561279296875s
License | MR license check for dblp Knowledge Graph took 0.14419174194335938s
License | HR license check for dblp Knowledge Graph took 30.126517295837402s
Amount of data | Number of property check for dblp Knowledge Graph took 0.154083251953125s
Understandability | Number of label check for dblp Knowledge Graph took 0.42418956756591797s
Understandability | URI regex check for dblp Knowledge Graph took 0.28436779975891113s
Understandability | Vocabs check for dblp Knowledge Graph took 0.1852872371673584s
Verifiability | Authors check for dblp Knowledge Graph took 0.18758630752563477s
Verifiability | Publishers check for dblp Knowledge Graph took 0.18435907363891602s
Performance | Throughput check for dblp Knowledge Graph took 10.7795250415802s
Amount of data | Check the number of entities for dblp Knowledge Graph took 7.700920104980469e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.13889622688293457s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.21298789978027344s
Interlinking | skos check for dblp Knowledge Graph took 0.15299105644226074s
Interlinking | skos check for dblp Knowledge Graph took 0.12878704071044922s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.1649010181427002s
Currency | Creation date check for dblp Knowledge Graph took 0.30359697341918945s
Currency | Modification date check for dblp Knowledge Graph took 0.2981386184692383s
Rep.Conc. | URIs length for dblp Knowledge Graph took 42.074116945266724s
Interoperability | New vocabularies check for dblp Knowledge Graph took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.18013596534729004s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.12922430038452148s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.14815831184387207s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 7.462033271789551s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.0938260555267334s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.316097974777222s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.18082952499389648s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.29462313652038574s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 6.7823920249938965s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 20465.966096401215s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 8.65691089630127s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.735400676727295s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.1618177890777588s
Security | Sign check for dblp Knowledge Graph took 0.13992881774902344s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 3.0207860469818115s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.71311354637146s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.022318601608276367s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 2.4080276489257812e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 5.9604644775390625e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 1.4781951904296875e-05s
INFO | --- Analysis for dblp-kg took 20666.042605876923s
Availability | SPARQL endpoint availability check for DBnary took 0.3564448356628418s
Availability | VoID file availability check for DBnary took 0.0006108283996582031s
Extra | Recovery of all triples for DBnary took 1.2838242053985596s
Performance | Total latancy measurement for DBnary took 0.5034425258636475s
Amount of data | Number of triples check for DBnary took 1.2202990055084229s
Interoperability | New terms check for DBnary took 3.8873114585876465s
Versatility | Languages check for DBnary took 60.682621717453s
Interpretability | Number of blank nodes check for DBnary took 4.931468963623047s
Security | Check HTTPS for DBnary took 0.2333967685699463s
Interpretability | RDF structures check for DBnary took 0.1740424633026123s
Versatility | Serialization formats check for DBnary took 0.17953920364379883s
Availability | RDF dump link check for DBnary took 0.07823395729064941s
License | MR license check for DBnary took 0.4196019172668457s
License | HR license check for DBnary took 61.9577956199646s
Amount of data | Number of property check for DBnary took 0.12847352027893066s
Understandability | Number of label check for DBnary took 0.9396159648895264s
Understandability | URI regex check for DBnary took 0.18115520477294922s
Understandability | Vocabs check for DBnary took 0.1392052173614502s
Verifiability | Authors check for DBnary took 0.1689600944519043s
Verifiability | Publishers check for DBnary took 0.17895102500915527s
Performance | Throughput check for DBnary took 10.358649730682373s
Amount of data | Check the number of entities for DBnary took 6.723403930664062e-05s
Verifiability | Contribs. check for DBnary took 0.174210786819458s
Interlinking | sameAs chians check for DBnary took 0.12564325332641602s
Interlinking | skos check for DBnary took 0.16040682792663574s
Interlinking | skos check for DBnary took 0.10194873809814453s
Timeliness | dataset update frequency check for DBnary took 0.1604759693145752s
Currency | Creation date check for DBnary took 0.3014664649963379s
Currency | Modification date check for DBnary took 0.22673964500427246s
Rep.Conc. | URIs length for DBnary took 11.22230839729309s
Interoperability | New vocabularies check for DBnary took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for DBnary took 0.11015653610229492s
Accuracy | Check Functional Property for DBnary took 0.19203472137451172s
Accuracy | Check Inverse Functional Property for DBnary took 0.14709854125976562s
Accuracy | Check Empty annotation labels for DBnary took 0.43607139587402344s
Accuracy | Check White space in annotation for DBnary took 0.02991962432861328s
Accuracy | Check Datatype consistency for DBnary took 0.029199838638305664s
Consistency | Disjoint class check for DBnary took 0.18000364303588867s
Consistency | Check Misplaced properties for DBnary took 8.764708518981934s
Consistency | Misplaced classes for DBnary took 0.26042604446411133s
Consistency | Check Ontology hijacking for DBnary took 2.098632574081421s
Consistency | Check Invalid usage of undefined classes for DBnary took 1.66969895362854s
Consistency | Check Invalid usage of undefined properties for DBnary took 10.20391035079956s
Conciseness | Check Extensional conciseness for DBnary took 0.039736270904541016s
Conciseness | Check Intensional conciseness for DBnary took 0.21496033668518066s
Security | Sign check for DBnary took 0.09127688407897949s
Availability | Check URIs Dereferenciability for DBnary took 10.916287660598755s
Completeness | Calculation of interlinking completeness for DBnary took 0.29702186584472656s
Reputation | Calculation of the PageRank for DBnary took 0.02131175994873047s
Interlinking | Calculation of Degree of Connection for DBnary took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for DBnary took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for DBnary took 6.318092346191406e-05s
Interoperability | Check the re-using of existing vocabs for DBnary took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBnary took 1.1444091796875e-05s
INFO | --- Analysis for dbnary took 316.5827476978302s
Availability | SPARQL endpoint availability check for DBpedia took 0.9511029720306396s
Availability | VoID file availability check for DBpedia took 0.0006041526794433594s
Extra | Recovery of all triples for DBpedia took 2.9554426670074463s
Performance | Total latancy measurement for DBpedia took 2.8406412601470947s
Amount of data | Number of triples check for DBpedia took 1.8096604347229004s
Interoperability | New terms check for DBpedia took 5.901817560195923s
Versatility | Languages check for DBpedia took 31.324931144714355s
Interpretability | Number of blank nodes check for DBpedia took 0.5571818351745605s
Security | Check HTTPS for DBpedia took 0.35759735107421875s
Interpretability | RDF structures check for DBpedia took 0.8536479473114014s
Versatility | Serialization formats check for DBpedia took 0.7220902442932129s
Availability | RDF dump link check for DBpedia took 0.5604891777038574s
License | MR license check for DBpedia took 0.6703917980194092s
License | HR license check for DBpedia took 31.92406988143921s
Amount of data | Number of property check for DBpedia took 0.6044743061065674s
Understandability | Number of label check for DBpedia took 4.926559925079346s
Understandability | URI regex check for DBpedia took 1.124915599822998s
Understandability | Vocabs check for DBpedia took 0.6673846244812012s
Verifiability | Authors check for DBpedia took 0.6131284236907959s
Verifiability | Publishers check for DBpedia took 0.6188650131225586s
Performance | Throughput check for DBpedia took 11.260270833969116s
Amount of data | Check the number of entities for DBpedia took 4.029273986816406e-05s
Verifiability | Contribs. check for DBpedia took 0.6109468936920166s
Interlinking | sameAs chians check for DBpedia took 2.625775098800659s
Interlinking | skos check for DBpedia took 0.5935163497924805s
Interlinking | skos check for DBpedia took 0.5615742206573486s
Timeliness | dataset update frequency check for DBpedia took 0.6220355033874512s
Currency | Creation date check for DBpedia took 1.2285146713256836s
Currency | Modification date check for DBpedia took 1.9805502891540527s
Rep.Conc. | URIs length for DBpedia took 35.42646527290344s
Interoperability | New vocabularies check for DBpedia took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.591834306716919s
Accuracy | Check Functional Property for DBpedia took 0.594285249710083s
Accuracy | Check Inverse Functional Property for DBpedia took 0.5700714588165283s
Accuracy | Check Empty annotation labels for DBpedia took 2.6904304027557373s
Accuracy | Check White space in annotation for DBpedia took 0.029628753662109375s
Accuracy | Check Datatype consistency for DBpedia took 0.028941869735717773s
Consistency | Disjoint class check for DBpedia took 0.5944278240203857s
Consistency | Check Misplaced properties for DBpedia took 33.33302688598633s
Consistency | Misplaced classes for DBpedia took 1.6651544570922852s
Consistency | Check Ontology hijacking for DBpedia took 3.8075015544891357s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.3871276378631592s
Consistency | Check Invalid usage of undefined properties for DBpedia took 2.9071288108825684s
Conciseness | Check Extensional conciseness for DBpedia took 0.032453298568725586s
Conciseness | Check Intensional conciseness for DBpedia took 3.4511473178863525s
Security | Sign check for DBpedia took 0.6138548851013184s
Availability | Check URIs Dereferenciability for DBpedia took 4074.8971939086914s
Completeness | Calculation of interlinking completeness for DBpedia took 0.8755321502685547s
Reputation | Calculation of the PageRank for DBpedia took 0.02680349349975586s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008978843688964844s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia took 1.0728836059570312e-05s
INFO | --- Analysis for dbpedia took 6572.785293579102s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 5.364418029785156e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.33101654052734375s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.02114701271057129s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 7.104873657226562e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.4066696166992188e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 7.962078332901001s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.179077863693237s
Availability | VoID file availability check for DBpedia Commons took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.3487262725830078s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.937980651855469e-05s
Believability | Calculation of trust value for DBpedia Commons took 1.3828277587890625e-05s
INFO | --- Analysis for dbpedia-commons took 16.629555702209473s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 0.3813149929046631s
Availability | VoID file availability check for DBpedia in Greek took 0.0006153583526611328s
Extra | Recovery of all triples for DBpedia in Greek took 1.499570369720459s
Performance | Total latancy measurement for DBpedia in Greek took 1.2041761875152588s
Amount of data | Number of triples check for DBpedia in Greek took 0.6037180423736572s
Interoperability | New terms check for DBpedia in Greek took 1.8052818775177002s
Versatility | Languages check for DBpedia in Greek took 13.457096338272095s
Interpretability | Number of blank nodes check for DBpedia in Greek took 0.25516796112060547s
Security | Check HTTPS for DBpedia in Greek took 0.1531686782836914s
Interpretability | RDF structures check for DBpedia in Greek took 0.2907419204711914s
Versatility | Serialization formats check for DBpedia in Greek took 0.2500028610229492s
Availability | RDF dump link check for DBpedia in Greek took 0.23372173309326172s
License | MR license check for DBpedia in Greek took 0.2655010223388672s
License | HR license check for DBpedia in Greek took 2.4306252002716064s
Amount of data | Number of property check for DBpedia in Greek took 0.25952839851379395s
Understandability | Number of label check for DBpedia in Greek took 0.328571081161499s
Understandability | URI regex check for DBpedia in Greek took 0.5009181499481201s
Understandability | Vocabs check for DBpedia in Greek took 0.2290356159210205s
Verifiability | Authors check for DBpedia in Greek took 0.23505520820617676s
Verifiability | Publishers check for DBpedia in Greek took 0.2289905548095703s
Performance | Throughput check for DBpedia in Greek took 11.632423162460327s
Amount of data | Check the number of entities for DBpedia in Greek took 8.511543273925781e-05s
Verifiability | Contribs. check for DBpedia in Greek took 0.2637038230895996s
Interlinking | sameAs chians check for DBpedia in Greek took 0.2856168746948242s
Interlinking | skos check for DBpedia in Greek took 0.3808298110961914s
Interlinking | skos check for DBpedia in Greek took 0.2446298599243164s
Timeliness | dataset update frequency check for DBpedia in Greek took 0.3355903625488281s
Currency | Creation date check for DBpedia in Greek took 0.46552419662475586s
Currency | Modification date check for DBpedia in Greek took 0.488814115524292s
Rep.Conc. | URIs length for DBpedia in Greek took 1.8165371417999268s
Interoperability | New vocabularies check for DBpedia in Greek took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Greek took 0.2472829818725586s
Accuracy | Check Functional Property for DBpedia in Greek took 0.26754188537597656s
Accuracy | Check Inverse Functional Property for DBpedia in Greek took 0.2784309387207031s
Accuracy | Check Empty annotation labels for DBpedia in Greek took 0.621894121170044s
Accuracy | Check White space in annotation for DBpedia in Greek took 0.032379865646362305s
Accuracy | Check Datatype consistency for DBpedia in Greek took 0.028381824493408203s
Consistency | Disjoint class check for DBpedia in Greek took 0.2238309383392334s
Consistency | Check Misplaced properties for DBpedia in Greek took 1.3962640762329102s
Consistency | Misplaced classes for DBpedia in Greek took 0.6709470748901367s
Consistency | Check Ontology hijacking for DBpedia in Greek took 2.050931215286255s
Consistency | Check Invalid usage of undefined classes for DBpedia in Greek took 1.4135613441467285s
Consistency | Check Invalid usage of undefined properties for DBpedia in Greek took 2.3825340270996094s
Conciseness | Check Extensional conciseness for DBpedia in Greek took 0.034372806549072266s
Conciseness | Check Intensional conciseness for DBpedia in Greek took 0.8042850494384766s
Security | Sign check for DBpedia in Greek took 0.2633349895477295s
Availability | Check URIs Dereferenciability for DBpedia in Greek took 2134.7775568962097s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.7711043357849121s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.022601842880249023s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.0002071857452392578s
Interoperability | Check the re-using of existing vocabs for DBpedia in Greek took 1.9073486328125e-06s
Believability | Calculation of trust value for DBpedia in Greek took 1.0728836059570312e-05s
INFO | --- Analysis for dbpedia-el took 2255.366961479187s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.4567134380340576s
Availability | VoID file availability check for DBpedia in Spanish took 0.0007691383361816406s
Extra | Recovery of all triples for DBpedia in Spanish took 2.108661651611328s
Performance | Total latancy measurement for DBpedia in Spanish took 1.2571351528167725s
Amount of data | Number of triples check for DBpedia in Spanish took 0.8445625305175781s
Interoperability | New terms check for DBpedia in Spanish took 3.072535514831543s
Versatility | Languages check for DBpedia in Spanish took 62.124682664871216s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.434110164642334s
Security | Check HTTPS for DBpedia in Spanish took 0.1383042335510254s
Interpretability | RDF structures check for DBpedia in Spanish took 1.0031700134277344s
Versatility | Serialization formats check for DBpedia in Spanish took 0.5441229343414307s
Availability | RDF dump link check for DBpedia in Spanish took 0.36796140670776367s
License | MR license check for DBpedia in Spanish took 0.8295130729675293s
License | HR license check for DBpedia in Spanish took 61.52339267730713s
Amount of data | Number of property check for DBpedia in Spanish took 0.328157901763916s
Understandability | Number of label check for DBpedia in Spanish took 1.9650208950042725s
Understandability | URI regex check for DBpedia in Spanish took 1.0043399333953857s
Understandability | Vocabs check for DBpedia in Spanish took 0.39861440658569336s
Verifiability | Authors check for DBpedia in Spanish took 0.31267786026000977s
Verifiability | Publishers check for DBpedia in Spanish took 0.31768202781677246s
Performance | Throughput check for DBpedia in Spanish took 11.462138652801514s
Amount of data | Check the number of entities for DBpedia in Spanish took 7.05718994140625e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.30068349838256836s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.7136492729187012s
Interlinking | skos check for DBpedia in Spanish took 0.6671404838562012s
Interlinking | skos check for DBpedia in Spanish took 0.23155713081359863s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.46315550804138184s
Currency | Creation date check for DBpedia in Spanish took 0.6497704982757568s
Currency | Modification date check for DBpedia in Spanish took 0.6311962604522705s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.811290979385376s
Interoperability | New vocabularies check for DBpedia in Spanish took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.3420546054840088s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.4924306869506836s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.5328273773193359s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.2530884742736816s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.03047657012939453s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.034496307373046875s
Consistency | Disjoint class check for DBpedia in Spanish took 0.5788998603820801s
Consistency | Check Misplaced properties for DBpedia in Spanish took 7.992007732391357s
Consistency | Misplaced classes for DBpedia in Spanish took 1.1452524662017822s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.5432283878326416s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.4022557735443115s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 6.888516902923584s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.033525705337524414s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.3881735801696777s
Security | Sign check for DBpedia in Spanish took 0.3359227180480957s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 3.2569196224212646s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.41167569160461426s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.021414995193481445s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00011229515075683594s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 9.775161743164062e-06s
INFO | --- Analysis for dbpedia-es took 1172.9626684188843s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.1997663974761963s
Availability | VoID file availability check for DBpedia in Basque took 0.0003790855407714844s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.3335092067718506s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.02132725715637207s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.337860107421875e-05s
Believability | Calculation of trust value for DBpedia in Basque took 6.67572021484375e-06s
INFO | --- Analysis for dbpedia-eu took 7.242784261703491s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.1911940574645996s
Availability | VoID file availability check for DBpedia in French took 0.0005593299865722656s
Extra | Recovery of all triples for DBpedia in French took 82.63072061538696s
Performance | Total latancy measurement for DBpedia in French took 0.40928053855895996s
Amount of data | Number of triples check for DBpedia in French took 2.070171594619751s
Interoperability | New terms check for DBpedia in French took 2.4748177528381348s
Versatility | Languages check for DBpedia in French took 300.04847717285156s
Interpretability | Number of blank nodes check for DBpedia in French took 0.3587627410888672s
Security | Check HTTPS for DBpedia in French took 0.21740102767944336s
Interpretability | RDF structures check for DBpedia in French took 0.5577454566955566s
Versatility | Serialization formats check for DBpedia in French took 0.386455774307251s
Availability | RDF dump link check for DBpedia in French took 6.827994108200073s
License | MR license check for DBpedia in French took 1.579361915588379s
License | HR license check for DBpedia in French took 87.9166669845581s
Amount of data | Number of property check for DBpedia in French took 0.18271088600158691s
Understandability | Number of label check for DBpedia in French took 2.342670440673828s
Understandability | URI regex check for DBpedia in French took 0.35092997550964355s
Understandability | Vocabs check for DBpedia in French took 0.1805117130279541s
Verifiability | Authors check for DBpedia in French took 0.2956235408782959s
Verifiability | Publishers check for DBpedia in French took 0.15123200416564941s
Performance | Throughput check for DBpedia in French took 10.490645408630371s
Amount of data | Check the number of entities for DBpedia in French took 2.2564516067504883s
Verifiability | Contribs. check for DBpedia in French took 0.2202754020690918s
Interlinking | sameAs chians check for DBpedia in French took 0.37940073013305664s
Interlinking | skos check for DBpedia in French took 0.36348533630371094s
Interlinking | skos check for DBpedia in French took 0.08747386932373047s
Timeliness | dataset update frequency check for DBpedia in French took 0.4926598072052002s
Currency | Creation date check for DBpedia in French took 0.29343223571777344s
Currency | Modification date check for DBpedia in French took 0.22903823852539062s
Rep.Conc. | URIs length for DBpedia in French took 38.58916234970093s
Interoperability | New vocabularies check for DBpedia in French took 19.946459770202637s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.12274932861328125s
Accuracy | Check Functional Property for DBpedia in French took 0.16778087615966797s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.12283849716186523s
Accuracy | Check Empty annotation labels for DBpedia in French took 26.338645935058594s
Accuracy | Check White space in annotation for DBpedia in French took 3.1163713932037354s
Accuracy | Check Datatype consistency for DBpedia in French took 2.6964168548583984s
Consistency | Disjoint class check for DBpedia in French took 0.2870604991912842s
Consistency | Check Misplaced properties for DBpedia in French took 7.358677625656128s
Consistency | Misplaced classes for DBpedia in French took 9.391188383102417s
Consistency | Check Ontology hijacking for DBpedia in French took 21.342429399490356s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.4836933612823486s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 8.120619058609009s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.0246057510375977s
Conciseness | Check Intensional conciseness for DBpedia in French took 1.9197192192077637s
Security | Sign check for DBpedia in French took 0.12441039085388184s
Availability | Check URIs Dereferenciability for DBpedia in French took 2337.9051880836487s
Completeness | Calculation of interlinking completeness for DBpedia in French took 1.441840648651123s
Reputation | Calculation of the PageRank for DBpedia in French took 0.022797346115112305s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0009355545043945312s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.0001628398895263672s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 41.860968351364136s
Believability | Calculation of trust value for DBpedia in French took 6.67572021484375e-06s
INFO | --- Analysis for dbpedia-fr took 3205.238360643387s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.9141476154327393s
Availability | VoID file availability check for DBpedia in Japanese took 4.087045669555664s
Extra | Recovery of all triples for DBpedia in Japanese took 5.514496564865112s
Performance | Total latancy measurement for DBpedia in Japanese took 6.672795534133911s
Amount of data | Number of triples check for DBpedia in Japanese took 55.52866196632385s
Interoperability | New terms check for DBpedia in Japanese took 19.16524338722229s
Versatility | Languages check for DBpedia in Japanese took 1.3364157676696777s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3459911346435547s
Security | Check HTTPS for DBpedia in Japanese took 0.7996814250946045s
Interpretability | RDF structures check for DBpedia in Japanese took 1.4022610187530518s
Versatility | Serialization formats check for DBpedia in Japanese took 1.7226436138153076s
Availability | RDF dump link check for DBpedia in Japanese took 1.3263182640075684s
License | MR license check for DBpedia in Japanese took 2.2980690002441406s
License | HR license check for DBpedia in Japanese took 121.34202551841736s
Amount of data | Number of property check for DBpedia in Japanese took 1.3656620979309082s
Understandability | Number of label check for DBpedia in Japanese took 10.04870057106018s
Understandability | URI regex check for DBpedia in Japanese took 2.688274621963501s
Understandability | Vocabs check for DBpedia in Japanese took 1.3469641208648682s
Verifiability | Authors check for DBpedia in Japanese took 1.364008903503418s
Verifiability | Publishers check for DBpedia in Japanese took 1.4029195308685303s
Performance | Throughput check for DBpedia in Japanese took 13.255439758300781s
Amount of data | Check the number of entities for DBpedia in Japanese took 7.414817810058594e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3259241580963135s
Interlinking | sameAs chians check for DBpedia in Japanese took 2.896233320236206s
Interlinking | skos check for DBpedia in Japanese took 1.3427648544311523s
Interlinking | skos check for DBpedia in Japanese took 1.3322806358337402s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.6321868896484375s
Currency | Creation date check for DBpedia in Japanese took 2.6747853755950928s
Currency | Modification date check for DBpedia in Japanese took 2.6563775539398193s
Rep.Conc. | URIs length for DBpedia in Japanese took 139.28075766563416s
Interoperability | New vocabularies check for DBpedia in Japanese took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.325495719909668s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.3480370044708252s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.3427510261535645s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 2.906381607055664s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.026155948638916016s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.02996206283569336s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4817585945129395s
Consistency | Check Misplaced properties for DBpedia in Japanese took 122.65158295631409s
Consistency | Misplaced classes for DBpedia in Japanese took 3.0467493534088135s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.4407594203948975s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.51558256149292s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 122.88418626785278s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.035025835037231445s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 3.217940330505371s
Security | Sign check for DBpedia in Japanese took 1.354555606842041s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 8.96028995513916s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.4255061149597168s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.02586984634399414s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00011920928955078125s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.9073486328125e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 1.1205673217773438e-05s
INFO | --- Analysis for dbpedia-ja took 1352.1674020290375s
Availability | SPARQL endpoint availability check for dbpedia lite took 5.340576171875e-05s
Availability | VoID file availability check for dbpedia lite took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.40932369232177734s
Reputation | Calculation of the PageRank for dbpedia lite took 0.021703004837036133s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.001188039779663086s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00012922286987304688s
Believability | Calculation of trust value for dbpedia lite took 6.67572021484375e-06s
INFO | --- Analysis for dbpedia-lite took 10.874831438064575s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.24563813209533691s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.3429386615753174s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.02066946029663086s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.0001659393310546875s
Believability | Calculation of trust value for DBpedia in Dutch took 9.775161743164062e-06s
INFO | --- Analysis for dbpedia-nl took 3.7479248046875s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 11.540444374084473s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.39379286766052246s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.021143198013305664s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.916854858398438e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 9.775161743164062e-06s
INFO | --- Analysis for dbpedia-pt took 21.19938087463379s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 5.793571472167969e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.33098459243774414s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.021123886108398438s
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.000804901123046875s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 8.082389831542969e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.0728836059570312e-05s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 14.048825979232788s
Availability | SPARQL endpoint availability check for DBTropes took 5.91278076171875e-05s
Availability | VoID file availability check for DBTropes took 0.00037360191345214844s
Completeness | Calculation of interlinking completeness for DBTropes took 0.5003769397735596s
Reputation | Calculation of the PageRank for DBTropes took 0.02116870880126953s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.989738464355469e-05s
Believability | Calculation of trust value for DBTropes took 1.0967254638671875e-05s
INFO | --- Analysis for dbtropes took 3.7342469692230225s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 0.00010275840759277344s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0007166862487792969s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.47811245918273926s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.022303104400634766s
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.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.364418029785156e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 1.5020370483398438e-05s
INFO | --- Analysis for dbtune-artists-last-fm took 5.809599876403809s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 5.173683166503906e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.33066701889038086s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.02156352996826172s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.695487976074219e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.4543533325195312e-05s
INFO | --- Analysis for dbtune-audioscrobbler took 5.770857095718384s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.509285926818848s
Availability | VoID file availability check for DBTune.org/classical took 0.0007529258728027344s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.32843017578125s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.02118515968322754s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 8.845329284667969e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.4781951904296875e-05s
INFO | --- Analysis for dbtune-classical took 19.901219129562378s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.3527672290802s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.4787561893463135s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020997285842895508s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 7.534027099609375e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 1.3828277587890625e-05s
INFO | --- Analysis for dbtune-john-peel-sessions took 24.673640966415405s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.347344160079956s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0008018016815185547s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.32616400718688965s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.02173614501953125s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 7.915496826171875e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.049041748046875e-05s
INFO | --- Analysis for dbtune-magnatune took 21.81066584587097s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.120320558547974s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0007395744323730469s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.33098816871643066s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.021282196044921875s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00011205673217773438s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.3589859008789062e-05s
INFO | --- Analysis for dbtune-musicbrainz took 21.12982702255249s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.338658094406128s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.3326992988586426s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020955562591552734s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.340576171875e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.0967254638671875e-05s
INFO | --- Analysis for dbtune-myspace took 18.713297128677368s
Availability | SPARQL endpoint availability check for data.dcs took 5.0067901611328125e-05s
Availability | VoID file availability check for data.dcs took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for data.dcs took 0.31772756576538086s
Reputation | Calculation of the PageRank for data.dcs took 0.021102190017700195s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.914138793945312e-05s
Believability | Calculation of trust value for data.dcs took 1.4543533325195312e-05s
INFO | --- Analysis for dcs-sheffield took 3.2000679969787598s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.863739013671875e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.31861186027526855s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.020915985107421875s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 4.029273986816406e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 1.4543533325195312e-05s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.878788948059082s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 9.703636169433594e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0008318424224853516s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.317699670791626s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.021275758743286133s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.9591064453125e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.430511474609375e-05s
INFO | --- Analysis for debian-package-tracking-system took 4.110309839248657s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.935264587402344e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.3107945919036865s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.021559953689575195s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 4.00543212890625e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.4543533325195312e-05s
INFO | --- Analysis for desaparecidos took 3.1414058208465576s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.792213439941406e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.3450756072998047s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.021131515502929688s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.00010919570922851562s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.049041748046875e-05s
INFO | --- Analysis for deustoentrepreneurship took 5.3026018142700195s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 5.14984130859375e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.00077056884765625s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.27405881881713867s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.02111363410949707s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00011324882507324219s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.0251998901367188e-05s
INFO | --- Analysis for deustotech took 5.854490041732788s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.3870651721954346s
Availability | VoID file availability check for Deutsche Biographie took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.3610665798187256s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.021663188934326172s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0010180473327636719s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.57763671875e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.52587890625e-05s
INFO | --- Analysis for deutsche-biographie took 4.5981361865997314s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 0.00010132789611816406s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.31465935707092285s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020894765853881836s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.888938903808594e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.0728836059570312e-05s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.384454965591431s
Availability | SPARQL endpoint availability check for dev8d took 9.608268737792969e-05s
Availability | VoID file availability check for dev8d took 0.0006461143493652344s
Completeness | Calculation of interlinking completeness for dev8d took 0.2893807888031006s
Reputation | Calculation of the PageRank for dev8d took 0.021385908126831055s
Interlinking | Calculation of Degree of Connection for dev8d took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for dev8d took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for dev8d took 7.414817810058594e-05s
Believability | Calculation of trust value for dev8d took 1.1920928955078125e-05s
INFO | --- Analysis for dev8d took 3.9260709285736084s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.259750843048096s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0008084774017333984s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.46158432960510254s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.02110576629638672s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.4836273193359375e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.0251998901367188e-05s
INFO | --- Analysis for dewey_decimal_classification took 93.48792147636414s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 5.078315734863281e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.3016808032989502s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.021216630935668945s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.2901763916015625e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 1.049041748046875e-05s
INFO | --- Analysis for DHSVM took 27.091551542282104s
Availability | SPARQL endpoint availability check for Diavgeia took 5.0067901611328125e-05s
Availability | VoID file availability check for Diavgeia took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.3189389705657959s
Reputation | Calculation of the PageRank for Diavgeia took 0.02137446403503418s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 9.250640869140625e-05s
Believability | Calculation of trust value for Diavgeia took 1.1444091796875e-05s
INFO | --- Analysis for diavgeia took 6.0759501457214355s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 9.918212890625e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.36795902252197266s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02109074592590332s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00012040138244628906s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.430511474609375e-05s
INFO | --- Analysis for didactalia took 16.139379262924194s
Availability | SPARQL endpoint availability check for DisGeNET took 2.2465872764587402s
Availability | VoID file availability check for DisGeNET took 0.0007808208465576172s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.32477736473083496s
Reputation | Calculation of the PageRank for DisGeNET took 0.02283167839050293s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015425682067871094s
Believability | Calculation of trust value for DisGeNET took 1.4066696166992188e-05s
INFO | --- Analysis for disgenet took 8.787623643875122s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 0.0001430511474609375s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2872302532196045s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.02088189125061035s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.075599670410156e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.5020370483398438e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 6.569870948791504s
Availability | SPARQL endpoint availability check for DM2E took 6.890296936035156e-05s
Availability | VoID file availability check for DM2E took 0.0007071495056152344s
Completeness | Calculation of interlinking completeness for DM2E took 0.3280167579650879s
Reputation | Calculation of the PageRank for DM2E took 0.021107912063598633s
Interlinking | Calculation of Degree of Connection for DM2E took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.0001227855682373047s
Believability | Calculation of trust value for DM2E took 1.0967254638671875e-05s
INFO | --- Analysis for dm2e took 3.461939573287964s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 4.8160552978515625e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.33945512771606445s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020947694778442383s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0008375644683837891s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00015687942504882812s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 8.821487426757812e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 8.050191402435303s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 0.00010061264038085938s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0009100437164306641s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.3487968444824219s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.021001100540161133s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.794929504394531e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 1.049041748046875e-05s
INFO | --- Analysis for doi took 8.610862731933594s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.9114227294921875e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0004112720489501953s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.3111226558685303s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.020894527435302734s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.147125244140625e-05s
Believability | Calculation of trust value for Driggu Florentino took 1.0013580322265625e-05s
INFO | --- Analysis for Driggu took 4.108246803283691s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 1.9816641807556152s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.32421302795410156s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.022905588150024414s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 4.863739013671875e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.4543533325195312e-05s
INFO | --- Analysis for drug-data-hifm took 16.717544555664062s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.7550678253174s
Availability | VoID file availability check for MetaLex Document Server took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.31577610969543457s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.02992725372314453s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0010874271392822266s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 5.7220458984375e-05s
Believability | Calculation of trust value for MetaLex Document Server took 1.3828277587890625e-05s
INFO | --- Analysis for dutch-national-regulations-metalex took 555.2899353504181s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.5459377765655518s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.28884053230285645s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.021467208862304688s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.076957702636719e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 1.5497207641601562e-05s
INFO | --- Analysis for dutch-ships-and-sailors took 14.901142358779907s
Availability | SPARQL endpoint availability check for DWS-Group took 4.76837158203125e-05s
Availability | VoID file availability check for DWS-Group took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.3138010501861572s
Reputation | Calculation of the PageRank for DWS-Group took 0.021185874938964844s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.0001049041748046875s
Believability | Calculation of trust value for DWS-Group took 1.0967254638671875e-05s
INFO | --- Analysis for dws-group took 2.9564707279205322s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 0.00010371208190917969s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.3469550609588623s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.020913124084472656s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.0279159545898438e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.4066696166992188e-05s
INFO | --- Analysis for E1 took 4.645249843597412s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.06334543228149414s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.2818915843963623s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.02109503746032715s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00012230873107910156s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.52587890625e-05s
INFO | --- Analysis for eagle-i-alaska took 2.8756630420684814s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.06312012672424316s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.326277494430542s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.021291017532348633s
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.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.745887756347656e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.5735626220703125e-05s
INFO | --- Analysis for eagle-i-cau took 3.332404851913452s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.06372666358947754s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.276691198348999s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.02341747283935547s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0010025501251220703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 8.273124694824219e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.52587890625e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.9348249435424805s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.06175518035888672s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.48687744140625s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.022528648376464844s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 0.0001010894775390625s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.4066696166992188e-05s
INFO | --- Analysis for eagle-i-cdrewu took 3.249128818511963s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.041825056076049805s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.3141157627105713s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.02105236053466797s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00014829635620117188s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.4066696166992188e-05s
INFO | --- Analysis for eagle-i-dartmouth took 3.012697458267212s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.044196367263793945s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.34441232681274414s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.021268844604492188s
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.00077056884765625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 9.322166442871094e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-famu took 2.9308817386627197s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.03995561599731445s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.3064849376678467s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.02097296714782715s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00013756752014160156s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.4543533325195312e-05s
INFO | --- Analysis for eagle-i-harvard took 2.867802619934082s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.04409456253051758s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.31348514556884766s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.02073049545288086s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.0001270771026611328s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.0013580322265625e-05s
INFO | --- Analysis for eagle-i-hawaii took 2.9975903034210205s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.04367423057556152s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.3300926685333252s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.02062511444091797s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.723403930664062e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.4066696166992188e-05s
INFO | --- Analysis for eagle-i-howard took 2.9637906551361084s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.04037952423095703s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.2759997844696045s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020893096923828125s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.104873657226562e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.3828277587890625e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 3.0744783878326416s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.04063987731933594s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.3145463466644287s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.021002769470214844s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011777877807617188s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 9.775161743164062e-06s
INFO | --- Analysis for eagle-i-jsu took 2.868180513381958s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.03202199935913086s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.3321259021759033s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.02151036262512207s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 4.0531158447265625e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i-meharry took 2.8817522525787354s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.030755281448364258s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.3438684940338135s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.021737337112426758s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.00010180473327636719s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.3828277587890625e-05s
INFO | --- Analysis for eagle-i-montana took 2.9904298782348633s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.04757404327392578s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.27620625495910645s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020837783813476562s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.965896606445312e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.52587890625e-05s
INFO | --- Analysis for eagle-i-msm took 3.018618583679199s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.049367427825927734s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.3375861644744873s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.020893335342407227s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00013136863708496094s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.52587890625e-05s
INFO | --- Analysis for eagle-i-ohsu took 3.014885663986206s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.06561160087585449s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.3016471862792969s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020860910415649414s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.794929504394531e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.5735626220703125e-05s
INFO | --- Analysis for eagle-i-psm took 3.114178419113159s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.07503437995910645s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.4012327194213867s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.023041963577270508s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 7.2479248046875e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.5020370483398438e-05s
INFO | --- Analysis for eagle-i-tsu took 3.1853153705596924s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.0438542366027832s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.32753896713256836s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.604194641113281e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.6927719116210938e-05s
INFO | --- Analysis for eagle-i-tuskegee took 2.9392318725585938s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.054546356201171875s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.29436421394348145s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.021237611770629883s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00010633468627929688s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i-uccaribe took 2.891430616378784s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.04865622520446777s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.3155558109283447s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.021132230758666992s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0001270771026611328s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.5735626220703125e-05s
INFO | --- Analysis for eagle-i-upr took 3.2113218307495117s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.04129481315612793s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.3128061294555664s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.021197795867919922s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0008711814880371094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.890296936035156e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.5497207641601562e-05s
INFO | --- Analysis for eagle-i-utep took 2.886312246322632s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.057033538818359375s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.5469632148742676s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 6.818771362304688e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.3828277587890625e-05s
INFO | --- Analysis for eagle-i-utsa took 4.194204568862915s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.15162992477416992s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.308840274810791s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.020821094512939453s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.489059448242188e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.5020370483398438e-05s
INFO | --- Analysis for eagle-i-vanderbilt took 2.9183945655822754s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.04507255554199219s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.29917359352111816s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020776033401489258s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.748603820800781e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-xula took 3.0766115188598633s
Availability | SPARQL endpoint availability check for Emergency situation took 0.6778955459594727s
Availability | VoID file availability check for Emergency situation took 0.0008230209350585938s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.38315844535827637s
Reputation | Calculation of the PageRank for Emergency situation took 0.02097463607788086s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.863739013671875e-05s
Believability | Calculation of trust value for Emergency situation took 1.430511474609375e-05s
INFO | --- Analysis for Earthquake took 4.340440511703491s
Availability | SPARQL endpoint availability check for ESO took 0.43088221549987793s
Availability | VoID file availability check for ESO took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for ESO took 0.2951009273529053s
Reputation | Calculation of the PageRank for ESO took 0.023076534271240234s
Interlinking | Calculation of Degree of Connection for ESO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for ESO took 8.821487426757812e-05s
Believability | Calculation of trust value for ESO took 1.5497207641601562e-05s
INFO | --- Analysis for Earthquake_case took 4.487421274185181s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.09918904304504395s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.339200496673584s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.000102996826171875s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 1.0728836059570312e-05s
INFO | --- Analysis for ecb-linked-data took 3.024803876876831s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 8.247543096542358s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.3070700168609619s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.02405691146850586s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0008873939514160156s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 4.57763671875e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 1.0728836059570312e-05s
INFO | --- Analysis for ecb-statistics-linked-data took 20.91754150390625s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 2.6822938919067383s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.31815004348754883s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020722627639770508s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.67572021484375e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.4066696166992188e-05s
INFO | --- Analysis for ecco-tcp-linked-data took 15.688270568847656s
Availability | SPARQL endpoint availability check for ECLAP took 20.322320461273193s
Availability | VoID file availability check for ECLAP took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for ECLAP took 0.31276845932006836s
Reputation | Calculation of the PageRank for ECLAP took 0.02086949348449707s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.482269287109375e-05s
Believability | Calculation of trust value for ECLAP took 1.5974044799804688e-05s
INFO | --- Analysis for eclap took 53.32364630699158s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 0.00015687942504882812s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.000640869140625s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.3432912826538086s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.3589859008789062e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 2.0265579223632812e-05s
INFO | --- Analysis for ECNU-GISer took 4.596320629119873s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.00011181831359863281s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.298886775970459s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.021969318389892578s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.00109100341796875s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 7.724761962890625e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.3589859008789062e-05s
INFO | --- Analysis for ecs took 3.2335727214813232s
Availability | SPARQL endpoint availability check for Edublogs took 0.00010895729064941406s
Availability | VoID file availability check for Edublogs took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Edublogs took 0.3302021026611328s
Reputation | Calculation of the PageRank for Edublogs took 0.02333664894104004s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0011053085327148438s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00012111663818359375s
Believability | Calculation of trust value for Edublogs took 1.5020370483398438e-05s
INFO | --- Analysis for edublogs took 3.9088897705078125s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.4559948444366455s
Availability | VoID file availability check for education.data.gov.uk took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.29026222229003906s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020891666412353516s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.703636169433594e-05s
Believability | Calculation of trust value for education.data.gov.uk took 1.1682510375976562e-05s
INFO | --- Analysis for education-data-gov-uk took 5.15423321723938s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 393.3239529132843s
Availability | VoID file availability check for Educational programs - SISVU took 0.0016274452209472656s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 5.7806715965271s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.021857500076293945s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 0.00010347366333007812s
Believability | Calculation of trust value for Educational programs - SISVU took 1.4066696166992188e-05s
INFO | --- Analysis for educationalprograms_sisvu took 1327.8550214767456s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 1.1898832321166992s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.3071167469024658s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.5299530029296875e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 1.049041748046875e-05s
INFO | --- Analysis for eea took 6.035473823547363s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.4898955821990967s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.35134053230285645s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.021178245544433594s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0009503364562988281s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 6.937980651855469e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 1.049041748046875e-05s
INFO | --- Analysis for eea-rod took 6.002459764480591s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.1718432903289795s
Availability | VoID file availability check for EEA Vocabularies took 0.0012905597686767578s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.3557918071746826s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.20159912109375e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.2636184692382812e-05s
INFO | --- Analysis for eea-vocabularies took 5.910043001174927s
Availability | SPARQL endpoint availability check for E-Government Ontology took 16.335099458694458s
Availability | VoID file availability check for E-Government Ontology took 0.00081634521484375s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.38123655319213867s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.02165055274963379s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0008080005645751953s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 5.1021575927734375e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.4543533325195312e-05s
INFO | --- Analysis for EGovOntology took 59.701966285705566s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.51053786277771s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0006670951843261719s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 2.919473648071289s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0758605003356934s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5897619724273682s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.040961503982544s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.3058180809021s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 3.763174295425415s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.550736665725708s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7134833335876465s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.20505738258361816s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.48441267013549805s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 5.79027247428894s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2303633689880371s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.375030517578125s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5503280162811279s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.284440279006958s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3213164806365967s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23354482650756836s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 10.524150848388672s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 8.940696716308594e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.32662415504455566s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.25417113304138184s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4291996955871582s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.22216081619262695s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.30733180046081543s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8069543838500977s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2195606231689453s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.496043920516968s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.21188902854919434s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.29585933685302734s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.30434417724609375s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8555824756622314s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03084540367126465s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.029679298400878906s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.21051430702209473s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 3.876476764678955s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5023627281188965s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.4086225032806396s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3923571109771729s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.958815336227417s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03508329391479492s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3639688491821289s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4117116928100586s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 2872.643726825714s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4013547897338867s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.022231101989746094s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 6.222724914550781e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.430511474609375e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 1.4781951904296875e-05s
INFO | --- Analysis for ei2a took 3093.69890832901s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 0.00010514259338378906s
Availability | VoID file availability check for EIONET RDF Data took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.3490924835205078s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.021305322647094727s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.000110626220703125s
Believability | Calculation of trust value for EIONET RDF Data took 1.3589859008789062e-05s
INFO | --- Analysis for eionet-rdf took 3.402215003967285s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 5.269050598144531e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.3029310703277588s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.021777868270874023s
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.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.1948089599609375e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 1.3589859008789062e-05s
INFO | --- Analysis for ElgooG_ took 3.1390740871429443s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.169982671737671s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.32660531997680664s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.024289608001708984s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 0.00010323524475097656s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.7881393432617188e-05s
INFO | --- Analysis for elviajero took 19.542400598526s
Availability | SPARQL endpoint availability check for EMN took 0.00012493133544921875s
Availability | VoID file availability check for EMN took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for EMN took 0.35198140144348145s
Reputation | Calculation of the PageRank for EMN took 0.022722482681274414s
Interlinking | Calculation of Degree of Connection for EMN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for EMN took 4.1961669921875e-05s
Believability | Calculation of trust value for EMN took 1.5735626220703125e-05s
INFO | --- Analysis for emn took 3.182332754135132s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 8.20159912109375e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.31105852127075195s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020953893661499023s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.459785461425781e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for enakting-co2emission took 3.405998706817627s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 6.461143493652344e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.2981743812561035s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.021845579147338867s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.410743713378906e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for enakting-crime took 2.9765326976776123s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.8160552978515625e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.3112611770629883s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.02112412452697754s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007948875427246094s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.076957702636719e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for enakting-energy took 2.800058364868164s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 0.00010776519775390625s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.2837095260620117s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.02142477035522461s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.655952453613281e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for enakting-mortality took 2.905761241912842s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 0.00011348724365234375s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.32346439361572266s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.021283864974975586s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 4.2438507080078125e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 1.0967254638671875e-05s
INFO | --- Analysis for enakting-nhs took 2.9290952682495117s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 6.389617919921875e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.3316996097564697s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.02098822593688965s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.626678466796875e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for enakting-population took 2.9684689044952393s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.8339216709136963s
Availability | VoID file availability check for English Heritage Periods List took 0.0007660388946533203s
Extra | Recovery of all triples for English Heritage Periods List took 0.32227325439453125s
Performance | Total latancy measurement for English Heritage Periods List took 1.5229930877685547s
Amount of data | Number of triples check for English Heritage Periods List took 0.4492499828338623s
Versatility | Languages check for English Heritage Periods List took 0.3047168254852295s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.4894561767578125s
Security | Check HTTPS for English Heritage Periods List took 0.20542073249816895s
Interpretability | RDF structures check for English Heritage Periods List took 0.27976298332214355s
Versatility | Serialization formats check for English Heritage Periods List took 0.603217601776123s
Availability | RDF dump link check for English Heritage Periods List took 0.3197903633117676s
License | MR license check for English Heritage Periods List took 0.4758734703063965s
License | HR license check for English Heritage Periods List took 0.3385894298553467s
Amount of data | Number of property check for English Heritage Periods List took 0.4242861270904541s
Understandability | Number of label check for English Heritage Periods List took 0.45502638816833496s
Understandability | URI regex check for English Heritage Periods List took 0.7035162448883057s
Understandability | Vocabs check for English Heritage Periods List took 0.5628604888916016s
Verifiability | Authors check for English Heritage Periods List took 0.5197069644927979s
Verifiability | Publishers check for English Heritage Periods List took 0.3067445755004883s
Performance | Throughput check for English Heritage Periods List took 12.329519510269165s
Amount of data | Check the number of entities for English Heritage Periods List took 8.153915405273438e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.2981605529785156s
Interlinking | sameAs chians check for English Heritage Periods List took 0.3741424083709717s
Interlinking | skos check for English Heritage Periods List took 0.35629940032958984s
Interlinking | skos check for English Heritage Periods List took 0.3596158027648926s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.4707658290863037s
Currency | Creation date check for English Heritage Periods List took 0.6242711544036865s
Currency | Modification date check for English Heritage Periods List took 0.8522462844848633s
Rep.Conc. | URIs length for English Heritage Periods List took 0.6680433750152588s
Interoperability | New vocabularies check for English Heritage Periods List took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.347548246383667s
Accuracy | Check Functional Property for English Heritage Periods List took 0.2958800792694092s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.3819870948791504s
Consistency | Disjoint class check for English Heritage Periods List took 0.37797021865844727s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.3408815860748291s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.7380058765411377s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0001728534698486328s
Security | Sign check for English Heritage Periods List took 0.385875940322876s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.3305492401123047s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020892858505249023s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.647804260253906e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 9.5367431640625e-07s
Believability | Calculation of trust value for English Heritage Periods List took 1.621246337890625e-05s
INFO | --- Analysis for english-heritage-periods-list took 54.832298040390015s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.38008952140808105s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0007712841033935547s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 1.1842031478881836s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 0.9540019035339355s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.30452919006347656s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.7801973819732666s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.4903111457824707s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 30.227746725082397s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.1637582778930664s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.46402788162231445s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.4073312282562256s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 52.14016342163086s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.3038923740386963s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.222352743148804s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.21996212005615234s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.23214054107666016s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 1.2893388271331787s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.3638288974761963s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.38367533683776855s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.3047783374786377s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 11.389309406280518s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 8.153915405273438e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.3582122325897217s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.3049609661102295s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.24132776260375977s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.1958763599395752s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.36661291122436523s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.3824000358581543s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.22704768180847168s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 1.432213306427002s
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.5272440910339355s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.3493921756744385s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.35639333724975586s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.27574729919433594s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 0.7337620258331299s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 1.0168051719665527s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.6265556812286377s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.0001761913299560547s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.4417531490325928s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.3820533752441406s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.7227272987365723s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02162456512451172s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 1.049041748046875e-05s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 277.9522693157196s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.2073357105255127s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0006566047668457031s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 1.2512001991271973s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.9540915489196777s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.21910595893859863s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.626560926437378s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.4432666301727295s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 30.2380690574646s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.22639107704162598s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.21855807304382324s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.5616252422332764s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 49.358052015304565s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.21374750137329102s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.23654842376709s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.1614820957183838s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.20365476608276367s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.2955012321472168s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.20223021507263184s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.19333672523498535s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.14992165565490723s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 11.316245079040527s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 0.0002067089080810547s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.40741539001464844s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.20830178260803223s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.21317672729492188s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.14144515991210938s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.22421026229858398s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.42205333709716797s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.6299982070922852s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.7317883968353271s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.25258350372314453s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.21506023406982422s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.2027292251586914s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.20130681991577148s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.5074937343597412s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 1.0797903537750244s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.7452278137207031s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.00016689300537109375s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.32044506072998047s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.22315025329589844s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.3746531009674072s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.021191120147705078s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Score 2010 took 2.1457672119140625e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 1.049041748046875e-05s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 262.8379328250885s
Availability | SPARQL endpoint availability check for English WordNet took 0.0001010894775390625s
Availability | VoID file availability check for English WordNet took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for English WordNet took 0.30248498916625977s
Reputation | Calculation of the PageRank for English WordNet took 0.02104926109313965s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.695487976074219e-05s
Believability | Calculation of trust value for English WordNet took 1.5020370483398438e-05s
INFO | --- Analysis for english-wordnet took 4.011988639831543s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.08950233459472656s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.32470226287841797s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.0210421085357666s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0008647441864013672s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 0.00010323524475097656s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.5020370483398438e-05s
INFO | --- Analysis for enipedia took 3.0610432624816895s
Availability | SPARQL endpoint availability check for Enslaved.org took 9.632110595703125e-05s
Availability | VoID file availability check for Enslaved.org took 0.0003905296325683594s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.30167126655578613s
Reputation | Calculation of the PageRank for Enslaved.org took 0.020824193954467773s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.337860107421875e-05s
Believability | Calculation of trust value for Enslaved.org took 1.0013580322265625e-05s
INFO | --- Analysis for enslaved.org took 5.318931579589844s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.40909862518310547s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.31923842430114746s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020931482315063477s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.245208740234375e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 1.4781951904296875e-05s
INFO | --- Analysis for entice-graph took 3.466494083404541s
Availability | SPARQL endpoint availability check for Entrez Gene took 0.00010347366333007812s
Availability | VoID file availability check for Entrez Gene took 0.0008192062377929688s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.30139589309692383s
Reputation | Calculation of the PageRank for Entrez Gene took 0.020914793014526367s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 4.029273986816406e-05s
Believability | Calculation of trust value for Entrez Gene took 1.049041748046875e-05s
INFO | --- Analysis for entrez_gene took 27.764589309692383s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.0789103507995605s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0007369518280029297s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.31500244140625s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.021728515625s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0010406970977783203s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.8650970458984375e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 1.0967254638671875e-05s
INFO | --- Analysis for environment-agency-bathing-water-quality took 12.193663358688354s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.31116247177124023s
Availability | VoID file availability check for environment.data.gov.uk took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.354778528213501s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.021112680435180664s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.792213439941406e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 1.0967254638671875e-05s
INFO | --- Analysis for environment-data-gov-uk took 9.912821054458618s
Availability | SPARQL endpoint availability check for EARTh took 270.34898042678833s
Availability | VoID file availability check for EARTh took 0.0007581710815429688s
Completeness | Calculation of interlinking completeness for EARTh took 0.3604245185852051s
Reputation | Calculation of the PageRank for EARTh took 0.021546602249145508s
Interlinking | Calculation of Degree of Connection for EARTh took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00010776519775390625s
Believability | Calculation of trust value for EARTh took 1.3828277587890625e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 562.0458428859711s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.5113532543182373s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0005135536193847656s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 116.51829695701599s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.9943885803222656s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 9.520463466644287s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 14.706898927688599s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.1580059528351s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.1988964080810547s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.2621033191680908s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 9.769250631332397s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.34099316596984863s
License | MR license check for Micka (EO metadata) @PSNC took 0.7821674346923828s
License | HR license check for Micka (EO metadata) @PSNC took 300.2299346923828s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.20562148094177246s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 2.327979803085327s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 0.9686529636383057s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.4806976318359375s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.2008378505706787s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.22136974334716797s
Performance | Throughput check for Micka (EO metadata) @PSNC took 11.13984227180481s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 7.796287536621094e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.19986557960510254s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.21593832969665527s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.5018057823181152s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.42232561111450195s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 4.564728260040283s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.4498145580291748s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.2359619140625s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 157.42003679275513s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 2.3126602172851562e-05s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.21656465530395508s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.4033024311065674s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.4084758758544922s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 33.25584626197815s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.6976823806762695s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.653750419616699s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.21338462829589844s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 86.81975412368774s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.323526620864868s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 32.52417612075806s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.509124755859375s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 87.26900219917297s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.8003158569335938s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.479400634765625s
Security | Sign check for Micka (EO metadata) @PSNC took 1.4385030269622803s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 9.273135423660278s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.5336635112762451s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.021728515625s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 4.38690185546875e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for EO_metadata took 2278.2394938468933s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 0.0001049041748046875s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0008230209350585938s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.34134697914123535s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.02092146873474121s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.3855438232421875e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 1.52587890625e-05s
INFO | --- Analysis for EOKP-Datasets took 3.805668830871582s
Availability | SPARQL endpoint availability check for EPA-CDR took 9.703636169433594e-05s
Availability | VoID file availability check for EPA-CDR took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.2919633388519287s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02099466323852539s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.6716461181640625e-05s
Believability | Calculation of trust value for EPA-CDR took 1.1205673217773438e-05s
INFO | --- Analysis for epa-cdr took 8.018773555755615s
Availability | SPARQL endpoint availability check for EPA-FRS took 5.245208740234375e-05s
Availability | VoID file availability check for EPA-FRS took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.30986666679382324s
Reputation | Calculation of the PageRank for EPA-FRS took 0.02118539810180664s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 8.7738037109375e-05s
Believability | Calculation of trust value for EPA-FRS took 7.3909759521484375e-06s
INFO | --- Analysis for epa-frs took 6.748988389968872s
Availability | SPARQL endpoint availability check for EPA-RCRA took 5.2928924560546875e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0007557868957519531s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.3099524974822998s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.022510290145874023s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.7670135498046875e-05s
Believability | Calculation of trust value for EPA-RCRA took 1.049041748046875e-05s
INFO | --- Analysis for epa-rcra took 6.7849907875061035s
Availability | SPARQL endpoint availability check for EPA-SRS took 0.00010085105895996094s
Availability | VoID file availability check for EPA-SRS took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.3118445873260498s
Reputation | Calculation of the PageRank for EPA-SRS took 0.02095317840576172s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 9.894371032714844e-05s
Believability | Calculation of trust value for EPA-SRS took 1.049041748046875e-05s
INFO | --- Analysis for epa-srs took 6.748603343963623s
Availability | SPARQL endpoint availability check for EPA-TRI took 5.030632019042969e-05s
Availability | VoID file availability check for EPA-TRI took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.3306851387023926s
Reputation | Calculation of the PageRank for EPA-TRI took 0.025954484939575195s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0013623237609863281s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 6.008148193359375e-05s
Believability | Calculation of trust value for EPA-TRI took 1.1205673217773438e-05s
INFO | --- Analysis for epa-tri took 6.973728179931641s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.04388070106506348s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.3359701633453369s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020918846130371094s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00013446807861328125s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 3.1388051509857178s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.484250545501709s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.00035643577575683594s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.3207080364227295s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.021488428115844727s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.893013000488281e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 9.775161743164062e-06s
INFO | --- Analysis for eprtr took 4.086095571517944s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.5696156024932861s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0007264614105224609s
Extra | Recovery of all triples for Railway Infrastructure KG took 60.293092250823975s
Performance | Total latancy measurement for Railway Infrastructure KG took 1.19450044631958s
Amount of data | Number of triples check for Railway Infrastructure KG took 0.23499751091003418s
Interoperability | New terms check for Railway Infrastructure KG took 1.8503479957580566s
Versatility | Languages check for Railway Infrastructure KG took 69.97644805908203s
Interpretability | Number of blank nodes check for Railway Infrastructure KG took 0.2362668514251709s
Interpretability | RDF structures check for Railway Infrastructure KG took 0.6108558177947998s
Versatility | Serialization formats check for Railway Infrastructure KG took 0.23660492897033691s
Availability | RDF dump link check for Railway Infrastructure KG took 0.2100374698638916s
License | MR license check for Railway Infrastructure KG took 0.28708982467651367s
License | HR license check for Railway Infrastructure KG took 63.16175889968872s
Amount of data | Number of property check for Railway Infrastructure KG took 0.2429335117340088s
Understandability | Number of label check for Railway Infrastructure KG took 0.4813857078552246s
Understandability | URI regex check for Railway Infrastructure KG took 0.42798471450805664s
Understandability | Vocabs check for Railway Infrastructure KG took 0.2151482105255127s
Verifiability | Authors check for Railway Infrastructure KG took 0.31269049644470215s
Verifiability | Publishers check for Railway Infrastructure KG took 0.20570755004882812s
Performance | Throughput check for Railway Infrastructure KG took 11.327600479125977s
Verifiability | Contribs. check for Railway Infrastructure KG took 0.33038759231567383s
Interlinking | sameAs chians check for Railway Infrastructure KG took 0.23294687271118164s
Interlinking | skos check for Railway Infrastructure KG took 0.2852931022644043s
Interlinking | skos check for Railway Infrastructure KG took 0.2469034194946289s
Timeliness | dataset update frequency check for Railway Infrastructure KG took 0.24031686782836914s
Currency | Creation date check for Railway Infrastructure KG took 0.47385621070861816s
Currency | Modification date check for Railway Infrastructure KG took 0.21991944313049316s
Rep.Conc. | URIs length for Railway Infrastructure KG took 23.10977602005005s
Interoperability | New vocabularies check for Railway Infrastructure KG took 37.201931953430176s
Consistency | Deprecated classes/propertiers check for Railway Infrastructure KG took 0.20819759368896484s
Accuracy | Check Functional Property for Railway Infrastructure KG took 0.2419118881225586s
Accuracy | Check Inverse Functional Property for Railway Infrastructure KG took 0.26114749908447266s
Accuracy | Check Empty annotation labels for Railway Infrastructure KG took 15.035401344299316s
Accuracy | Check White space in annotation for Railway Infrastructure KG took 2.7528891563415527s
Accuracy | Check Datatype consistency for Railway Infrastructure KG took 2.654369592666626s
Consistency | Disjoint class check for Railway Infrastructure KG took 0.24399280548095703s
Consistency | Check Misplaced properties for Railway Infrastructure KG took 1.6829650402069092s
Consistency | Misplaced classes for Railway Infrastructure KG took 8.426968812942505s
Consistency | Check Ontology hijacking for Railway Infrastructure KG took 18.970115423202515s
Consistency | Check Invalid usage of undefined classes for Railway Infrastructure KG took 1.619438886642456s
Consistency | Check Invalid usage of undefined properties for Railway Infrastructure KG took 2.959587812423706s
Conciseness | Check Extensional conciseness for Railway Infrastructure KG took 2.920973062515259s
Conciseness | Check Intensional conciseness for Railway Infrastructure KG took 0.35850977897644043s
Security | Sign check for Railway Infrastructure KG took 0.7217962741851807s
Availability | Check URIs Dereferenciability for Railway Infrastructure KG took 2371.739907026291s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.8004591464996338s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.022114276885986328s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0008375644683837891s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 0.00018405914306640625s
Interoperability | Check the re-using of existing vocabs for Railway Infrastructure KG took 32.072728395462036s
Believability | Calculation of trust value for Railway Infrastructure KG took 1.71661376953125e-05s
INFO | --- Analysis for ERAKG took 2909.319731235504s
Availability | SPARQL endpoint availability check for reg took 4.887580871582031e-05s
Availability | VoID file availability check for reg took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for reg took 0.3333616256713867s
Reputation | Calculation of the PageRank for reg took 0.02079629898071289s
Interlinking | Calculation of Degree of Connection for reg took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for reg took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for reg took 1.5974044799804688e-05s
Believability | Calculation of trust value for reg took 1.3589859008789062e-05s
INFO | --- Analysis for erg took 3.062018871307373s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.23507261276245117s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007953643798828125s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.3140890598297119s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.021159648895263672s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.1948089599609375e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 1.0013580322265625e-05s
INFO | --- Analysis for es-msssi-drug-prices took 3.5274012088775635s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 5.125999450683594e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.34406447410583496s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.020712614059448242s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 9.512901306152344e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 1.0013580322265625e-05s
INFO | --- Analysis for esd-standards took 4.68160080909729s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 7.081031799316406e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.3133506774902344s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020945072174072266s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.462501525878906e-05s
Believability | Calculation of trust value for ESD-Toolkit took 1.049041748046875e-05s
INFO | --- Analysis for esd-toolkit took 3.9547512531280518s
Availability | SPARQL endpoint availability check for Dataset Esis took 5.1975250244140625e-05s
Availability | VoID file availability check for Dataset Esis took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.34454941749572754s
Reputation | Calculation of the PageRank for Dataset Esis took 0.02141594886779785s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.337860107421875e-05s
Believability | Calculation of trust value for Dataset Esis took 1.5735626220703125e-05s
INFO | --- Analysis for esislearning took 3.7720234394073486s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 0.00017571449279785156s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.3334827423095703s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020675182342529297s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.170967102050781e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 1.239776611328125e-05s
INFO | --- Analysis for ESV took 5.01205849647522s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.5892505645751953s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.28537726402282715s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.02074599266052246s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 6.628036499023438e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.2636184692382812e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.657506465911865s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 7.251891613006592s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.31066226959228516s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020737648010253906s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007729530334472656s
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.239776611328125e-05s
INFO | --- Analysis for eu-agencies-bodies took 21.014591455459595s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 9.870529174804688e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.3326694965362549s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.02277541160583496s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.939338684082031e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 1.049041748046875e-05s
INFO | --- Analysis for eu-institutions took 9.26687741279602s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.2866666316986084s
Availability | VoID file availability check for EU Parliament Media Library took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.3095052242279053s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.020862579345703125s
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.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.457069396972656e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 1.0251998901367188e-05s
INFO | --- Analysis for eu-parliament-media took 9.703037738800049s
Availability | SPARQL endpoint availability check for EU Who Is Who took 1.2364017963409424s
Availability | VoID file availability check for EU Who Is Who took 0.0007483959197998047s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.3321664333343506s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.022854089736938477s
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.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.814697265625e-05s
Believability | Calculation of trust value for EU Who Is Who took 1.1205673217773438e-05s
INFO | --- Analysis for eu-who-is-who took 13.68425965309143s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 1.1714816093444824s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0009157657623291016s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.3117654323577881s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.021225929260253906s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.7206878662109375e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for eumida-linked-data took 11.577327966690063s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.3808138370513916s
Availability | VoID file availability check for European Nature Information System took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.40790271759033203s
Reputation | Calculation of the PageRank for European Nature Information System took 0.021294832229614258s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00011777877807617188s
Believability | Calculation of trust value for European Nature Information System took 1.4543533325195312e-05s
INFO | --- Analysis for eunis took 5.016411542892456s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 6.623371601104736s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0008349418640136719s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.4987807273864746s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.02172398567199707s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 8.034706115722656e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 1.5020370483398438e-05s
INFO | --- Analysis for eur-lex-rdf took 20.086281538009644s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 1.2558131217956543s
Availability | VoID file availability check for Standard Eurobarometer took 0.0008008480072021484s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.3691272735595703s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.02097797393798828s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.1961669921875e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 6.4373016357421875e-06s
INFO | --- Analysis for eurobarometer-standard took 11.882535219192505s
Availability | SPARQL endpoint availability check for European Election Results took 1.2805671691894531s
Availability | VoID file availability check for European Election Results took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for European Election Results took 0.31549882888793945s
Reputation | Calculation of the PageRank for European Election Results took 0.020798444747924805s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.719329833984375e-05s
Believability | Calculation of trust value for European Election Results took 1.049041748046875e-05s
INFO | --- Analysis for european-election-results took 12.570765018463135s
Availability | SPARQL endpoint availability check for EPO patents took 0.435194730758667s
Availability | VoID file availability check for EPO patents took 0.0007164478302001953s
Extra | Recovery of all triples for EPO patents took 21.960059642791748s
Performance | Total latancy measurement for EPO patents took 0.9842512607574463s
Amount of data | Number of triples check for EPO patents took 90.21776342391968s
Versatility | Languages check for EPO patents took 100.21168065071106s
Interpretability | Number of blank nodes check for EPO patents took 90.26343393325806s
Interpretability | RDF structures check for EPO patents took 0.2758336067199707s
Versatility | Serialization formats check for EPO patents took 0.2214977741241455s
Availability | RDF dump link check for EPO patents took 0.16787290573120117s
License | MR license check for EPO patents took 0.21596813201904297s
License | HR license check for EPO patents took 90.15596985816956s
Amount of data | Number of property check for EPO patents took 0.2330944538116455s
Understandability | Number of label check for EPO patents took 90.27123427391052s
Understandability | URI regex check for EPO patents took 0.39899301528930664s
Understandability | Vocabs check for EPO patents took 0.20221471786499023s
Verifiability | Authors check for EPO patents took 0.20252466201782227s
Verifiability | Publishers check for EPO patents took 0.2847321033477783s
Performance | Throughput check for EPO patents took 10.877038478851318s
Amount of data | Check the number of entities for EPO patents took 0.00022363662719726562s
Verifiability | Contribs. check for EPO patents took 0.16774821281433105s
Interlinking | sameAs chians check for EPO patents took 0.1795663833618164s
Interlinking | skos check for EPO patents took 0.18813753128051758s
Interlinking | skos check for EPO patents took 0.17011022567749023s
Timeliness | dataset update frequency check for EPO patents took 0.2052903175354004s
Currency | Creation date check for EPO patents took 0.49535059928894043s
Currency | Modification date check for EPO patents took 0.3556556701660156s
Rep.Conc. | URIs length for EPO patents took 132.12644386291504s
Interoperability | New vocabularies check for EPO patents took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.20324087142944336s
Accuracy | Check Empty annotation labels for EPO patents took 20.11753010749817s
Accuracy | Check White space in annotation for EPO patents took 3.0196566581726074s
Accuracy | Check Datatype consistency for EPO patents took 5.004587650299072s
Consistency | Disjoint class check for EPO patents took 0.23730826377868652s
Consistency | Check Misplaced properties for EPO patents took 100.4556815624237s
Consistency | Check Ontology hijacking for EPO patents took 23.530028104782104s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.7609286308288574s
Consistency | Check Invalid usage of undefined properties for EPO patents took 101.69589281082153s
Conciseness | Check Extensional conciseness for EPO patents took 2.8966188430786133s
Conciseness | Check Intensional conciseness for EPO patents took 0.2927696704864502s
Security | Sign check for EPO patents took 0.20444345474243164s
Availability | Check URIs Dereferenciability for EPO patents took 1.5686204433441162s
Completeness | Calculation of interlinking completeness for EPO patents took 0.5967442989349365s
Reputation | Calculation of the PageRank for EPO patents took 0.028206348419189453s
Interlinking | Calculation of Degree of Connection for EPO patents took 3.266334533691406e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0012798309326171875s
Interlinking | Calculation of Clustering coefficient for EPO patents took 6.747245788574219e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 4.291534423828125e-06s
Believability | Calculation of trust value for EPO patents took 1.430511474609375e-05s
INFO | --- Analysis for European_Patent_Information took 1188.7015352249146s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 0.00010633468627929688s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.45702552795410156s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.020968914031982422s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.870529174804688e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 1.0967254638671875e-05s
INFO | --- Analysis for europeana-lod-v1 took 8.20284628868103s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.38668274879455566s
Availability | VoID file availability check for Europeana SPARQL took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.35813236236572266s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020613431930541992s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.125999450683594e-05s
Believability | Calculation of trust value for Europeana SPARQL took 3.0279159545898438e-05s
INFO | --- Analysis for europeana-sparql took 6.294689655303955s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.10727572441101074s
Availability | VoID file availability check for EuroSentiment took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.4105257987976074s
Reputation | Calculation of the PageRank for EuroSentiment took 0.022167444229125977s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0013303756713867188s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 5.3882598876953125e-05s
Believability | Calculation of trust value for EuroSentiment took 1.621246337890625e-05s
INFO | --- Analysis for eurosentiment took 4.613250494003296s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 0.00011086463928222656s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.33707261085510254s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.026232242584228516s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0014426708221435547s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 0.00011682510375976562s
Believability | Calculation of trust value for Eurostat RDF datasets took 1.1205673217773438e-05s
INFO | --- Analysis for eurostat-rdf took 14.048408269882202s
Availability | SPARQL endpoint availability check for EuroVoc took 0.19783306121826172s
Availability | VoID file availability check for EuroVoc took 0.0007791519165039062s
Extra | Recovery of all triples for EuroVoc took 199.05358958244324s
Performance | Total latancy measurement for EuroVoc took 1.3730254173278809s
Amount of data | Number of triples check for EuroVoc took 65.39034986495972s
Interoperability | New terms check for EuroVoc took 57.99209666252136s
Versatility | Languages check for EuroVoc took 300.0760672092438s
Interpretability | Number of blank nodes check for EuroVoc took 16.55933713912964s
Security | Check HTTPS for EuroVoc took 0.34207749366760254s
Interpretability | RDF structures check for EuroVoc took 0.34612584114074707s
Versatility | Serialization formats check for EuroVoc took 3.3950016498565674s
Availability | RDF dump link check for EuroVoc took 0.2727022171020508s
License | MR license check for EuroVoc took 0.2803316116333008s
License | HR license check for EuroVoc took 300.0746376514435s
Amount of data | Number of property check for EuroVoc took 0.17577362060546875s
Understandability | Number of label check for EuroVoc took 1.5598833560943604s
Understandability | URI regex check for EuroVoc took 0.45241713523864746s
Understandability | Vocabs check for EuroVoc took 0.11126899719238281s
Verifiability | Authors check for EuroVoc took 0.12469267845153809s
Verifiability | Publishers check for EuroVoc took 0.18296360969543457s
Performance | Throughput check for EuroVoc took 10.556873083114624s
Amount of data | Check the number of entities for EuroVoc took 0.00017452239990234375s
Verifiability | Contribs. check for EuroVoc took 0.20970678329467773s
Interlinking | sameAs chians check for EuroVoc took 6.946315765380859s
Interlinking | skos check for EuroVoc took 0.1821434497833252s
Interlinking | skos check for EuroVoc took 0.16558241844177246s
Timeliness | dataset update frequency check for EuroVoc took 0.3384828567504883s
Currency | Creation date check for EuroVoc took 0.28955650329589844s
Currency | Modification date check for EuroVoc took 0.18262004852294922s
Rep.Conc. | URIs length for EuroVoc took 420.9141638278961s
Interoperability | New vocabularies check for EuroVoc took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.17666959762573242s
Accuracy | Check Functional Property for EuroVoc took 0.22717523574829102s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.23160314559936523s
Accuracy | Check Empty annotation labels for EuroVoc took 40.78254532814026s
Accuracy | Check White space in annotation for EuroVoc took 3.211961030960083s
Accuracy | Check Datatype consistency for EuroVoc took 2.73583984375s
Consistency | Disjoint class check for EuroVoc took 0.13245630264282227s
Consistency | Check Misplaced properties for EuroVoc took 300.55530524253845s
Consistency | Misplaced classes for EuroVoc took 8.593003511428833s
Consistency | Check Ontology hijacking for EuroVoc took 37.8458137512207s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.9199304580688477s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.5607213973999s
Conciseness | Check Extensional conciseness for EuroVoc took 3.1121654510498047s
Conciseness | Check Intensional conciseness for EuroVoc took 0.49688291549682617s
Security | Sign check for EuroVoc took 0.4784822463989258s
Availability | Check URIs Dereferenciability for EuroVoc took 11.191732406616211s
Completeness | Calculation of interlinking completeness for EuroVoc took 0.5376496315002441s
Reputation | Calculation of the PageRank for EuroVoc took 0.021581411361694336s
Interlinking | Calculation of Degree of Connection for EuroVoc took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0010037422180175781s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 9.560585021972656e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.9073486328125e-06s
Believability | Calculation of trust value for EuroVoc took 1.0251998901367188e-05s
INFO | --- Analysis for eurovoc took 15205.786993265152s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 5.5789947509765625e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.3216428756713867s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.021172761917114258s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 5.2928924560546875e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 1.0251998901367188e-05s
INFO | --- Analysis for euskadi-farmacias took 5.973984479904175s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.6716194152832031s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.3444252014160156s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.021155118942260742s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.2901763916015625e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 1.4781951904296875e-05s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.811209201812744s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.5455222129821777s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0008072853088378906s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.30327320098876953s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.02114391326904297s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.772445678710938e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 1.4781951904296875e-05s
INFO | --- Analysis for eutc-productions took 8.164401769638062s
Availability | SPARQL endpoint availability check for EventMedia took 0.39603757858276367s
Availability | VoID file availability check for EventMedia took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for EventMedia took 0.31475067138671875s
Reputation | Calculation of the PageRank for EventMedia took 0.021290063858032227s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00011348724365234375s
Believability | Calculation of trust value for EventMedia took 1.3589859008789062e-05s
INFO | --- Analysis for event-media took 20.388656854629517s
Availability | SPARQL endpoint availability check for EventKG took 5.8650970458984375e-05s
Availability | VoID file availability check for EventKG took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for EventKG took 0.3238859176635742s
Reputation | Calculation of the PageRank for EventKG took 0.021579980850219727s
Interlinking | Calculation of Degree of Connection for EventKG took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.368492126464844e-05s
Believability | Calculation of trust value for EventKG took 1.4066696166992188e-05s
INFO | --- Analysis for eventkg took 5.844165325164795s
Availability | SPARQL endpoint availability check for Eventseer took 1.3596465587615967s
Availability | VoID file availability check for Eventseer took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Eventseer took 0.297271728515625s
Reputation | Calculation of the PageRank for Eventseer took 0.02093029022216797s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Eventseer took 5.054473876953125e-05s
Believability | Calculation of trust value for Eventseer took 1.5974044799804688e-05s
INFO | --- Analysis for eventseer took 4.7171313762664795s
Availability | SPARQL endpoint availability check for Face Link took 5.841255187988281e-05s
Availability | VoID file availability check for Face Link took 0.0003113746643066406s
Completeness | Calculation of interlinking completeness for Face Link took 0.3194122314453125s
Reputation | Calculation of the PageRank for Face Link took 0.02077174186706543s
Interlinking | Calculation of Degree of Connection for Face Link took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.552436828613281e-05s
Believability | Calculation of trust value for Face Link took 1.7642974853515625e-05s
INFO | --- Analysis for Face_Link took 3.131377935409546s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4990091323852539s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0005114078521728516s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 108.27383613586426s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0036044120788574s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.13033390045166s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 14.115942239761353s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.2435231208801s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.2115111351013184s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2740135192871094s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.508161306381226s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3309593200683594s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.8068962097167969s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.1901822090149s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21097040176391602s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.157729387283325s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.034897804260254s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4405815601348877s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.1930537223815918s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.25403857231140137s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.220394849777222s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.9577484130859375e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2014172077178955s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21453022956848145s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.40702295303344727s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4023411273956299s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 6.6745617389678955s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5212087631225586s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2521681785583496s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 147.96357774734497s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.20243072509765625s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.46747756004333496s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4233663082122803s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 43.42665719985962s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6867313385009766s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.7064435482025146s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19948506355285645s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 85.7955870628357s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.498524904251099s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 37.14560675621033s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.510974645614624s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 86.97376322746277s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.7914018630981445s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5431492328643799s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.4565610885620117s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.74906301498413s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4679231643676758s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.021970748901367188s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.86102294921875e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0967254638671875e-05s
INFO | --- Analysis for FADN_(2019) took 2274.855935573578s
Availability | SPARQL endpoint availability check for FAMEData took 0.00017690658569335938s
Availability | VoID file availability check for FAMEData took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for FAMEData took 0.33432579040527344s
Reputation | Calculation of the PageRank for FAMEData took 0.02483820915222168s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.504753112792969e-05s
Believability | Calculation of trust value for FAMEData took 9.775161743164062e-06s
INFO | --- Analysis for famedata took 7.1512274742126465s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 9.584426879882812e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.34955501556396484s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.021206378936767578s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.0001251697540283203s
Believability | Calculation of trust value for FAO geopolitical ontology took 6.67572021484375e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 11.715279817581177s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.24533557891845703s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.31078672409057617s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.022006511688232422s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00086212158203125s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00011897087097167969s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.0013580322265625e-05s
INFO | --- Analysis for fao-linked-data took 3.4972286224365234s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 5.14984130859375e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.33651232719421387s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.021896839141845703s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0009222030639648438s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.838539123535156e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.4543533325195312e-05s
INFO | --- Analysis for FAO_species took 3.0846610069274902s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.567575216293335s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.33310580253601074s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.02091670036315918s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.6253204345703125e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.3589859008789062e-05s
INFO | --- Analysis for farmbio-chembl took 66.18160700798035s
Availability | SPARQL endpoint availability check for I4.0-Onto took 5.078315734863281e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0003209114074707031s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.33310413360595703s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.02110910415649414s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0008106231689453125s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.528594970703125e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.430511474609375e-05s
INFO | --- Analysis for fatimazahra took 2.954986810684204s
Availability | SPARQL endpoint availability check for FHIR STU3 took 5.221366882324219e-05s
Availability | VoID file availability check for FHIR STU3 took 0.00039505958557128906s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.3154795169830322s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.021281003952026367s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 4.029273986816406e-05s
Believability | Calculation of trust value for FHIR STU3 took 9.775161743164062e-06s
INFO | --- Analysis for FHIR_STU3 took 3.2314581871032715s
Availability | SPARQL endpoint availability check for FiESTA took 5.793571472167969e-05s
Availability | VoID file availability check for FiESTA took 0.0007917881011962891s
Completeness | Calculation of interlinking completeness for FiESTA took 0.3426227569580078s
Reputation | Calculation of the PageRank for FiESTA took 0.02107548713684082s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for FiESTA took 4.363059997558594e-05s
Believability | Calculation of trust value for FiESTA took 1.0967254638671875e-05s
INFO | --- Analysis for fiesta took 13.258665323257446s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00012063980102539062s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0003724098205566406s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.3103218078613281s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02104806900024414s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.528594970703125e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.621246337890625e-05s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 3.0641775131225586s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 5.221366882324219e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0004115104675292969s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.3045029640197754s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.021378278732299805s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.867813110351562e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 7.3909759521484375e-06s
INFO | --- Analysis for finnish-municipalities took 3.7968223094940186s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.2079465389251709s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0007021427154541016s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 116.94172310829163s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 0.9678747653961182s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 8.863296270370483s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 14.607159852981567s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.19637179374695s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 1.799088478088379s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.22550225257873535s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 7.52286171913147s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.32158946990966797s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.6301240921020508s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.16720509529114s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.20288372039794922s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 2.1099965572357178s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 0.6852781772613525s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.21864581108093262s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.21463871002197266s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.28214263916015625s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 11.55283522605896s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 4.649162292480469e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.1969280242919922s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.1831510066986084s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4166431427001953s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.3945958614349365s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 4.617839097976685s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.4774003028869629s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.2325749397277832s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 151.4803581237793s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.1877610683441162s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.21145200729370117s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.19795894622802734s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 40.0050163269043s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.7063474655151367s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.710819959640503s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.21188688278198242s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 85.82325744628906s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.515251159667969s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 30.37093710899353s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.5204832553863525s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 86.93455362319946s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.808584213256836s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.570711612701416s
Security | Sign check for Norway fishery stocks dataset @PSNC took 0.8153061866760254s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 10.428510665893555s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.5526936054229736s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.022301673889160156s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0008111000061035156s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 4.1484832763671875e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.0013580322265625e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 2269.279098510742s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.8160552978515625e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.36997365951538086s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.020946979522705078s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.821487426757812e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.0013580322265625e-05s
INFO | --- Analysis for fishes-of-texas took 3.4684665203094482s
Availability | SPARQL endpoint availability check for flickr? wrappr took 9.989738464355469e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.3010258674621582s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.02259540557861328s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.584426879882812e-05s
Believability | Calculation of trust value for flickr? wrappr took 1.3828277587890625e-05s
INFO | --- Analysis for flickr-wrappr took 4.1974382400512695s
Availability | SPARQL endpoint availability check for Future land use simulation model took 0.00010657310485839844s
Availability | VoID file availability check for Future land use simulation model took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.2763054370880127s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.0210723876953125s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.314018249511719e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.2874603271484375e-05s
INFO | --- Analysis for FLUS took 8.13820505142212s
Availability | SPARQL endpoint availability check for Flybase took 40.87015104293823s
Availability | VoID file availability check for Flybase took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for Flybase took 0.38730549812316895s
Reputation | Calculation of the PageRank for Flybase took 0.023327112197875977s
Interlinking | Calculation of Degree of Connection for Flybase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Flybase took 4.1484832763671875e-05s
Believability | Calculation of trust value for Flybase took 1.8835067749023438e-05s
INFO | --- Analysis for flybase took 165.02428030967712s
Availability | SPARQL endpoint availability check for Flyted took 0.9749619960784912s
Availability | VoID file availability check for Flyted took 0.0007319450378417969s
Completeness | Calculation of interlinking completeness for Flyted took 0.36971378326416016s
Reputation | Calculation of the PageRank for Flyted took 0.021487951278686523s
Interlinking | Calculation of Degree of Connection for Flyted took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.2901763916015625e-05s
Believability | Calculation of trust value for Flyted took 1.0728836059570312e-05s
INFO | --- Analysis for flyted took 6.786257982254028s
Availability | SPARQL endpoint availability check for Foodista took 1.7331430912017822s
Availability | VoID file availability check for Foodista took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Foodista took 0.29575538635253906s
Reputation | Calculation of the PageRank for Foodista took 0.021494388580322266s
Interlinking | Calculation of Degree of Connection for Foodista took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.266334533691406e-05s
Believability | Calculation of trust value for Foodista took 1.3589859008789062e-05s
INFO | --- Analysis for foodista took 11.213594913482666s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.17667531967163086s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.3461878299713135s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.021456003189086914s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.486343383789062e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.049041748046875e-05s
INFO | --- Analysis for foodpedia took 3.297976016998291s
Availability | SPARQL endpoint availability check for FrameBase schema took 0.0001087188720703125s
Availability | VoID file availability check for FrameBase schema took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.39870619773864746s
Reputation | Calculation of the PageRank for FrameBase schema took 0.020893573760986328s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.673004150390625e-05s
Believability | Calculation of trust value for FrameBase schema took 3.409385681152344e-05s
INFO | --- Analysis for framebase-schema took 3.8294482231140137s
Availability | SPARQL endpoint availability check for Framester took 5.1975250244140625e-05s
Availability | VoID file availability check for Framester took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for Framester took 0.2946970462799072s
Reputation | Calculation of the PageRank for Framester took 0.022187471389770508s
Interlinking | Calculation of Degree of Connection for Framester took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Framester took 7.462501525878906e-05s
Believability | Calculation of trust value for Framester took 1.52587890625e-05s
INFO | --- Analysis for framester took 4.404004096984863s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.05914783477783203s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.32308459281921387s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.02091360092163086s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0008521080017089844s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 9.274482727050781e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 1.4781951904296875e-05s
INFO | --- Analysis for frb-linked-data took 3.1344146728515625s
Availability | SPARQL endpoint availability check for 1989shack Inc. E-Commerce  took 5.221366882324219e-05s
Availability | VoID file availability check for 1989shack Inc. E-Commerce  took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for 1989shack Inc. E-Commerce  took 0.2878601551055908s
Reputation | Calculation of the PageRank for 1989shack Inc. E-Commerce  took 0.02077770233154297s
Interlinking | Calculation of Degree of Connection for 1989shack Inc. E-Commerce  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 1989shack Inc. E-Commerce  took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for 1989shack Inc. E-Commerce  took 0.00026917457580566406s
Believability | Calculation of trust value for 1989shack Inc. E-Commerce  took 1.4066696166992188e-05s
INFO | --- Analysis for freebase took 4.76082181930542s
Availability | SPARQL endpoint availability check for Freeyork took 0.0001494884490966797s
Availability | VoID file availability check for Freeyork took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Freeyork took 0.3379373550415039s
Reputation | Calculation of the PageRank for Freeyork took 0.023327112197875977s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.0001087188720703125s
Believability | Calculation of trust value for Freeyork took 1.4781951904296875e-05s
INFO | --- Analysis for freeyork-org took 3.6736254692077637s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7359881401062012s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.30761075019836426s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.02257823944091797s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.82012939453125e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 7.62939453125e-06s
INFO | --- Analysis for fu-berlin-cordis took 5.247545957565308s
Availability | SPARQL endpoint availability check for DailyMed took 0.7123608589172363s
Availability | VoID file availability check for DailyMed took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for DailyMed took 0.4854562282562256s
Reputation | Calculation of the PageRank for DailyMed took 0.021116256713867188s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.000820159912109375s
Interlinking | Calculation of Clustering coefficient for DailyMed took 0.00011086463928222656s
Believability | Calculation of trust value for DailyMed took 1.4066696166992188e-05s
INFO | --- Analysis for fu-berlin-dailymed took 6.891373872756958s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.6859006881713867s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.34082889556884766s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.02068018913269043s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 9.393692016601562e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.0251998901367188e-05s
INFO | --- Analysis for fu-berlin-dblp took 4.980023622512817s
Availability | SPARQL endpoint availability check for Diseasome took 0.720440149307251s
Availability | VoID file availability check for Diseasome took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for Diseasome took 0.355849027633667s
Reputation | Calculation of the PageRank for Diseasome took 0.02120184898376465s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00011467933654785156s
Believability | Calculation of trust value for Diseasome took 1.0728836059570312e-05s
INFO | --- Analysis for fu-berlin-diseasome took 6.161766529083252s
Availability | SPARQL endpoint availability check for DrugBank took 0.7149863243103027s
Availability | VoID file availability check for DrugBank took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for DrugBank took 0.3602294921875s
Reputation | Calculation of the PageRank for DrugBank took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011563301086425781s
Believability | Calculation of trust value for DrugBank took 1.0728836059570312e-05s
INFO | --- Analysis for fu-berlin-drugbank took 6.36790132522583s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.7084567546844482s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0007891654968261719s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.28349804878234863s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.0212860107421875s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 6.246566772460938e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 4.9272706508636475s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.7447865009307861s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.414844274520874s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.020778179168701172s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 8.225440979003906e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 1.0013580322265625e-05s
INFO | --- Analysis for fu-berlin-euraxess took 5.236579418182373s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.9043736457824707s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.28572988510131836s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.02190089225769043s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 9.012222290039062e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-eures took 5.505514860153198s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.7473502159118652s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.696868896484375s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020877361297607422s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.894371032714844e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 1.0967254638671875e-05s
INFO | --- Analysis for fu-berlin-eurostat took 5.972736835479736s
Availability | SPARQL endpoint availability check for MediCare took 0.7453830242156982s
Availability | VoID file availability check for MediCare took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for MediCare took 0.27565813064575195s
Reputation | Calculation of the PageRank for MediCare took 0.021977901458740234s
Interlinking | Calculation of Degree of Connection for MediCare took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0008709430694580078s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.506111145019531e-05s
Believability | Calculation of trust value for MediCare took 1.6450881958007812e-05s
INFO | --- Analysis for fu-berlin-medicare took 5.608165740966797s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.7024226188659668s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.3574352264404297s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020975828170776367s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.796287536621094e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 1.4066696166992188e-05s
INFO | --- Analysis for fu-berlin-project-gutenberg took 5.249346971511841s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.7289676666259766s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.32114124298095703s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.02253437042236328s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.822845458984375e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.5020370483398438e-05s
INFO | --- Analysis for fu-berlin-sider took 5.6844635009765625s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.9150998592376709s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.3314633369445801s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020964622497558594s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 0.00010013580322265625s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.4781951904296875e-05s
INFO | --- Analysis for fu-berlin-stitch took 5.360642194747925s
Availability | SPARQL endpoint availability check for fvdb took 5.626678466796875e-05s
Availability | VoID file availability check for fvdb took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for fvdb took 0.30430102348327637s
Reputation | Calculation of the PageRank for fvdb took 0.020885705947875977s
Interlinking | Calculation of Degree of Connection for fvdb took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.600120544433594e-05s
Believability | Calculation of trust value for fvdb took 1.4781951904296875e-05s
INFO | --- Analysis for fv took 13.080817699432373s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 5.3882598876953125e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.00041031837463378906s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.33182382583618164s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.02092432975769043s
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.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.170967102050781e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 1.5497207641601562e-05s
INFO | --- Analysis for GACS took 3.8270645141601562s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.00013709068298339844s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0008227825164794922s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.3947713375091553s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.02104806900024414s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.124641418457031e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.52587890625e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 7.060545206069946s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 5.316734313964844e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.5150108337402344s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.020832300186157227s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00010275840759277344s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.3828277587890625e-05s
INFO | --- Analysis for garnicaplywood took 5.208137273788452s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0001049041748046875s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.3032071590423584s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.021506547927856445s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.465217590332031e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.4781951904296875e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.888546943664551s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.3318147659301758s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.2778651714324951s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020977258682250977s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.001194000244140625s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 0.00011324882507324219s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.5735626220703125e-05s
INFO | --- Analysis for gemet took 5.4790003299713135s
Availability | SPARQL endpoint availability check for gemet-annotated took 0.0001087188720703125s
Availability | VoID file availability check for gemet-annotated took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.5290448665618896s
Reputation | Calculation of the PageRank for gemet-annotated took 0.02101421356201172s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.933906555175781e-05s
Believability | Calculation of trust value for gemet-annotated took 1.049041748046875e-05s
INFO | --- Analysis for gemet-annotated took 4.2183802127838135s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.7236583232879639s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.35568809509277344s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.028340578079223633s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 5.8650970458984375e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.4543533325195312e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 5.007323741912842s
Availability | SPARQL endpoint availability check for Super Ontology took 0.7920000553131104s
Availability | VoID file availability check for Super Ontology took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.29398274421691895s
Reputation | Calculation of the PageRank for Super Ontology took 0.021106958389282227s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.6716461181640625e-05s
Believability | Calculation of trust value for Super Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 4.509402275085449s
Availability | SPARQL endpoint availability check for Geographic detector model took 6.079673767089844e-05s
Availability | VoID file availability check for Geographic detector model took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.32949066162109375s
Reputation | Calculation of the PageRank for Geographic detector model took 0.020685911178588867s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.2901763916015625e-05s
Believability | Calculation of trust value for Geographic detector model took 1.5020370483398438e-05s
INFO | --- Analysis for GeoDetector took 22.486615419387817s
Availability | SPARQL endpoint availability check for geodomainwn took 5.53131103515625e-05s
Availability | VoID file availability check for geodomainwn took 0.001367807388305664s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.3153834342956543s
Reputation | Calculation of the PageRank for geodomainwn took 0.021719694137573242s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0010552406311035156s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 6.127357482910156e-05s
Believability | Calculation of trust value for geodomainwn took 1.9073486328125e-05s
INFO | --- Analysis for geodomainwn took 4.994495630264282s
Availability | SPARQL endpoint availability check for GeoEcuador took 0.00010466575622558594s
Availability | VoID file availability check for GeoEcuador took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.3597276210784912s
Reputation | Calculation of the PageRank for GeoEcuador took 0.021508216857910156s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0008063316345214844s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 8.058547973632812e-05s
Believability | Calculation of trust value for GeoEcuador took 1.049041748046875e-05s
INFO | --- Analysis for geoecuador took 13.450587511062622s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 2.664285898208618s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0007939338684082031s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.4080996513366699s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.021996736526489258s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 7.939338684082031e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.52587890625e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 47.8162305355072s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.5679147243499756s
Availability | VoID file availability check for GeoLinkedData took 0.0005633831024169922s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.33455324172973633s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.02189040184020996s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 9.512901306152344e-05s
Believability | Calculation of trust value for GeoLinkedData took 6.67572021484375e-06s
INFO | --- Analysis for geolinkeddata took 4.9098334312438965s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.20606231689453125s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0005795955657958984s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 8.89500379562378s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.38794755935668945s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.16018128395080566s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.533623456954956s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.22275018692016602s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.17575287818908691s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.20839715003967285s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.11815667152404785s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.12162208557128906s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.06980466842651367s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.11142277717590332s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 2.4375736713409424s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.10321593284606934s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.1152803897857666s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.13835620880126953s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.1141366958618164s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.07681965827941895s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.10691332817077637s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.305943727493286s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 9.799003601074219e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.07541871070861816s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.06923460960388184s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.10071992874145508s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.06983089447021484s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.07010507583618164s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.16678524017333984s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.17424750328063965s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.415827751159668s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 2.9871909618377686s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.11731123924255371s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06983780860900879s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.061838388442993164s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.35268235206604004s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007428646087646484s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.23896241188049316s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.06934452056884766s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.19356274604797363s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5311975479125977s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.200575113296509s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.5831339359283447s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.7389438152313232s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.1796400547027588s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.0608212947845459s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.0666108131408691s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.3438091278076172s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020995616912841797s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.440017700195312e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 3.828129529953003s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 1.7404556274414062e-05s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 119.62057948112488s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 9.679794311523438e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.3277885913848877s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020799875259399414s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004999637603759766s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.3589859008789062e-05s
INFO | --- Analysis for geonames-semantic-web took 3.986673355102539s
Availability | SPARQL endpoint availability check for Geospatial World  took 9.417533874511719e-05s
Availability | VoID file availability check for Geospatial World  took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.6511378288269043s
Reputation | Calculation of the PageRank for Geospatial World  took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010943412780761719s
Believability | Calculation of trust value for Geospatial World  took 1.5735626220703125e-05s
INFO | --- Analysis for geospatialworld-net took 3.6839327812194824s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5290102958679199s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.31079721450805664s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.02196049690246582s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.000152587890625s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 1.1444091796875e-05s
INFO | --- Analysis for geospecies took 6.317792892456055s
Availability | SPARQL endpoint availability check for GeoWordNet took 0.00010013580322265625s
Availability | VoID file availability check for GeoWordNet took 0.0011510848999023438s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.3072700500488281s
Reputation | Calculation of the PageRank for GeoWordNet took 0.02985858917236328s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0014159679412841797s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 9.274482727050781e-05s
Believability | Calculation of trust value for GeoWordNet took 1.4066696166992188e-05s
INFO | --- Analysis for geowordnet took 7.6278557777404785s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.08963847160339355s
Availability | VoID file availability check for German labor law thesaurus took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.2993910312652588s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.02179408073425293s
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.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.392333984375e-05s
Believability | Calculation of trust value for German labor law thesaurus took 1.0728836059570312e-05s
INFO | --- Analysis for german-labor-law-thesaurus took 3.371319532394409s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.7206878662109375e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.3209958076477051s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.2438507080078125e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 8.821487426757812e-06s
INFO | --- Analysis for germlex took 3.314833641052246s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.381969690322876s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.3469691276550293s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020940542221069336s
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.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.560585021972656e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.4543533325195312e-05s
INFO | --- Analysis for gesis-thesoz took 5.699775457382202s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.8277506828308105s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.3568737506866455s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.022106170654296875s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.700920104980469e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 1.4781951904296875e-05s
INFO | --- Analysis for getty-aat took 16.936274766921997s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.1647319793701172s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0006430149078369141s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.34819912910461426s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.021662235260009766s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0008413791656494141s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.9604644775390625e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.5497207641601562e-05s
INFO | --- Analysis for getty-tgn took 13.084306478500366s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 7.109737396240234s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0007321834564208984s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.3175528049468994s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.02091193199157715s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 5.53131103515625e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 1.049041748046875e-05s
INFO | --- Analysis for gipuzkoademografia took 31.209247827529907s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.935264587402344e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0007784366607666016s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.7657985687255859s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.1948089599609375e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 1.4781951904296875e-05s
INFO | --- Analysis for glastonbury-2011 took 6.557416200637817s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 5.030632019042969e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0006737709045410156s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.3122568130493164s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.863739013671875e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 1.5497207641601562e-05s
INFO | --- Analysis for global-hunger-index-2011 took 4.009680271148682s
Availability | SPARQL endpoint availability check for Glottolog took 0.00010395050048828125s
Availability | VoID file availability check for Glottolog took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2974734306335449s
Reputation | Calculation of the PageRank for Glottolog took 0.022424697875976562s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Glottolog took 6.031990051269531e-05s
Believability | Calculation of trust value for Glottolog took 1.0251998901367188e-05s
INFO | --- Analysis for glottolog took 6.923067331314087s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 9.799003601074219e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0007236003875732422s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.27405595779418945s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.02081441879272461s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010991096496582031s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.6689300537109375e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 11.484529495239258s
Availability | SPARQL endpoint availability check for 1121 took 0.00010132789611816406s
Availability | VoID file availability check for 1121 took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for 1121 took 0.29889631271362305s
Reputation | Calculation of the PageRank for 1121 took 0.022968769073486328s
Interlinking | Calculation of Degree of Connection for 1121 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.361701965332031e-05s
Believability | Calculation of trust value for 1121 took 1.4781951904296875e-05s
INFO | --- Analysis for God_ took 3.909562826156616s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 0.00010395050048828125s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.34497570991516113s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.022535324096679688s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.555152893066406e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.1920928955078125e-05s
INFO | --- Analysis for gold took 4.5287580490112305s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 0.0001270771026611328s
Availability | VoID file availability check for GoogleArt wrapper took 0.0007071495056152344s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.3252534866333008s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020991802215576172s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 7.271766662597656e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 1.430511474609375e-05s
INFO | --- Analysis for googleart-wrapper took 3.4724924564361572s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.09376072883605957s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.37176966667175293s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.504753112792969e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.4781951904296875e-05s
INFO | --- Analysis for govagribus-denmark took 32.53592252731323s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.485987663269043s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0006184577941894531s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.3123328685760498s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020786285400390625s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.392333984375e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for government-web-integration-for-linked-data took 24.69688129425049s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.6635589599609375s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0008220672607421875s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.29003167152404785s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020904064178466797s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 0.00010442733764648438s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 1.0251998901367188e-05s
INFO | --- Analysis for govtrack took 11.552598714828491s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 5.054473876953125e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.3900563716888428s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.02095627784729004s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 5.888938903808594e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.2159347534179688e-05s
INFO | --- Analysis for greek-administrative-geography took 3.1873955726623535s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.22029638290405273s
Availability | VoID file availability check for Greek Wordnet took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.32567524909973145s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.021318912506103516s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.3392181396484375e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.621246337890625e-05s
INFO | --- Analysis for greek-wordnet took 3.252357006072998s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.2626931667327881s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0008351802825927734s
Extra | Recovery of all triples for Greek prisons releases Jan 2018 - Dec 2023 took 12.279071807861328s
Performance | Total latancy measurement for Greek prisons releases Jan 2018 - Dec 2023 took 0.6040256023406982s
Amount of data | Number of triples check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5587382316589355s
Interoperability | New terms check for Greek prisons releases Jan 2018 - Dec 2023 took 1.7350287437438965s
Versatility | Languages check for Greek prisons releases Jan 2018 - Dec 2023 took 1.64308500289917s
Interpretability | Number of blank nodes check for Greek prisons releases Jan 2018 - Dec 2023 took 0.44311022758483887s
Interpretability | RDF structures check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1313469409942627s
Versatility | Serialization formats check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1167290210723877s
Availability | RDF dump link check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11420226097106934s
License | MR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1230461597442627s
License | HR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5530176162719727s
Amount of data | Number of property check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12226533889770508s
Understandability | Number of label check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1825857162475586s
Understandability | URI regex check for Greek prisons releases Jan 2018 - Dec 2023 took 0.24389028549194336s
Understandability | Vocabs check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1219472885131836s
Verifiability | Authors check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12307620048522949s
Verifiability | Publishers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13011813163757324s
Performance | Throughput check for Greek prisons releases Jan 2018 - Dec 2023 took 10.931491613388062s
Amount of data | Check the number of entities for Greek prisons releases Jan 2018 - Dec 2023 took 7.796287536621094e-05s
Verifiability | Contribs. check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12240839004516602s
Interlinking | sameAs chians check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12229084968566895s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12114906311035156s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1221933364868164s
Timeliness | dataset update frequency check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12954354286193848s
Currency | Creation date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.2594590187072754s
Currency | Modification date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.2524404525756836s
Rep.Conc. | URIs length for Greek prisons releases Jan 2018 - Dec 2023 took 7.856277227401733s
Interoperability | New vocabularies check for Greek prisons releases Jan 2018 - Dec 2023 took 1.239776611328125e-05s
Consistency | Deprecated classes/propertiers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12378096580505371s
Accuracy | Check Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.12109112739562988s
Accuracy | Check Inverse Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.1129140853881836s
Accuracy | Check Empty annotation labels for Greek prisons releases Jan 2018 - Dec 2023 took 2.4851365089416504s
Accuracy | Check White space in annotation for Greek prisons releases Jan 2018 - Dec 2023 took 0.2863023281097412s
Accuracy | Check Datatype consistency for Greek prisons releases Jan 2018 - Dec 2023 took 4.872741222381592s
Consistency | Disjoint class check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12184357643127441s
Consistency | Check Misplaced properties for Greek prisons releases Jan 2018 - Dec 2023 took 1.2029509544372559s
Consistency | Check Ontology hijacking for Greek prisons releases Jan 2018 - Dec 2023 took 3.012256383895874s
Consistency | Check Invalid usage of undefined classes for Greek prisons releases Jan 2018 - Dec 2023 took 1.3709945678710938s
Consistency | Check Invalid usage of undefined properties for Greek prisons releases Jan 2018 - Dec 2023 took 2.580390691757202s
Conciseness | Check Extensional conciseness for Greek prisons releases Jan 2018 - Dec 2023 took 2.9434375762939453s
Security | Sign check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12850189208984375s
Availability | Check URIs Dereferenciability for Greek prisons releases Jan 2018 - Dec 2023 took 4946.287280797958s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.8468501567840576s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.021586179733276367s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.8596649169921875e-05s
Interoperability | Check the re-using of existing vocabs for Greek prisons releases Jan 2018 - Dec 2023 took 2.384185791015625e-06s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 1.6450881958007812e-05s
INFO | --- Analysis for greek_prisons_releases took 5025.146667480469s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.8109900951385498s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.3352854251861572s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.021943092346191406s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0011997222900390625s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 0.00011324882507324219s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.3589859008789062e-05s
INFO | --- Analysis for greekchildrensartmuseum took 5.319674253463745s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 0.0001690387725830078s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0008172988891601562s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.38904380798339844s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0008983612060546875s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00010037422180175781s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.33514404296875e-05s
INFO | --- Analysis for green-competitiveness-gnoss took 7.703963041305542s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.4567811489105225s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.35393810272216797s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.02138233184814453s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.9591064453125e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 1.0967254638671875e-05s
INFO | --- Analysis for grrp took 4.730245113372803s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.2932713031768799s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007698535919189453s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.3845372200012207s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.02629399299621582s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0011398792266845703s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 9.655952453613281e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 1.049041748046875e-05s
INFO | --- Analysis for grrt took 4.754878520965576s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.0199058055877686s
Availability | VoID file availability check for Geological Timescale took 0.0006964206695556641s
Extra | Recovery of all triples for Geological Timescale took 3.053964376449585s
Performance | Total latancy measurement for Geological Timescale took 5.61914587020874s
Amount of data | Number of triples check for Geological Timescale took 1.2280383110046387s
Interoperability | New terms check for Geological Timescale took 1.8111639022827148s
Versatility | Languages check for Geological Timescale took 1.0301182270050049s
Interpretability | Number of blank nodes check for Geological Timescale took 0.6341404914855957s
Security | Check HTTPS for Geological Timescale took 0.8984436988830566s
Interpretability | RDF structures check for Geological Timescale took 0.39931178092956543s
Versatility | Serialization formats check for Geological Timescale took 0.9469811916351318s
Availability | RDF dump link check for Geological Timescale took 1.92044997215271s
License | MR license check for Geological Timescale took 0.932086706161499s
License | HR license check for Geological Timescale took 0.520897626876831s
Amount of data | Number of property check for Geological Timescale took 1.114551305770874s
Understandability | Number of label check for Geological Timescale took 0.9394848346710205s
Understandability | URI regex check for Geological Timescale took 2.292039632797241s
Understandability | Vocabs check for Geological Timescale took 0.9504654407501221s
Verifiability | Authors check for Geological Timescale took 0.9520316123962402s
Verifiability | Publishers check for Geological Timescale took 0.5023295879364014s
Performance | Throughput check for Geological Timescale took 17.965551137924194s
Amount of data | Check the number of entities for Geological Timescale took 0.023949384689331055s
Verifiability | Contribs. check for Geological Timescale took 0.4649953842163086s
Interlinking | sameAs chians check for Geological Timescale took 0.94215989112854s
Interlinking | skos check for Geological Timescale took 0.9248185157775879s
Interlinking | skos check for Geological Timescale took 0.9531393051147461s
Timeliness | dataset update frequency check for Geological Timescale took 1.179765224456787s
Currency | Creation date check for Geological Timescale took 2.273249626159668s
Currency | Modification date check for Geological Timescale took 0.9215545654296875s
Rep.Conc. | URIs length for Geological Timescale took 2.5742223262786865s
Interoperability | New vocabularies check for Geological Timescale took 10.363860607147217s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.9355061054229736s
Accuracy | Check Functional Property for Geological Timescale took 0.9433917999267578s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.9014914035797119s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.2611768245697021s
Accuracy | Check White space in annotation for Geological Timescale took 0.015393495559692383s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07510519027709961s
Consistency | Disjoint class check for Geological Timescale took 0.41120028495788574s
Consistency | Check Misplaced properties for Geological Timescale took 1.9512944221496582s
Consistency | Misplaced classes for Geological Timescale took 1.039461374282837s
Consistency | Check Ontology hijacking for Geological Timescale took 2.5692267417907715s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.3597533702850342s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.3567333221435547s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.05199074745178223s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.972496747970581s
Security | Sign check for Geological Timescale took 0.9116716384887695s
Availability | Check URIs Dereferenciability for Geological Timescale took 3.3650929927825928s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.39110279083251953s
Reputation | Calculation of the PageRank for Geological Timescale took 0.02117776870727539s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 8.749961853027344e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 10.455995321273804s
Believability | Calculation of trust value for Geological Timescale took 1.5974044799804688e-05s
INFO | --- Analysis for GTS took 147.62401032447815s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0008296966552734375s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.31986403465270996s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.021542072296142578s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0009353160858154297s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 4.3392181396484375e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for GTS-ont took 3.292710065841675s
Availability | SPARQL endpoint availability check for GUTSTOK  took 9.965896606445312e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.4224560260772705s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.02254509925842285s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.1948089599609375e-05s
Believability | Calculation of trust value for GUTSTOK  took 1.430511474609375e-05s
INFO | --- Analysis for Guillaume_Forget took 3.2334866523742676s
Availability | SPARQL endpoint availability check for Project Gutenberg took 5.173683166503906e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0011608600616455078s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.37303590774536133s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.02196216583251953s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.985664367675781e-05s
Believability | Calculation of trust value for Project Gutenberg took 1.52587890625e-05s
INFO | --- Analysis for gutenberg took 9.386599779129028s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 9.894371032714844e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007944107055664062s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.4301755428314209s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.020802974700927734s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.910064697265625e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.430511474609375e-05s
INFO | --- Analysis for gwa-ili took 6.834779977798462s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.7206878662109375e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.42559051513671875s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.021059274673461914s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.647804260253906e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 1.5974044799804688e-05s
INFO | --- Analysis for GWR took 29.836188077926636s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 5.054473876953125e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0007700920104980469s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.3460073471069336s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.022328853607177734s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 5.1975250244140625e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 1.0251998901367188e-05s
INFO | --- Analysis for HASM took 23.53921341896057s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 3.179030418395996s
Availability | VoID file availability check for HealthCare Ontology took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.36364269256591797s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.02373647689819336s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0013897418975830078s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 5.0067901611328125e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.4781951904296875e-05s
INFO | --- Analysis for HealthCare_Ontology took 6.906174898147583s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 0.00013685226440429688s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.3538367748260498s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.020792007446289062s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 7.009506225585938e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 1.5020370483398438e-05s
INFO | --- Analysis for heartfailure took 3.509983539581299s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.5787513256073s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0008120536804199219s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.4183967113494873s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.02105236053466797s
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.239776611328125e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0008120536804199219s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 4.1484832763671875e-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.4066696166992188e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 122.0667142868042s
Availability | SPARQL endpoint availability check for Hedatuz took 0.21307682991027832s
Availability | VoID file availability check for Hedatuz took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.3366124629974365s
Reputation | Calculation of the PageRank for Hedatuz took 0.02121448516845703s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 4.76837158203125e-05s
Believability | Calculation of trust value for Hedatuz took 1.4066696166992188e-05s
INFO | --- Analysis for hedatuz took 4.123263120651245s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.1078331470489502s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.00040340423583984375s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.3344438076019287s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.021630048751831055s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00013780593872070312s
Believability | Calculation of trust value for Hellenic Fire Brigade took 1.0013580322265625e-05s
INFO | --- Analysis for hellenic-fire-brigade took 3.280714511871338s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.029469966888427734s
Availability | VoID file availability check for Hellenic Police took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.37948083877563477s
Reputation | Calculation of the PageRank for Hellenic Police took 0.020716428756713867s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00013136863708496094s
Believability | Calculation of trust value for Hellenic Police took 1.0013580322265625e-05s
INFO | --- Analysis for hellenic-police took 3.3699560165405273s
Availability | SPARQL endpoint availability check for Hermos took 0.0001163482666015625s
Availability | VoID file availability check for Hermos took 0.0008306503295898438s
Completeness | Calculation of interlinking completeness for Hermos took 0.34599781036376953s
Reputation | Calculation of the PageRank for Hermos took 0.02276158332824707s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hermos took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Hermos took 3.337860107421875e-05s
Believability | Calculation of trust value for Hermos took 1.52587890625e-05s
INFO | --- Analysis for Hermos took 3.613454818725586s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 0.0001323223114013672s
Availability | VoID file availability check for Himanshu Mahawar took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.35037732124328613s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.023162126541137695s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 3.409385681152344e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 1.6689300537109375e-05s
INFO | --- Analysis for Himanshu_Mahawar took 3.092153549194336s
Availability | SPARQL endpoint availability check for HITO took 0.6065208911895752s
Availability | VoID file availability check for HITO took 0.0007255077362060547s
Extra | Recovery of all triples for HITO took 1.9733872413635254s
Performance | Total latancy measurement for HITO took 0.9695723056793213s
Amount of data | Number of triples check for HITO took 0.19890117645263672s
Interoperability | New terms check for HITO took 1.5868861675262451s
Versatility | Languages check for HITO took 0.24984955787658691s
Interpretability | Number of blank nodes check for HITO took 0.18325567245483398s
Interpretability | RDF structures check for HITO took 0.20087504386901855s
Versatility | Serialization formats check for HITO took 0.18683457374572754s
Availability | RDF dump link check for HITO took 0.21070194244384766s
License | MR license check for HITO took 0.1812429428100586s
License | HR license check for HITO took 0.19516515731811523s
Amount of data | Number of property check for HITO took 0.206773042678833s
Understandability | Number of label check for HITO took 0.20538067817687988s
Understandability | URI regex check for HITO took 0.38205623626708984s
Understandability | Vocabs check for HITO took 0.2114264965057373s
Verifiability | Authors check for HITO took 0.20822763442993164s
Verifiability | Publishers check for HITO took 0.1797332763671875s
Performance | Throughput check for HITO took 11.397763729095459s
Amount of data | Check the number of entities for HITO took 0.00012087821960449219s
Verifiability | Contribs. check for HITO took 0.1956009864807129s
Interlinking | sameAs chians check for HITO took 0.17086267471313477s
Interlinking | skos check for HITO took 0.20198488235473633s
Interlinking | skos check for HITO took 0.19273948669433594s
Timeliness | dataset update frequency check for HITO took 0.1930711269378662s
Currency | Creation date check for HITO took 0.39198899269104004s
Currency | Modification date check for HITO took 0.3740086555480957s
Rep.Conc. | URIs length for HITO took 1.1288492679595947s
Interoperability | New vocabularies check for HITO took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.20161938667297363s
Accuracy | Check Functional Property for HITO took 0.19803071022033691s
Accuracy | Check Inverse Functional Property for HITO took 0.19160747528076172s
Accuracy | Check Empty annotation labels for HITO took 0.5149755477905273s
Accuracy | Check White space in annotation for HITO took 0.013452529907226562s
Accuracy | Check Datatype consistency for HITO took 0.07438254356384277s
Consistency | Disjoint class check for HITO took 0.20328211784362793s
Consistency | Check Misplaced properties for HITO took 0.5105721950531006s
Consistency | Misplaced classes for HITO took 0.3654036521911621s
Consistency | Check Ontology hijacking for HITO took 1.8331279754638672s
Consistency | Check Invalid usage of undefined classes for HITO took 1.357867956161499s
Consistency | Check Invalid usage of undefined properties for HITO took 1.6030464172363281s
Conciseness | Check Extensional conciseness for HITO took 0.061731815338134766s
Conciseness | Check Intensional conciseness for HITO took 0.20663714408874512s
Security | Sign check for HITO took 0.19068169593811035s
Availability | Check URIs Dereferenciability for HITO took 1855.7761459350586s
Completeness | Calculation of interlinking completeness for HITO took 0.584092378616333s
Reputation | Calculation of the PageRank for HITO took 0.023282527923583984s
Interlinking | Calculation of Degree of Connection for HITO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for HITO took 0.0001354217529296875s
Interoperability | Check the re-using of existing vocabs for HITO took 1.1920928955078125e-06s
Believability | Calculation of trust value for HITO took 1.5497207641601562e-05s
INFO | --- Analysis for hito took 1913.4006333351135s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 18.212875843048096s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0007557868957519531s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.3473787307739258s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.020853519439697266s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 3.409385681152344e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 1.4543533325195312e-05s
INFO | --- Analysis for Hoa_Thinh_Phat took 56.34513568878174s
Availability | SPARQL endpoint availability check for gseg took 5.125999450683594e-05s
Availability | VoID file availability check for gseg took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for gseg took 0.308164119720459s
Reputation | Calculation of the PageRank for gseg took 0.02088022232055664s
Interlinking | Calculation of Degree of Connection for gseg took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for gseg took 3.170967102050781e-05s
Believability | Calculation of trust value for gseg took 1.4543533325195312e-05s
INFO | --- Analysis for hongse took 4.3655924797058105s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 2.0617916584014893s
Availability | VoID file availability check for COURAGE Dataset took 0.0007405281066894531s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.37473607063293457s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020818233489990234s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.123283386230469e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.5974044799804688e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 6.673081636428833s
Availability | SPARQL endpoint availability check for RoadTrb took 0.00010800361633300781s
Availability | VoID file availability check for RoadTrb took 0.00037479400634765625s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.3725240230560303s
Reputation | Calculation of the PageRank for RoadTrb took 0.020843982696533203s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.24249267578125e-05s
Believability | Calculation of trust value for RoadTrb took 1.4543533325195312e-05s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 3.1927599906921387s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 0.00010848045349121094s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0008652210235595703s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.38369321823120117s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020830869674682617s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 4.100799560546875e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.867813110351562e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 30.400927305221558s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 8.58306884765625e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.33596372604370117s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.021149873733520508s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.647804260253906e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.049041748046875e-05s
INFO | --- Analysis for http:pakistan.com took 3.2577297687530518s
Availability | SPARQL endpoint availability check for CEDICT took 4.9591064453125e-05s
Availability | VoID file availability check for CEDICT took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for CEDICT took 0.33587121963500977s
Reputation | Calculation of the PageRank for CEDICT took 0.02103900909423828s
Interlinking | Calculation of Degree of Connection for CEDICT took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CEDICT took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.218650817871094e-05s
Believability | Calculation of trust value for CEDICT took 1.0728836059570312e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.71511173248291s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.67844295501709s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.5083904266357422s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.022944211959838867s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.628036499023438e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.52587890625e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 11.655263900756836s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.887580871582031e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.3467390537261963s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.020937442779541016s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.24249267578125e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 1.5974044799804688e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 3.866239547729492s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 9.655952453613281e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.3413197994232178s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.0213010311126709s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.4332275390625e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.33514404296875e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 3.105423927307129s
Availability | SPARQL endpoint availability check for Soccer Dataset took 0.00016450881958007812s
Availability | VoID file availability check for Soccer Dataset took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.361234188079834s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.02072763442993164s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.1948089599609375e-05s
Believability | Calculation of trust value for Soccer Dataset took 1.3828277587890625e-05s
INFO | --- Analysis for http:www.msm.com took 3.4929447174072266s
Availability | SPARQL endpoint availability check for Game Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Game Ontology took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.36206531524658203s
Reputation | Calculation of the PageRank for Game Ontology took 0.02069568634033203s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.3855438232421875e-05s
Believability | Calculation of trust value for Game Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for http:www.RAG.comgameonto# took 3.8581221103668213s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0001087188720703125s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.34894609451293945s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.021604299545288086s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0009615421295166016s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.5497207641601562e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 4.11894679069519s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 6.103515625e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.32018446922302246s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02159428596496582s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0009121894836425781s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.457069396972656e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1682510375976562e-05s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 3.0649237632751465s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 5.1975250244140625e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3961203098297119s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.022096872329711914s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0010983943939208984s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.933906555175781e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.5020370483398438e-05s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 3.1720340251922607s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 5.1975250244140625e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3572390079498291s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021845579147338867s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0008091926574707031s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.4332275390625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 9.775161743164062e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 3.790717124938965s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 7.772445678710938e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3033778667449951s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021474838256835938s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0010004043579101562s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.7670135498046875e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.4543533325195312e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 3.317573070526123s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 5.030632019042969e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.3383018970489502s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021446704864501953s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0008981227874755859s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.7670135498046875e-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.578228950500488s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 5.125999450683594e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.35567212104797363s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02177906036376953s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0011174678802490234s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 4.00543212890625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.430511474609375e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 3.319882869720459s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 6.723403930664062e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.3308427333831787s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.021637439727783203s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.409385681152344e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.049041748046875e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 5.95464015007019s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.0530474185943604s
Availability | VoID file availability check for Bookkeeping took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.3800497055053711s
Reputation | Calculation of the PageRank for Bookkeeping took 0.02182292938232422s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.3855438232421875e-05s
Believability | Calculation of trust value for Bookkeeping took 1.0251998901367188e-05s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 5.0980024337768555s
Availability | SPARQL endpoint availability check for Legal Ontology took 6.341934204101562e-05s
Availability | VoID file availability check for Legal Ontology took 0.0003464221954345703s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.34888553619384766s
Reputation | Calculation of the PageRank for Legal Ontology took 0.02112865447998047s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0008761882781982422s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.981590270996094e-05s
Believability | Calculation of trust value for Legal Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 3.9112486839294434s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 6.389617919921875e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.00039315223693847656s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.31900835037231445s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.021219253540039062s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.821487426757812e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.430511474609375e-05s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 3.5087056159973145s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 5.2928924560546875e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0007271766662597656s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.5716605186462402s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.023027420043945312s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0009829998016357422s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 3.8623809814453125e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 1.430511474609375e-05s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 3.815066337585449s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 0.4474658966064453s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.31441569328308105s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.021972179412841797s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0009012222290039062s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00013780593872070312s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 1.5974044799804688e-05s
INFO | --- Analysis for hungarian-national-library-catalog took 3.6743712425231934s
Availability | SPARQL endpoint availability check for IATE RDF took 5.1021575927734375e-05s
Availability | VoID file availability check for IATE RDF took 0.0007014274597167969s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.3099937438964844s
Reputation | Calculation of the PageRank for IATE RDF took 0.022491455078125s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0011143684387207031s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 4.696846008300781e-05s
Believability | Calculation of trust value for IATE RDF took 1.4781951904296875e-05s
INFO | --- Analysis for iate-rdf took 3.268700361251831s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.508860349655151s
Availability | VoID file availability check for IATI as Linked Data took 0.0004074573516845703s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.43259215354919434s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.021024465560913086s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 9.059906005859375e-05s
Believability | Calculation of trust value for IATI as Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for iati-as-linked-data took 14.873533964157104s
Availability | SPARQL endpoint availability check for ICANE took 0.3069422245025635s
Availability | VoID file availability check for ICANE took 0.001085519790649414s
Completeness | Calculation of interlinking completeness for ICANE took 0.3171062469482422s
Reputation | Calculation of the PageRank for ICANE took 0.02188563346862793s
Interlinking | Calculation of Degree of Connection for ICANE took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ICANE took 0.001010894775390625s
Interlinking | Calculation of Clustering coefficient for ICANE took 0.00010561943054199219s
Believability | Calculation of trust value for ICANE took 7.152557373046875e-06s
INFO | --- Analysis for icane took 4.257237195968628s
Availability | SPARQL endpoint availability check for ichoose took 0.14979791641235352s
Availability | VoID file availability check for ichoose took 0.0003085136413574219s
Completeness | Calculation of interlinking completeness for ichoose took 0.3390989303588867s
Reputation | Calculation of the PageRank for ichoose took 0.02132439613342285s
Interlinking | Calculation of Degree of Connection for ichoose took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0010106563568115234s
Interlinking | Calculation of Clustering coefficient for ichoose took 8.320808410644531e-05s
Believability | Calculation of trust value for ichoose took 1.4543533325195312e-05s
INFO | --- Analysis for ichoose took 41.5396466255188s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 0.2575674057006836s
Availability | VoID file availability check for The Iconology Dataset took 0.0006442070007324219s
Extra | Recovery of all triples for The Iconology Dataset took 3.9446234703063965s
Performance | Total latancy measurement for The Iconology Dataset took 0.43141770362854004s
Amount of data | Number of triples check for The Iconology Dataset took 0.19774198532104492s
Interoperability | New terms check for The Iconology Dataset took 1.6015567779541016s
Versatility | Languages check for The Iconology Dataset took 0.49207448959350586s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.23345708847045898s
Interpretability | RDF structures check for The Iconology Dataset took 0.11994290351867676s
Versatility | Serialization formats check for The Iconology Dataset took 0.10368990898132324s
Availability | RDF dump link check for The Iconology Dataset took 0.08332610130310059s
License | MR license check for The Iconology Dataset took 0.09929513931274414s
License | HR license check for The Iconology Dataset took 0.28055429458618164s
Amount of data | Number of property check for The Iconology Dataset took 0.10147595405578613s
Understandability | Number of label check for The Iconology Dataset took 0.14921307563781738s
Understandability | URI regex check for The Iconology Dataset took 0.1660153865814209s
Understandability | Vocabs check for The Iconology Dataset took 0.09124970436096191s
Verifiability | Authors check for The Iconology Dataset took 0.09900474548339844s
Verifiability | Publishers check for The Iconology Dataset took 0.08920669555664062s
Performance | Throughput check for The Iconology Dataset took 10.521091938018799s
Amount of data | Check the number of entities for The Iconology Dataset took 9.107589721679688e-05s
Verifiability | Contribs. check for The Iconology Dataset took 0.09060311317443848s
Interlinking | sameAs chians check for The Iconology Dataset took 0.0857081413269043s
Interlinking | skos check for The Iconology Dataset took 0.09520244598388672s
Interlinking | skos check for The Iconology Dataset took 0.09233689308166504s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.09334468841552734s
Currency | Creation date check for The Iconology Dataset took 0.24564146995544434s
Currency | Modification date check for The Iconology Dataset took 0.19575214385986328s
Rep.Conc. | URIs length for The Iconology Dataset took 1.2890174388885498s
Interoperability | New vocabularies check for The Iconology Dataset took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08218073844909668s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.26248645782470703s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.01646900177001953s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.4410972595214844s
Consistency | Disjoint class check for The Iconology Dataset took 0.08058047294616699s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.15381669998168945s
Consistency | Misplaced classes for The Iconology Dataset took 0.8645126819610596s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.74214506149292s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.3871138095855713s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.4658219814300537s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.2960021495819092s
Security | Sign check for The Iconology Dataset took 0.08195090293884277s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2641.0858125686646s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 0.9952578544616699s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.0220491886138916s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.3828277587890625e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for The Iconology Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for iconology-dataset took 2697.974591732025s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 0.00013375282287597656s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0007140636444091797s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.6316719055175781s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02094435691833496s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.843971252441406e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 1.5497207641601562e-05s
INFO | --- Analysis for idreffr took 4.95012092590332s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 1.8101117610931396s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.5496585369110107s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020934343338012695s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 5.078315734863281e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 1.5020370483398438e-05s
INFO | --- Analysis for ids took 5.889207124710083s
Availability | SPARQL endpoint availability check for ietflang took 6.198883056640625e-05s
Availability | VoID file availability check for ietflang took 0.0007796287536621094s
Completeness | Calculation of interlinking completeness for ietflang took 0.32581520080566406s
Reputation | Calculation of the PageRank for ietflang took 0.02278423309326172s
Interlinking | Calculation of Degree of Connection for ietflang took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ietflang took 0.000835418701171875s
Interlinking | Calculation of Clustering coefficient for ietflang took 6.318092346191406e-05s
Believability | Calculation of trust value for ietflang took 1.5020370483398438e-05s
INFO | --- Analysis for ietflang took 15.20855164527893s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.5900905132293701s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0012869834899902344s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.31983089447021484s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02109694480895996s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0010390281677246094s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 4.696846008300781e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.5020370483398438e-05s
INFO | --- Analysis for IGVLL took 4.969602823257446s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.4489428997039795s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0006287097930908203s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.4809949398040771s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9474680423736572s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.20007801055908203s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.55928635597229s
Versatility | Languages check for 3LGM² IHE Ontology took 0.22204327583312988s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.1821122169494629s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.22842168807983398s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.21587729454040527s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.18927407264709473s
License | MR license check for 3LGM² IHE Ontology took 0.1976947784423828s
License | HR license check for 3LGM² IHE Ontology took 0.20693445205688477s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.19881916046142578s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.20915675163269043s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.4093739986419678s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.1806795597076416s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.19883441925048828s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.19207096099853516s
Performance | Throughput check for 3LGM² IHE Ontology took 11.84896206855774s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 7.43865966796875e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.19446682929992676s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.21008658409118652s
Interlinking | skos check for 3LGM² IHE Ontology took 0.20470952987670898s
Interlinking | skos check for 3LGM² IHE Ontology took 0.1890718936920166s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.21126174926757812s
Currency | Creation date check for 3LGM² IHE Ontology took 0.3720846176147461s
Currency | Modification date check for 3LGM² IHE Ontology took 0.37905216217041016s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8117115497589111s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.19820022583007812s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.20177102088928223s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.18877768516540527s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.3521566390991211s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.0035521984100341797s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.0536651611328125s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.1907024383544922s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.43375563621520996s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.2759125232696533s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.660907506942749s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.3512208461761475s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.6249346733093262s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.031511783599853516s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.1818251609802246s
Security | Sign check for 3LGM² IHE Ontology took 0.20548248291015625s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 389.9921066761017s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.4492912292480469s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.02138352394104004s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 3.743171691894531e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.9073486328125e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 1.4781951904296875e-05s
INFO | --- Analysis for IHE took 438.3737094402313s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 2.399315357208252s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0007226467132568359s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 5.096069574356079s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 7.841078042984009s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 14.404215812683105s
Interoperability | New terms check for Test Site, LOD Lab 317 took 8.091181755065918s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.55356287956238s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 1.6839547157287598s
Security | Check HTTPS for Test Site, LOD Lab 317 took 1.0531339645385742s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 1.5849597454071045s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.603437900543213s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.5762295722961426s
License | MR license check for Test Site, LOD Lab 317 took 1.600266456604004s
License | HR license check for Test Site, LOD Lab 317 took 1.9038162231445312s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.622227668762207s
Understandability | Number of label check for Test Site, LOD Lab 317 took 1.573655128479004s
Understandability | URI regex check for Test Site, LOD Lab 317 took 3.1187422275543213s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.5693929195404053s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.5664656162261963s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 1.588418960571289s
Performance | Throughput check for Test Site, LOD Lab 317 took 15.683119773864746s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 8.344650268554688e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.590181589126587s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.5846621990203857s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.5742135047912598s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.6240575313568115s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.583261489868164s
Currency | Creation date check for Test Site, LOD Lab 317 took 3.142578125s
Currency | Modification date check for Test Site, LOD Lab 317 took 3.1775803565979004s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 34.79272651672363s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.5725390911102295s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.5690970420837402s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.569457769393921s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.5631470680236816s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 25.240839958190918s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 1.861335039138794s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 2.284640073776245s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 25.122560501098633s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.00018835067749023438s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.112863779067993s
Security | Sign check for Test Site, LOD Lab 317 took 1.5415539741516113s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.44631481170654297s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.02208089828491211s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0010063648223876953s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 0.00010180473327636719s
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.5974044799804688e-05s
INFO | --- Analysis for iislod-test took 515.3080251216888s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 5.340576171875e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.3813326358795166s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.02155613899230957s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0010235309600830078s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 4.553794860839844e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 1.0967254638671875e-05s
INFO | --- Analysis for ILUSOC took 21.862377643585205s
Availability | SPARQL endpoint availability check for im@sparql took 6.699548721313477s
Availability | VoID file availability check for im@sparql took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for im@sparql took 0.36215686798095703s
Reputation | Calculation of the PageRank for im@sparql took 0.02092146873474121s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.075599670410156e-05s
Believability | Calculation of trust value for im@sparql took 1.430511474609375e-05s
INFO | --- Analysis for im@sparql took 14.692142963409424s
Availability | SPARQL endpoint availability check for imagery bailingniao took 5.14984130859375e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.3314473628997803s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.020947694778442383s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.337860107421875e-05s
Believability | Calculation of trust value for imagery bailingniao took 1.0251998901367188e-05s
INFO | --- Analysis for imagery_bailingniao took 4.063543796539307s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.1738193035125732s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0007843971252441406s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 20.405086040496826s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.4776036739349365s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.723108291625977s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.8120040893554688s
Versatility | Languages check for Imagesnippets Image Descriptions took 19.434956073760986s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.608156204223633s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.6573448181152344s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7393076419830322s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7026321887969971s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7354090213775635s
License | MR license check for Imagesnippets Image Descriptions took 0.737163782119751s
License | HR license check for Imagesnippets Image Descriptions took 30.735673666000366s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7270433902740479s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.6202287673950195s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.4258482456207275s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7423379421234131s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7290654182434082s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7415764331817627s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.873867511749268s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 8.034706115722656e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7384145259857178s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.6917803287506104s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7485918998718262s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6905062198638916s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7387666702270508s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.4987261295318604s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.4827594757080078s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 33.55410313606262s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7580697536468506s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7159690856933594s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7217445373535156s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 11.902965068817139s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.2473690509796143s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.492621898651123s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7609250545501709s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.958642482757568s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 5.36332893371582s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.5642380714416504s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.904361963272095s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 2.9498350620269775s
Security | Sign check for Imagesnippets Image Descriptions took 0.7475302219390869s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 11.997342109680176s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.4402749538421631s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.02115488052368164s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.942054748535156e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.9073486328125e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 8.58306884765625e-06s
INFO | --- Analysis for imagesnippets took 379.11819100379944s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.11807608604431152s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.3750433921813965s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.020733356475830078s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 0.00010156631469726562s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for imf-linked-data took 3.346487283706665s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 0.00015473365783691406s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.363034725189209s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.021427154541015625s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.2874603271484375e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 1.4781951904296875e-05s
INFO | --- Analysis for Imtiaz took 3.318574905395508s
Availability | SPARQL endpoint availability check for Royalty Free Music took 5.7220458984375e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.4617464542388916s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.0208742618560791s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 3.147125244140625e-05s
Believability | Calculation of trust value for Royalty Free Music took 1.3828277587890625e-05s
INFO | --- Analysis for inaudio.org took 5.067389011383057s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.4831202030181885s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0007479190826416016s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.3177618980407715s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.02201223373413086s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.001041412353515625s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 4.887580871582031e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 1.5020370483398438e-05s
INFO | --- Analysis for IndexThomisticusTreebank took 4.5560688972473145s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.00011777877807617188s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.33713293075561523s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.02335214614868164s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0009224414825439453s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00012493133544921875s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 1.3828277587890625e-05s
INFO | --- Analysis for ineverycrea took 22.81725263595581s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.00012302398681640625s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.3890261650085449s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.02118849754333496s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0001308917999267578s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.5497207641601562e-05s
INFO | --- Analysis for ineverycrea-argentina took 11.340440273284912s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 271.8928861618042s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.3685457706451416s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.021695375442504883s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.200241088867188e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 1.4781951904296875e-05s
INFO | --- Analysis for influence-tracker-dataset took 567.6549804210663s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 0.0001277923583984375s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.36080050468444824s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.021043777465820312s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 1.5020370483398438e-05s
INFO | --- Analysis for instance-hub-fiscal-years took 3.4425015449523926s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 5.7220458984375e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.4149599075317383s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.021765947341918945s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00010728836059570312s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.4781951904296875e-05s
INFO | --- Analysis for interactivemaps-gnoss took 12.54846477508545s
Availability | SPARQL endpoint availability check for intervalue took 0.18796014785766602s
Availability | VoID file availability check for intervalue took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for intervalue took 0.9662439823150635s
Reputation | Calculation of the PageRank for intervalue took 0.027439355850219727s
Interlinking | Calculation of Degree of Connection for intervalue took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0009539127349853516s
Interlinking | Calculation of Clustering coefficient for intervalue took 8.916854858398438e-05s
Believability | Calculation of trust value for intervalue took 1.430511474609375e-05s
INFO | --- Analysis for intervalue took 4.104253530502319s
Availability | SPARQL endpoint availability check for Inztrow took 0.0001697540283203125s
Availability | VoID file availability check for Inztrow took 0.0008406639099121094s
Completeness | Calculation of interlinking completeness for Inztrow took 0.35889577865600586s
Reputation | Calculation of the PageRank for Inztrow took 0.021520376205444336s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0009465217590332031s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.6716461181640625e-05s
Believability | Calculation of trust value for Inztrow took 1.5735626220703125e-05s
INFO | --- Analysis for Inztrow took 4.197219133377075s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 9.942054748535156e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.3296375274658203s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.0234375s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.314018249511719e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 1.4543533325195312e-05s
INFO | --- Analysis for ipbes took 4.618249893188477s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 5.030632019042969e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.33049535751342773s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.02317643165588379s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0010020732879638672s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 5.650520324707031e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 1.5735626220703125e-05s
INFO | --- Analysis for iptc-newscodes took 4.135424613952637s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.4305272102355957s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0008981227874755859s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.3941164016723633s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.02108001708984375s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 0.00010180473327636719s
Believability | Calculation of trust value for iServe: Linked Services Registry took 1.5974044799804688e-05s
INFO | --- Analysis for iserve took 9.126067161560059s
Availability | SPARQL endpoint availability check for ISIC V4 took 21.16488528251648s
Availability | VoID file availability check for ISIC V4 took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.34996914863586426s
Reputation | Calculation of the PageRank for ISIC V4 took 0.021003246307373047s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.552436828613281e-05s
Believability | Calculation of trust value for ISIC V4 took 9.5367431640625e-06s
INFO | --- Analysis for isic-v4 took 115.30424189567566s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 0.00026035308837890625s
Availability | VoID file availability check for ISIL->DBpedia took 0.00031638145446777344s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.3259134292602539s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020898818969726562s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.390975952148438e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 7.152557373046875e-06s
INFO | --- Analysis for isil-dbpedia took 5.19570779800415s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 5.364418029785156e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.3593106269836426s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.020719528198242188s
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.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.5762786865234375e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 1.4781951904296875e-05s
INFO | --- Analysis for iso-639-oasis took 4.280210494995117s
Availability | SPARQL endpoint availability check for ISOcat took 0.00011944770812988281s
Availability | VoID file availability check for ISOcat took 0.0008051395416259766s
Completeness | Calculation of interlinking completeness for ISOcat took 0.3351733684539795s
Reputation | Calculation of the PageRank for ISOcat took 0.0208890438079834s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.437301635742188e-05s
Believability | Calculation of trust value for ISOcat took 1.4781951904296875e-05s
INFO | --- Analysis for isocat took 8.599068880081177s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 0.00010132789611816406s
Availability | VoID file availability check for ISOcat-metadata took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.38709282875061035s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.0215151309967041s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.9577484130859375e-05s
Believability | Calculation of trust value for ISOcat-metadata took 1.52587890625e-05s
INFO | --- Analysis for isocat-metadata took 5.963117837905884s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9322032928466797s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007786750793457031s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.5811121463775635s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3034210205078125s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14963483810424805s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.0627198219299316s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.02373838424683s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09270334243774414s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.03269147872924805s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.11514854431152344s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10920882225036621s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09521603584289551s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1535778045654297s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.85815453529358s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09482717514038086s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3747613430023193s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3279857635498047s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1422731876373291s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14217829704284668s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09056615829467773s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.246606349945068s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.416175842285156e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14265131950378418s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.21360087394714355s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.454866886138916s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.42425107955932617s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14601898193359375s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1852555274963379s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09249329566955566s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 12.833311319351196s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08839774131774902s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09407687187194824s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0941324234008789s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.8761115074157715s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.31181979179382324s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.27185559272766113s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08956241607666016s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.862605571746826s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.903749942779541s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.9887523651123047s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.4317712783813477s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.217992305755615s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2945106029510498s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1018059253692627s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.11112713813781738s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.557724714279175s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.46245384216308594s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.022115468978881836s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0013206005096435547s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.000133514404296875s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.0994415283203125e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.5020370483398438e-05s
INFO | --- Analysis for ispra-lod-place took 446.70388078689575s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.05190277099609375s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0003306865692138672s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 5.264963626861572s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.27954602241516113s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.15343070030212402s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 3.022904396057129s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 90.85801243782043s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.0917825698852539s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.032904624938964844s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.11488819122314453s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.10618209838867188s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.09467887878417969s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.1847705841064453s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 90.92137908935547s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.09373784065246582s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.4207332134246826s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.34447789192199707s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.1450045108795166s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.1444084644317627s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.09125733375549316s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.47241735458374s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 7.033348083496094e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.1432034969329834s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.2279818058013916s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.47505879402160645s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.43300819396972656s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.14637136459350586s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.18544983863830566s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.09993386268615723s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 12.826595544815063s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.09076666831970215s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.09864521026611328s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.09515833854675293s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 2.939314126968384s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.3151702880859375s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.2735581398010254s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.09008240699768066s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 8.903611421585083s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9244074821472168s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 3.0215418338775635s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.4250705242156982s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.239861488342285s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.29850149154663086s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.09836864471435547s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.10931777954101562s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 8.2618088722229s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.567371129989624s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.021472692489624023s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 3.981590270996094e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.430511474609375e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 1.430511474609375e-05s
INFO | --- Analysis for ispra-lod-ron took 442.50249886512756s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.7776458263397217s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0007836818695068359s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.3419499397277832s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.021187782287597656s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 0.00010418891906738281s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 1.5020370483398438e-05s
INFO | --- Analysis for issa-agritrop took 5.485575199127197s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 0.00012254714965820312s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.39273810386657715s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02154684066772461s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.218650817871094e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.5020370483398438e-05s
INFO | --- Analysis for ISSN:0080-3626 took 3.6775853633880615s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 0.00010323524475097656s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.3878304958343506s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02120661735534668s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0010802745819091797s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.981590270996094e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.5497207641601562e-05s
INFO | --- Analysis for ISSN:_0080-3626 took 3.8249080181121826s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.3392181396484375e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.3851149082183838s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.021886348724365234s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.001016378402709961s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.838539123535156e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 1.5735626220703125e-05s
INFO | --- Analysis for ISSN:_0080-3626. took 3.553945541381836s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.3629403114318848s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.32566189765930176s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.02109360694885254s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.845329284667969e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 1.0251998901367188e-05s
INFO | --- Analysis for istat-immigration took 4.7560200691223145s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.2312467098236084s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0013387203216552734s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.3460123538970947s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.021547794342041016s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0009372234344482422s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 1.0967254638671875e-05s
INFO | --- Analysis for it-aifa-drug-prices took 3.571552276611328s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.3509550094604492s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.35825204849243164s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020828962326049805s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 8.082389831542969e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 1.430511474609375e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 4.591612339019775s
Availability | SPARQL endpoint availability check for IWN took 4.792213439941406e-05s
Availability | VoID file availability check for IWN took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for IWN took 0.31218791007995605s
Reputation | Calculation of the PageRank for IWN took 0.020838022232055664s
Interlinking | Calculation of Degree of Connection for IWN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for IWN took 3.886222839355469e-05s
Believability | Calculation of trust value for IWN took 1.52587890625e-05s
INFO | --- Analysis for iwn took 4.191571474075317s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 6.392763614654541s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0007984638214111328s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.344928503036499s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.021109342575073242s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.365776062011719e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 1.430511474609375e-05s
INFO | --- Analysis for jamendo-dbtune took 19.16514754295349s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 0.00010228157043457031s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.37338972091674805s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.02173638343811035s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 5.14984130859375e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 1.0728836059570312e-05s
INFO | --- Analysis for japan-radioactivity-stat took 5.378399133682251s
Availability | SPARQL endpoint availability check for JEL Classification took 0.00011467933654785156s
Availability | VoID file availability check for JEL Classification took 0.0013470649719238281s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.35289978981018066s
Reputation | Calculation of the PageRank for JEL Classification took 0.023027420043945312s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.075599670410156e-05s
Believability | Calculation of trust value for JEL Classification took 1.52587890625e-05s
INFO | --- Analysis for jel-classification took 5.515031337738037s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.1378297805786133s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.3817770481109619s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020847797393798828s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.1948089599609375e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 1.5974044799804688e-05s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 8.162936687469482s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.6223316192627s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.37003111839294434s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.02120828628540039s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 8.487701416015625e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.52587890625e-05s
INFO | --- Analysis for jita took 540.6749105453491s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.050883531570435s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.5180444717407227s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.021051645278930664s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 9.822845458984375e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.430511474609375e-05s
INFO | --- Analysis for john-goodwins-family-tree took 63.712223052978516s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 0.00012159347534179688s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.3498847484588623s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.020775318145751953s
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.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.4332275390625e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 1.1920928955078125e-05s
INFO | --- Analysis for jp-cos took 5.537642478942871s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 0.00015616416931152344s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.3666057586669922s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.022151708602905273s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 3.886222839355469e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 1.2874603271484375e-05s
INFO | --- Analysis for jp-textbook took 5.030723333358765s
Availability | SPARQL endpoint availability check for JRC-Names took 4.9114227294921875e-05s
Availability | VoID file availability check for JRC-Names took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.33107948303222656s
Reputation | Calculation of the PageRank for JRC-Names took 0.02074575424194336s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.62396240234375e-05s
Believability | Calculation of trust value for JRC-Names took 1.4066696166992188e-05s
INFO | --- Analysis for jrc-names-ec took 5.694293022155762s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 0.9479975700378418s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.4022490978240967s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.02090167999267578s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.67572021484375e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 1.2636184692382812e-05s
INFO | --- Analysis for jrc-names-mlode took 4.635281562805176s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.9591064453125e-05s
Availability | VoID file availability check for JudaicaLink took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.3202545642852783s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020728349685668945s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00010061264038085938s
Believability | Calculation of trust value for JudaicaLink took 1.4543533325195312e-05s
INFO | --- Analysis for judaicalink took 5.356605768203735s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.06719493865966797s
Availability | VoID file availability check for Kallikratis municipalities took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.3692622184753418s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.020881175994873047s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.560585021972656e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 5.4836273193359375e-06s
INFO | --- Analysis for kallikratis-municipalities took 3.1489603519439697s
Availability | SPARQL endpoint availability check for EU Soccer League took 4.935264587402344e-05s
Availability | VoID file availability check for EU Soccer League took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.33246755599975586s
Reputation | Calculation of the PageRank for EU Soccer League took 0.020610570907592773s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.0994415283203125e-05s
Believability | Calculation of trust value for EU Soccer League took 1.4543533325195312e-05s
INFO | --- Analysis for KG:Course_Submission took 5.29046630859375s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 5.030632019042969e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.4067254066467285s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.02076125144958496s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.239776611328125e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 1.3113021850585938e-05s
INFO | --- Analysis for KING took 3.514493703842163s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 0.00011491775512695312s
Availability | VoID file availability check for Klappstuhlclub took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.5057878494262695s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.022694110870361328s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.651878356933594e-05s
Believability | Calculation of trust value for Klappstuhlclub took 1.0728836059570312e-05s
INFO | --- Analysis for klappstuhlclub took 13.610345125198364s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.863997459411621s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.3277130126953125s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.022523164749145508s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 5.91278076171875e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 1.4543533325195312e-05s
INFO | --- Analysis for knoesis-linked-sensor-data took 24.073833227157593s
Availability | SPARQL endpoint availability check for Knowledge Forest took 9.965896606445312e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.34464097023010254s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.022492408752441406s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0008153915405273438s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.5762786865234375e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.4543533325195312e-05s
INFO | --- Analysis for KnowledgeFusion took 3.2803821563720703s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 0.0001010894775390625s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.35062146186828613s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.02084517478942871s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 7.033348083496094e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 1.0728836059570312e-05s
INFO | --- Analysis for kore-50-nif-ner-corpus took 15.040013074874878s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 5.1975250244140625e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.3291590213775635s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.0994415283203125e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 8.344650268554688e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 3.094468593597412s
Availability | SPARQL endpoint availability check for Informatics Studies took 0.00017189979553222656s
Availability | VoID file availability check for Informatics Studies took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.33145952224731445s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020970821380615234s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 3.1948089599609375e-05s
Believability | Calculation of trust value for Informatics Studies took 1.4781951904296875e-05s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 3.829622268676758s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.07435464859008789s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.00034499168395996094s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.34017014503479004s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.8623809814453125e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 1.0967254638671875e-05s
INFO | --- Analysis for kupkb took 10.666670560836792s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 8.221078872680664s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0004000663757324219s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.3804128170013428s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.0206296443939209s
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.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 8.153915405273438e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 1.0251998901367188e-05s
INFO | --- Analysis for l3s-dblp took 42.719558000564575s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 23.785745859146118s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.3513920307159424s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.021277666091918945s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007627010345458984s
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 1.3828277587890625e-05s
INFO | --- Analysis for lak-dataset took 68.01980137825012s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.19607210159301758s
Availability | VoID file availability check for  Language Name Authority List  took 0.0005548000335693359s
Extra | Recovery of all triples for  Language Name Authority List  took 160.54821586608887s
Performance | Total latancy measurement for  Language Name Authority List  took 0.6002273559570312s
Amount of data | Number of triples check for  Language Name Authority List  took 45.59921884536743s
Interoperability | New terms check for  Language Name Authority List  took 57.11230278015137s
Versatility | Languages check for  Language Name Authority List  took 300.1312165260315s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 60.522374629974365s
Security | Check HTTPS for  Language Name Authority List  took 0.43541789054870605s
Interpretability | RDF structures check for  Language Name Authority List  took 0.7436387538909912s
Versatility | Serialization formats check for  Language Name Authority List  took 4.278159856796265s
Availability | RDF dump link check for  Language Name Authority List  took 0.21296453475952148s
License | MR license check for  Language Name Authority List  took 0.6435551643371582s
License | HR license check for  Language Name Authority List  took 290.93387269973755s
Amount of data | Number of property check for  Language Name Authority List  took 0.18668317794799805s
Understandability | Number of label check for  Language Name Authority List  took 2.7557129859924316s
Understandability | URI regex check for  Language Name Authority List  took 0.37036609649658203s
Understandability | Vocabs check for  Language Name Authority List  took 0.10449528694152832s
Verifiability | Authors check for  Language Name Authority List  took 0.24642205238342285s
Verifiability | Publishers check for  Language Name Authority List  took 0.16277027130126953s
Performance | Throughput check for  Language Name Authority List  took 10.634588479995728s
Amount of data | Check the number of entities for  Language Name Authority List  took 3.743171691894531e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.14731812477111816s
Interlinking | sameAs chians check for  Language Name Authority List  took 6.270893096923828s
Interlinking | skos check for  Language Name Authority List  took 0.3705151081085205s
Interlinking | skos check for  Language Name Authority List  took 0.17552971839904785s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.2443997859954834s
Currency | Creation date check for  Language Name Authority List  took 0.467998743057251s
Currency | Modification date check for  Language Name Authority List  took 0.24945688247680664s
Rep.Conc. | URIs length for  Language Name Authority List  took 430.16271567344666s
Interoperability | New vocabularies check for  Language Name Authority List  took 5.7220458984375e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.3061964511871338s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.19085407257080078s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.17606401443481445s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 41.36756467819214s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.116198778152466s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.7921910285949707s
Consistency | Disjoint class check for  Language Name Authority List  took 0.15801548957824707s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.4635510444641s
Consistency | Misplaced classes for  Language Name Authority List  took 8.783953666687012s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 42.664082765579224s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 2.037532329559326s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.6421284675598s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 3.1421375274658203s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.49875521659851074s
Security | Sign check for  Language Name Authority List  took 0.1336534023284912s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 11.283488988876343s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 1.474217414855957s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.021610736846923828s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.369850158691406e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.9073486328125e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.5735626220703125e-05s
INFO | --- Analysis for language-authority-list took 14756.69268321991s
Availability | SPARQL endpoint availability check for Lark took 384.5043394565582s
Availability | VoID file availability check for Lark took 0.0010266304016113281s
Completeness | Calculation of interlinking completeness for Lark took 0.4506106376647949s
Reputation | Calculation of the PageRank for Lark took 0.0222928524017334s
Interlinking | Calculation of Degree of Connection for Lark took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Lark took 8.249282836914062e-05s
Believability | Calculation of trust value for Lark took 1.3828277587890625e-05s
INFO | --- Analysis for LARK took 1676.4938707351685s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.5170750617980957s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.3352024555206299s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020682334899902344s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 4.1961669921875e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 9.775161743164062e-06s
INFO | --- Analysis for LASLA took 4.700101613998413s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.5032322406768799s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.3542468547821045s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 4.124641418457031e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 1.5020370483398438e-05s
INFO | --- Analysis for Latin_Vallex2.0 took 4.971490383148193s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.43711256980895996s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.3300001621246338s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.02140665054321289s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 1.52587890625e-05s
INFO | --- Analysis for LatinAffectus took 4.600471496582031s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.43737125396728516s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0008785724639892578s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.4676938056945801s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.022366046905517578s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.482269287109375e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 1.5735626220703125e-05s
INFO | --- Analysis for LatinWordnetLiLa took 5.315945148468018s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 5.054473876953125e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0007503032684326172s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.3213531970977783s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02065563201904297s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00012826919555664062s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.5497207641601562e-05s
INFO | --- Analysis for lcsh took 8.23312520980835s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 5.340576171875e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.36679935455322266s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.020748615264892578s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.511543273925781e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 1.5974044799804688e-05s
INFO | --- Analysis for lcsubjects took 4.066442966461182s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.157790660858154s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0007588863372802734s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.35356926918029785s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020881175994873047s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.458427429199219e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.52587890625e-05s
INFO | --- Analysis for ldt@library took 35.451372385025024s
Availability | SPARQL endpoint availability check for U ime Legije took 9.751319885253906e-05s
Availability | VoID file availability check for U ime Legije took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.34821557998657227s
Reputation | Calculation of the PageRank for U ime Legije took 0.020721912384033203s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.337860107421875e-05s
Believability | Calculation of trust value for U ime Legije took 9.775161743164062e-06s
INFO | --- Analysis for LEGIJA_STRANACA took 3.308790683746338s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.43500471115112305s
Availability | VoID file availability check for LiLa Lemma Bank took 0.00081634521484375s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.4152207374572754s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.021564006805419922s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.653236389160156e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.5497207641601562e-05s
INFO | --- Analysis for LemmaBank took 5.15851354598999s
Availability | SPARQL endpoint availability check for lemonUby took 0.00010538101196289062s
Availability | VoID file availability check for lemonUby took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for lemonUby took 0.34864330291748047s
Reputation | Calculation of the PageRank for lemonUby took 0.020954608917236328s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.818771362304688e-05s
Believability | Calculation of trust value for lemonUby took 1.4781951904296875e-05s
INFO | --- Analysis for lemonuby took 4.323267936706543s
Availability | SPARQL endpoint availability check for LemonWiktionary took 0.0001513957977294922s
Availability | VoID file availability check for LemonWiktionary took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.36951136589050293s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.022571086883544922s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.504753112792969e-05s
Believability | Calculation of trust value for LemonWiktionary took 1.3589859008789062e-05s
INFO | --- Analysis for lemonwiktionary took 5.3564770221710205s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.4598259925842285s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.3731515407562256s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02257394790649414s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007317066192626953s
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.52587890625e-05s
INFO | --- Analysis for LewisShort took 11.99882960319519s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.126162052154541s
Availability | VoID file availability check for LEXIN-RDF took 0.0007293224334716797s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.3711402416229248s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.020953655242919922s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.24249267578125e-05s
Believability | Calculation of trust value for LEXIN-RDF took 1.3113021850585938e-05s
INFO | --- Analysis for lexin-rdf took 6.824778079986572s
Availability | SPARQL endpoint availability check for lexinfo took 5.125999450683594e-05s
Availability | VoID file availability check for lexinfo took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for lexinfo took 0.32740139961242676s
Reputation | Calculation of the PageRank for lexinfo took 0.02098822593688965s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for lexinfo took 9.584426879882812e-05s
Believability | Calculation of trust value for lexinfo took 1.4781951904296875e-05s
INFO | --- Analysis for lexinfo took 4.269930839538574s
Availability | SPARQL endpoint availability check for Lexvo took 0.0001456737518310547s
Availability | VoID file availability check for Lexvo took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for Lexvo took 0.32677435874938965s
Reputation | Calculation of the PageRank for Lexvo took 0.021169185638427734s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017714500427246094s
Believability | Calculation of trust value for Lexvo took 7.867813110351562e-06s
INFO | --- Analysis for lexvo took 3.727879047393799s
Availability | SPARQL endpoint availability check for Lexvo.org took 0.00010251998901367188s
Availability | VoID file availability check for Lexvo.org took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.36354970932006836s
Reputation | Calculation of the PageRank for Lexvo.org took 0.02115011215209961s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.510185241699219e-05s
Believability | Calculation of trust value for Lexvo.org took 1.33514404296875e-05s
INFO | --- Analysis for lexvo-org took 3.22562837600708s
Availability | SPARQL endpoint availability check for LIBRIS took 0.3560779094696045s
Availability | VoID file availability check for LIBRIS took 0.0006852149963378906s
Extra | Recovery of all triples for LIBRIS took 6.771633625030518s
Performance | Total latancy measurement for LIBRIS took 0.7885599136352539s
Amount of data | Number of triples check for LIBRIS took 23.15781259536743s
Interoperability | New terms check for LIBRIS took 18.023067712783813s
Versatility | Languages check for LIBRIS took 0.20199346542358398s
Interpretability | Number of blank nodes check for LIBRIS took 300.0367696285248s
Security | Check HTTPS for LIBRIS took 0.424846887588501s
Interpretability | RDF structures check for LIBRIS took 0.21311163902282715s
Versatility | Serialization formats check for LIBRIS took 0.2112741470336914s
Availability | RDF dump link check for LIBRIS took 0.14964818954467773s
License | MR license check for LIBRIS took 0.18260717391967773s
License | HR license check for LIBRIS took 0.14918923377990723s
Amount of data | Number of property check for LIBRIS took 0.21746087074279785s
Understandability | Number of label check for LIBRIS took 0.2251138687133789s
Understandability | URI regex check for LIBRIS took 0.28876256942749023s
Understandability | Vocabs check for LIBRIS took 0.1518692970275879s
Verifiability | Authors check for LIBRIS took 0.15417194366455078s
Verifiability | Publishers check for LIBRIS took 0.1517338752746582s
Performance | Throughput check for LIBRIS took 10.52768063545227s
Amount of data | Check the number of entities for LIBRIS took 9.846687316894531e-05s
Verifiability | Contribs. check for LIBRIS took 0.15123867988586426s
Interlinking | sameAs chians check for LIBRIS took 0.1524639129638672s
Interlinking | skos check for LIBRIS took 0.15213871002197266s
Interlinking | skos check for LIBRIS took 0.1501295566558838s
Timeliness | dataset update frequency check for LIBRIS took 0.1530306339263916s
Currency | Creation date check for LIBRIS took 0.34784841537475586s
Currency | Modification date check for LIBRIS took 0.6685268878936768s
Rep.Conc. | URIs length for LIBRIS took 94.38099765777588s
Interoperability | New vocabularies check for LIBRIS took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.1990964412689209s
Accuracy | Check Functional Property for LIBRIS took 0.1927473545074463s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.14963984489440918s
Accuracy | Check Datatype consistency for LIBRIS took 0.28179311752319336s
Consistency | Disjoint class check for LIBRIS took 0.19431328773498535s
Consistency | Check Misplaced properties for LIBRIS took 70.69646191596985s
Consistency | Misplaced classes for LIBRIS took 1.1591601371765137s
Consistency | Check Ontology hijacking for LIBRIS took 3.5510220527648926s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.3842382431030273s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 71.68035078048706s
Conciseness | Check Extensional conciseness for LIBRIS took 0.2853207588195801s
Conciseness | Check Intensional conciseness for LIBRIS took 0.4545867443084717s
Security | Sign check for LIBRIS took 0.14583349227905273s
Availability | Check URIs Dereferenciability for LIBRIS took 9.032533407211304s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.4593479633331299s
Reputation | Calculation of the PageRank for LIBRIS took 0.020720720291137695s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 9.655952453613281e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.430511474609375e-06s
Believability | Calculation of trust value for LIBRIS took 1.9073486328125e-05s
INFO | --- Analysis for libris took 1115.7984755039215s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.06478476524353027s
Availability | VoID file availability check for Public Library of Veroia took 0.0007126331329345703s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.3124656677246094s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.021015644073486328s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.724761962890625e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.4543533325195312e-05s
INFO | --- Analysis for libver took 4.454218149185181s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.16257977485656738s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.35803842544555664s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.020984172821044922s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.130073547363281e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 1.049041748046875e-05s
INFO | --- Analysis for lichfield-spending took 3.6371991634368896s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.9114227294921875e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0007824897766113281s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.34775567054748535s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.022381067276000977s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.743171691894531e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.5497207641601562e-05s
INFO | --- Analysis for lime took 7.35556173324585s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 5.555152893066406e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.46477842330932617s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.32116031646728516s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.02090167999267578s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00011968612670898438s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.2874603271484375e-05s
INFO | --- Analysis for lingvoj took 12.98814082145691s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 9.489059448242188e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.3288760185241699s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.02139878273010254s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.20159912109375e-05s
Believability | Calculation of trust value for Linked Crunchbase took 1.2636184692382812e-05s
INFO | --- Analysis for linked-crunchbase took 15.938143968582153s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.3322868347167969s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007474422454833984s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.3403010368347168s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.020587921142578125s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.295608520507812e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.3828277587890625e-05s
INFO | --- Analysis for linked-drugs took 7.334927797317505s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 0.00010037422180175781s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.33978843688964844s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020772933959960938s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.72747802734375e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 1.0013580322265625e-05s
INFO | --- Analysis for linked-edgar took 5.107054233551025s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 5.0067901611328125e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.3729679584503174s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.655952453613281e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 1.3589859008789062e-05s
INFO | --- Analysis for linked-eurostat took 4.4591686725616455s
Availability | SPARQL endpoint availability check for linked hypernyms took 0.00018405914306640625s
Availability | VoID file availability check for linked hypernyms took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.3716092109680176s
Reputation | Calculation of the PageRank for linked hypernyms took 0.021691322326660156s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.581710815429688e-05s
Believability | Calculation of trust value for linked hypernyms took 1.5020370483398438e-05s
INFO | --- Analysis for linked-hypernyms took 5.166160821914673s
Availability | SPARQL endpoint availability check for Linked Life Data took 223.8178825378418s
Availability | VoID file availability check for Linked Life Data took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.8344697952270508s
Reputation | Calculation of the PageRank for Linked Life Data took 0.022302865982055664s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0008425712585449219s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 5.1975250244140625e-05s
Believability | Calculation of trust value for Linked Life Data took 1.71661376953125e-05s
INFO | --- Analysis for linked-life-data took 638.3091268539429s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.32437801361083984s
Availability | VoID file availability check for Linked Logainm took 0.0003104209899902344s
Extra | Recovery of all triples for Linked Logainm took 1.6246800422668457s
Performance | Total latancy measurement for Linked Logainm took 0.6459746360778809s
Amount of data | Number of triples check for Linked Logainm took 0.23299360275268555s
Interoperability | New terms check for Linked Logainm took 1.5330171585083008s
Versatility | Languages check for Linked Logainm took 1.4636099338531494s
Interpretability | Number of blank nodes check for Linked Logainm took 0.14754295349121094s
Security | Check HTTPS for Linked Logainm took 0.31498098373413086s
Interpretability | RDF structures check for Linked Logainm took 0.25557780265808105s
Versatility | Serialization formats check for Linked Logainm took 0.16478228569030762s
Availability | RDF dump link check for Linked Logainm took 0.1369168758392334s
License | MR license check for Linked Logainm took 0.13452434539794922s
License | HR license check for Linked Logainm took 0.14182424545288086s
Amount of data | Number of property check for Linked Logainm took 0.15549516677856445s
Understandability | Number of label check for Linked Logainm took 0.20884060859680176s
Understandability | URI regex check for Linked Logainm took 0.2630927562713623s
Understandability | Vocabs check for Linked Logainm took 0.12855172157287598s
Verifiability | Authors check for Linked Logainm took 0.12453484535217285s
Verifiability | Publishers check for Linked Logainm took 0.1367635726928711s
Performance | Throughput check for Linked Logainm took 10.865738153457642s
Amount of data | Check the number of entities for Linked Logainm took 7.295608520507812e-05s
Verifiability | Contribs. check for Linked Logainm took 0.12338471412658691s
Interlinking | sameAs chians check for Linked Logainm took 0.15155267715454102s
Interlinking | skos check for Linked Logainm took 0.1786801815032959s
Interlinking | skos check for Linked Logainm took 0.12056159973144531s
Timeliness | dataset update frequency check for Linked Logainm took 0.13727664947509766s
Currency | Creation date check for Linked Logainm took 0.28103160858154297s
Currency | Modification date check for Linked Logainm took 0.2793598175048828s
Rep.Conc. | URIs length for Linked Logainm took 0.9925413131713867s
Interoperability | New vocabularies check for Linked Logainm took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.15354418754577637s
Accuracy | Check Functional Property for Linked Logainm took 0.22570061683654785s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.1995835304260254s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.6077835559844971s
Accuracy | Check White space in annotation for Linked Logainm took 0.02406597137451172s
Accuracy | Check Datatype consistency for Linked Logainm took 0.029501676559448242s
Consistency | Disjoint class check for Linked Logainm took 0.2043437957763672s
Consistency | Check Misplaced properties for Linked Logainm took 0.3558175563812256s
Consistency | Misplaced classes for Linked Logainm took 0.3174550533294678s
Consistency | Check Ontology hijacking for Linked Logainm took 1.9120197296142578s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.368502140045166s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.5866448879241943s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.03260946273803711s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.2346494197845459s
Security | Sign check for Linked Logainm took 0.14678215980529785s
Availability | Check URIs Dereferenciability for Linked Logainm took 1085.2552027702332s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.463925838470459s
Reputation | Calculation of the PageRank for Linked Logainm took 0.022321462631225586s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0010266304016113281s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 0.00010013580322265625s
Interoperability | Check the re-using of existing vocabs for Linked Logainm took 1.430511474609375e-06s
Believability | Calculation of trust value for Linked Logainm took 1.5974044799804688e-05s
INFO | --- Analysis for linked-logainm took 1145.0277121067047s
Availability | SPARQL endpoint availability check for Linked NUTS took 5.054473876953125e-05s
Availability | VoID file availability check for Linked NUTS took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.3261749744415283s
Reputation | Calculation of the PageRank for Linked NUTS took 0.022957324981689453s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.435943603515625e-05s
Believability | Calculation of trust value for Linked NUTS took 1.0251998901367188e-05s
INFO | --- Analysis for linked-nuts took 3.258396625518799s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.5088472366333008s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.3695709705352783s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020850658416748047s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 4.0531158447265625e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 1.1205673217773438e-05s
INFO | --- Analysis for linked-open-camera took 5.203032732009888s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.445884943008423s
Availability | VoID file availability check for Linked Open Commerce took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.37036895751953125s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.023155927658081055s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.266334533691406e-05s
Believability | Calculation of trust value for Linked Open Commerce took 1.4781951904296875e-05s
INFO | --- Analysis for linked-open-commerce took 15.752240657806396s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 0.3553333282470703s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.33928394317626953s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.02192831039428711s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010538101196289062s
Believability | Calculation of trust value for Linked Open Data of Ecology took 1.430511474609375e-05s
INFO | --- Analysis for linked-open-data-of-ecology took 3.5071966648101807s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 5.316734313964844e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.3294491767883301s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020781755447387695s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 0.00010013580322265625s
Believability | Calculation of trust value for Linked Open Numbers took 1.430511474609375e-05s
INFO | --- Analysis for linked-open-numbers took 3.480266571044922s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 0.00010204315185546875s
Availability | VoID file availability check for Linked Open Piracy took 0.0008788108825683594s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.3629636764526367s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.02102518081665039s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 3.1948089599609375e-05s
Believability | Calculation of trust value for Linked Open Piracy took 1.1444091796875e-05s
INFO | --- Analysis for linked-open-piracy took 8.589019298553467s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 4.460249662399292s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0007441043853759766s
Extra | Recovery of all triples for Linked Open Vocabularies (LOV) took 116.95468258857727s
Performance | Total latancy measurement for Linked Open Vocabularies (LOV) took 4.267150402069092s
Amount of data | Number of triples check for Linked Open Vocabularies (LOV) took 2.846764087677002s
Interoperability | New terms check for Linked Open Vocabularies (LOV) took 4.63254976272583s
Versatility | Languages check for Linked Open Vocabularies (LOV) took 14.86216688156128s
Interpretability | Number of blank nodes check for Linked Open Vocabularies (LOV) took 4.892153263092041s
Interpretability | RDF structures check for Linked Open Vocabularies (LOV) took 1.571854591369629s
Versatility | Serialization formats check for Linked Open Vocabularies (LOV) took 2.160949945449829s
Availability | RDF dump link check for Linked Open Vocabularies (LOV) took 2.8173067569732666s
License | MR license check for Linked Open Vocabularies (LOV) took 0.853590726852417s
License | HR license check for Linked Open Vocabularies (LOV) took 50.62746214866638s
Amount of data | Number of property check for Linked Open Vocabularies (LOV) took 2.807377815246582s
Understandability | Number of label check for Linked Open Vocabularies (LOV) took 3.302513837814331s
Understandability | URI regex check for Linked Open Vocabularies (LOV) took 3.8741607666015625s
Understandability | Vocabs check for Linked Open Vocabularies (LOV) took 1.4761762619018555s
Verifiability | Authors check for Linked Open Vocabularies (LOV) took 1.6529600620269775s
Verifiability | Publishers check for Linked Open Vocabularies (LOV) took 1.9866886138916016s
Performance | Throughput check for Linked Open Vocabularies (LOV) took 18.425164222717285s
Amount of data | Check the number of entities for Linked Open Vocabularies (LOV) took 1.1406760215759277s
Verifiability | Contribs. check for Linked Open Vocabularies (LOV) took 1.5083389282226562s
Interlinking | sameAs chians check for Linked Open Vocabularies (LOV) took 1.897643804550171s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 2.2558741569519043s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.9403367042541504s
Timeliness | dataset update frequency check for Linked Open Vocabularies (LOV) took 2.320605993270874s
Currency | Creation date check for Linked Open Vocabularies (LOV) took 3.879786729812622s
Currency | Modification date check for Linked Open Vocabularies (LOV) took 2.452115058898926s
Rep.Conc. | URIs length for Linked Open Vocabularies (LOV) took 33.22843956947327s
Interoperability | New vocabularies check for Linked Open Vocabularies (LOV) took 95.6828134059906s
Consistency | Deprecated classes/propertiers check for Linked Open Vocabularies (LOV) took 1.758110761642456s
Accuracy | Check Functional Property for Linked Open Vocabularies (LOV) took 0.9589943885803223s
Accuracy | Check Inverse Functional Property for Linked Open Vocabularies (LOV) took 1.785722017288208s
Accuracy | Check Empty annotation labels for Linked Open Vocabularies (LOV) took 13.731485605239868s
Accuracy | Check White space in annotation for Linked Open Vocabularies (LOV) took 0.6972436904907227s
Accuracy | Check Datatype consistency for Linked Open Vocabularies (LOV) took 4.922473669052124s
Consistency | Disjoint class check for Linked Open Vocabularies (LOV) took 1.1531119346618652s
Consistency | Check Misplaced properties for Linked Open Vocabularies (LOV) took 13.12541651725769s
Consistency | Misplaced classes for Linked Open Vocabularies (LOV) took 1.6198320388793945s
Consistency | Check Ontology hijacking for Linked Open Vocabularies (LOV) took 12.64856219291687s
Consistency | Check Invalid usage of undefined classes for Linked Open Vocabularies (LOV) took 1.5146524906158447s
Conciseness | Check Extensional conciseness for Linked Open Vocabularies (LOV) took 2.926542282104492s
Conciseness | Check Intensional conciseness for Linked Open Vocabularies (LOV) took 5.61667799949646s
Security | Sign check for Linked Open Vocabularies (LOV) took 1.1238975524902344s
Availability | Check URIs Dereferenciability for Linked Open Vocabularies (LOV) took 5981.327637910843s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.46968841552734375s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.023270845413208008s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 0.00018906593322753906s
Interoperability | Check the re-using of existing vocabs for Linked Open Vocabularies (LOV) took 28.183226346969604s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.4543533325195312e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 7285.167957782745s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.935264587402344e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.3789560794830322s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.02137923240661621s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0008766651153564453s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 4.220008850097656e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 6.9141387939453125e-06s
INFO | --- Analysis for linked-periodicals took 4.034295082092285s
Availability | SPARQL endpoint availability check for Linked Index took 6.151199340820312e-05s
Availability | VoID file availability check for Linked Index took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for Linked Index took 0.3660094738006592s
Reputation | Calculation of the PageRank for Linked Index took 0.0212857723236084s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.869171142578125e-05s
Believability | Calculation of trust value for Linked Index took 1.5735626220703125e-05s
INFO | --- Analysis for linked-stockindex took 4.116903781890869s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.764273405075073s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.3783721923828125s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.020828723907470703s
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.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.8623809814453125e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.5974044799804688e-05s
INFO | --- Analysis for linked-structured-product-labels took 20.291085958480835s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.053468942642211914s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.00032639503479003906s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.31136083602905273s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.020823001861572266s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.528594970703125e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 1.4781951904296875e-05s
INFO | --- Analysis for linked-taiwan-geo-names took 3.3921990394592285s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.23979115486145s
Availability | VoID file availability check for Linked TCGA took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.36139631271362305s
Reputation | Calculation of the PageRank for Linked TCGA took 0.021680116653442383s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 9.34600830078125e-05s
Believability | Calculation of trust value for Linked TCGA took 1.430511474609375e-05s
INFO | --- Analysis for linked-tcga took 63.69570565223694s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.08538341522216797s
Availability | VoID file availability check for Linked User Feedback took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.3277609348297119s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.02077507972717285s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 4.673004150390625e-05s
Believability | Calculation of trust value for Linked User Feedback took 0.0001418590545654297s
INFO | --- Analysis for linked-user-feedback took 3.818800449371338s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.887580871582031e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0012664794921875s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.33834385871887207s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020973682403564453s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0008282661437988281s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 8.177757263183594e-05s
Believability | Calculation of trust value for USPTO Patent data took 1.9550323486328125e-05s
INFO | --- Analysis for linked-uspto-patent-data took 54.244163274765015s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.0811772346496582s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.43379664421081543s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.02111077308654785s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0008013248443603516s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.647804260253906e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.621246337890625e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 3.6291239261627197s
Availability | SPARQL endpoint availability check for LinkedCT took 1.402893304824829s
Availability | VoID file availability check for LinkedCT took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.3497343063354492s
Reputation | Calculation of the PageRank for LinkedCT took 0.020934581756591797s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.000102996826171875s
Believability | Calculation of trust value for LinkedCT took 1.4781951904296875e-05s
INFO | --- Analysis for linkedct took 5.923412561416626s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.16617059707641602s
Availability | VoID file availability check for LinkedGeoData took 0.0005917549133300781s
Extra | Recovery of all triples for LinkedGeoData took 7.030094861984253s
Performance | Total latancy measurement for LinkedGeoData took 0.6956315040588379s
Amount of data | Number of triples check for LinkedGeoData took 69.63338494300842s
Interoperability | New terms check for LinkedGeoData took 90.95535111427307s
Versatility | Languages check for LinkedGeoData took 181.88028812408447s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.21194672584533691s
Security | Check HTTPS for LinkedGeoData took 0.3160557746887207s
Interpretability | RDF structures check for LinkedGeoData took 1.369330883026123s
Versatility | Serialization formats check for LinkedGeoData took 0.4829401969909668s
Availability | RDF dump link check for LinkedGeoData took 0.16561150550842285s
License | MR license check for LinkedGeoData took 1.0324487686157227s
License | HR license check for LinkedGeoData took 118.77190923690796s
Amount of data | Number of property check for LinkedGeoData took 0.281796932220459s
Understandability | Number of label check for LinkedGeoData took 3.1881470680236816s
Understandability | URI regex check for LinkedGeoData took 0.45236659049987793s
Understandability | Vocabs check for LinkedGeoData took 0.16588068008422852s
Verifiability | Authors check for LinkedGeoData took 0.18446922302246094s
Verifiability | Publishers check for LinkedGeoData took 0.13321828842163086s
Performance | Throughput check for LinkedGeoData took 10.556486129760742s
Amount of data | Check the number of entities for LinkedGeoData took 0.07535767555236816s
Verifiability | Contribs. check for LinkedGeoData took 2.4218761920928955s
Interlinking | sameAs chians check for LinkedGeoData took 0.32382726669311523s
Interlinking | skos check for LinkedGeoData took 0.4338083267211914s
Interlinking | skos check for LinkedGeoData took 0.13910603523254395s
Timeliness | dataset update frequency check for LinkedGeoData took 0.40499019622802734s
Currency | Creation date check for LinkedGeoData took 0.49285364151000977s
Currency | Modification date check for LinkedGeoData took 0.2829747200012207s
Rep.Conc. | URIs length for LinkedGeoData took 273.15668082237244s
Interoperability | New vocabularies check for LinkedGeoData took 26.628441333770752s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.15403461456298828s
Accuracy | Check Functional Property for LinkedGeoData took 0.2345592975616455s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.19637036323547363s
Accuracy | Check Empty annotation labels for LinkedGeoData took 1.888225793838501s
Accuracy | Check White space in annotation for LinkedGeoData took 0.16628026962280273s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.13964223861694336s
Consistency | Disjoint class check for LinkedGeoData took 0.2662968635559082s
Consistency | Check Misplaced properties for LinkedGeoData took 180.76577067375183s
Consistency | Misplaced classes for LinkedGeoData took 0.6716930866241455s
Consistency | Check Ontology hijacking for LinkedGeoData took 3.722714424133301s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.3762550354003906s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 182.28092527389526s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.14986824989318848s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.24025630950927734s
Security | Sign check for LinkedGeoData took 0.8389110565185547s
Availability | Check URIs Dereferenciability for LinkedGeoData took 35.2699613571167s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.37189626693725586s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.021961212158203125s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00013685226440429688s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 23.654402017593384s
Believability | Calculation of trust value for LinkedGeoData took 1.6450881958007812e-05s
INFO | --- Analysis for linkedgeodata took 2274.1400356292725s
Availability | SPARQL endpoint availability check for LinkedLCCN took 6.419922590255737s
Availability | VoID file availability check for LinkedLCCN took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.32033538818359375s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.021696805953979492s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00012040138244628906s
Believability | Calculation of trust value for LinkedLCCN took 1.0013580322265625e-05s
INFO | --- Analysis for linkedlccn took 23.856822967529297s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 5.316734313964844e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0002987384796142578s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.35767388343811035s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.021683216094970703s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 4.00543212890625e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.430511474609375e-05s
INFO | --- Analysis for linkedmarkmail took 3.847261667251587s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 3.528458595275879s
Availability | VoID file availability check for Linked Movie DataBase took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.3689267635345459s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.023850202560424805s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.001257181167602539s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00017523765563964844s
Believability | Calculation of trust value for Linked Movie DataBase took 1.0251998901367188e-05s
INFO | --- Analysis for linkedmdb took 19.505107164382935s
Availability | SPARQL endpoint availability check for LinkedSpending took 0.537630558013916s
Availability | VoID file availability check for LinkedSpending took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for LinkedSpending took 0.34894514083862305s
Reputation | Calculation of the PageRank for LinkedSpending took 0.020985126495361328s
Interlinking | Calculation of Degree of Connection for LinkedSpending took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for LinkedSpending took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for LinkedSpending took 7.462501525878906e-05s
Believability | Calculation of trust value for LinkedSpending took 1.52587890625e-05s
INFO | --- Analysis for linkedspending took 5.167221307754517s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.20490717887878418s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.3287179470062256s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.020941734313964844s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00011181831359863281s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.4543533325195312e-05s
INFO | --- Analysis for linklion took 3.328805923461914s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 600.3714740276337s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.00036978721618652344s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.3334684371948242s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.021472692489624023s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 6.961822509765625e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 1.0013580322265625e-05s
INFO | --- Analysis for lista-encabezamientos-materia took 1215.0320782661438s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.0839018821716309s
Availability | VoID file availability check for lobid-organisations took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.3673713207244873s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02108621597290039s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 0.00010538101196289062s
Believability | Calculation of trust value for lobid-organisations took 1.52587890625e-05s
INFO | --- Analysis for lobid-organisations took 6.579652547836304s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.872319221496582s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0007455348968505859s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.3515458106994629s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.02098846435546875s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00010442733764648438s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 1.5497207641601562e-05s
INFO | --- Analysis for lobid-resources took 9.000482559204102s
Availability | SPARQL endpoint availability check for Linked Open Colors took 5.984306335449219e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.3336954116821289s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.021602630615234375s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.00086212158203125s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 8.034706115722656e-05s
Believability | Calculation of trust value for Linked Open Colors took 1.5735626220703125e-05s
INFO | --- Analysis for loc took 8.39092493057251s
Availability | SPARQL endpoint availability check for Location Ontology took 4.9114227294921875e-05s
Availability | VoID file availability check for Location Ontology took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.3270416259765625s
Reputation | Calculation of the PageRank for Location Ontology took 0.02106499671936035s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for Location Ontology took 1.6450881958007812e-05s
INFO | --- Analysis for Location_Ontology took 5.969001531600952s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 0.0001747608184814453s
Availability | VoID file availability check for Linked Open Computer Vision took 0.00033473968505859375s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.37196969985961914s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.021416902542114258s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.981590270996094e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 1.0967254638671875e-05s
INFO | --- Analysis for locv took 33.322264671325684s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.8874177932739258s
Availability | VoID file availability check for LOD-a-lot took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.3635737895965576s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.02116227149963379s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.409385681152344e-05s
Believability | Calculation of trust value for LOD-a-lot took 1.0251998901367188e-05s
INFO | --- Analysis for lod-a-lot took 15.110157489776611s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 0.00016546249389648438s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0008268356323242188s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.38550639152526855s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.021173954010009766s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 9.131431579589844e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 1.621246337890625e-05s
INFO | --- Analysis for lod2-project-wiki took 3.9388129711151123s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.6205060482025146s
Availability | VoID file availability check for LODAC BDLS took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.3830101490020752s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020693302154541016s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.605552673339844e-05s
Believability | Calculation of trust value for LODAC BDLS took 1.4066696166992188e-05s
INFO | --- Analysis for lodac-bdls took 14.660499811172485s
Availability | SPARQL endpoint availability check for lofd took 0.1315011978149414s
Availability | VoID file availability check for lofd took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for lofd took 0.36998677253723145s
Reputation | Calculation of the PageRank for lofd took 0.020997285842895508s
Interlinking | Calculation of Degree of Connection for lofd took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for lofd took 3.2901763916015625e-05s
Believability | Calculation of trust value for lofd took 1.52587890625e-05s
INFO | --- Analysis for lofd took 3.1734461784362793s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 271.7626268863678s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0007424354553222656s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.37575721740722656s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.02181267738342285s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 6.461143493652344e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 1.0728836059570312e-05s
INFO | --- Analysis for loius took 586.0116784572601s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.6641051769256592s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0006544589996337891s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.32060909271240234s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.02114558219909668s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.650520324707031e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 1.0728836059570312e-05s
INFO | --- Analysis for london-gazette took 5.05620551109314s
Availability | SPARQL endpoint availability check for Weather Stations took 0.00052642822265625s
Availability | VoID file availability check for Weather Stations took 0.00077056884765625s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.40042757987976074s
Reputation | Calculation of the PageRank for Weather Stations took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.106231689453125e-05s
Believability | Calculation of trust value for Weather Stations took 1.430511474609375e-05s
INFO | --- Analysis for los_metar took 11.35705304145813s
Availability | SPARQL endpoint availability check for Lotico took 0.581779956817627s
Availability | VoID file availability check for Lotico took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for Lotico took 0.3550984859466553s
Reputation | Calculation of the PageRank for Lotico took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for Lotico took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.20159912109375e-05s
Believability | Calculation of trust value for Lotico took 1.2636184692382812e-05s
INFO | --- Analysis for lotico took 6.248035669326782s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.4383573532104492s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0007665157318115234s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 1.015195369720459s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 1.0466423034667969s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.31116676330566406s
Interoperability | New terms check for Lower Layer Super Output Areas took 2.315469741821289s
Versatility | Languages check for Lower Layer Super Output Areas took 0.5233709812164307s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 30.16808533668518s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.1555469036102295s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.31993961334228516s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.2267916202545166s
Availability | RDF dump link check for Lower Layer Super Output Areas took 50.63799166679382s
License | MR license check for Lower Layer Super Output Areas took 0.31605958938598633s
License | HR license check for Lower Layer Super Output Areas took 30.257632970809937s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.2253556251525879s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.25162816047668457s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.41504955291748047s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.1927635669708252s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.21436738967895508s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.3042328357696533s
Performance | Throughput check for Lower Layer Super Output Areas took 12.27013635635376s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 3.2901763916015625e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.20157337188720703s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.30912089347839355s
Interlinking | skos check for Lower Layer Super Output Areas took 0.301196813583374s
Interlinking | skos check for Lower Layer Super Output Areas took 0.21225214004516602s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.2111358642578125s
Currency | Creation date check for Lower Layer Super Output Areas took 0.4775562286376953s
Currency | Modification date check for Lower Layer Super Output Areas took 0.3199484348297119s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 1.3449692726135254s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.7125873565673828s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.22082948684692383s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.21872591972351074s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.23641467094421387s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 0.6938588619232178s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 1.148026466369629s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.6572566032409668s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.00034737586975097656s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.42900514602661133s
Security | Sign check for Lower Layer Super Output Areas took 0.14957237243652344s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.3697352409362793s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.021387815475463867s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 1.1920928955078125e-06s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.0728836059570312e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 272.8236644268036s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6021556854248047s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0005180835723876953s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 102.69979524612427s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9915506839752197s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.44267225265503s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.17123031616211s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2346272468567s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.265238046646118s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2771952152252197s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.3095121383667s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3289177417755127s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.7251152992248535s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.21110677719116s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20152950286865234s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.1896846294403076s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.2672677040100098s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5876977443695068s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20392274856567383s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.23401880264282227s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.491676807403564s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.441375732421875e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.1836707592010498s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.1845104694366455s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5275435447692871s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.42995285987854004s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 5.787516355514526s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.47190070152282715s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.25496602058410645s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 151.3676221370697s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20311975479125977s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4918653964996338s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.43561387062072754s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 35.29697608947754s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.687656879425049s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.817596673965454s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.18291997909545898s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 85.77224612236023s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.631631851196289s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 36.644522190093994s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.5258243083953857s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 87.28793573379517s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.813079833984375s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5132417678833008s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.388761281967163s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 17.665135860443115s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5975437164306641s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.021541833877563477s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.100799560546875e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.821487426757812e-06s
INFO | --- Analysis for LPIS_(Poland) took 2279.7279028892517s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19501972198486328s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0005354881286621094s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 116.03380346298218s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.9490792751312256s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.105602741241455s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 14.205788850784302s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.24792408943176s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.9619722366333008s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19653534889221191s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.810731887817383s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19867944717407227s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3240830898284912s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.25171279907227s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.22099065780639648s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.2175908088684082s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.41367220878601074s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4145016670227051s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.22448277473449707s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.24984240531921387s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.25254201889038s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.034706115722656e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19160032272338867s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2202436923980713s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.41870856285095215s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.418834924697876s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.410816431045532s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.47626399993896484s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2510955333709717s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 155.1490981578827s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21515178680419922s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4458794593811035s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1903700828552246s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 31.287797689437866s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.6792118549346924s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.9476370811462402s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19752740859985352s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 86.18636298179626s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.600427627563477s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 34.8826470375061s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.5136842727661133s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 86.99443912506104s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.974126100540161s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5395598411560059s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5210006237030029s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.996496438980103s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.8092882633209229s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.021406173706054688s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.1975250244140625e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.5735626220703125e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 2264.105595111847s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 0.0003466606140136719s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.3308224678039551s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.021325111389160156s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.337860107421875e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 1.71661376953125e-05s
INFO | --- Analysis for lremap-auth took 3.7625796794891357s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.9591064453125e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.3430314064025879s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02142167091369629s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.409385681152344e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.52587890625e-05s
INFO | --- Analysis for lremap-conf took 3.4253439903259277s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 0.00010132789611816406s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.32820701599121094s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.022430419921875s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.0517578125e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.621246337890625e-05s
INFO | --- Analysis for lremap-ri took 3.3573081493377686s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0001049041748046875s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.36048173904418945s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.020966291427612305s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 4.220008850097656e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.0251998901367188e-05s
INFO | --- Analysis for lremap-sub took 3.4843246936798096s
Availability | SPARQL endpoint availability check for LSQ took 5.078315734863281e-05s
Availability | VoID file availability check for LSQ took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for LSQ took 0.36254167556762695s
Reputation | Calculation of the PageRank for LSQ took 0.022622108459472656s
Interlinking | Calculation of Degree of Connection for LSQ took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.0517578125e-05s
Believability | Calculation of trust value for LSQ took 9.775161743164062e-06s
INFO | --- Analysis for lsq took 4.382056474685669s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.6269772052764893s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0007474422454833984s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.36766982078552246s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.020793914794921875s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 1.7642974853515625e-05s
INFO | --- Analysis for LucaniPharsalia took 4.849114179611206s
Availability | SPARQL endpoint availability check for Linked rules took 4.9114227294921875e-05s
Availability | VoID file availability check for Linked rules took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Linked rules took 0.3527090549468994s
Reputation | Calculation of the PageRank for Linked rules took 0.022206783294677734s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.0994415283203125e-05s
Believability | Calculation of trust value for Linked rules took 1.4066696166992188e-05s
INFO | --- Analysis for Luminaires_senlis took 3.1615095138549805s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.216899633407593s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.35730814933776855s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.022670507431030273s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 4.410743713378906e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 1.1444091796875e-05s
INFO | --- Analysis for makg took 64.26345682144165s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 0.00010061264038085938s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.368924617767334s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.02117609977722168s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.743171691894531e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 1.4543533325195312e-05s
INFO | --- Analysis for manchester-university-reading-lists took 4.149984836578369s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 6.461143493652344e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0003497600555419922s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.3861382007598877s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.314018249511719e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.0728836059570312e-05s
INFO | --- Analysis for manish took 3.545792579650879s
Availability | SPARQL endpoint availability check for MARC Codes List took 0.00010061264038085938s
Availability | VoID file availability check for MARC Codes List took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.3363001346588135s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0008087158203125s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00013113021850585938s
Believability | Calculation of trust value for MARC Codes List took 1.430511474609375e-05s
INFO | --- Analysis for marc-codes took 14.233065843582153s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.792213439941406e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.34430480003356934s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.021568775177001953s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.363059997558594e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.5974044799804688e-05s
INFO | --- Analysis for masc took 7.1775617599487305s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 7.915496826171875e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.35022425651550293s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.02086663246154785s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.981590270996094e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.52587890625e-05s
INFO | --- Analysis for masc-bn-nif took 3.3713676929473877s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 0.09019923210144043s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.3456997871398926s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.021991968154907227s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.24249267578125e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 1.4066696166992188e-05s
INFO | --- Analysis for massobservationarchivecatalogue took 3.5488924980163574s
Availability | SPARQL endpoint availability check for medline took 0.00010037422180175781s
Availability | VoID file availability check for medline took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for medline took 0.32308316230773926s
Reputation | Calculation of the PageRank for medline took 0.021572113037109375s
Interlinking | Calculation of Degree of Connection for medline took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for medline took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for medline took 3.910064697265625e-05s
Believability | Calculation of trust value for medline took 1.1444091796875e-05s
INFO | --- Analysis for medline took 7.278390169143677s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 3.460716724395752s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0007810592651367188s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.3290553092956543s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.021061182022094727s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 7.271766662597656e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 1.4066696166992188e-05s
INFO | --- Analysis for meducator took 14.225520849227905s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 0.00010037422180175781s
Availability | VoID file availability check for MetaShare metadata model took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.3211185932159424s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.021370649337768555s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.343292236328125e-05s
Believability | Calculation of trust value for MetaShare metadata model took 1.5020370483398438e-05s
INFO | --- Analysis for metashare took 3.1321828365325928s
Availability | SPARQL endpoint availability check for MExiCo took 5.221366882324219e-05s
Availability | VoID file availability check for MExiCo took 0.0008056163787841797s
Completeness | Calculation of interlinking completeness for MExiCo took 0.3907008171081543s
Reputation | Calculation of the PageRank for MExiCo took 0.02083754539489746s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for MExiCo took 6.127357482910156e-05s
Believability | Calculation of trust value for MExiCo took 1.1205673217773438e-05s
INFO | --- Analysis for mexico took 23.323859214782715s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.027829885482788s
Availability | VoID file availability check for Coronavirus dataset took 0.0005161762237548828s
Extra | Recovery of all triples for Coronavirus dataset took 2.940800189971924s
Performance | Total latancy measurement for Coronavirus dataset took 2.539451837539673s
Amount of data | Number of triples check for Coronavirus dataset took 1.1369175910949707s
Interoperability | New terms check for Coronavirus dataset took 2.7184431552886963s
Versatility | Languages check for Coronavirus dataset took 60.529993295669556s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.290776252746582s
Interpretability | RDF structures check for Coronavirus dataset took 0.5494725704193115s
Versatility | Serialization formats check for Coronavirus dataset took 0.5503542423248291s
Availability | RDF dump link check for Coronavirus dataset took 0.5044043064117432s
License | MR license check for Coronavirus dataset took 0.5665276050567627s
License | HR license check for Coronavirus dataset took 42.67055678367615s
Amount of data | Number of property check for Coronavirus dataset took 0.5330181121826172s
Understandability | Number of label check for Coronavirus dataset took 1.5509116649627686s
Understandability | URI regex check for Coronavirus dataset took 1.0110831260681152s
Understandability | Vocabs check for Coronavirus dataset took 0.49645209312438965s
Verifiability | Authors check for Coronavirus dataset took 0.5443410873413086s
Verifiability | Publishers check for Coronavirus dataset took 0.5058166980743408s
Performance | Throughput check for Coronavirus dataset took 14.429040670394897s
Amount of data | Check the number of entities for Coronavirus dataset took 9.894371032714844e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.495880126953125s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5442357063293457s
Interlinking | skos check for Coronavirus dataset took 0.5609407424926758s
Interlinking | skos check for Coronavirus dataset took 0.4995856285095215s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.5141146183013916s
Currency | Creation date check for Coronavirus dataset took 1.0420925617218018s
Currency | Modification date check for Coronavirus dataset took 1.0332489013671875s
Rep.Conc. | URIs length for Coronavirus dataset took 7.400190114974976s
Interoperability | New vocabularies check for Coronavirus dataset took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5184674263000488s
Accuracy | Check Functional Property for Coronavirus dataset took 0.7588980197906494s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.5440037250518799s
Consistency | Disjoint class check for Coronavirus dataset took 0.7054293155670166s
Consistency | Misplaced classes for Coronavirus dataset took 0.5360183715820312s
Consistency | Check Ontology hijacking for Coronavirus dataset took 1.1054885387420654s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.843315839767456s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.00016069412231445312s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5359616279602051s
Security | Sign check for Coronavirus dataset took 0.5211739540100098s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.4490773677825928s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.022710800170898438s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 5.9604644775390625e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Coronavirus dataset took 1.5020370483398438e-05s
INFO | --- Analysis for micro-coronavirus took 244.6770098209381s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 5.0067901611328125e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.30877137184143066s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.020660877227783203s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010395050048828125s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.4543533325195312e-05s
INFO | --- Analysis for miguiadeviajes-gnoss took 6.436707258224487s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00011467933654785156s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.4291691780090332s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.02236342430114746s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.0967254638671875e-05s
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.00011014938354492188s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.52587890625e-05s
INFO | --- Analysis for mismuseos-gnoss took 8.422152042388916s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.11674141883850098s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.3448460102081299s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.021269798278808594s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0008003711700439453s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.696846008300781e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.4781951904296875e-05s
INFO | --- Analysis for mlsa took 3.92362904548645s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 0.00010657310485839844s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.35007476806640625s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.02081775665283203s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.0994415283203125e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 1.5020370483398438e-05s
INFO | --- Analysis for model took 34.44516468048096s
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 0.00015974044799804688s
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.0007059574127197266s
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.32563161849975586s
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.02093982696533203s
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.0967254638671875e-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.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 3.0040740966796875e-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.6450881958007812e-05s
INFO | --- Analysis for model1 took 21.017616033554077s
Availability | SPARQL endpoint availability check for MORElab took 1.1048448085784912s
Availability | VoID file availability check for MORElab took 0.000385284423828125s
Completeness | Calculation of interlinking completeness for MORElab took 0.33014488220214844s
Reputation | Calculation of the PageRank for MORElab took 0.021471500396728516s
Interlinking | Calculation of Degree of Connection for MORElab took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for MORElab took 9.274482727050781e-05s
Believability | Calculation of trust value for MORElab took 1.0013580322265625e-05s
INFO | --- Analysis for morelab took 5.716898202896118s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 1.935319185256958s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.33643007278442383s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.020717859268188477s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.630752563476562e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 1.0728836059570312e-05s
INFO | --- Analysis for msc took 18.212395429611206s
Availability | SPARQL endpoint availability check for Multext-East took 0.00011396408081054688s
Availability | VoID file availability check for Multext-East took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Multext-East took 0.34696388244628906s
Reputation | Calculation of the PageRank for Multext-East took 0.02248668670654297s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.790855407714844e-05s
Believability | Calculation of trust value for Multext-East took 1.5497207641601562e-05s
INFO | --- Analysis for multext-east took 3.102047920227051s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.649162292480469e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.319394588470459s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.0223388671875s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.600120544433594e-05s
Believability | Calculation of trust value for Multimedia Lab took 1.6450881958007812e-05s
INFO | --- Analysis for multimedia-lab took 3.013124704360962s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.7753574848175049s
Availability | VoID file availability check for Muninn World War I took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.33559155464172363s
Reputation | Calculation of the PageRank for Muninn World War I took 0.02255392074584961s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.058547973632812e-05s
Believability | Calculation of trust value for Muninn World War I took 1.4066696166992188e-05s
INFO | --- Analysis for muninn-world-war-i took 11.852563619613647s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 5.793571472167969e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.3372626304626465s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.021932125091552734s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0008878707885742188s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00012183189392089844s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.4066696166992188e-05s
INFO | --- Analysis for museosespania-gnoss took 38.5622718334198s
Availability | SPARQL endpoint availability check for Italian Museums took 1.4773991107940674s
Availability | VoID file availability check for Italian Museums took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.32048630714416504s
Reputation | Calculation of the PageRank for Italian Museums took 0.020816802978515625s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.988380432128906e-05s
Believability | Calculation of trust value for Italian Museums took 1.5020370483398438e-05s
INFO | --- Analysis for museums-in-italy took 4.623704433441162s
Availability | SPARQL endpoint availability check for Muziekweb took 0.7680933475494385s
Availability | VoID file availability check for Muziekweb took 0.0006403923034667969s
Extra | Recovery of all triples for Muziekweb took 1.4490892887115479s
Performance | Total latancy measurement for Muziekweb took 1.6664912700653076s
Amount of data | Number of triples check for Muziekweb took 0.3187110424041748s
Interoperability | New terms check for Muziekweb took 1.6902103424072266s
Versatility | Languages check for Muziekweb took 0.31525564193725586s
Interpretability | Number of blank nodes check for Muziekweb took 0.3629124164581299s
Interpretability | RDF structures check for Muziekweb took 0.3340916633605957s
Versatility | Serialization formats check for Muziekweb took 0.3142697811126709s
Availability | RDF dump link check for Muziekweb took 0.32311296463012695s
License | MR license check for Muziekweb took 0.3211662769317627s
License | HR license check for Muziekweb took 0.3452153205871582s
Amount of data | Number of property check for Muziekweb took 0.31925487518310547s
Understandability | Number of label check for Muziekweb took 0.36324596405029297s
Understandability | URI regex check for Muziekweb took 0.6036832332611084s
Understandability | Vocabs check for Muziekweb took 0.29575371742248535s
Verifiability | Authors check for Muziekweb took 0.31668806076049805s
Verifiability | Publishers check for Muziekweb took 0.35471677780151367s
Performance | Throughput check for Muziekweb took 11.42349624633789s
Amount of data | Check the number of entities for Muziekweb took 0.00014972686767578125s
Verifiability | Contribs. check for Muziekweb took 0.3023717403411865s
Interlinking | sameAs chians check for Muziekweb took 0.36155271530151367s
Interlinking | skos check for Muziekweb took 0.3281857967376709s
Interlinking | skos check for Muziekweb took 0.35324978828430176s
Timeliness | dataset update frequency check for Muziekweb took 0.32727551460266113s
Currency | Creation date check for Muziekweb took 0.6575167179107666s
Currency | Modification date check for Muziekweb took 0.6424131393432617s
Rep.Conc. | URIs length for Muziekweb took 1.2971522808074951s
Interoperability | New vocabularies check for Muziekweb took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.3365042209625244s
Accuracy | Check Functional Property for Muziekweb took 0.32677125930786133s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.3203926086425781s
Accuracy | Check Empty annotation labels for Muziekweb took 2.8552396297454834s
Accuracy | Check White space in annotation for Muziekweb took 0.027797937393188477s
Accuracy | Check Datatype consistency for Muziekweb took 0.029334545135498047s
Consistency | Disjoint class check for Muziekweb took 0.2988765239715576s
Consistency | Check Misplaced properties for Muziekweb took 0.7023277282714844s
Consistency | Check Ontology hijacking for Muziekweb took 2.0211288928985596s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.3378734588623047s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.6775801181793213s
Conciseness | Check Extensional conciseness for Muziekweb took 0.035720109939575195s
Conciseness | Check Intensional conciseness for Muziekweb took 0.3338184356689453s
Security | Sign check for Muziekweb took 0.3164830207824707s
Availability | Check URIs Dereferenciability for Muziekweb took 2397.605288505554s
Completeness | Calculation of interlinking completeness for Muziekweb took 1.0100739002227783s
Reputation | Calculation of the PageRank for Muziekweb took 0.021296977996826172s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 6.985664367675781e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.9073486328125e-06s
Believability | Calculation of trust value for Muziekweb took 1.049041748046875e-05s
INFO | --- Analysis for muziekweb took 2461.8591883182526s
Availability | SPARQL endpoint availability check for myExperiment took 0.6987273693084717s
Availability | VoID file availability check for myExperiment took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for myExperiment took 0.3522176742553711s
Reputation | Calculation of the PageRank for myExperiment took 0.021390438079833984s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00010561943054199219s
Believability | Calculation of trust value for myExperiment took 1.0013580322265625e-05s
INFO | --- Analysis for my-experiment took 5.269948482513428s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.08558845520019531s
Availability | VoID file availability check for My Family Lineage took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.3185126781463623s
Reputation | Calculation of the PageRank for My Family Lineage took 0.021120309829711914s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.869171142578125e-05s
Believability | Calculation of trust value for My Family Lineage took 1.4781951904296875e-05s
INFO | --- Analysis for my-family-lineage took 4.213632106781006s
Availability | SPARQL endpoint availability check for My ontology test took 0.9159426689147949s
Availability | VoID file availability check for My ontology test took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for My ontology test took 0.33270263671875s
Reputation | Calculation of the PageRank for My ontology test took 0.02097034454345703s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.266334533691406e-05s
Believability | Calculation of trust value for My ontology test took 9.298324584960938e-06s
INFO | --- Analysis for myontologytest took 4.402378082275391s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 4.9114227294921875e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0007870197296142578s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.35153889656066895s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.02142333984375s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.00011181831359863281s
Believability | Calculation of trust value for myopenlink dataspaces took 1.52587890625e-05s
INFO | --- Analysis for myopenlink-dataspaces took 4.654853343963623s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 7.529487371444702s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0009174346923828125s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.6224126815795898s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.020850419998168945s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0008842945098876953s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 7.843971252441406e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for n-lex-as-linked-data took 19.609533309936523s
Availability | SPARQL endpoint availability check for NAICS 2007 took 26.111667156219482s
Availability | VoID file availability check for NAICS 2007 took 0.0009093284606933594s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.3448450565338135s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.0220949649810791s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.601478576660156e-05s
Believability | Calculation of trust value for NAICS 2007 took 1.0967254638671875e-05s
INFO | --- Analysis for naics-2007 took 125.2958037853241s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.84753131866455s
Availability | VoID file availability check for NAICS 2012 took 0.0007531642913818359s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.3696894645690918s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.021120071411132812s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 4.673004150390625e-05s
Believability | Calculation of trust value for NAICS 2012 took 1.0251998901367188e-05s
INFO | --- Analysis for naics-2012 took 123.74509239196777s
Availability | SPARQL endpoint availability check for Usernames  took 5.91278076171875e-05s
Availability | VoID file availability check for Usernames  took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for Usernames  took 0.34876155853271484s
Reputation | Calculation of the PageRank for Usernames  took 0.02097606658935547s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.24249267578125e-05s
Believability | Calculation of trust value for Usernames  took 1.5020370483398438e-05s
INFO | --- Analysis for Names took 3.349583625793457s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.0391349792480469s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0008406639099121094s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 0.9871094226837158s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 3.0412657260894775s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.736599206924438s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 15.688064098358154s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.8081285953521729s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.495748281478882s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.3031461238861084s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.7756092548370361s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.3922560214996338s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.3227226734161377s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.84358811378479s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.3757975101471s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.8281183242797852s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 6.41546368598938s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 1.1806039810180664s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.8490142822265625s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.8339674472808838s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.36181116104125977s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.607457160949707s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 4.744529724121094e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.8413524627685547s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.9212720394134521s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.709782361984253s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.0560805797576904s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.3585677146911621s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.566237211227417s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 1.1563255786895752s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.2102789878845215s
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.3371748924255371s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3556239604949951s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.39493680000305176s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.3984971046447754s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007343292236328125s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.00106048583984375s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.810288667678833s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.7101247310638428s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.3766913414001465s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.7291429042816162s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.3493189811706543s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.7075800895690918s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0008797645568847656s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.3678607940673828s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 4.618494510650635s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.5523831844329834s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02118229866027832s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.771087646484375e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.1920928955078125e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 6.67572021484375e-06s
INFO | --- Analysis for national-diet-library-authorities took 240.56831288337708s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.33168721199035645s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.00037670135498046875s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.1620078086853027s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 2.908311605453491s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.489497423171997s
Interoperability | New terms check for National Diet Library of Japan subject headings took 19.219851970672607s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.3537106513977051s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.341953992843628s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.7572460174560547s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.38321566581726074s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.3797953128814697s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.3350663185119629s
License | MR license check for National Diet Library of Japan subject headings took 0.34063053131103516s
License | HR license check for National Diet Library of Japan subject headings took 91.35586977005005s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.43676233291625977s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.02498459815979s
Understandability | URI regex check for National Diet Library of Japan subject headings took 1.2301304340362549s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.7864713668823242s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.3592710494995117s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.8219118118286133s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.481926441192627s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 0.00016641616821289062s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.371335506439209s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.8988227844238281s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.4462149143218994s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.3274502754211426s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.3252851963043213s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.0981025695800781s
Currency | Modification date check for National Diet Library of Japan subject headings took 1.2123804092407227s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.7181727886199951s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.7756912708282471s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.3256402015686035s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.3867299556732178s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.359804630279541s
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.001062631607055664s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.35535717010498047s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.7177259922027588s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.3512587547302246s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.7365696430206299s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.3625733852386475s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.7340481281280518s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0007846355438232422s
Security | Sign check for National Diet Library of Japan subject headings took 0.34586167335510254s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 5.019075155258179s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.39142608642578125s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02119588851928711s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.936622619628906e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 1.4543533325195312e-05s
INFO | --- Analysis for national-diet-library-subject-headings took 234.67202353477478s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.1893365383148193s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0006103515625s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.3745548725128174s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.02097606658935547s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.57763671875e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 1.5974044799804688e-05s
INFO | --- Analysis for national-library-of-greece-authority-records took 6.631460428237915s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0001888275146484375s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007944107055664062s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.3292064666748047s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02118062973022461s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0011506080627441406s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.179115295410156e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.4781951904296875e-05s
INFO | --- Analysis for Naturopathy took 3.8656506538391113s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.456359624862671s
Availability | VoID file availability check for COVID-19 Data took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.3470578193664551s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.02100849151611328s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.337860107421875e-05s
Believability | Calculation of trust value for COVID-19 Data took 1.5735626220703125e-05s
INFO | --- Analysis for NCMI-COVID-19 took 8.14751935005188s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.4352378845214844s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.38435888290405273s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.020785808563232422s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.4066696166992188e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 1.5735626220703125e-05s
INFO | --- Analysis for NCMICOVID-19 took 7.084030389785767s
Availability | SPARQL endpoint availability check for Near took 9.465217590332031e-05s
Availability | VoID file availability check for Near took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for Near took 0.3382096290588379s
Reputation | Calculation of the PageRank for Near took 0.02086472511291504s
Interlinking | Calculation of Degree of Connection for Near took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Near took 0.0007987022399902344s
Interlinking | Calculation of Clustering coefficient for Near took 9.703636169433594e-05s
Believability | Calculation of trust value for Near took 1.4781951904296875e-05s
INFO | --- Analysis for near took 8.608376026153564s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 5.173683166503906e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.3374173641204834s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020910978317260742s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.2901763916015625e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.5497207641601562e-05s
INFO | --- Analysis for neurolex-wiki took 3.4976065158843994s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 0.0001010894775390625s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.6752431392669678s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.021114110946655273s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.458427429199219e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 1.4066696166992188e-05s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 4.518356084823608s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 0.00010228157043457031s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.326275110244751s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.022468090057373047s
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.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 7.319450378417969e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 1.1444091796875e-05s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.983928918838501s
Availability | SPARQL endpoint availability check for neXtProt took 2.048321008682251s
Availability | VoID file availability check for neXtProt took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for neXtProt took 0.36543893814086914s
Reputation | Calculation of the PageRank for neXtProt took 0.022874832153320312s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.981590270996094e-05s
Believability | Calculation of trust value for neXtProt took 1.3828277587890625e-05s
INFO | --- Analysis for nextprot took 6.091001510620117s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 5.316734313964844e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007529258728027344s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.36225247383117676s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.02191781997680664s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0009565353393554688s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00012612342834472656s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.52587890625e-05s
INFO | --- Analysis for nextweb-gnoss took 10.085137367248535s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 0.0001785755157470703s
Availability | VoID file availability check for NHS Jargon RDF took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.3263826370239258s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.02126145362854004s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.249282836914062e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 6.9141387939453125e-06s
INFO | --- Analysis for nhs-jargon took 3.5136525630950928s
Availability | SPARQL endpoint availability check for NIT Patna took 0.0002079010009765625s
Availability | VoID file availability check for NIT Patna took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.5347695350646973s
Reputation | Calculation of the PageRank for NIT Patna took 0.021032333374023438s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0008141994476318359s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 7.462501525878906e-05s
Believability | Calculation of trust value for NIT Patna took 1.0251998901367188e-05s
INFO | --- Analysis for NITP took 4.226122856140137s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.649162292480469e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0006346702575683594s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.3658602237701416s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.021114826202392578s
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.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.266334533691406e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 1.6450881958007812e-05s
INFO | --- Analysis for nlr-dataset-mod took 5.458348989486694s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.6311440467834473s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.31885623931884766s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.020921707153320312s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 1.0013580322265625e-05s
INFO | --- Analysis for NLW took 4.640511512756348s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.6216742992401123s
Availability | VoID file availability check for Nobel Prizes took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.3385598659515381s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02092599868774414s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.560585021972656e-05s
Believability | Calculation of trust value for Nobel Prizes took 1.52587890625e-05s
INFO | --- Analysis for nobelprizes took 10.441790580749512s
Availability | SPARQL endpoint availability check for NoiPA took 0.3054320812225342s
Availability | VoID file availability check for NoiPA took 0.0005309581756591797s
Extra | Recovery of all triples for NoiPA took 1.071122407913208s
Performance | Total latancy measurement for NoiPA took 0.48908543586730957s
Amount of data | Number of triples check for NoiPA took 2.346518039703369s
Interoperability | New terms check for NoiPA took 2.7905452251434326s
Versatility | Languages check for NoiPA took 60.14091730117798s
Interpretability | Number of blank nodes check for NoiPA took 0.15444016456604004s
Interpretability | RDF structures check for NoiPA took 0.1718461513519287s
Versatility | Serialization formats check for NoiPA took 0.11975455284118652s
Availability | RDF dump link check for NoiPA took 0.13710689544677734s
License | MR license check for NoiPA took 0.3094940185546875s
License | HR license check for NoiPA took 60.14455246925354s
Amount of data | Number of property check for NoiPA took 0.17783451080322266s
Understandability | Number of label check for NoiPA took 0.5154187679290771s
Understandability | URI regex check for NoiPA took 0.35700154304504395s
Understandability | Vocabs check for NoiPA took 0.12180924415588379s
Verifiability | Authors check for NoiPA took 0.09979462623596191s
Verifiability | Publishers check for NoiPA took 0.1060178279876709s
Performance | Throughput check for NoiPA took 10.624833345413208s
Amount of data | Check the number of entities for NoiPA took 9.632110595703125e-05s
Verifiability | Contribs. check for NoiPA took 0.14699244499206543s
Interlinking | sameAs chians check for NoiPA took 0.12655425071716309s
Interlinking | skos check for NoiPA took 0.49216485023498535s
Interlinking | skos check for NoiPA took 0.10991168022155762s
Timeliness | dataset update frequency check for NoiPA took 0.11441755294799805s
Currency | Creation date check for NoiPA took 0.2317049503326416s
Currency | Modification date check for NoiPA took 0.1236259937286377s
Rep.Conc. | URIs length for NoiPA took 17.77821135520935s
Interoperability | New vocabularies check for NoiPA took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.1484241485595703s
Accuracy | Check Functional Property for NoiPA took 0.17794227600097656s
Accuracy | Check Inverse Functional Property for NoiPA took 0.15848731994628906s
Accuracy | Check Empty annotation labels for NoiPA took 0.3831965923309326s
Accuracy | Check White space in annotation for NoiPA took 0.026419639587402344s
Accuracy | Check Datatype consistency for NoiPA took 0.029369115829467773s
Consistency | Disjoint class check for NoiPA took 0.14609003067016602s
Consistency | Check Misplaced properties for NoiPA took 15.80143666267395s
Consistency | Misplaced classes for NoiPA took 0.20168471336364746s
Consistency | Check Ontology hijacking for NoiPA took 1.6868462562561035s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.3311753273010254s
Consistency | Check Invalid usage of undefined properties for NoiPA took 17.14487075805664s
Conciseness | Check Extensional conciseness for NoiPA took 0.037691593170166016s
Conciseness | Check Intensional conciseness for NoiPA took 0.16307854652404785s
Security | Sign check for NoiPA took 0.12659144401550293s
Availability | Check URIs Dereferenciability for NoiPA took 10.440224647521973s
Completeness | Calculation of interlinking completeness for NoiPA took 0.36822080612182617s
Reputation | Calculation of the PageRank for NoiPA took 0.021509885787963867s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for NoiPA took 4.076957702636719e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 9.5367431640625e-07s
Believability | Calculation of trust value for NoiPA took 1.52587890625e-05s
INFO | --- Analysis for NoiPA took 512.1605079174042s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 1.0350215435028076s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.3412210941314697s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02272939682006836s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.512901306152344e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.4543533325195312e-05s
INFO | --- Analysis for nom took 8.881078481674194s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 24.95293951034546s
Availability | VoID file availability check for Nomenclator Asturias took 0.0008530616760253906s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.3771085739135742s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.021030664443969727s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 9.036064147949219e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 3.4809112548828125e-05s
INFO | --- Analysis for nomenclator-asturias took 136.55703616142273s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.41348981857299805s
Availability | VoID file availability check for Nomisma.org  took 0.0006275177001953125s
Extra | Recovery of all triples for Nomisma.org  took 843.6887245178223s
Performance | Total latancy measurement for Nomisma.org  took 1.6646499633789062s
Amount of data | Number of triples check for Nomisma.org  took 32.76496911048889s
Interoperability | New terms check for Nomisma.org  took 5.642130613327026s
Versatility | Languages check for Nomisma.org  took 95.28019952774048s
Interpretability | Number of blank nodes check for Nomisma.org  took 28.7522234916687s
Security | Check HTTPS for Nomisma.org  took 0.7132766246795654s
Interpretability | RDF structures check for Nomisma.org  took 0.35360264778137207s
Versatility | Serialization formats check for Nomisma.org  took 0.35756564140319824s
Availability | RDF dump link check for Nomisma.org  took 856.2153112888336s
License | MR license check for Nomisma.org  took 0.37089014053344727s
License | HR license check for Nomisma.org  took 58.081198930740356s
Amount of data | Number of property check for Nomisma.org  took 0.3757033348083496s
Understandability | Number of label check for Nomisma.org  took 6.268953084945679s
Understandability | URI regex check for Nomisma.org  took 0.6894538402557373s
Understandability | Vocabs check for Nomisma.org  took 0.32469725608825684s
Verifiability | Authors check for Nomisma.org  took 0.32550668716430664s
Verifiability | Publishers check for Nomisma.org  took 0.3518245220184326s
Performance | Throughput check for Nomisma.org  took 12.098169326782227s
Amount of data | Check the number of entities for Nomisma.org  took 66.9431164264679s
Verifiability | Contribs. check for Nomisma.org  took 0.3558363914489746s
Interlinking | sameAs chians check for Nomisma.org  took 0.34998631477355957s
Interlinking | skos check for Nomisma.org  took 1.0790939331054688s
Interlinking | skos check for Nomisma.org  took 0.4541943073272705s
Timeliness | dataset update frequency check for Nomisma.org  took 0.3115510940551758s
Currency | Creation date check for Nomisma.org  took 0.6960771083831787s
Currency | Modification date check for Nomisma.org  took 0.6820564270019531s
Rep.Conc. | URIs length for Nomisma.org  took 314.49421882629395s
Interoperability | New vocabularies check for Nomisma.org  took 1.2636184692382812e-05s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.34834980964660645s
Accuracy | Check Functional Property for Nomisma.org  took 0.3463013172149658s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.31554651260375977s
Accuracy | Check Empty annotation labels for Nomisma.org  took 263.07835125923157s
Accuracy | Check White space in annotation for Nomisma.org  took 2.761104106903076s
Accuracy | Check Datatype consistency for Nomisma.org  took 5.668058156967163s
Consistency | Disjoint class check for Nomisma.org  took 0.3827955722808838s
Consistency | Check Misplaced properties for Nomisma.org  took 26.727129459381104s
Consistency | Check Ontology hijacking for Nomisma.org  took 280.36539793014526s
Consistency | Check Invalid usage of undefined classes for Nomisma.org  took 2.300729274749756s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 26.190457820892334s
Conciseness | Check Extensional conciseness for Nomisma.org  took 2.887932777404785s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.3744316101074219s
Security | Sign check for Nomisma.org  took 0.33886289596557617s
Availability | Check URIs Dereferenciability for Nomisma.org  took 1963.5944194793701s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 0.4727509021759033s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.023677825927734375s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 6.4849853515625e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 0.00013136863708496094s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 2.1457672119140625e-06s
Believability | Calculation of trust value for Nomisma.org  took 6.222724914550781e-05s
INFO | --- Analysis for nomisma_org took 8051.555697441101s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.3720417022705078s
Availability | VoID file availability check for Curriculum Vitae took 0.0005772113800048828s
Extra | Recovery of all triples for Curriculum Vitae took 0.7254769802093506s
Performance | Total latancy measurement for Curriculum Vitae took 0.9407000541687012s
Amount of data | Number of triples check for Curriculum Vitae took 0.16604185104370117s
Interoperability | New terms check for Curriculum Vitae took 1.8054440021514893s
Versatility | Languages check for Curriculum Vitae took 0.25719451904296875s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.23108720779418945s
Interpretability | RDF structures check for Curriculum Vitae took 0.14693593978881836s
Versatility | Serialization formats check for Curriculum Vitae took 0.14651179313659668s
Availability | RDF dump link check for Curriculum Vitae took 0.12815141677856445s
License | MR license check for Curriculum Vitae took 0.11887907981872559s
License | HR license check for Curriculum Vitae took 0.26697421073913574s
Amount of data | Number of property check for Curriculum Vitae took 0.16669106483459473s
Understandability | Number of label check for Curriculum Vitae took 0.2664520740509033s
Understandability | URI regex check for Curriculum Vitae took 0.3177757263183594s
Understandability | Vocabs check for Curriculum Vitae took 0.20972204208374023s
Verifiability | Authors check for Curriculum Vitae took 0.22441315650939941s
Verifiability | Publishers check for Curriculum Vitae took 0.1498420238494873s
Performance | Throughput check for Curriculum Vitae took 10.698612213134766s
Amount of data | Check the number of entities for Curriculum Vitae took 3.647804260253906e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.17057323455810547s
Interlinking | sameAs chians check for Curriculum Vitae took 0.12452983856201172s
Interlinking | skos check for Curriculum Vitae took 0.13424444198608398s
Interlinking | skos check for Curriculum Vitae took 0.14736723899841309s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.11598587036132812s
Currency | Creation date check for Curriculum Vitae took 0.2863280773162842s
Currency | Modification date check for Curriculum Vitae took 0.24145102500915527s
Rep.Conc. | URIs length for Curriculum Vitae took 0.34679532051086426s
Interoperability | New vocabularies check for Curriculum Vitae took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.12701845169067383s
Accuracy | Check Functional Property for Curriculum Vitae took 0.1393566131591797s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.13880538940429688s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.11760234832763672s
Accuracy | Check White space in annotation for Curriculum Vitae took 8.082389831542969e-05s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.0018427371978759766s
Consistency | Disjoint class check for Curriculum Vitae took 0.1188058853149414s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.3072049617767334s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.8311686515808105s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.7962698936462402s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.9587361812591553s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0016512870788574219s
Security | Sign check for Curriculum Vitae took 0.12471914291381836s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 19.503882884979248s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.36493659019470215s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.021016597747802734s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 3.4332275390625e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.430511474609375e-06s
Believability | Calculation of trust value for Curriculum Vitae took 1.1205673217773438e-05s
INFO | --- Analysis for Nordine_Bittich took 60.17689633369446s
Availability | SPARQL endpoint availability check for NorPark took 0.17600464820861816s
Availability | VoID file availability check for NorPark took 0.0007450580596923828s
Completeness | Calculation of interlinking completeness for NorPark took 0.382354736328125s
Reputation | Calculation of the PageRank for NorPark took 0.02245640754699707s
Interlinking | Calculation of Degree of Connection for NorPark took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.506111145019531e-05s
Believability | Calculation of trust value for NorPark took 1.5497207641601562e-05s
INFO | --- Analysis for norpark took 3.6499757766723633s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.02456974983215332s
Availability | VoID file availability check for Parking Dataset took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.324462890625s
Reputation | Calculation of the PageRank for Parking Dataset took 0.022683143615722656s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 5.1021575927734375e-05s
Believability | Calculation of trust value for Parking Dataset took 1.7642974853515625e-05s
INFO | --- Analysis for norpark2 took 3.4339101314544678s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.5791308879852295s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0005059242248535156s
Extra | Recovery of all triples for Norway fishery stocks dataset took 111.04848146438599s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.9466345310211182s
Amount of data | Number of triples check for Norway fishery stocks dataset took 8.938492059707642s
Interoperability | New terms check for Norway fishery stocks dataset took 14.427720546722412s
Versatility | Languages check for Norway fishery stocks dataset took 300.2133746147156s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 2.238537073135376s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.2984626293182373s
Versatility | Serialization formats check for Norway fishery stocks dataset took 9.889985799789429s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.3427455425262451s
License | MR license check for Norway fishery stocks dataset took 0.7567315101623535s
License | HR license check for Norway fishery stocks dataset took 300.2306215763092s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.20064949989318848s
Understandability | Number of label check for Norway fishery stocks dataset took 2.6968955993652344s
Understandability | URI regex check for Norway fishery stocks dataset took 1.0511765480041504s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.6014671325683594s
Verifiability | Authors check for Norway fishery stocks dataset took 0.21723198890686035s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.24988818168640137s
Performance | Throughput check for Norway fishery stocks dataset took 11.313042402267456s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 0.00015997886657714844s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.2110147476196289s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.21866631507873535s
Interlinking | skos check for Norway fishery stocks dataset took 0.4913647174835205s
Interlinking | skos check for Norway fishery stocks dataset took 0.42219018936157227s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 5.977535724639893s
Currency | Creation date check for Norway fishery stocks dataset took 0.45950913429260254s
Currency | Modification date check for Norway fishery stocks dataset took 0.25153470039367676s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 154.22327423095703s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.17641258239746094s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.4009878635406494s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.3956477642059326s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 38.55137920379639s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.684065818786621s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.838982582092285s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.17971014976501465s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 86.5143358707428s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.725446939468384s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 33.42319464683533s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.512848138809204s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 87.32256507873535s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.783278465270996s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.5357954502105713s
Security | Sign check for Norway fishery stocks dataset took 1.080228567123413s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 10.20654821395874s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.37923288345336914s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.021636247634887695s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0010209083557128906s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 5.14984130859375e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 2.6226043701171875e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 1.4781951904296875e-05s
INFO | --- Analysis for Norway_Fishery_ took 2286.102106332779s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.483212947845459s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0008370876312255859s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.3615908622741699s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.021016597747802734s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 5.2928924560546875e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.0013580322265625e-05s
INFO | --- Analysis for norwegian-geo-divisions took 5.011382818222046s
Availability | SPARQL endpoint availability check for NITP took 0.0001735687255859375s
Availability | VoID file availability check for NITP took 0.0008413791656494141s
Completeness | Calculation of interlinking completeness for NITP took 0.34963107109069824s
Reputation | Calculation of the PageRank for NITP took 0.021088838577270508s
Interlinking | Calculation of Degree of Connection for NITP took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for NITP took 7.152557373046875e-05s
Believability | Calculation of trust value for NITP took 1.4781951904296875e-05s
INFO | --- Analysis for notIdentifier took 4.179654836654663s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 0.0001068115234375s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.3224983215332031s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.021475791931152344s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.6716461181640625e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 1.4781951904296875e-05s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 4.021115303039551s
Availability | SPARQL endpoint availability check for NPM took 4.935264587402344e-05s
Availability | VoID file availability check for NPM took 0.0008180141448974609s
Completeness | Calculation of interlinking completeness for NPM took 0.3180811405181885s
Reputation | Calculation of the PageRank for NPM took 0.02095818519592285s
Interlinking | Calculation of Degree of Connection for NPM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for NPM took 3.600120544433594e-05s
Believability | Calculation of trust value for NPM took 1.2636184692382812e-05s
INFO | --- Analysis for npm took 4.861157655715942s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.025072813034057617s
Availability | VoID file availability check for NTNU special collections took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.3181800842285156s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020727872848510742s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 6.031990051269531e-05s
Believability | Calculation of trust value for NTNU special collections took 9.5367431640625e-06s
INFO | --- Analysis for ntnusc took 6.347266435623169s
Availability | SPARQL endpoint availability check for links took 0.0001227855682373047s
Availability | VoID file availability check for links took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for links took 0.38423776626586914s
Reputation | Calculation of the PageRank for links took 0.020859479904174805s
Interlinking | Calculation of Degree of Connection for links took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for links took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for links took 1.2874603271484375e-05s
Believability | Calculation of trust value for links took 1.430511474609375e-05s
INFO | --- Analysis for nugmyanmar took 3.2593934535980225s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 0.00011205673217773438s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0007312297821044922s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.3407120704650879s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.020940065383911133s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 0.00011301040649414062s
Believability | Calculation of trust value for NUTS (GeoVocab) took 1.239776611328125e-05s
INFO | --- Analysis for nuts-geovocab took 3.584589719772339s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.47110915184020996s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0007097721099853516s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.35473203659057617s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.021419763565063477s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0008101463317871094s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 7.414817810058594e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 1.6689300537109375e-05s
INFO | --- Analysis for nvd took 4.981518507003784s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.8631844520568848s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.357022762298584s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.02291560173034668s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.559226989746094e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.4543533325195312e-05s
INFO | --- Analysis for nvs took 9.882855415344238s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.8160552978515625e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.37679338455200195s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.021042585372924805s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00018906593322753906s
Believability | Calculation of trust value for New York Times - Linked Open Data took 1.52587890625e-05s
INFO | --- Analysis for nytimes-linked-open-data took 3.2707293033599854s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.7309684753417969s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0006546974182128906s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.4540107250213623s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.9889910221099854s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 2.691089630126953s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.8323211669921875s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 58.260374307632446s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.8140249252319336s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.34305596351623535s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.3938908576965332s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.505122184753418s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.499406099319458s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.35387325286865234s
License | HR license check for Italian Chamber of Deputies - official dataset took 58.2226037979126s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.3884444236755371s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.533013105392456s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.7589600086212158s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.48027682304382324s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.383594274520874s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.39362478256225586s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 11.391937971115112s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 7.033348083496094e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.38851094245910645s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.3914985656738281s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.4005570411682129s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.3987152576446533s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.41981053352355957s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.6878764629364014s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.3901946544647217s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 16.921090841293335s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.41183900833129883s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.3791537284851074s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.360260009765625s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.8349158763885498s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.023868322372436523s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.02967548370361328s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.3945796489715576s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 12.71272349357605s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.4489421844482422s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.3039958477020264s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.3234875202178955s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 13.743515491485596s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.033402204513549805s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.4312281608581543s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.39896464347839355s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 9.849952220916748s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 1.0368099212646484s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.021089553833007812s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00010609626770019531s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 2.384185791015625e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 1.0967254638671875e-05s
INFO | --- Analysis for ocd took 399.66301798820496s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 0.00010418891906738281s
Availability | VoID file availability check for oceandrilling-borehole took 0.0008819103240966797s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.31224679946899414s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.021108388900756836s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.001047372817993164s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 5.745887756347656e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.5974044799804688e-05s
INFO | --- Analysis for oceandrilling-borehole took 4.449874401092529s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 3.353816032409668s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0008623600006103516s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.42671656608581543s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.022427082061767578s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.320808410644531e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 2.0742416381835938e-05s
INFO | --- Analysis for oceandrilling-codices took 10.798892974853516s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 3.0776662826538086s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.38660168647766113s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.0209197998046875s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.600120544433594e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.5020370483398438e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 8.547194480895996s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 3.2250261306762695s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0009326934814453125s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.3429865837097168s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.4332275390625e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.3113021850585938e-05s
INFO | --- Analysis for oceandrilling-forams took 8.823558330535889s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 3.370816946029663s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0008471012115478516s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.36478400230407715s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020670175552368164s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.647804260253906e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.4066696166992188e-05s
INFO | --- Analysis for oceandrilling-janus took 8.977001905441284s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 12.524746656417847s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0008788108825683594s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.39022135734558105s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020760536193847656s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.552436828613281e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.52587890625e-05s
INFO | --- Analysis for oceandrilling-janusamp took 18.08168053627014s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.811140775680542s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0008807182312011719s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.36621785163879395s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.020918846130371094s
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.0008718967437744141s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.409385681152344e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.0251998901367188e-05s
INFO | --- Analysis for oceandrilling-ldeo took 8.120750427246094s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 5.14984130859375e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.4197263717651367s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.02091503143310547s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.91278076171875e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.5974044799804688e-05s
INFO | --- Analysis for oclc-fast took 10.284408569335938s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.00011324882507324219s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.33564305305480957s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.022794723510742188s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.24249267578125e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.0728836059570312e-05s
INFO | --- Analysis for odc-imd-environment-score took 6.528989791870117s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.2113192081451416s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0008647441864013672s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 0.9805903434753418s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 1.4109015464782715s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.20025396347045898s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.6450185775756836s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.44039201736450195s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 30.171996116638184s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.09368348121643066s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.21895432472229004s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.21759414672851562s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 51.29159450531006s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.13300442695617676s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 30.245556592941284s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.22080039978027344s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.22510433197021484s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.37296104431152344s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.21255993843078613s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.22950315475463867s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.1495957374572754s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 11.555198669433594s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 7.772445678710938e-05s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.200697660446167s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.22229576110839844s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.22394061088562012s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.22049283981323242s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.2084972858428955s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.894033670425415s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.14449763298034668s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 1.2690038681030273s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.21881723403930664s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.21201491355895996s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.21831989288330078s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.15232157707214355s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.3970799446105957s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 1.835789442062378s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.5936458110809326s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.0001804828643798828s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.5131001472473145s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.13037848472595215s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.6265928745269775s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.020932674407958984s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 5.030632019042969e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 1.0728836059570312e-05s
INFO | --- Analysis for odc-lsoa took 283.1539957523346s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.10115957260131836s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.35575151443481445s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.02258610725402832s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.894371032714844e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for oecd-linked-data took 3.3528385162353516s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.249298810958862s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.3592565059661865s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.021352291107177734s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.38690185546875e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 1.0013580322265625e-05s
INFO | --- Analysis for ogolod took 103.41844820976257s
Availability | SPARQL endpoint availability check for OLAC Metadata took 0.00011181831359863281s
Availability | VoID file availability check for OLAC Metadata took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.33864855766296387s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.02129077911376953s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 3.933906555175781e-05s
Believability | Calculation of trust value for OLAC Metadata took 1.4781951904296875e-05s
INFO | --- Analysis for olac took 23.623733520507812s
Availability | SPARQL endpoint availability check for OLiA took 0.00011491775512695312s
Availability | VoID file availability check for OLiA took 0.00135040283203125s
Completeness | Calculation of interlinking completeness for OLiA took 0.32079577445983887s
Reputation | Calculation of the PageRank for OLiA took 0.02231621742248535s
Interlinking | Calculation of Degree of Connection for OLiA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00012445449829101562s
Believability | Calculation of trust value for OLiA took 1.1682510375976562e-05s
INFO | --- Analysis for olia took 14.616707563400269s
Availability | SPARQL endpoint availability check for OLiA Discourse took 0.0001361370086669922s
Availability | VoID file availability check for OLiA Discourse took 0.0009179115295410156s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.4184408187866211s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020811796188354492s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.076957702636719e-05s
Believability | Calculation of trust value for OLiA Discourse took 1.239776611328125e-05s
INFO | --- Analysis for olia-discourse took 8.04714822769165s
Availability | SPARQL endpoint availability check for Open Land Use took 0.18065953254699707s
Availability | VoID file availability check for Open Land Use took 0.0004987716674804688s
Extra | Recovery of all triples for Open Land Use took 116.38794374465942s
Performance | Total latancy measurement for Open Land Use took 0.9371404647827148s
Amount of data | Number of triples check for Open Land Use took 8.86516261100769s
Interoperability | New terms check for Open Land Use took 14.420856237411499s
Versatility | Languages check for Open Land Use took 300.20901918411255s
Interpretability | Number of blank nodes check for Open Land Use took 2.0869152545928955s
Interpretability | RDF structures check for Open Land Use took 0.30787062644958496s
Versatility | Serialization formats check for Open Land Use took 9.685287714004517s
Availability | RDF dump link check for Open Land Use took 0.3289628028869629s
License | MR license check for Open Land Use took 0.8501121997833252s
License | HR license check for Open Land Use took 300.2191879749298s
Amount of data | Number of property check for Open Land Use took 0.21039509773254395s
Understandability | Number of label check for Open Land Use took 2.6098756790161133s
Understandability | URI regex check for Open Land Use took 0.9987318515777588s
Understandability | Vocabs check for Open Land Use took 0.5555708408355713s
Verifiability | Authors check for Open Land Use took 0.21353650093078613s
Verifiability | Publishers check for Open Land Use took 0.2622411251068115s
Performance | Throughput check for Open Land Use took 11.462396383285522s
Amount of data | Check the number of entities for Open Land Use took 0.00010371208190917969s
Verifiability | Contribs. check for Open Land Use took 0.18508219718933105s
Interlinking | sameAs chians check for Open Land Use took 0.2181410789489746s
Interlinking | skos check for Open Land Use took 0.47289180755615234s
Interlinking | skos check for Open Land Use took 0.40997886657714844s
Timeliness | dataset update frequency check for Open Land Use took 5.225952625274658s
Currency | Creation date check for Open Land Use took 0.4584064483642578s
Currency | Modification date check for Open Land Use took 0.23969435691833496s
Rep.Conc. | URIs length for Open Land Use took 151.00250101089478s
Interoperability | New vocabularies check for Open Land Use took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.201019287109375s
Accuracy | Check Functional Property for Open Land Use took 0.4061107635498047s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.3992743492126465s
Accuracy | Check Empty annotation labels for Open Land Use took 40.68658185005188s
Accuracy | Check White space in annotation for Open Land Use took 2.687204599380493s
Accuracy | Check Datatype consistency for Open Land Use took 2.8727147579193115s
Consistency | Disjoint class check for Open Land Use took 0.19753289222717285s
Consistency | Check Misplaced properties for Open Land Use took 86.54681015014648s
Consistency | Misplaced classes for Open Land Use took 8.46979570388794s
Consistency | Check Ontology hijacking for Open Land Use took 34.77908539772034s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.5076584815979004s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 86.92448282241821s
Conciseness | Check Extensional conciseness for Open Land Use took 2.8531382083892822s
Conciseness | Check Intensional conciseness for Open Land Use took 0.5814135074615479s
Security | Sign check for Open Land Use took 0.18070340156555176s
Availability | Check URIs Dereferenciability for Open Land Use took 10.19301438331604s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.6597707271575928s
Reputation | Calculation of the PageRank for Open Land Use took 0.02157139778137207s
Interlinking | Calculation of Degree of Connection for Open Land Use took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 4.1484832763671875e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 2.384185791015625e-06s
Believability | Calculation of trust value for Open Land Use took 1.5020370483398438e-05s
INFO | --- Analysis for OLU took 2285.671005964279s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 1.508533000946045s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.3670060634613037s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.02120804786682129s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 1.5497207641601562e-05s
INFO | --- Analysis for omwn-als took 5.247306823730469s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.27248477935791016s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.3322560787200928s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.021086454391479492s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0008447170257568359s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 4.1961669921875e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 1.52587890625e-05s
INFO | --- Analysis for omwn-arb took 3.9635603427886963s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.2933945655822754s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.33229708671569824s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.021082162857055664s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0009620189666748047s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 4.792213439941406e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.5735626220703125e-05s
INFO | --- Analysis for omwn-bul took 3.795992374420166s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.25640249252319336s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.3168060779571533s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.023508310317993164s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.5497207641601562e-05s
INFO | --- Analysis for omwn-cow took 4.00397801399231s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.25624704360961914s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.36292505264282227s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0206453800201416s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007314682006835938s
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.5735626220703125e-05s
INFO | --- Analysis for omwn-cwn took 3.7831649780273438s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.2809891700744629s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.33795619010925293s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.020961999893188477s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 1.5497207641601562e-05s
INFO | --- Analysis for omwn-dan took 3.8836750984191895s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.25431084632873535s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.34228086471557617s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.022500276565551758s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0008068084716796875s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 4.172325134277344e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.5497207641601562e-05s
INFO | --- Analysis for omwn-ell took 3.753999948501587s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2519805431365967s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.30959153175354004s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.020937442779541016s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 1.5735626220703125e-05s
INFO | --- Analysis for omwn-eng took 3.7237393856048584s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.27013707160949707s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.3748595714569092s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.022407054901123047s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 1.5020370483398438e-05s
INFO | --- Analysis for omwn-fas took 3.938295602798462s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.25122714042663574s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.35213255882263184s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.022132396697998047s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0013544559478759766s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 5.91278076171875e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.6450881958007812e-05s
INFO | --- Analysis for omwn-fin took 4.292407751083374s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.23034334182739258s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.3769845962524414s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.02149033546447754s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 4.00543212890625e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-fra took 3.795649528503418s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.22499680519104004s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.33250999450683594s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.02093672752380371s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007536411285400391s
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.621246337890625e-05s
INFO | --- Analysis for omwn-heb took 3.7494051456451416s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2319197654724121s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.31517553329467773s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.020978689193725586s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 4.172325134277344e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 1.4543533325195312e-05s
INFO | --- Analysis for omwn-hrv took 3.7398924827575684s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.28432178497314453s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.3575015068054199s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.020757436752319336s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 4.673004150390625e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.621246337890625e-05s
INFO | --- Analysis for omwn-isl took 5.183641672134399s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.26158928871154785s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.452258825302124s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.02058267593383789s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.4781951904296875e-05s
INFO | --- Analysis for omwn-ita took 4.0002148151397705s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.27131175994873047s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.37700390815734863s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.02108001708984375s
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.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 2.574920654296875e-05s
INFO | --- Analysis for omwn-iwn took 3.729562282562256s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.283888578414917s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.3467702865600586s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.020977497100830078s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.52587890625e-05s
INFO | --- Analysis for omwn-jpn took 3.8493332862854004s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.26129984855651855s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.3740251064300537s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.020560503005981445s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.4543533325195312e-05s
INFO | --- Analysis for omwn-mcr took 3.7526869773864746s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.23671960830688477s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.3386857509613037s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.020879745483398438s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.52587890625e-05s
INFO | --- Analysis for omwn-msa took 3.6924617290496826s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.263202428817749s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.3310568332672119s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.024942874908447266s
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.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 4.1961669921875e-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.996363401412964s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.26402974128723145s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.31615734100341797s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.02111506462097168s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-nor took 4.370095252990723s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2655324935913086s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2911720275878906s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020818471908569336s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.5020370483398438e-05s
INFO | --- Analysis for omwn-pol took 3.848198175430298s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.24048137664794922s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.32937049865722656s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.02221846580505371s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.4066696166992188e-05s
INFO | --- Analysis for omwn-por took 3.7517120838165283s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2571852207183838s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.37229204177856445s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.02076125144958496s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-ron took 3.7233340740203857s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2500264644622803s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.3463726043701172s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.021326780319213867s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 1.5020370483398438e-05s
INFO | --- Analysis for omwn-slk took 3.9656827449798584s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.2784140110015869s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.3395993709564209s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020740509033203125s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.4066696166992188e-05s
INFO | --- Analysis for omwn-slv took 4.00120210647583s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.24352693557739258s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.3269379138946533s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.021084308624267578s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.52587890625e-05s
INFO | --- Analysis for omwn-swe took 3.8027594089508057s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.255845308303833s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.35170531272888184s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.02225184440612793s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-tha took 3.9715821743011475s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 5.0196356773376465s
Availability | VoID file availability check for OntoBeef Domain took 0.0007436275482177734s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.37412381172180176s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 5.3882598876953125e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.52587890625e-05s
INFO | --- Analysis for ontobeef-domain took 30.056978464126587s
Availability | SPARQL endpoint availability check for Ontos News Portal took 5.1975250244140625e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.3534514904022217s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.1552734375e-05s
Believability | Calculation of trust value for Ontos News Portal took 1.3589859008789062e-05s
INFO | --- Analysis for ontos-news-portal took 14.092536687850952s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 0.00011110305786132812s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.3619377613067627s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.02068495750427246s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.24249267578125e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 1.4543533325195312e-05s
INFO | --- Analysis for ookaboo-rdf-dump took 3.2831497192382812s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 5.91278076171875e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.32392072677612305s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.020817041397094727s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.886222839355469e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 1.52587890625e-05s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 11.377198457717896s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 0.0001125335693359375s
Availability | VoID file availability check for Open Data Euskadi took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.3591599464416504s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.021671295166015625s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.887580871582031e-05s
Believability | Calculation of trust value for Open Data Euskadi took 9.5367431640625e-06s
INFO | --- Analysis for open-data-euskadi took 8.763638734817505s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 0.00012540817260742188s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0007987022399902344s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.32663440704345703s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.020972728729248047s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010561943054199219s
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 6.960909366607666s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.204864501953125s
Availability | VoID file availability check for Open Data Thesaurus took 0.0006959438323974609s
Extra | Recovery of all triples for Open Data Thesaurus took 1.116166353225708s
Performance | Total latancy measurement for Open Data Thesaurus took 0.4486057758331299s
Amount of data | Number of triples check for Open Data Thesaurus took 0.11116647720336914s
Interoperability | New terms check for Open Data Thesaurus took 1.428407907485962s
Versatility | Languages check for Open Data Thesaurus took 0.11656665802001953s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.12320971488952637s
Security | Check HTTPS for Open Data Thesaurus took 0.31806087493896484s
Interpretability | RDF structures check for Open Data Thesaurus took 0.13053631782531738s
Versatility | Serialization formats check for Open Data Thesaurus took 0.11043000221252441s
Availability | RDF dump link check for Open Data Thesaurus took 1.0703034400939941s
License | MR license check for Open Data Thesaurus took 0.11956787109375s
License | HR license check for Open Data Thesaurus took 0.09705233573913574s
Amount of data | Number of property check for Open Data Thesaurus took 0.12588214874267578s
Understandability | Number of label check for Open Data Thesaurus took 0.12355852127075195s
Understandability | URI regex check for Open Data Thesaurus took 0.19338607788085938s
Understandability | Vocabs check for Open Data Thesaurus took 0.12452054023742676s
Verifiability | Authors check for Open Data Thesaurus took 0.11882185935974121s
Verifiability | Publishers check for Open Data Thesaurus took 0.11161661148071289s
Performance | Throughput check for Open Data Thesaurus took 10.518784046173096s
Amount of data | Check the number of entities for Open Data Thesaurus took 6.890296936035156e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.12433671951293945s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.10936689376831055s
Interlinking | skos check for Open Data Thesaurus took 0.12860560417175293s
Interlinking | skos check for Open Data Thesaurus took 0.09888529777526855s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.09038925170898438s
Currency | Creation date check for Open Data Thesaurus took 0.1695239543914795s
Currency | Modification date check for Open Data Thesaurus took 0.2045280933380127s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.4388399124145508s
Interoperability | New vocabularies check for Open Data Thesaurus took 1.526792049407959s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.12469744682312012s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.0873405933380127s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.08574247360229492s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.1853780746459961s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011317729949951172s
Consistency | Disjoint class check for Open Data Thesaurus took 0.08728146553039551s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.18781256675720215s
Consistency | Misplaced classes for Open Data Thesaurus took 0.07998275756835938s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.4899494647979736s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.3995170593261719s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.0001544952392578125s
Security | Sign check for Open Data Thesaurus took 0.0947117805480957s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.325089693069458s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.021402835845947266s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.225440979003906e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 1.4102287292480469s
Believability | Calculation of trust value for Open Data Thesaurus took 1.4066696166992188e-05s
INFO | --- Analysis for open-data-thesaurus took 75.09000587463379s
Availability | SPARQL endpoint availability check for Open Election Data Project took 0.00010228157043457031s
Availability | VoID file availability check for Open Election Data Project took 0.0007746219635009766s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.44002413749694824s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.02158665657043457s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 3.218650817871094e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 7.390975952148438e-05s
Believability | Calculation of trust value for Open Election Data Project took 1.049041748046875e-05s
INFO | --- Analysis for open-election-data-project took 43.4907648563385s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.921959638595581s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0008025169372558594s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.3443796634674072s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02109050750732422s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0009012222290039062s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 0.00010132789611816406s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 1.049041748046875e-05s
INFO | --- Analysis for open-energy-info-wiki took 14.403072357177734s
Availability | SPARQL endpoint availability check for Open Library took 5.14984130859375e-05s
Availability | VoID file availability check for Open Library took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for Open Library took 0.31804847717285156s
Reputation | Calculation of the PageRank for Open Library took 0.021224021911621094s
Interlinking | Calculation of Degree of Connection for Open Library took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0008225440979003906s
Interlinking | Calculation of Clustering coefficient for Open Library took 7.748603820800781e-05s
Believability | Calculation of trust value for Open Library took 1.4543533325195312e-05s
INFO | --- Analysis for open-library took 10.34657907485962s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.18438148498535156s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0005190372467041016s
Extra | Recovery of all triples for Open Land Use @PSNC took 113.7682204246521s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.9855690002441406s
Amount of data | Number of triples check for Open Land Use @PSNC took 8.973969221115112s
Interoperability | New terms check for Open Land Use @PSNC took 14.297691822052002s
Versatility | Languages check for Open Land Use @PSNC took 300.20234847068787s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 2.1474344730377197s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.324127197265625s
Versatility | Serialization formats check for Open Land Use @PSNC took 6.816622018814087s
Availability | RDF dump link check for Open Land Use @PSNC took 0.33667922019958496s
License | MR license check for Open Land Use @PSNC took 0.8384478092193604s
License | HR license check for Open Land Use @PSNC took 300.2491912841797s
Amount of data | Number of property check for Open Land Use @PSNC took 0.2082507610321045s
Understandability | Number of label check for Open Land Use @PSNC took 1.476304054260254s
Understandability | URI regex check for Open Land Use @PSNC took 0.700615406036377s
Understandability | Vocabs check for Open Land Use @PSNC took 0.5865812301635742s
Verifiability | Authors check for Open Land Use @PSNC took 0.19312334060668945s
Verifiability | Publishers check for Open Land Use @PSNC took 0.22980952262878418s
Performance | Throughput check for Open Land Use @PSNC took 11.498539924621582s
Amount of data | Check the number of entities for Open Land Use @PSNC took 8.511543273925781e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.21745729446411133s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.214188814163208s
Interlinking | skos check for Open Land Use @PSNC took 0.43300890922546387s
Interlinking | skos check for Open Land Use @PSNC took 0.40410518646240234s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 4.349116802215576s
Currency | Creation date check for Open Land Use @PSNC took 0.4728410243988037s
Currency | Modification date check for Open Land Use @PSNC took 0.2232203483581543s
Rep.Conc. | URIs length for Open Land Use @PSNC took 152.5570888519287s
Interoperability | New vocabularies check for Open Land Use @PSNC took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.21549010276794434s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.4286682605743408s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.4211246967315674s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 42.27144241333008s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.6957406997680664s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.769763469696045s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.19352126121520996s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 86.8246660232544s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.588602781295776s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 32.96744155883789s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.5147738456726074s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 88.48971629142761s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.8413939476013184s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.5946760177612305s
Security | Sign check for Open Land Use @PSNC took 0.19421815872192383s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 10.033328533172607s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.4889335632324219s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.021721839904785156s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 6.29425048828125e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 2.6226043701171875e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.430511474609375e-05s
INFO | --- Analysis for Open_Land_Use took 2288.249940633774s
Availability | SPARQL endpoint availability check for flyatlas took 3.1786839962005615s
Availability | VoID file availability check for flyatlas took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for flyatlas took 0.3579676151275635s
Reputation | Calculation of the PageRank for flyatlas took 0.020979881286621094s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.743171691894531e-05s
Believability | Calculation of trust value for flyatlas took 1.7404556274414062e-05s
INFO | --- Analysis for openbiomed-flyatlas took 8.098525285720825s
Availability | SPARQL endpoint availability check for OpenCalais took 5.173683166503906e-05s
Availability | VoID file availability check for OpenCalais took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.337970495223999s
Reputation | Calculation of the PageRank for OpenCalais took 0.02169060707092285s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00012111663818359375s
Believability | Calculation of trust value for OpenCalais took 1.430511474609375e-05s
INFO | --- Analysis for opencalais took 6.9270007610321045s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 5.125999450683594e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0008552074432373047s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.31223177909851074s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.022635221481323242s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 8.273124694824219e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 1.0967254638671875e-05s
INFO | --- Analysis for opencorporates took 3.5804946422576904s
Availability | SPARQL endpoint availability check for OpenCyc took 5.221366882324219e-05s
Availability | VoID file availability check for OpenCyc took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.3333091735839844s
Reputation | Calculation of the PageRank for OpenCyc took 0.021024465560913086s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00011229515075683594s
Believability | Calculation of trust value for OpenCyc took 1.52587890625e-05s
INFO | --- Analysis for opencyc took 3.3520405292510986s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 0.00013113021850585938s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.3240821361541748s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.02157139778137207s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 9.5367431640625e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 5.084827184677124s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 5.269050598144531e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.3581411838531494s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.021043062210083008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 1.5497207641601562e-05s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 4.8721771240234375s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 5.078315734863281e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.3616492748260498s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.020979642868041992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0008459091186523438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.9961695671081543s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 5.1021575927734375e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.3649027347564697s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.02118706703186035s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-households-2008 took 3.2831175327301025s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 5.555152893066406e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.36664390563964844s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020905256271362305s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 4.170267581939697s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 0.00015544891357421875s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.3565034866333008s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.021117687225341797s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 6.6066155433654785s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 0.00010156631469726562s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.5092756748199463s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.021877288818359375s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 4.940221548080444s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.00011706352233886719s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.3583669662475586s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020881175994873047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.166513442993164s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 5.0067901611328125e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0008060932159423828s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.6468427181243896s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020923614501953125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 6.631662607192993s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 9.894371032714844e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.352886438369751s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.021159648895263672s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.5497207641601562e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 3.948777198791504s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 5.412101745605469e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.000637054443359375s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.3500499725341797s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.021605491638183594s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 4.819005012512207s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 0.0001049041748046875s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0007436275482177734s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.3435955047607422s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.02139902114868164s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 3.970491409301758s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 7.82012939453125e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.34364891052246094s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.020685434341430664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 1.52587890625e-05s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 4.588406324386597s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 5.984306335449219e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.35087037086486816s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.0211789608001709s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 1.52587890625e-05s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 3.230121374130249s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 0.00010633468627929688s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0007278919219970703s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.32875990867614746s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.022492647171020508s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 1.5735626220703125e-05s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 4.996076822280884s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.00018453598022460938s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.3179178237915039s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.021145343780517578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 1.5974044799804688e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 4.007754564285278s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 5.1975250244140625e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.33920860290527344s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.020839929580688477s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.5020370483398438e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.134886980056763s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 0.00019073486328125s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0007300376892089844s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.3534996509552002s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.021729230880737305s
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.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.5497207641601562e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 4.443580150604248s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 9.822845458984375e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.3805887699127197s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.020799875259399414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 1.52587890625e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 3.2068967819213867s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.00010609626770019531s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007801055908203125s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.29050230979919434s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.021561861038208008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.52587890625e-05s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.240604639053345s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 0.00012159347534179688s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0007741451263427734s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.3468794822692871s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.021126508712768555s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 4.0896735191345215s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 0.00010895729064941406s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.34905338287353516s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020771026611328125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.5497207641601562e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 4.931273698806763s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 5.1975250244140625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007824897766113281s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.3624534606933594s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020688295364379883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.5497207641601562e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.5765910148620605s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.00010228157043457031s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.39667415618896484s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0209348201751709s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.6689300537109375e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.916748046875s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 5.245208740234375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007290840148925781s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.7472882270812988s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.02283310890197754s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.57763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.696516990661621s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 5.340576171875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007460117340087891s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.36279726028442383s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.02077794075012207s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.4543533325195312e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.827742099761963s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.00011849403381347656s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.33943653106689453s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.020803213119506836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.327261447906494s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.00010347366333007812s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.37284016609191895s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.021369457244873047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.5974044799804688e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.932981729507446s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 6.437301635742188e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.4142782688140869s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.020872831344604492s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.960057735443115s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 8.511543273925781e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.35468029975891113s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.021055221557617188s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.5974044799804688e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.525009393692017s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 5.269050598144531e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.3401169776916504s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.023333072662353516s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0008182525634765625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.70834493637085s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.00010156631469726562s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007905960083007812s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.38954758644104004s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.022345542907714844s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 5.030632019042969e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.5497207641601562e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.875331163406372s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0001850128173828125s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0009381771087646484s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.3368113040924072s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.022585153579711914s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.9114227294921875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.52587890625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.392239809036255s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.221366882324219e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.000274658203125s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.3736732006072998s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.021778583526611328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 6.0558319091796875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 9.775161743164062e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 3.2948789596557617s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 5.4836273193359375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.36098313331604004s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.021187305450439453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.000804901123046875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.6450881958007812e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 3.4676764011383057s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 9.298324584960938e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007288455963134766s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.3775057792663574s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.021103382110595703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.76837158203125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 1.52587890625e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 4.747488737106323s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.00010204315185546875s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007236003875732422s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.3774404525756836s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.021329164505004883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.52587890625e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.225660085678101s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.00011134147644042969s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.001354217529296875s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.3678581714630127s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.023089170455932617s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 1.6689300537109375e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 5.046895265579224s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 5.269050598144531e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0003864765167236328s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.3233780860900879s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.021075725555419922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.649162292480469e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.006886005401611s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 5.364418029785156e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.3484795093536377s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.021358728408813477s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.792213439941406e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.1999287605285645s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 9.870529174804688e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.3455784320831299s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.02093815803527832s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.743762731552124s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 8.559226989746094e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.36801862716674805s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.021221637725830078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.6450881958007812e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 5.699850082397461s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.9114227294921875e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.3440573215484619s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.02133345603942871s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0010914802551269531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 5.793571472167969e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.4543533325195312e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 4.751661062240601s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 4.258434772491455s
Availability | VoID file availability check for Open Data of Ecuador took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.342742919921875s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.021625041961669922s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 9.036064147949219e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.1444091796875e-05s
INFO | --- Analysis for opendataec took 11.444410800933838s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.00018334388732910156s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0003781318664550781s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.38486313819885254s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.021306276321411133s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 5.078315734863281e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.5497207641601562e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 13.54150390625s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 0.0001862049102783203s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.00041484832763671875s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.3251826763153076s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020833730697631836s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 1.52587890625e-05s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 4.4036865234375s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 0.00017881393432617188s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.3196241855621338s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020884037017822266s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 1.5497207641601562e-05s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 4.1198647022247314s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 5.269050598144531e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.3800327777862549s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.021006345748901367s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 9.059906005859375e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 4.464719533920288s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 5.245208740234375e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.00030350685119628906s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.32976531982421875s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.02128434181213379s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.2159347534179688e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 5.304444789886475s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 6.0558319091796875e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.33171653747558594s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020961284637451172s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 1.4543533325195312e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 4.236162424087524s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 5.3882598876953125e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.3336329460144043s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.021055936813354492s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 1.52587890625e-05s
INFO | --- Analysis for opendatascotland-simd-health-rank took 4.442428350448608s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 0.00012946128845214844s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.39058876037597656s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020830392837524414s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 1.5974044799804688e-05s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 4.090539455413818s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 0.00010204315185546875s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.3082096576690674s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.021130084991455078s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 1.4781951904296875e-05s
INFO | --- Analysis for opendatascotland-simd-income-rank took 3.173161268234253s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.442039489746094s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.00034689903259277344s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.5268909931182861s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.02135753631591797s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.170967102050781e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 2.5033950805664062e-05s
INFO | --- Analysis for openlink-lod-cache took 64.27563428878784s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 5.1975250244140625e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.3229100704193115s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.020967721939086914s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.846687316894531e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 1.52587890625e-05s
INFO | --- Analysis for openlinksw-dataspaces took 3.7982139587402344s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 5.53131103515625e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.4133942127227783s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.021183490753173828s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.751319885253906e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 1.0251998901367188e-05s
INFO | --- Analysis for openlylocal took 7.3610570430755615s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.5535063743591309s
Availability | VoID file availability check for OpenMobileNetwork took 0.0009419918060302734s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.33756375312805176s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02234649658203125s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.939338684082031e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 1.4781951904296875e-05s
INFO | --- Analysis for openmobilenetwork took 5.731136798858643s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.7160279750823975s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0007610321044921875s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.42128515243530273s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.022488832473754883s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 0.00010013580322265625s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 1.5020370483398438e-05s
INFO | --- Analysis for ordnance-survey-linked-data took 6.425646781921387s
Availability | SPARQL endpoint availability check for oreilly took 6.103515625e-05s
Availability | VoID file availability check for oreilly took 0.0004165172576904297s
Completeness | Calculation of interlinking completeness for oreilly took 0.48134636878967285s
Reputation | Calculation of the PageRank for oreilly took 0.031095504760742188s
Interlinking | Calculation of Degree of Connection for oreilly took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for oreilly took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for oreilly took 5.626678466796875e-05s
Believability | Calculation of trust value for oreilly took 1.7881393432617188e-05s
INFO | --- Analysis for oreilly took 6.232815504074097s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.463589906692505s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.35376787185668945s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.0212857723236084s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.4332275390625e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 1.52587890625e-05s
INFO | --- Analysis for Organchem-Data took 7.999500513076782s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.06476950645446777s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0003178119659423828s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.3727288246154785s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.02095937728881836s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 7.152557373046875e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.049041748046875e-05s
INFO | --- Analysis for organic-edunet took 9.845748662948608s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.4044480323791504s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0005774497985839844s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 5.918656349182129s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.7689950466156006s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.18515276908874512s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.6981444358825684s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 5.2795116901397705s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.21083998680114746s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.3645453453063965s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.1840670108795166s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.18683338165283203s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.14574027061462402s
License | HR license check for Open Research Knowledge Graph (ORKG) took 3.0895893573760986s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.1757657527923584s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.1807417869567871s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.3233191967010498s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.17348003387451172s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.1629633903503418s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.18206119537353516s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.86318063735962s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 7.414817810058594e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.17145657539367676s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.17354083061218262s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.19615912437438965s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.18457245826721191s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.15349555015563965s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.3541266918182373s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.33406567573547363s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 4.005123138427734s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.15362167358398438s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.16831445693969727s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.18637347221374512s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 2.3435049057006836s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.26142334938049316s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.29892587661743164s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.25714898109436035s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.3067166805267334s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.8918135166168213s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 3.324244976043701s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.3996057510375977s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.2946054935455322s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.2983572483062744s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.1613302230834961s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.17809844017028809s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2181.0220782756805s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.8266732692718506s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.02304530143737793s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.7404556274414062e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 2.384185791015625e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.8358230590820312e-05s
INFO | --- Analysis for orkg took 2431.1143577098846s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.125497817993164s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.4823179244995117s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.02127814292907715s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.559226989746094e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 1.1920928955078125e-05s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 29.89188313484192s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.653850793838501s
Availability | VoID file availability check for OSM Semantic Network took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.3605356216430664s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020723819732666016s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.695487976074219e-05s
Believability | Calculation of trust value for OSM Semantic Network took 1.5497207641601562e-05s
INFO | --- Analysis for osm-semantic-network took 10.341857194900513s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.6022000312805176s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.0002968311309814453s
Extra | Recovery of all triples for Open Transport Map @PSNC took 111.20732688903809s
Performance | Total latancy measurement for Open Transport Map @PSNC took 0.98158860206604s
Amount of data | Number of triples check for Open Transport Map @PSNC took 9.139728784561157s
Interoperability | New terms check for Open Transport Map @PSNC took 14.470026731491089s
Versatility | Languages check for Open Transport Map @PSNC took 300.26212525367737s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 2.0124692916870117s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.3105356693267822s
Versatility | Serialization formats check for Open Transport Map @PSNC took 11.754775524139404s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.3824794292449951s
License | MR license check for Open Transport Map @PSNC took 0.7692911624908447s
License | HR license check for Open Transport Map @PSNC took 300.15713238716125s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.20137906074523926s
Understandability | Number of label check for Open Transport Map @PSNC took 2.7539167404174805s
Understandability | URI regex check for Open Transport Map @PSNC took 1.157043218612671s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.5838086605072021s
Verifiability | Authors check for Open Transport Map @PSNC took 0.19306707382202148s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.2365739345550537s
Performance | Throughput check for Open Transport Map @PSNC took 11.34352445602417s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 8.702278137207031e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.2001948356628418s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.1976466178894043s
Interlinking | skos check for Open Transport Map @PSNC took 0.5101287364959717s
Interlinking | skos check for Open Transport Map @PSNC took 0.4537503719329834s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 4.13148832321167s
Currency | Creation date check for Open Transport Map @PSNC took 0.4697134494781494s
Currency | Modification date check for Open Transport Map @PSNC took 0.2582995891571045s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 152.1120285987854s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.20419931411743164s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.40148210525512695s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.4129757881164551s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 35.55604004859924s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.680619955062866s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.7527873516082764s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.1833336353302002s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 86.33224320411682s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.467292308807373s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 33.198668479919434s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.5157487392425537s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 87.654949426651s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.863246202468872s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.5115108489990234s
Security | Sign check for Open Transport Map @PSNC took 0.19420194625854492s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 8.64171314239502s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.45575428009033203s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.022934436798095703s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0008265972137451172s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 8.654594421386719e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 6.4373016357421875e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 1.5497207641601562e-05s
INFO | --- Analysis for OTM took 2281.6653802394867s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.6249754428863525s
Availability | VoID file availability check for Pali English Lexicon took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.3954801559448242s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.021532535552978516s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 3.981590270996094e-05s
Believability | Calculation of trust value for Pali English Lexicon took 1.5020370483398438e-05s
INFO | --- Analysis for pali-english-lexicon took 8.709106922149658s
Availability | SPARQL endpoint availability check for PanLex took 1.7345128059387207s
Availability | VoID file availability check for PanLex took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for PanLex took 0.3415529727935791s
Reputation | Calculation of the PageRank for PanLex took 0.020882606506347656s
Interlinking | Calculation of Degree of Connection for PanLex took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.724761962890625e-05s
Believability | Calculation of trust value for PanLex took 1.5974044799804688e-05s
INFO | --- Analysis for panlex took 5.19211483001709s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.00010442733764648438s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.33812379837036133s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.021070003509521484s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.981590270996094e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.5974044799804688e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 6.268941164016724s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.07743310928344727s
Availability | VoID file availability check for patents.data.gov.uk took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.34836769104003906s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.02194976806640625s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 5.435943603515625e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 1.1205673217773438e-05s
INFO | --- Analysis for patents-data-gov-uk took 3.403001308441162s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 8.630752563476562e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0008935928344726562s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.3679842948913574s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.021161556243896484s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 5.245208740234375e-05s
Believability | Calculation of trust value for PDEV-Lemon took 1.6689300537109375e-05s
INFO | --- Analysis for pdev-lemon took 4.545627593994141s
Availability | SPARQL endpoint availability check for pdevlemon took 5.4836273193359375e-05s
Availability | VoID file availability check for pdevlemon took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.37438058853149414s
Reputation | Calculation of the PageRank for pdevlemon took 0.020943403244018555s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.075599670410156e-05s
Believability | Calculation of trust value for pdevlemon took 1.5020370483398438e-05s
INFO | --- Analysis for pdevlemon took 3.8203585147857666s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 0.00010180473327636719s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0009043216705322266s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.3107748031616211s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.021056652069091797s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.106231689453125e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 9.059906005859375e-06s
INFO | --- Analysis for periodo took 19.74842619895935s
Availability | SPARQL endpoint availability check for Personal_Homepages took 0.00010418891906738281s
Availability | VoID file availability check for Personal_Homepages took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.3265111446380615s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.022672414779663086s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00039005279541015625s
Believability | Calculation of trust value for Personal_Homepages took 1.6450881958007812e-05s
INFO | --- Analysis for personal-homepages took 3.646930694580078s
Availability | SPARQL endpoint availability check for Ontology of University People took 8.034706115722656e-05s
Availability | VoID file availability check for Ontology of University People took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.32793307304382324s
Reputation | Calculation of the PageRank for Ontology of University People took 0.023218154907226562s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0010137557983398438s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 3.62396240234375e-05s
Believability | Calculation of trust value for Ontology of University People took 1.4066696166992188e-05s
INFO | --- Analysis for PersonOnto took 3.124274253845215s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 4.408309459686279s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.30403852462768555s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.021410703659057617s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0011148452758789062s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.4543533325195312e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.4543533325195312e-05s
INFO | --- Analysis for PFKHS took 10.65575909614563s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 2.1288065910339355s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007708072662353516s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.3511652946472168s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.021159648895263672s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.52587890625e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.430511474609375e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.8596649169921875e-05s
INFO | --- Analysis for PFRPPH took 7.145848512649536s
Availability | SPARQL endpoint availability check for PGxLOD took 30.19187831878662s
Availability | VoID file availability check for PGxLOD took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.33684754371643066s
Reputation | Calculation of the PageRank for PGxLOD took 0.032486677169799805s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0013115406036376953s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 6.699562072753906e-05s
Believability | Calculation of trust value for PGxLOD took 1.4781951904296875e-05s
INFO | --- Analysis for PGxLOD took 73.49160671234131s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1201043128967285s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.39548325538635254s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.02130746841430664s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 1.52587890625e-05s
INFO | --- Analysis for phoible took 5.528760671615601s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 0.00011992454528808594s
Availability | VoID file availability check for Parallel ice sheet model took 0.0007536411285400391s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.3271968364715576s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.021222591400146484s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0008175373077392578s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.337860107421875e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 1.4543533325195312e-05s
INFO | --- Analysis for PISM took 14.372978210449219s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.9591064453125e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.3496389389038086s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.02071857452392578s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.535385131835938e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 1.5020370483398438e-05s
INFO | --- Analysis for planetdata-project-wiki took 3.324350357055664s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.0203750133514404s
Availability | VoID file availability check for digitized plant specimen took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.4245114326477051s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.020882844924926758s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 7.796287536621094e-05s
Believability | Calculation of trust value for digitized plant specimen took 1.5735626220703125e-05s
INFO | --- Analysis for plant-specimen took 4.500834941864014s
Availability | SPARQL endpoint availability check for Pleiades took 5.5789947509765625e-05s
Availability | VoID file availability check for Pleiades took 0.0013740062713623047s
Completeness | Calculation of interlinking completeness for Pleiades took 0.3541994094848633s
Reputation | Calculation of the PageRank for Pleiades took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.749961853027344e-05s
Believability | Calculation of trust value for Pleiades took 1.5020370483398438e-05s
INFO | --- Analysis for pleiades took 12.810718297958374s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 5.650520324707031e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0009014606475830078s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.38401293754577637s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020671367645263672s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.0994415283203125e-05s
Believability | Calculation of trust value for podorozhnyk.com took 1.4781951904296875e-05s
INFO | --- Analysis for podorozhnyk took 4.001662015914917s
Availability | SPARQL endpoint availability check for Poképédia took 5.14984130859375e-05s
Availability | VoID file availability check for Poképédia took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for Poképédia took 0.323028564453125s
Reputation | Calculation of the PageRank for Poképédia took 0.0250396728515625s
Interlinking | Calculation of Degree of Connection for Poképédia took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0016658306121826172s
Interlinking | Calculation of Clustering coefficient for Poképédia took 0.0001468658447265625s
Believability | Calculation of trust value for Poképédia took 1.0967254638671875e-05s
INFO | --- Analysis for pokepedia-fr took 3.411836862564087s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 5.53131103515625e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.3084397315979004s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.02152729034423828s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0013000965118408203s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0001049041748046875s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.5497207641601562e-05s
INFO | --- Analysis for polymath-virtual-library took 6.399563789367676s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2519874572753906s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007014274597167969s
Extra | Recovery of all triples for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.984448671340942s
Performance | Total latancy measurement for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.6192748546600342s
Amount of data | Number of triples check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.37256765365600586s
Interoperability | New terms check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6779229640960693s
Versatility | Languages check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.2037932872772217s
Interpretability | Number of blank nodes check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.382035493850708s
Interpretability | RDF structures check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12048768997192383s
Versatility | Serialization formats check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13303804397583008s
Availability | RDF dump link check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13731837272644043s
License | MR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11762046813964844s
License | HR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.712108850479126s
Amount of data | Number of property check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12336945533752441s
Understandability | Number of label check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1657557487487793s
Understandability | URI regex check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2541038990020752s
Understandability | Vocabs check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1243906021118164s
Verifiability | Authors check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1213226318359375s
Verifiability | Publishers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12390995025634766s
Performance | Throughput check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.94298529624939s
Amount of data | Check the number of entities for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.00012302398681640625s
Verifiability | Contribs. check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12593889236450195s
Interlinking | sameAs chians check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12401390075683594s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13254690170288086s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1170964241027832s
Timeliness | dataset update frequency check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13913917541503906s
Currency | Creation date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2474203109741211s
Currency | Modification date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.24860048294067383s
Rep.Conc. | URIs length for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.769638776779175s
Interoperability | New vocabularies check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1398453712463379s
Accuracy | Check Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11327648162841797s
Accuracy | Check Inverse Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12843036651611328s
Accuracy | Check Empty annotation labels for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.143747329711914s
Accuracy | Check White space in annotation for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.20102477073669434s
Accuracy | Check Datatype consistency for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.974200963973999s
Consistency | Disjoint class check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11493611335754395s
Consistency | Check Misplaced properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.8564436435699463s
Consistency | Check Ontology hijacking for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.5938596725463867s
Consistency | Check Invalid usage of undefined classes for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.4035007953643799s
Consistency | Check Invalid usage of undefined properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.2695844173431396s
Conciseness | Check Extensional conciseness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.5594613552093506s
Security | Sign check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13126778602600098s
Availability | Check URIs Dereferenciability for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 4985.044159173965s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.6159393787384033s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.023432254791259766s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.937980651855469e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0008175373077392578s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.747245788574219e-05s
Interoperability | Check the re-using of existing vocabs for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.9141387939453125e-06s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 8.153915405273438e-05s
INFO | --- Analysis for portuguese_prisons_releases took 5058.776369333267s
Availability | SPARQL endpoint availability check for prefix.cc took 9.965896606445312e-05s
Availability | VoID file availability check for prefix.cc took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.3436741828918457s
Reputation | Calculation of the PageRank for prefix.cc took 0.02149796485900879s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0009307861328125s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 4.839897155761719e-05s
Believability | Calculation of trust value for prefix.cc took 1.0013580322265625e-05s
INFO | --- Analysis for prefix-cc took 3.9051082134246826s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.601590871810913s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0007834434509277344s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.35887670516967773s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.02062678337097168s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.982948303222656e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.3828277587890625e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 8.095403671264648s
Availability | SPARQL endpoint availability check for PreLex took 8.15335488319397s
Availability | VoID file availability check for PreLex took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for PreLex took 0.4624478816986084s
Reputation | Calculation of the PageRank for PreLex took 0.022667646408081055s
Interlinking | Calculation of Degree of Connection for PreLex took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.891654968261719e-05s
Believability | Calculation of trust value for PreLex took 1.33514404296875e-05s
INFO | --- Analysis for prelex took 22.56770396232605s
Availability | SPARQL endpoint availability check for Prelinger Archives took 1.6860313415527344s
Availability | VoID file availability check for Prelinger Archives took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.36243224143981934s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020881175994873047s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.9577484130859375e-05s
Believability | Calculation of trust value for Prelinger Archives took 1.5735626220703125e-05s
INFO | --- Analysis for prelinger_archives took 13.070353031158447s
Availability | SPARQL endpoint availability check for PreMOn took 0.5178825855255127s
Availability | VoID file availability check for PreMOn took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for PreMOn took 0.3613274097442627s
Reputation | Calculation of the PageRank for PreMOn took 0.021631479263305664s
Interlinking | Calculation of Degree of Connection for PreMOn took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for PreMOn took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for PreMOn took 5.2928924560546875e-05s
Believability | Calculation of trust value for PreMOn took 1.5974044799804688e-05s
INFO | --- Analysis for premon took 8.953828811645508s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 0.000102996826171875s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0008463859558105469s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.4547734260559082s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.021392345428466797s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.793571472167969e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 1.5020370483398438e-05s
INFO | --- Analysis for princeton-library-findingaids took 4.37142276763916s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.5876259803771973s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.3851034641265869s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.021203994750976562s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0008137226104736328s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 4.3392181396484375e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for PrinParLat took 4.923992156982422s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.14842009544372559s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.3220369815826416s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020845890045166016s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.821487426757812e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.4781951904296875e-05s
INFO | --- Analysis for printed-book-auction-catalogues took 4.6732017993927s
Availability | SPARQL endpoint availability check for Prior Panel took 9.822845458984375e-05s
Availability | VoID file availability check for Prior Panel took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.36123156547546387s
Reputation | Calculation of the PageRank for Prior Panel took 0.02155756950378418s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.600120544433594e-05s
Believability | Calculation of trust value for Prior Panel took 1.5974044799804688e-05s
INFO | --- Analysis for Prior_Panel took 3.5948050022125244s
Availability | SPARQL endpoint availability check for ProductDB took 0.7195773124694824s
Availability | VoID file availability check for ProductDB took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for ProductDB took 0.3794841766357422s
Reputation | Calculation of the PageRank for ProductDB took 0.021220922470092773s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0009398460388183594s
Interlinking | Calculation of Clustering coefficient for ProductDB took 9.131431579589844e-05s
Believability | Calculation of trust value for ProductDB took 1.5020370483398438e-05s
INFO | --- Analysis for productdb took 4.44463324546814s
Availability | SPARQL endpoint availability check for Product Types Ontology took 5.4836273193359375e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.34294843673706055s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.020956039428710938s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 8.654594421386719e-05s
Believability | Calculation of trust value for Product Types Ontology took 9.298324584960938e-06s
INFO | --- Analysis for productontology took 4.196759939193726s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 6.318092346191406e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0008051395416259766s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.35300207138061523s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.02095627784729004s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00011730194091796875s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.4543533325195312e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 7.342356443405151s
Availability | SPARQL endpoint availability check for provenanceweb took 0.05733537673950195s
Availability | VoID file availability check for provenanceweb took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.562241792678833s
Reputation | Calculation of the PageRank for provenanceweb took 0.02145695686340332s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 8.058547973632812e-05s
Believability | Calculation of trust value for provenanceweb took 1.5020370483398438e-05s
INFO | --- Analysis for provenanceweb took 55.15164828300476s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0001881122589111328s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007739067077636719s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.7506229877471924s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.021161317825317383s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00010514259338378906s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.6450881958007812e-05s
INFO | --- Analysis for proyectoapadrina took 7.268424987792969s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.320274114608765s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008676052093505859s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.46458983421325684s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.022587060928344727s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 4.38690185546875e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 1.1444091796875e-05s
INFO | --- Analysis for pscs-catalogue took 125.1076455116272s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 0.00010609626770019531s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.4290904998779297s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.024025678634643555s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0008814334869384766s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 8.654594421386719e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 1.5497207641601562e-05s
INFO | --- Analysis for psh-subject-headings took 4.025105237960815s
Availability | SPARQL endpoint availability check for Depression took 0.6138777732849121s
Availability | VoID file availability check for Depression took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for Depression took 0.3717026710510254s
Reputation | Calculation of the PageRank for Depression took 0.025848865509033203s
Interlinking | Calculation of Degree of Connection for Depression took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Depression took 0.0013556480407714844s
Interlinking | Calculation of Clustering coefficient for Depression took 4.9114227294921875e-05s
Believability | Calculation of trust value for Depression took 1.5735626220703125e-05s
INFO | --- Analysis for Psychology took 3.7718236446380615s
Availability | SPARQL endpoint availability check for PubChem RDF took 5.412101745605469e-05s
Availability | VoID file availability check for PubChem RDF took 0.0006711483001708984s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.3779118061065674s
Reputation | Calculation of the PageRank for PubChem RDF took 0.025690078735351562s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0013167858123779297s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 6.175041198730469e-05s
Believability | Calculation of trust value for PubChem RDF took 1.5974044799804688e-05s
INFO | --- Analysis for PubChem_RDF took 5.959843397140503s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 60.06263780593872s
Availability | VoID file availability check for Public Spending in Greece took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.360853910446167s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.02117180824279785s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 8.58306884765625e-05s
Believability | Calculation of trust value for Public Spending in Greece took 1.4781951904296875e-05s
INFO | --- Analysis for public-spending-in-greece took 148.16642045974731s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.20466899871826172s
Availability | VoID file availability check for Publications Office Authority tables took 0.0006954669952392578s
Extra | Recovery of all triples for Publications Office Authority tables took 189.7343831062317s
Performance | Total latancy measurement for Publications Office Authority tables took 0.618741512298584s
Amount of data | Number of triples check for Publications Office Authority tables took 62.0877799987793s
Interoperability | New terms check for Publications Office Authority tables took 57.17330718040466s
Versatility | Languages check for Publications Office Authority tables took 300.0866265296936s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 16.3633975982666s
Security | Check HTTPS for Publications Office Authority tables took 0.36779212951660156s
Interpretability | RDF structures check for Publications Office Authority tables took 0.5581703186035156s
Versatility | Serialization formats check for Publications Office Authority tables took 3.0419185161590576s
Availability | RDF dump link check for Publications Office Authority tables took 0.21227121353149414s
License | MR license check for Publications Office Authority tables took 0.32810354232788086s
License | HR license check for Publications Office Authority tables took 298.5731375217438s
Amount of data | Number of property check for Publications Office Authority tables took 0.18654894828796387s
Understandability | Number of label check for Publications Office Authority tables took 1.859126329421997s
Understandability | URI regex check for Publications Office Authority tables took 0.47440600395202637s
Understandability | Vocabs check for Publications Office Authority tables took 0.1091001033782959s
Verifiability | Authors check for Publications Office Authority tables took 0.18973684310913086s
Verifiability | Publishers check for Publications Office Authority tables took 0.18765044212341309s
Performance | Throughput check for Publications Office Authority tables took 10.639172315597534s
Amount of data | Check the number of entities for Publications Office Authority tables took 9.703636169433594e-05s
Verifiability | Contribs. check for Publications Office Authority tables took 0.21323776245117188s
Interlinking | sameAs chians check for Publications Office Authority tables took 7.652932643890381s
Interlinking | skos check for Publications Office Authority tables took 0.3654630184173584s
Interlinking | skos check for Publications Office Authority tables took 0.14861440658569336s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.25295019149780273s
Currency | Creation date check for Publications Office Authority tables took 0.5192527770996094s
Currency | Modification date check for Publications Office Authority tables took 0.15028738975524902s
Rep.Conc. | URIs length for Publications Office Authority tables took 405.2004415988922s
Interoperability | New vocabularies check for Publications Office Authority tables took 1.239776611328125e-05s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.16005492210388184s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.2019345760345459s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.20023632049560547s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 49.944833278656006s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.2387208938598633s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.871835231781006s
Consistency | Disjoint class check for Publications Office Authority tables took 0.13135838508605957s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.3846871852875s
Consistency | Misplaced classes for Publications Office Authority tables took 8.871700048446655s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 52.28585600852966s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.9004740715026855s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.72985792160034s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 3.176452398300171s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.39769482612609863s
Security | Sign check for Publications Office Authority tables took 0.5523290634155273s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 11.192378282546997s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 5.83757758140564s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.023144245147705078s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.506111145019531e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.6689300537109375e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 1.1205673217773438e-05s
INFO | --- Analysis for publications_office_authority_tables took 14827.571929454803s
Availability | SPARQL endpoint availability check for QBOAirbase took 0.00010657310485839844s
Availability | VoID file availability check for QBOAirbase took 0.0009319782257080078s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.40717315673828125s
Reputation | Calculation of the PageRank for QBOAirbase took 0.0248568058013916s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 9.131431579589844e-05s
Believability | Calculation of trust value for QBOAirbase took 1.621246337890625e-05s
INFO | --- Analysis for qboairbase took 139.39106583595276s
Availability | SPARQL endpoint availability check for Qualité de l'air took 5.412101745605469e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.3279304504394531s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.0213472843170166s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 3.361701965332031e-05s
Believability | Calculation of trust value for Qualité de l'air took 1.5020370483398438e-05s
INFO | --- Analysis for Qualité_de_l'air took 3.4276187419891357s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 9.417533874511719e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.3527815341949463s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.02109980583190918s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.361701965332031e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 1.52587890625e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 49.59405040740967s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.5893716812133789s
Availability | VoID file availability check for Querolus in LiLa took 0.0007801055908203125s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.32441043853759766s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.02118539810180664s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.981590270996094e-05s
Believability | Calculation of trust value for Querolus in LiLa took 9.775161743164062e-06s
INFO | --- Analysis for Querolus took 4.872598886489868s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.5923211574554443s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007145404815673828s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 29.56315541267395s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.7414853572845459s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.4703102111816406s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.0047168731689453s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.715535163879395s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.6537084579467773s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1592545509338379s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14753961563110352s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14208030700683594s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14210867881774902s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.21742486953735352s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.17725419998168945s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1437227725982666s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2742655277252197s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.25896525382995605s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1649620532989502s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.21054553985595703s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.737222909927368s
Amount of data | Check the number of entities for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.246566772460938e-05s
Verifiability | Contribs. check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1406407356262207s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14109325408935547s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14028239250183105s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15225648880004883s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15200042724609375s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.29360294342041016s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.29553675651550293s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 21.63118004798889s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.19731831550598145s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15486502647399902s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14263653755187988s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1328115463256836s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.814697265625e-05s
Accuracy | Check Datatype consistency for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.352771282196045s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14480161666870117s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.614206314086914s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.100461959838867s
Consistency | Check Invalid usage of undefined classes for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.5378477573394775s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.098770380020142s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.8757236003875732s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14170098304748535s
Availability | Check URIs Dereferenciability for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 14.230162143707275s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.3804619312286377s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.021394014358520508s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.030632019042969e-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 1.52587890625e-05s
INFO | --- Analysis for racai-legalnero took 163.74733757972717s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 0.0001049041748046875s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.3365364074707031s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.022405385971069336s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0010609626770019531s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 4.172325134277344e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 1.430511474609375e-05s
INFO | --- Analysis for racai-llod-corola-we took 3.434732675552368s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.1445753574371338s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0005922317504882812s
Extra | Recovery of all triples for PARSEME-Ro corpus took 31.086939096450806s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.689749002456665s
Amount of data | Number of triples check for PARSEME-Ro corpus took 6.7241058349609375s
Interoperability | New terms check for PARSEME-Ro corpus took 2.3006234169006348s
Versatility | Languages check for PARSEME-Ro corpus took 17.909590482711792s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.595630168914795s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.15394377708435059s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.16592860221862793s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.14130949974060059s
License | MR license check for PARSEME-Ro corpus took 0.15339088439941406s
License | HR license check for PARSEME-Ro corpus took 10.197566509246826s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.1306898593902588s
Understandability | Number of label check for PARSEME-Ro corpus took 0.24640655517578125s
Understandability | URI regex check for PARSEME-Ro corpus took 0.2849743366241455s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.13054943084716797s
Verifiability | Authors check for PARSEME-Ro corpus took 0.14269351959228516s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.14301133155822754s
Performance | Throughput check for PARSEME-Ro corpus took 10.745238304138184s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 8.082389831542969e-05s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.15311980247497559s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 0.1415259838104248s
Interlinking | skos check for PARSEME-Ro corpus took 0.14249229431152344s
Interlinking | skos check for PARSEME-Ro corpus took 0.1427173614501953s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 0.1419968605041504s
Currency | Creation date check for PARSEME-Ro corpus took 0.30858850479125977s
Currency | Modification date check for PARSEME-Ro corpus took 0.2845139503479004s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 79.87792181968689s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.14256858825683594s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.14026188850402832s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.14285492897033691s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 2.043872117996216s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.23251748085021973s
Accuracy | Check Datatype consistency for PARSEME-Ro corpus took 4.128790616989136s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.1429591178894043s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 11.287647008895874s
Consistency | Check Ontology hijacking for PARSEME-Ro corpus took 31.513901233673096s
Consistency | Check Invalid usage of undefined classes for PARSEME-Ro corpus took 1.7957463264465332s
Consistency | Check Invalid usage of undefined properties for PARSEME-Ro corpus took 13.260725498199463s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 2.9032034873962402s
Security | Sign check for PARSEME-Ro corpus took 0.14128899574279785s
Availability | Check URIs Dereferenciability for PARSEME-Ro corpus took 7.287578821182251s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.4673621654510498s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.025977134704589844s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.001150369644165039s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for PARSEME-Ro corpus took 7.867813110351562e-06s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.5497207641601562e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 283.1509358882904s
Availability | SPARQL endpoint availability check for RoLEX took 0.13153767585754395s
Availability | VoID file availability check for RoLEX took 0.0007455348968505859s
Extra | Recovery of all triples for RoLEX took 36.15334701538086s
Performance | Total latancy measurement for RoLEX took 0.685593843460083s
Amount of data | Number of triples check for RoLEX took 1.5998306274414062s
Interoperability | New terms check for RoLEX took 1.8268153667449951s
Versatility | Languages check for RoLEX took 4.092198848724365s
Interpretability | Number of blank nodes check for RoLEX took 1.1679198741912842s
Interpretability | RDF structures check for RoLEX took 0.2911975383758545s
Versatility | Serialization formats check for RoLEX took 0.25142836570739746s
Availability | RDF dump link check for RoLEX took 0.1738719940185547s
License | MR license check for RoLEX took 0.13077640533447266s
License | HR license check for RoLEX took 0.14253687858581543s
Amount of data | Number of property check for RoLEX took 0.140625s
Understandability | Number of label check for RoLEX took 0.1424257755279541s
Understandability | URI regex check for RoLEX took 0.2849314212799072s
Understandability | Vocabs check for RoLEX took 0.15334463119506836s
Verifiability | Authors check for RoLEX took 0.14138245582580566s
Verifiability | Publishers check for RoLEX took 0.14052224159240723s
Performance | Throughput check for RoLEX took 10.862761497497559s
Amount of data | Check the number of entities for RoLEX took 9.989738464355469e-05s
Verifiability | Contribs. check for RoLEX took 0.129685640335083s
Interlinking | sameAs chians check for RoLEX took 0.14282941818237305s
Interlinking | skos check for RoLEX took 0.13034701347351074s
Interlinking | skos check for RoLEX took 0.14077544212341309s
Timeliness | dataset update frequency check for RoLEX took 0.1591498851776123s
Currency | Creation date check for RoLEX took 0.2741563320159912s
Currency | Modification date check for RoLEX took 0.29604101181030273s
Rep.Conc. | URIs length for RoLEX took 56.87724041938782s
Interoperability | New vocabularies check for RoLEX took 1.2874603271484375e-05s
Consistency | Deprecated classes/propertiers check for RoLEX took 0.13027644157409668s
Accuracy | Check Functional Property for RoLEX took 0.15324783325195312s
Accuracy | Check Inverse Functional Property for RoLEX took 0.14179778099060059s
Accuracy | Check Datatype consistency for RoLEX took 4.251476049423218s
Consistency | Disjoint class check for RoLEX took 0.1352388858795166s
Consistency | Check Misplaced properties for RoLEX took 2.650486707687378s
Consistency | Check Ontology hijacking for RoLEX took 8.987178325653076s
Consistency | Check Invalid usage of undefined classes for RoLEX took 2.1072797775268555s
Consistency | Check Invalid usage of undefined properties for RoLEX took 4.1452956199646s
Conciseness | Check Extensional conciseness for RoLEX took 3.23256516456604s
Security | Sign check for RoLEX took 0.15272188186645508s
Availability | Check URIs Dereferenciability for RoLEX took 7.334774494171143s
Completeness | Calculation of interlinking completeness for RoLEX took 0.44213294982910156s
Reputation | Calculation of the PageRank for RoLEX took 0.02483987808227539s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0012998580932617188s
Interlinking | Calculation of Clustering coefficient for RoLEX took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for RoLEX took 3.337860107421875e-06s
Believability | Calculation of trust value for RoLEX took 1.3589859008789062e-05s
INFO | --- Analysis for racai-llod-rolex took 179.98757553100586s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 8.106231689453125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0006868839263916016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.3803997039794922s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.026360750198364258s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0013988018035888672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 5.030632019042969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.049041748046875e-05s
INFO | --- Analysis for racai-llod-romanian-treebank took 3.683330535888672s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 0.00010991096496582031s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.4156177043914795s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.025641202926635742s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0013632774353027344s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 5.1975250244140625e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 1.52587890625e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 3.7735047340393066s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 5.030632019042969e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.32703089714050293s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.02281785011291504s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.266334533691406e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 1.3828277587890625e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 3.4716145992279053s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 5.1975250244140625e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.33814525604248047s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.027161836624145508s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0014672279357910156s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 4.887580871582031e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.621246337890625e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 3.46835994720459s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.13374590873718262s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0006875991821289062s
Extra | Recovery of all triples for ROBIN Technical Acquisition Speech Corpus took 9.401076078414917s
Performance | Total latancy measurement for ROBIN Technical Acquisition Speech Corpus took 0.6980867385864258s
Amount of data | Number of triples check for ROBIN Technical Acquisition Speech Corpus took 0.30434417724609375s
Interoperability | New terms check for ROBIN Technical Acquisition Speech Corpus took 1.5737683773040771s
Versatility | Languages check for ROBIN Technical Acquisition Speech Corpus took 0.6012482643127441s
Interpretability | Number of blank nodes check for ROBIN Technical Acquisition Speech Corpus took 0.27049756050109863s
Interpretability | RDF structures check for ROBIN Technical Acquisition Speech Corpus took 0.1509392261505127s
Versatility | Serialization formats check for ROBIN Technical Acquisition Speech Corpus took 0.14053940773010254s
Availability | RDF dump link check for ROBIN Technical Acquisition Speech Corpus took 0.13872456550598145s
License | MR license check for ROBIN Technical Acquisition Speech Corpus took 0.14186620712280273s
License | HR license check for ROBIN Technical Acquisition Speech Corpus took 0.15712285041809082s
Amount of data | Number of property check for ROBIN Technical Acquisition Speech Corpus took 0.13908600807189941s
Understandability | Number of label check for ROBIN Technical Acquisition Speech Corpus took 0.13315796852111816s
Understandability | URI regex check for ROBIN Technical Acquisition Speech Corpus took 0.27853918075561523s
Understandability | Vocabs check for ROBIN Technical Acquisition Speech Corpus took 0.12891888618469238s
Verifiability | Authors check for ROBIN Technical Acquisition Speech Corpus took 0.17323899269104004s
Verifiability | Publishers check for ROBIN Technical Acquisition Speech Corpus took 0.12830352783203125s
Performance | Throughput check for ROBIN Technical Acquisition Speech Corpus took 10.859447002410889s
Amount of data | Check the number of entities for ROBIN Technical Acquisition Speech Corpus took 0.00014281272888183594s
Verifiability | Contribs. check for ROBIN Technical Acquisition Speech Corpus took 0.13209176063537598s
Interlinking | sameAs chians check for ROBIN Technical Acquisition Speech Corpus took 0.14281940460205078s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.14185166358947754s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.13100028038024902s
Timeliness | dataset update frequency check for ROBIN Technical Acquisition Speech Corpus took 0.15390563011169434s
Currency | Creation date check for ROBIN Technical Acquisition Speech Corpus took 0.2840235233306885s
Currency | Modification date check for ROBIN Technical Acquisition Speech Corpus took 0.30303263664245605s
Rep.Conc. | URIs length for ROBIN Technical Acquisition Speech Corpus took 2.6239142417907715s
Interoperability | New vocabularies check for ROBIN Technical Acquisition Speech Corpus took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for ROBIN Technical Acquisition Speech Corpus took 0.14126920700073242s
Accuracy | Check Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.14065146446228027s
Accuracy | Check Inverse Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.14127516746520996s
Accuracy | Check Empty annotation labels for ROBIN Technical Acquisition Speech Corpus took 0.42365145683288574s
Accuracy | Check White space in annotation for ROBIN Technical Acquisition Speech Corpus took 0.009814262390136719s
Accuracy | Check Datatype consistency for ROBIN Technical Acquisition Speech Corpus took 1.2352490425109863s
Consistency | Disjoint class check for ROBIN Technical Acquisition Speech Corpus took 0.1305372714996338s
Consistency | Check Misplaced properties for ROBIN Technical Acquisition Speech Corpus took 0.5039060115814209s
Consistency | Check Ontology hijacking for ROBIN Technical Acquisition Speech Corpus took 2.1528360843658447s
Consistency | Check Invalid usage of undefined classes for ROBIN Technical Acquisition Speech Corpus took 1.4072656631469727s
Consistency | Check Invalid usage of undefined properties for ROBIN Technical Acquisition Speech Corpus took 1.7753264904022217s
Conciseness | Check Extensional conciseness for ROBIN Technical Acquisition Speech Corpus took 0.8490407466888428s
Security | Sign check for ROBIN Technical Acquisition Speech Corpus took 0.1526353359222412s
Availability | Check URIs Dereferenciability for ROBIN Technical Acquisition Speech Corpus took 7.27333927154541s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.36795926094055176s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.021154165267944336s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 3.4332275390625e-05s
Interoperability | Check the re-using of existing vocabs for ROBIN Technical Acquisition Speech Corpus took 1.430511474609375e-06s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 1.4781951904296875e-05s
INFO | --- Analysis for racai-llod-rtasc took 64.9610767364502s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.15420007705688477s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0005967617034912109s
Extra | Recovery of all triples for SiMoNERo - the Romanian medical treebank took 35.344202518463135s
Performance | Total latancy measurement for SiMoNERo - the Romanian medical treebank took 0.7025148868560791s
Amount of data | Number of triples check for SiMoNERo - the Romanian medical treebank took 1.0806164741516113s
Interoperability | New terms check for SiMoNERo - the Romanian medical treebank took 1.6218616962432861s
Versatility | Languages check for SiMoNERo - the Romanian medical treebank took 2.3658015727996826s
Interpretability | Number of blank nodes check for SiMoNERo - the Romanian medical treebank took 0.8359346389770508s
Interpretability | RDF structures check for SiMoNERo - the Romanian medical treebank took 0.14259910583496094s
Versatility | Serialization formats check for SiMoNERo - the Romanian medical treebank took 0.133650541305542s
Availability | RDF dump link check for SiMoNERo - the Romanian medical treebank took 0.1407945156097412s
License | MR license check for SiMoNERo - the Romanian medical treebank took 0.13217568397521973s
License | HR license check for SiMoNERo - the Romanian medical treebank took 4.678276300430298s
Amount of data | Number of property check for SiMoNERo - the Romanian medical treebank took 0.14154982566833496s
Understandability | Number of label check for SiMoNERo - the Romanian medical treebank took 0.1584789752960205s
Understandability | URI regex check for SiMoNERo - the Romanian medical treebank took 0.28368401527404785s
Understandability | Vocabs check for SiMoNERo - the Romanian medical treebank took 0.1415114402770996s
Verifiability | Authors check for SiMoNERo - the Romanian medical treebank took 0.15318799018859863s
Verifiability | Publishers check for SiMoNERo - the Romanian medical treebank took 0.1422872543334961s
Performance | Throughput check for SiMoNERo - the Romanian medical treebank took 10.797956228256226s
Amount of data | Check the number of entities for SiMoNERo - the Romanian medical treebank took 0.00010657310485839844s
Verifiability | Contribs. check for SiMoNERo - the Romanian medical treebank took 0.14276528358459473s
Interlinking | sameAs chians check for SiMoNERo - the Romanian medical treebank took 0.14176464080810547s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.15314769744873047s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.13099408149719238s
Timeliness | dataset update frequency check for SiMoNERo - the Romanian medical treebank took 0.14203453063964844s
Currency | Creation date check for SiMoNERo - the Romanian medical treebank took 0.321819543838501s
Currency | Modification date check for SiMoNERo - the Romanian medical treebank took 0.29563188552856445s
Rep.Conc. | URIs length for SiMoNERo - the Romanian medical treebank took 9.344514846801758s
Interoperability | New vocabularies check for SiMoNERo - the Romanian medical treebank took 1.621246337890625e-05s
Consistency | Deprecated classes/propertiers check for SiMoNERo - the Romanian medical treebank took 0.14311552047729492s
Accuracy | Check Functional Property for SiMoNERo - the Romanian medical treebank took 0.12946224212646484s
Accuracy | Check Inverse Functional Property for SiMoNERo - the Romanian medical treebank took 0.1525287628173828s
Accuracy | Check Empty annotation labels for SiMoNERo - the Romanian medical treebank took 0.7187354564666748s
Accuracy | Check White space in annotation for SiMoNERo - the Romanian medical treebank took 0.01920914649963379s
Accuracy | Check Datatype consistency for SiMoNERo - the Romanian medical treebank took 4.105558395385742s
Consistency | Disjoint class check for SiMoNERo - the Romanian medical treebank took 0.13176369667053223s
Consistency | Check Misplaced properties for SiMoNERo - the Romanian medical treebank took 1.7393054962158203s
Consistency | Check Ontology hijacking for SiMoNERo - the Romanian medical treebank took 4.626633167266846s
Consistency | Check Invalid usage of undefined classes for SiMoNERo - the Romanian medical treebank took 1.4595754146575928s
Consistency | Check Invalid usage of undefined properties for SiMoNERo - the Romanian medical treebank took 2.9933812618255615s
Conciseness | Check Extensional conciseness for SiMoNERo - the Romanian medical treebank took 2.9857845306396484s
Security | Sign check for SiMoNERo - the Romanian medical treebank took 0.15268635749816895s
Availability | Check URIs Dereferenciability for SiMoNERo - the Romanian medical treebank took 1537.8933701515198s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.3544337749481201s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.022825002670288086s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 4.9114227294921875e-05s
Interoperability | Check the re-using of existing vocabs for SiMoNERo - the Romanian medical treebank took 2.1457672119140625e-06s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 1.5974044799804688e-05s
INFO | --- Analysis for racai-llod-simonero took 1644.5209670066833s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.11544513702392578s
Availability | VoID file availability check for Rådata nå! took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.36444830894470215s
Reputation | Calculation of the PageRank for Rådata nå! took 0.021174907684326172s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.58306884765625e-05s
Believability | Calculation of trust value for Rådata nå! took 1.6450881958007812e-05s
INFO | --- Analysis for radatana took 4.9637017250061035s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 5.316734313964844e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.33056068420410156s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.02303004264831543s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 4.0531158447265625e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 1.430511474609375e-05s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 17.383140563964844s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 14.092408657073975s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0009095668792724609s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.30738306045532227s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.021796464920043945s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.266334533691406e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.5735626220703125e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 30.985126972198486s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 392.62421679496765s
Availability | VoID file availability check for Polish LGU financial statements took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.3460221290588379s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.02146625518798828s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 3.8623809814453125e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 1.5020370483398438e-05s
INFO | --- Analysis for Rb_PL_LGU took 667.8024320602417s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 0.00010919570922851562s
Availability | VoID file availability check for RDF Book Mashup took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.36469411849975586s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.026880979537963867s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 9.34600830078125e-05s
Believability | Calculation of trust value for RDF Book Mashup took 1.430511474609375e-05s
INFO | --- Analysis for rdf-book-mashup took 4.642884731292725s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 0.00010752677917480469s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.31121253967285156s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020853757858276367s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00010728836059570312s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 1.5020370483398438e-05s
INFO | --- Analysis for rdfize-lastfm took 3.2446532249450684s
Availability | SPARQL endpoint availability check for RDFLicense took 261.2251646518707s
Availability | VoID file availability check for RDFLicense took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.39254307746887207s
Reputation | Calculation of the PageRank for RDFLicense took 0.021409034729003906s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.814697265625e-05s
Believability | Calculation of trust value for RDFLicense took 1.621246337890625e-05s
INFO | --- Analysis for rdflicense took 536.3885977268219s
Availability | SPARQL endpoint availability check for RDFohloh took 0.0001761913299560547s
Availability | VoID file availability check for RDFohloh took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.5673155784606934s
Reputation | Calculation of the PageRank for RDFohloh took 0.021259307861328125s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 0.00010251998901367188s
Believability | Calculation of trust value for RDFohloh took 1.52587890625e-05s
INFO | --- Analysis for rdfohloh took 7.857296705245972s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.6096045970916748s
Availability | VoID file availability check for Reactome RDF took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.44321274757385254s
Reputation | Calculation of the PageRank for Reactome RDF took 0.021163463592529297s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.981590270996094e-05s
Believability | Calculation of trust value for Reactome RDF took 1.049041748046875e-05s
INFO | --- Analysis for reactome-rdf took 4.579116106033325s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.09425544738769531s
Availability | VoID file availability check for Rechtspraak.nl took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.34998130798339844s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.02266979217529297s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 0.00010013580322265625s
Believability | Calculation of trust value for Rechtspraak.nl took 1.1682510375976562e-05s
INFO | --- Analysis for rechtspraak took 3.6891982555389404s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 5.14984130859375e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0007688999176025391s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.3543977737426758s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.023423194885253906s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 9.1552734375e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 1.049041748046875e-05s
INFO | --- Analysis for red-uno-internacional-santillana took 11.680038690567017s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.05077385902404785s
Availability | VoID file availability check for reference.data.gov.uk took 0.0003027915954589844s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.323897123336792s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.02099299430847168s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.0001652240753173828s
Believability | Calculation of trust value for reference.data.gov.uk took 1.2159347534179688e-05s
INFO | --- Analysis for reference-data-gov-uk took 3.3099236488342285s
Availability | SPARQL endpoint availability check for RELD took 0.6810753345489502s
Availability | VoID file availability check for RELD took 0.0003883838653564453s
Completeness | Calculation of interlinking completeness for RELD took 0.3821141719818115s
Reputation | Calculation of the PageRank for RELD took 0.021036386489868164s
Interlinking | Calculation of Degree of Connection for RELD took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for RELD took 3.24249267578125e-05s
Believability | Calculation of trust value for RELD took 1.52587890625e-05s
INFO | --- Analysis for RELD took 4.67255163192749s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.21665501594543457s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0006191730499267578s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.1295998096466064s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.4627525806427002s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.273773193359375s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.7615678310394287s
Versatility | Languages check for Repository for Linked Open Archival Data took 17.48388433456421s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 6.570791006088257s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.24495744705200195s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.21802568435668945s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.23364949226379395s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.14473557472229004s
License | MR license check for Repository for Linked Open Archival Data took 0.320681095123291s
License | HR license check for Repository for Linked Open Archival Data took 8.00868558883667s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.13701415061950684s
Understandability | Number of label check for Repository for Linked Open Archival Data took 0.8035407066345215s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.33986639976501465s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.08292222023010254s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.13678312301635742s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.1136319637298584s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.543934345245361s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 0.00010251998901367188s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.05904793739318848s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.14440703392028809s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.20447683334350586s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.07037472724914551s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.18284988403320312s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.20678377151489258s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.17473649978637695s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.516786813735962s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.11712884902954102s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.11442184448242188s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.06850123405456543s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.3233222961425781s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.028082609176635742s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.029673337936401367s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.14481329917907715s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 1.8285391330718994s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.22136235237121582s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.6122987270355225s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.337414026260376s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.3715157508850098s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.034639596939086914s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.12706923484802246s
Security | Sign check for Repository for Linked Open Archival Data took 0.3436405658721924s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 1003.2224369049072s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.37752819061279297s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.027643203735351562s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 5.340576171875e-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.5497207641601562e-05s
INFO | --- Analysis for reload took 1129.3117468357086s
Availability | SPARQL endpoint availability check for Land use merced dataset took 0.00010347366333007812s
Availability | VoID file availability check for Land use merced dataset took 0.0007085800170898438s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.3744347095489502s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.021151304244995117s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0008194446563720703s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.504753112792969e-05s
Believability | Calculation of trust value for Land use merced dataset took 1.430511474609375e-05s
INFO | --- Analysis for remote_Sensing took 4.140222072601318s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.907304286956787s
Availability | VoID file availability check for Renewable Energy Generators took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.3253970146179199s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.021678686141967773s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.8160552978515625e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 1.1205673217773438e-05s
INFO | --- Analysis for renewable_energy_generators took 16.018898248672485s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.0813455581665039s
Availability | VoID file availability check for research.data.gov.uk took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.3929572105407715s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.021970748901367188s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.846687316894531e-05s
Believability | Calculation of trust value for research.data.gov.uk took 1.0967254638671875e-05s
INFO | --- Analysis for research-data-gov-uk took 3.4115517139434814s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 0.00010466575622558594s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0007889270782470703s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.3336784839630127s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.021019458770751953s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 7.343292236328125e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 1.5497207641601562e-05s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 4.90516996383667s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.06625199317932129s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.4394528865814209s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.020949363708496094s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.218650817871094e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 1.430511474609375e-05s
INFO | --- Analysis for revistas_turismo took 3.307807207107544s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.2733955383300781s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.8692007064819336s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.021060943603515625s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0009202957153320312s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.0001385211944580078s
Believability | Calculation of trust value for Revyu.com - Review Anything took 1.430511474609375e-05s
INFO | --- Analysis for revyu took 3.931156873703003s
Availability | SPARQL endpoint availability check for sdafsadf took 0.3994479179382324s
Availability | VoID file availability check for sdafsadf took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.32238006591796875s
Reputation | Calculation of the PageRank for sdafsadf took 0.020918607711791992s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.0279159545898438e-05s
Believability | Calculation of trust value for sdafsadf took 1.430511474609375e-05s
INFO | --- Analysis for rgsdfg took 4.177056074142456s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.00010824203491210938s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007836818695068359s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.3430173397064209s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.021039247512817383s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 5.245208740234375e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 1.239776611328125e-05s
INFO | --- Analysis for riese took 23.48062753677368s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.37838172912597656s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0006411075592041016s
Extra | Recovery of all triples for Répertoire International des Sources Musicales - RISM took 23.67915654182434s
Performance | Total latancy measurement for Répertoire International des Sources Musicales - RISM took 0.5483841896057129s
Amount of data | Number of triples check for Répertoire International des Sources Musicales - RISM took 52.80701231956482s
Interoperability | New terms check for Répertoire International des Sources Musicales - RISM took 1.8853912353515625s
Versatility | Languages check for Répertoire International des Sources Musicales - RISM took 168.00984168052673s
Interpretability | Number of blank nodes check for Répertoire International des Sources Musicales - RISM took 48.72594904899597s
Security | Check HTTPS for Répertoire International des Sources Musicales - RISM took 0.266021728515625s
Interpretability | RDF structures check for Répertoire International des Sources Musicales - RISM took 0.13972234725952148s
Versatility | Serialization formats check for Répertoire International des Sources Musicales - RISM took 0.14483857154846191s
Availability | RDF dump link check for Répertoire International des Sources Musicales - RISM took 0.10672807693481445s
License | MR license check for Répertoire International des Sources Musicales - RISM took 0.11549806594848633s
License | HR license check for Répertoire International des Sources Musicales - RISM took 300.06479120254517s
Amount of data | Number of property check for Répertoire International des Sources Musicales - RISM took 0.13349604606628418s
Understandability | Number of label check for Répertoire International des Sources Musicales - RISM took 7.014228820800781s
Understandability | URI regex check for Répertoire International des Sources Musicales - RISM took 0.27184176445007324s
Understandability | Vocabs check for Répertoire International des Sources Musicales - RISM took 0.1069173812866211s
Verifiability | Authors check for Répertoire International des Sources Musicales - RISM took 0.11311173439025879s
Verifiability | Publishers check for Répertoire International des Sources Musicales - RISM took 0.11424708366394043s
Performance | Throughput check for Répertoire International des Sources Musicales - RISM took 10.332659721374512s
Amount of data | Check the number of entities for Répertoire International des Sources Musicales - RISM took 8.96453857421875e-05s
Verifiability | Contribs. check for Répertoire International des Sources Musicales - RISM took 0.11842918395996094s
Interlinking | sameAs chians check for Répertoire International des Sources Musicales - RISM took 1.1373589038848877s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.1506195068359375s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.10727858543395996s
Timeliness | dataset update frequency check for Répertoire International des Sources Musicales - RISM took 0.11368799209594727s
Currency | Creation date check for Répertoire International des Sources Musicales - RISM took 0.2578418254852295s
Currency | Modification date check for Répertoire International des Sources Musicales - RISM took 0.2576174736022949s
Rep.Conc. | URIs length for Répertoire International des Sources Musicales - RISM took 79.08929491043091s
Interoperability | New vocabularies check for Répertoire International des Sources Musicales - RISM took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Répertoire International des Sources Musicales - RISM took 0.1652688980102539s
Accuracy | Check Functional Property for Répertoire International des Sources Musicales - RISM took 0.1368401050567627s
Accuracy | Check Inverse Functional Property for Répertoire International des Sources Musicales - RISM took 0.11759305000305176s
Accuracy | Check Empty annotation labels for Répertoire International des Sources Musicales - RISM took 12.145353078842163s
Accuracy | Check White space in annotation for Répertoire International des Sources Musicales - RISM took 2.409966230392456s
Accuracy | Check Datatype consistency for Répertoire International des Sources Musicales - RISM took 3.887735366821289s
Consistency | Disjoint class check for Répertoire International des Sources Musicales - RISM took 0.11627459526062012s
Consistency | Check Misplaced properties for Répertoire International des Sources Musicales - RISM took 52.8728551864624s
Consistency | Check Ontology hijacking for Répertoire International des Sources Musicales - RISM took 4.629843235015869s
Consistency | Check Invalid usage of undefined classes for Répertoire International des Sources Musicales - RISM took 1.5015575885772705s
Consistency | Check Invalid usage of undefined properties for Répertoire International des Sources Musicales - RISM took 47.62439966201782s
Conciseness | Check Extensional conciseness for Répertoire International des Sources Musicales - RISM took 2.809938907623291s
Security | Sign check for Répertoire International des Sources Musicales - RISM took 0.0979926586151123s
Availability | Check URIs Dereferenciability for Répertoire International des Sources Musicales - RISM took 1.5333900451660156s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.4341244697570801s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.022202253341674805s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0008816719055175781s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 7.200241088867188e-05s
Interoperability | Check the re-using of existing vocabs for Répertoire International des Sources Musicales - RISM took 2.384185791015625e-06s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 1.5497207641601562e-05s
INFO | --- Analysis for rism took 1250.234784603119s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.11679863929748535s
Availability | VoID file availability check for RISM Authority data took 0.0007731914520263672s
Extra | Recovery of all triples for RISM Authority data took 22.587517976760864s
Performance | Total latancy measurement for RISM Authority data took 0.5728204250335693s
Amount of data | Number of triples check for RISM Authority data took 52.69413113594055s
Interoperability | New terms check for RISM Authority data took 1.6860878467559814s
Versatility | Languages check for RISM Authority data took 169.95221757888794s
Interpretability | Number of blank nodes check for RISM Authority data took 48.16152024269104s
Security | Check HTTPS for RISM Authority data took 0.17796063423156738s
Interpretability | RDF structures check for RISM Authority data took 0.14630866050720215s
Versatility | Serialization formats check for RISM Authority data took 0.14688849449157715s
Availability | RDF dump link check for RISM Authority data took 0.10652589797973633s
License | MR license check for RISM Authority data took 0.09937715530395508s
License | HR license check for RISM Authority data took 300.08199524879456s
Amount of data | Number of property check for RISM Authority data took 0.13782691955566406s
Understandability | Number of label check for RISM Authority data took 5.906009197235107s
Understandability | URI regex check for RISM Authority data took 0.2700800895690918s
Understandability | Vocabs check for RISM Authority data took 0.11440658569335938s
Verifiability | Authors check for RISM Authority data took 0.10923624038696289s
Verifiability | Publishers check for RISM Authority data took 0.1064455509185791s
Performance | Throughput check for RISM Authority data took 10.402697563171387s
Amount of data | Check the number of entities for RISM Authority data took 0.0001399517059326172s
Verifiability | Contribs. check for RISM Authority data took 0.10566902160644531s
Interlinking | sameAs chians check for RISM Authority data took 1.3652212619781494s
Interlinking | skos check for RISM Authority data took 0.14415359497070312s
Interlinking | skos check for RISM Authority data took 0.12132883071899414s
Timeliness | dataset update frequency check for RISM Authority data took 0.10974335670471191s
Currency | Creation date check for RISM Authority data took 0.2448272705078125s
Currency | Modification date check for RISM Authority data took 0.26108622550964355s
Rep.Conc. | URIs length for RISM Authority data took 78.85462307929993s
Interoperability | New vocabularies check for RISM Authority data took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for RISM Authority data took 0.14773011207580566s
Accuracy | Check Functional Property for RISM Authority data took 0.1704273223876953s
Accuracy | Check Inverse Functional Property for RISM Authority data took 0.10850143432617188s
Accuracy | Check Empty annotation labels for RISM Authority data took 12.342608213424683s
Accuracy | Check White space in annotation for RISM Authority data took 2.4221527576446533s
Accuracy | Check Datatype consistency for RISM Authority data took 4.0157790184021s
Consistency | Disjoint class check for RISM Authority data took 0.10303544998168945s
Consistency | Check Misplaced properties for RISM Authority data took 47.230719327926636s
Consistency | Check Ontology hijacking for RISM Authority data took 5.59326434135437s
Consistency | Check Invalid usage of undefined classes for RISM Authority data took 1.5090458393096924s
Consistency | Check Invalid usage of undefined properties for RISM Authority data took 55.4695987701416s
Conciseness | Check Extensional conciseness for RISM Authority data took 2.9779229164123535s
Security | Sign check for RISM Authority data took 0.13673806190490723s
Availability | Check URIs Dereferenciability for RISM Authority data took 1.5549161434173584s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.4215517044067383s
Reputation | Calculation of the PageRank for RISM Authority data took 0.021793842315673828s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 5.7220458984375e-05s
Interoperability | Check the re-using of existing vocabs for RISM Authority data took 1.9073486328125e-06s
Believability | Calculation of trust value for RISM Authority data took 1.71661376953125e-05s
INFO | --- Analysis for rism-authorities took 1255.964886188507s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 5.364418029785156e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.5252270698547363s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.022496461868286133s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.361701965332031e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.52587890625e-05s
INFO | --- Analysis for rk took 3.287601947784424s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0850222110748291s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.3400876522064209s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007369518280029297s
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.5020370483398438e-05s
INFO | --- Analysis for rkb-explorer-acm took 3.3169307708740234s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.04310154914855957s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.3602008819580078s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.021088361740112305s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00015354156494140625s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-budapest took 3.288111925125122s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.03931832313537598s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.4011805057525635s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.022873401641845703s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0010919570922851562s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.0002474784851074219s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 1.9311904907226562e-05s
INFO | --- Analysis for rkb-explorer-citeseer took 3.379157304763794s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.043048858642578125s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.35164785385131836s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020717620849609375s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00016236305236816406s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.621246337890625e-05s
INFO | --- Analysis for rkb-explorer-cordis took 3.361001968383789s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.0444331169128418s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.4048619270324707s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.02084040641784668s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.0001595020294189453s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-courseware took 4.368003606796265s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.04804182052612305s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.32703065872192383s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.021393775939941406s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 4.124641418457031e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-crime took 3.3130524158477783s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.04377913475036621s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.32187509536743164s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.021825551986694336s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0010981559753417969s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0001442432403564453s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-curriculum took 3.4883322715759277s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.04399561882019043s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.34615588188171387s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.02084946632385254s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.507469177246094e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 1.52587890625e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 4.152918815612793s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.05794835090637207s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.35110926628112793s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.02073073387145996s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.00023293495178222656s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-dblp took 3.214015245437622s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.046022891998291016s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.3787527084350586s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.020991802215576172s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.867813110351562e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-deepblue took 3.2506752014160156s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.43426036834716797s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.3490719795227051s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.02095651626586914s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 0.000102996826171875s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-deploy took 4.847966909408569s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.049788713455200195s
Availability | VoID file availability check for digitaleconomy took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.3415336608886719s
Reputation | Calculation of the PageRank for digitaleconomy took 0.021835803985595703s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 4.601478576660156e-05s
Believability | Calculation of trust value for digitaleconomy took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 3.2229552268981934s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.04711127281188965s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.31727027893066406s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.02093791961669922s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.0001423358917236328s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.52587890625e-05s
INFO | --- Analysis for rkb-explorer-dotac took 3.2918503284454346s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.045061588287353516s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.3300204277038574s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020891904830932617s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.935264587402344e-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 3.7047383785247803s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.050740718841552734s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.3524460792541504s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.022025108337402344s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00017881393432617188s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.5497207641601562e-05s
INFO | --- Analysis for rkb-explorer-eprints took 3.6107048988342285s
Availability | SPARQL endpoint availability check for epsrc took 0.03625130653381348s
Availability | VoID file availability check for epsrc took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for epsrc took 0.33028173446655273s
Reputation | Calculation of the PageRank for epsrc took 0.021866798400878906s
Interlinking | Calculation of Degree of Connection for epsrc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.817413330078125e-05s
Believability | Calculation of trust value for epsrc took 1.5735626220703125e-05s
INFO | --- Analysis for rkb-explorer-epsrc took 3.5249037742614746s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.045369625091552734s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.3415977954864502s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.021851301193237305s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.797645568847656e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.5020370483398438e-05s
INFO | --- Analysis for rkb-explorer-era took 3.874112606048584s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.043358802795410156s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.5207247734069824s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.02124476432800293s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00011134147644042969s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-eurecom took 3.72454571723938s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.4119541645050049s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.36139702796936035s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.022960901260375977s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.131431579589844e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-ft took 4.88191294670105s
Availability | SPARQL endpoint availability check for fun took 0.04544568061828613s
Availability | VoID file availability check for fun took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for fun took 0.33040452003479004s
Reputation | Calculation of the PageRank for fun took 0.02096080780029297s
Interlinking | Calculation of Degree of Connection for fun took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for fun took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for fun took 7.939338684082031e-05s
Believability | Calculation of trust value for fun took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-fun took 3.3535537719726562s
Availability | SPARQL endpoint availability check for gdlc took 0.049138545989990234s
Availability | VoID file availability check for gdlc took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for gdlc took 0.3443315029144287s
Reputation | Calculation of the PageRank for gdlc took 0.020794391632080078s
Interlinking | Calculation of Degree of Connection for gdlc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.866455078125e-05s
Believability | Calculation of trust value for gdlc took 1.6450881958007812e-05s
INFO | --- Analysis for rkb-explorer-gdlc took 3.4383060932159424s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.05026745796203613s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.3262648582458496s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.021108388900756836s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0008313655853271484s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00012135505676269531s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.7642974853515625e-05s
INFO | --- Analysis for rkb-explorer-ibm took 3.64302659034729s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.04345440864562988s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.33156394958496094s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.021121501922607422s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001323223114013672s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 1.52587890625e-05s
INFO | --- Analysis for rkb-explorer-ieee took 3.2371764183044434s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.04687380790710449s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.48411107063293457s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.022446632385253906s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0013914108276367188s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00021910667419433594s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 7.224082946777344e-05s
INFO | --- Analysis for rkb-explorer-irit took 3.2772750854492188s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.04905056953430176s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.37416791915893555s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.699562072753906e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-italy took 4.3306310176849365s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.04852151870727539s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.4004673957824707s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.02061152458190918s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.605552673339844e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 1.5020370483398438e-05s
INFO | --- Analysis for rkb-explorer-jisc took 3.204773426055908s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.04654550552368164s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.3484938144683838s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.02099013328552246s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.6253204345703125e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-kaunas took 3.1670897006988525s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.036774635314941406s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.3392622470855713s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020717859268188477s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.000164031982421875s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-kisti took 3.233792304992676s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.050116539001464844s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.31296491622924805s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.022089481353759766s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0008335113525390625s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00015163421630859375s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-laas took 3.699070692062378s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.04082536697387695s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.36684489250183105s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.021270036697387695s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007979869842529297s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 7.2479248046875e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.5735626220703125e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 3.5112850666046143s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.046237945556640625s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.34647083282470703s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020727872848510742s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00015282630920410156s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 1.6450881958007812e-05s
INFO | --- Analysis for rkb-explorer-newcastle took 3.5307412147521973s
Availability | SPARQL endpoint availability check for notube took 0.05048418045043945s
Availability | VoID file availability check for notube took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for notube took 0.3660392761230469s
Reputation | Calculation of the PageRank for notube took 0.02101898193359375s
Interlinking | Calculation of Degree of Connection for notube took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for notube took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for notube took 4.4345855712890625e-05s
Believability | Calculation of trust value for notube took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-notube took 3.270920515060425s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.03495359420776367s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.000518798828125s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.3312816619873047s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.022856712341308594s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00013399124145507812s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 1.3589859008789062e-05s
INFO | --- Analysis for rkb-explorer-nsf took 3.2586326599121094s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.04126453399658203s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.3299407958984375s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00015163421630859375s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-oai took 3.2025210857391357s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.03142380714416504s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.315659761428833s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.02107977867126465s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 8.106231689453125e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-os took 3.1102001667022705s
Availability | SPARQL endpoint availability check for photos took 0.03602170944213867s
Availability | VoID file availability check for photos took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for photos took 0.39803004264831543s
Reputation | Calculation of the PageRank for photos took 0.020944833755493164s
Interlinking | Calculation of Degree of Connection for photos took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for photos took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for photos took 7.677078247070312e-05s
Believability | Calculation of trust value for photos took 1.5735626220703125e-05s
INFO | --- Analysis for rkb-explorer-photos took 3.191232204437256s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.041573286056518555s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.341353178024292s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.02166295051574707s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0009524822235107422s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00014138221740722656s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 1.4543533325195312e-05s
INFO | --- Analysis for rkb-explorer-pisa took 3.8399524688720703s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.04851174354553223s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.3732757568359375s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.02205944061279297s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019431114196777344s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-rae2001 took 3.5360231399536133s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.04673147201538086s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.38623476028442383s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.022036314010620117s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.000141143798828125s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.621246337890625e-05s
INFO | --- Analysis for rkb-explorer-resex took 3.9405455589294434s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.04923391342163086s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.32335400581359863s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020872116088867188s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.5367431640625e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.5974044799804688e-05s
INFO | --- Analysis for rkb-explorer-risks took 3.1938130855560303s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.04380083084106445s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0003120899200439453s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.32084226608276367s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.021813631057739258s
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.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00013017654418945312s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-roma took 3.194446563720703s
Availability | SPARQL endpoint availability check for roni took 0.04712247848510742s
Availability | VoID file availability check for roni took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for roni took 0.33739614486694336s
Reputation | Calculation of the PageRank for roni took 0.020909786224365234s
Interlinking | Calculation of Degree of Connection for roni took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for roni took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for roni took 3.0517578125e-05s
Believability | Calculation of trust value for roni took 1.5020370483398438e-05s
INFO | --- Analysis for rkb-explorer-roni took 3.2178955078125s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.04166865348815918s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.35109925270080566s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0002124309539794922s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-southampton took 3.199411153793335s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.04316592216491699s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.3389134407043457s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.020528078079223633s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00010609626770019531s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-ulm took 3.286320924758911s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.04602789878845215s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.33796119689941406s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.02127361297607422s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0008962154388427734s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 0.00011873245239257812s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 1.6689300537109375e-05s
INFO | --- Analysis for rkb-explorer-unlocode took 3.7025139331817627s
Availability | SPARQL endpoint availability check for webconf took 0.04512333869934082s
Availability | VoID file availability check for webconf took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for webconf took 0.35286402702331543s
Reputation | Calculation of the PageRank for webconf took 0.020967483520507812s
Interlinking | Calculation of Degree of Connection for webconf took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010991096496582031s
Believability | Calculation of trust value for webconf took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-webconf took 13.63966965675354s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.03717827796936035s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.42502784729003906s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.022279739379882812s
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.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 7.390975952148438e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-webscience took 3.6242117881774902s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.04470396041870117s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.3092944622039795s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.022485017776489258s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00024008750915527344s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-wiki took 3.3149609565734863s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.04979372024536133s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.3602733612060547s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.02110004425048828s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.918212890625e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-wordnet took 3.5468482971191406s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.43197107315063477s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0007538795471191406s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 29.553679943084717s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.516040563583374s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 2.1583032608032227s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.806652307510376s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 5.143650054931641s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.3598380088806152s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.11281919479370117s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.11555647850036621s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.11113715171813965s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.09699392318725586s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.1050114631652832s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.10273194313049316s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.10566210746765137s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.21206927299499512s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.10413026809692383s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.1074821949005127s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.09671783447265625s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.350381135940552s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 8.821487426757812e-05s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.1023712158203125s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.10938286781311035s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.10321831703186035s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.1015481948852539s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.09594058990478516s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.21240234375s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.20361542701721191s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 20.09510087966919s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.10397911071777344s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.10182619094848633s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.10122966766357422s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 3.9807376861572266s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.10468363761901855s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 3.0555295944213867s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 6.787602663040161s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.5503921508789062s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.522680997848511s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 3.1195132732391357s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.1022331714630127s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 802.4355602264404s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.413684606552124s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.02859210968017578s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 9.179115295410156e-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.7404556274414062e-05s
INFO | --- Analysis for roceeh-road took 921.4442341327667s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 5.412101745605469e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.3824622631072998s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.021148204803466797s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 3.0994415283203125e-05s
Believability | Calculation of trust value for ontology terrorist attack took 1.0251998901367188e-05s
INFO | --- Analysis for ROSHANI took 6.440029859542847s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 9.989738464355469e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0003082752227783203s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.4761958122253418s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.02134227752685547s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.62396240234375e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 9.775161743164062e-06s
INFO | --- Analysis for ROSHANI_SAHU took 3.2990810871124268s
Availability | SPARQL endpoint availability check for x took 5.817413330078125e-05s
Availability | VoID file availability check for x took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for x took 0.31546759605407715s
Reputation | Calculation of the PageRank for x took 0.02100062370300293s
Interlinking | Calculation of Degree of Connection for x took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for x took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for x took 3.361701965332031e-05s
Believability | Calculation of trust value for x took 1.5497207641601562e-05s
INFO | --- Analysis for Rozprawa,_artykuł took 3.085111618041992s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 5.340576171875e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.3012425899505615s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.020952939987182617s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 7.152557373046875e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 1.430511474609375e-05s
INFO | --- Analysis for rss-500-nif-ner-corpus took 4.778164863586426s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 5.316734313964844e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.3506429195404053s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.02135753631591797s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.000990152359008789s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 9.989738464355469e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 9.5367431640625e-06s
INFO | --- Analysis for rubentaelman took 3.798020839691162s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 5.316734313964844e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0003466606140136719s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.3196725845336914s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.021793842315673828s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0008640289306640625s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 0.00011563301086425781s
Believability | Calculation of trust value for Ruben Verborgh's data took 1.3589859008789062e-05s
INFO | --- Analysis for rubenverborgh took 3.660823345184326s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 392.91215801239014s
Availability | VoID file availability check for Russian Universities Specialities took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.3297426700592041s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.021743297576904297s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 3.5762786865234375e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 9.775161743164062e-06s
INFO | --- Analysis for russian-universities-specialities took 678.4683084487915s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 7.439361333847046s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.3671445846557617s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.021435260772705078s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.2901763916015625e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 1.049041748046875e-05s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 13.090527534484863s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.1507885456085205s
Availability | VoID file availability check for SALDO-RDF took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.3605351448059082s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.02304673194885254s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.814697265625e-05s
Believability | Calculation of trust value for SALDO-RDF took 1.2874603271484375e-05s
INFO | --- Analysis for saldo-rdf took 6.560430526733398s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.7196171283721924s
Availability | VoID file availability check for SALDOM-RDF took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.3358008861541748s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.021494150161743164s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 4.124641418457031e-05s
Believability | Calculation of trust value for SALDOM-RDF took 1.3828277587890625e-05s
INFO | --- Analysis for saldom-rdf took 5.935720682144165s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 0.0001201629638671875s
Availability | VoID file availability check for Salzburgerland DE took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.36130547523498535s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.020849227905273438s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010824203491210938s
Believability | Calculation of trust value for Salzburgerland DE took 1.430511474609375e-05s
INFO | --- Analysis for salzburgerland-com-de took 6.165113925933838s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 5.53131103515625e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.39617133140563965s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.021086931228637695s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0009210109710693359s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.0001361370086669922s
Believability | Calculation of trust value for Salzburgerland EN took 1.1444091796875e-05s
INFO | --- Analysis for salzburgerland-com-en took 3.6634912490844727s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 9.846687316894531e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.3626832962036133s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.021020889282226562s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00011444091796875s
Believability | Calculation of trust value for Salzburgerland IT took 1.3828277587890625e-05s
INFO | --- Analysis for salzburgerland-com-it took 3.5150959491729736s
Availability | SPARQL endpoint availability check for sandrart.net took 5.221366882324219e-05s
Availability | VoID file availability check for sandrart.net took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.35617995262145996s
Reputation | Calculation of the PageRank for sandrart.net took 0.020935535430908203s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 7.033348083496094e-05s
Believability | Calculation of trust value for sandrart.net took 1.52587890625e-05s
INFO | --- Analysis for sandrart-net took 4.819487571716309s
Availability | SPARQL endpoint availability check for Taxons  took 0.546788215637207s
Availability | VoID file availability check for Taxons  took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for Taxons  took 0.363466739654541s
Reputation | Calculation of the PageRank for Taxons  took 0.020966529846191406s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Taxons  took 7.152557373046875e-05s
Believability | Calculation of trust value for Taxons  took 1.5974044799804688e-05s
INFO | --- Analysis for sandre took 10.181889057159424s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 2.2109920978546143s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.4006531238555908s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020774364471435547s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.457069396972656e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 9.775161743164062e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 9.332990407943726s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 265.5682005882263s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.3841407299041748s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.022491931915283203s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 4.1484832763671875e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 1.430511474609375e-05s
INFO | --- Analysis for santillana_guide_dataset took 670.380820274353s
Availability | SPARQL endpoint availability check for SATAR test  took 0.00010752677917480469s
Availability | VoID file availability check for SATAR test  took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.5826287269592285s
Reputation | Calculation of the PageRank for SATAR test  took 0.021692514419555664s
Interlinking | Calculation of Degree of Connection for SATAR test  took 3.0040740966796875e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 3.24249267578125e-05s
Believability | Calculation of trust value for SATAR test  took 1.430511474609375e-05s
INFO | --- Analysis for SATAR_test took 6.146597385406494s
Availability | SPARQL endpoint availability check for SCBG Data took 22.425893306732178s
Availability | VoID file availability check for SCBG Data took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.3380277156829834s
Reputation | Calculation of the PageRank for SCBG Data took 0.021318912506103516s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.726119995117188e-05s
Believability | Calculation of trust value for SCBG Data took 1.0728836059570312e-05s
INFO | --- Analysis for SCBG-Data took 55.98816776275635s
Availability | SPARQL endpoint availability check for Schemantra took 5.14984130859375e-05s
Availability | VoID file availability check for Schemantra took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for Schemantra took 0.3593926429748535s
Reputation | Calculation of the PageRank for Schemantra took 0.021006345748901367s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Schemantra took 3.170967102050781e-05s
Believability | Calculation of trust value for Schemantra took 1.0013580322265625e-05s
INFO | --- Analysis for Schemantra took 3.2115347385406494s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 0.8387002944946289s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.394273042678833s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.021270751953125s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007569789886474609s
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.5735626220703125e-05s
INFO | --- Analysis for schemapedia took 4.500319480895996s
Availability | SPARQL endpoint availability check for Scholarometer took 0.00010275840759277344s
Availability | VoID file availability check for Scholarometer took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.3149688243865967s
Reputation | Calculation of the PageRank for Scholarometer took 0.021190643310546875s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 9.179115295410156e-05s
Believability | Calculation of trust value for Scholarometer took 1.4066696166992188e-05s
INFO | --- Analysis for scholarometer took 8.55481243133545s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 5.173683166503906e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.36625051498413086s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.02100229263305664s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 3.1948089599609375e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 1.1682510375976562e-05s
INFO | --- Analysis for scoreboard took 5.249524831771851s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.00010418891906738281s
Availability | VoID file availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.537203311920166s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.020868778228759766s
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.1444091796875e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.337860107421875e-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.0251998901367188e-05s
INFO | --- Analysis for SDDEC took 32.85032773017883s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 5.698204040527344e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.3226931095123291s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.02124190330505371s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 3.24249267578125e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.0728836059570312e-05s
INFO | --- Analysis for SDG took 3.9045515060424805s
Availability | SPARQL endpoint availability check for sears.com took 5.078315734863281e-05s
Availability | VoID file availability check for sears.com took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for sears.com took 0.3162999153137207s
Reputation | Calculation of the PageRank for sears.com took 0.021759033203125s
Interlinking | Calculation of Degree of Connection for sears.com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for sears.com took 7.295608520507812e-05s
Believability | Calculation of trust value for sears.com took 1.4543533325195312e-05s
INFO | --- Analysis for sears took 6.626372814178467s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.09340119361877441s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.3694784641265869s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.02161264419555664s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.702278137207031e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0967254638671875e-05s
INFO | --- Analysis for sec-rdfabout took 7.005666017532349s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.826014041900635s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.3863222599029541s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.022573471069335938s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0008764266967773438s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 0.00010037422180175781s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for secold took 168.81806421279907s
Availability | SPARQL endpoint availability check for semanlink took 9.584426879882812e-05s
Availability | VoID file availability check for semanlink took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for semanlink took 0.3369169235229492s
Reputation | Calculation of the PageRank for semanlink took 0.023223400115966797s
Interlinking | Calculation of Degree of Connection for semanlink took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0008113384246826172s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00015592575073242188s
Believability | Calculation of trust value for semanlink took 1.0967254638671875e-05s
INFO | --- Analysis for semanlink took 4.210385084152222s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.08345317840576172s
Availability | VoID file availability check for Semantic Universe Data took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.3601360321044922s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.020959138870239258s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.2901763916015625e-05s
Believability | Calculation of trust value for Semantic Universe Data took 1.4543533325195312e-05s
INFO | --- Analysis for semantic-universe took 3.5012855529785156s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.345165967941284s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.3317868709564209s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.021130084991455078s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011539459228515625s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.3589859008789062e-05s
INFO | --- Analysis for semantic-web-dog-food took 83.88028645515442s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 0.00010371208190917969s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.3476400375366211s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.021173715591430664s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.935264587402344e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 1.5497207641601562e-05s
INFO | --- Analysis for semantic-web-grundlagen took 3.7591826915740967s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 0.000102996826171875s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.3405802249908447s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020912885665893555s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.797645568847656e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 1.1205673217773438e-05s
INFO | --- Analysis for semantic-xbrl took 4.335835218429565s
Availability | SPARQL endpoint availability check for Semantic Quran took 6.987128496170044s
Availability | VoID file availability check for Semantic Quran took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Semantic Quran took 0.4901721477508545s
Reputation | Calculation of the PageRank for Semantic Quran took 0.020905017852783203s
Interlinking | Calculation of Degree of Connection for Semantic Quran took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Semantic Quran took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Semantic Quran took 7.557868957519531e-05s
Believability | Calculation of trust value for Semantic Quran took 1.6927719116210938e-05s
INFO | --- Analysis for semanticquran took 16.258906364440918s
Availability | SPARQL endpoint availability check for SemanticTweet took 0.00010013580322265625s
Availability | VoID file availability check for SemanticTweet took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.3403022289276123s
Reputation | Calculation of the PageRank for SemanticTweet took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.817413330078125e-05s
Believability | Calculation of trust value for SemanticTweet took 1.52587890625e-05s
INFO | --- Analysis for semantictweet took 3.4421815872192383s
Availability | SPARQL endpoint availability check for semanticweb.org took 0.00010204315185546875s
Availability | VoID file availability check for semanticweb.org took 0.0007307529449462891s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.34578514099121094s
Reputation | Calculation of the PageRank for semanticweb.org took 0.020917892456054688s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 8.320808410644531e-05s
Believability | Calculation of trust value for semanticweb.org took 1.4781951904296875e-05s
INFO | --- Analysis for semanticweb-org took 23.855913400650024s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.0815889835357666s
Availability | VoID file availability check for Semantic CrunchBase took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.3142108917236328s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.021803855895996094s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.001039743423461914s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 9.036064147949219e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 1.4543533325195312e-05s
INFO | --- Analysis for semsol-crunchbase took 3.2626044750213623s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.2603785991668701s
Availability | VoID file availability check for SentimentWortschatz took 0.00035881996154785156s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.39357829093933105s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020897388458251953s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.458427429199219e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.8596649169921875e-05s
INFO | --- Analysis for sentiws took 5.502241611480713s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.08528470993042s
Availability | VoID file availability check for seoul-bike-data took 0.0008034706115722656s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.5608577728271484s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.021013736724853516s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0008256435394287109s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 4.506111145019531e-05s
Believability | Calculation of trust value for seoul-bike-data took 1.3828277587890625e-05s
INFO | --- Analysis for seoul-bike-data took 74.14826893806458s
Availability | SPARQL endpoint availability check for Serendipity took 3.9942407608032227s
Availability | VoID file availability check for Serendipity took 0.0003497600555419922s
Completeness | Calculation of interlinking completeness for Serendipity took 0.48949718475341797s
Reputation | Calculation of the PageRank for Serendipity took 0.021039485931396484s
Interlinking | Calculation of Degree of Connection for Serendipity took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Serendipity took 7.796287536621094e-05s
Believability | Calculation of trust value for Serendipity took 1.6927719116210938e-05s
INFO | --- Analysis for serendipity took 11.199325323104858s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 0.00011038780212402344s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.5323233604431152s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.02231740951538086s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.4809112548828125e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 1.5735626220703125e-05s
INFO | --- Analysis for Sherry_Wine took 3.530179738998413s
Availability | SPARQL endpoint availability check for Sherry Wine took 8.916854858398438e-05s
Availability | VoID file availability check for Sherry Wine took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.32838988304138184s
Reputation | Calculation of the PageRank for Sherry Wine took 0.021225690841674805s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.337860107421875e-05s
Believability | Calculation of trust value for Sherry Wine took 1.4543533325195312e-05s
INFO | --- Analysis for Sherry_Wine_ took 3.0322000980377197s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.22977566719055176s
Availability | VoID file availability check for Shoah victims? names took 0.2585718631744385s
Extra | Recovery of all triples for Shoah victims? names took 1.0190424919128418s
Performance | Total latancy measurement for Shoah victims? names took 0.4057469367980957s
Amount of data | Number of triples check for Shoah victims? names took 1.2286460399627686s
Interoperability | New terms check for Shoah victims? names took 2.312809467315674s
Versatility | Languages check for Shoah victims? names took 19.207372903823853s
Interpretability | Number of blank nodes check for Shoah victims? names took 3.0652661323547363s
Security | Check HTTPS for Shoah victims? names took 0.3229193687438965s
Interpretability | RDF structures check for Shoah victims? names took 0.25775837898254395s
Versatility | Serialization formats check for Shoah victims? names took 0.2915985584259033s
Availability | RDF dump link check for Shoah victims? names took 0.16690468788146973s
License | MR license check for Shoah victims? names took 0.384197473526001s
License | HR license check for Shoah victims? names took 8.904813289642334s
Amount of data | Number of property check for Shoah victims? names took 0.13389873504638672s
Understandability | Number of label check for Shoah victims? names took 1.1019489765167236s
Understandability | URI regex check for Shoah victims? names took 0.4422876834869385s
Understandability | Vocabs check for Shoah victims? names took 0.11723732948303223s
Verifiability | Authors check for Shoah victims? names took 0.18099474906921387s
Verifiability | Publishers check for Shoah victims? names took 0.17906522750854492s
Performance | Throughput check for Shoah victims? names took 10.610921144485474s
Amount of data | Check the number of entities for Shoah victims? names took 3.24249267578125e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.06003117561340332s
Interlinking | sameAs chians check for Shoah victims? names took 0.14517498016357422s
Interlinking | skos check for Shoah victims? names took 0.23855853080749512s
Interlinking | skos check for Shoah victims? names took 0.05422377586364746s
Timeliness | dataset update frequency check for Shoah victims? names took 0.2739841938018799s
Currency | Creation date check for Shoah victims? names took 0.16049528121948242s
Currency | Modification date check for Shoah victims? names took 0.17771553993225098s
Rep.Conc. | URIs length for Shoah victims? names took 2.609909772872925s
Interoperability | New vocabularies check for Shoah victims? names took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.08911323547363281s
Accuracy | Check Functional Property for Shoah victims? names took 0.11381387710571289s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.06480836868286133s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.3755626678466797s
Accuracy | Check White space in annotation for Shoah victims? names took 0.02820444107055664s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.030133962631225586s
Consistency | Disjoint class check for Shoah victims? names took 0.193878173828125s
Consistency | Check Misplaced properties for Shoah victims? names took 1.8968925476074219s
Consistency | Misplaced classes for Shoah victims? names took 0.22539687156677246s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.8086998462677002s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.357931137084961s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.1155550479888916s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.037795305252075195s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.17597317695617676s
Security | Sign check for Shoah victims? names took 0.5315639972686768s
Availability | Check URIs Dereferenciability for Shoah victims? names took 1036.6013283729553s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.35822343826293945s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.021863222122192383s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0008382797241210938s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.3392181396484375e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.1920928955078125e-06s
Believability | Calculation of trust value for Shoah victims? names took 1.6450881958007812e-05s
INFO | --- Analysis for shoah-victims-names took 1155.706438779831s
Availability | SPARQL endpoint availability check for Person took 0.00010347366333007812s
Availability | VoID file availability check for Person took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Person took 0.5398349761962891s
Reputation | Calculation of the PageRank for Person took 0.02116560935974121s
Interlinking | Calculation of Degree of Connection for Person took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Person took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Person took 3.123283386230469e-05s
Believability | Calculation of trust value for Person took 1.4543533325195312e-05s
INFO | --- Analysis for Shripriya_Dubey took 3.705198049545288s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 0.00010514259338378906s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.34388256072998047s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.021494388580322266s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 3.266334533691406e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 1.5020370483398438e-05s
INFO | --- Analysis for Shutterstock took 3.474626302719116s
Availability | SPARQL endpoint availability check for SIMPLE took 0.00010275840759277344s
Availability | VoID file availability check for SIMPLE took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.3802816867828369s
Reputation | Calculation of the PageRank for SIMPLE took 0.021020889282226562s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.410743713378906e-05s
Believability | Calculation of trust value for SIMPLE took 1.52587890625e-05s
INFO | --- Analysis for simple took 9.459505796432495s
Availability | SPARQL endpoint availability check for SITC-V4 took 25.575051307678223s
Availability | VoID file availability check for SITC-V4 took 0.0008902549743652344s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.42923521995544434s
Reputation | Calculation of the PageRank for SITC-V4 took 0.02147388458251953s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.76837158203125e-05s
Believability | Calculation of trust value for SITC-V4 took 1.1444091796875e-05s
INFO | --- Analysis for sitc-v4 took 126.45156383514404s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.00017380714416503906s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0008015632629394531s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.39849066734313965s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.021126985549926758s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 5.650520324707031e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.0013580322265625e-05s
INFO | --- Analysis for sli_galnet_rdf took 13.3367760181427s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 0.00010251998901367188s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.37520933151245117s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.023669004440307617s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.409385681152344e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 1.5020370483398438e-05s
INFO | --- Analysis for slideshare2rdf took 3.2979445457458496s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.5905604362487793s
Availability | VoID file availability check for Linked Stage Graph took 0.0002808570861816406s
Extra | Recovery of all triples for Linked Stage Graph took 2.462769031524658s
Performance | Total latancy measurement for Linked Stage Graph took 1.5543475151062012s
Amount of data | Number of triples check for Linked Stage Graph took 0.3376624584197998s
Interoperability | New terms check for Linked Stage Graph took 1.7184927463531494s
Versatility | Languages check for Linked Stage Graph took 0.7597050666809082s
Interpretability | Number of blank nodes check for Linked Stage Graph took 0.3136742115020752s
Security | Check HTTPS for Linked Stage Graph took 0.209852933883667s
Interpretability | RDF structures check for Linked Stage Graph took 0.5643923282623291s
Versatility | Serialization formats check for Linked Stage Graph took 0.409299373626709s
Availability | RDF dump link check for Linked Stage Graph took 0.2996032238006592s
License | MR license check for Linked Stage Graph took 0.54610276222229s
License | HR license check for Linked Stage Graph took 1.7925350666046143s
Amount of data | Number of property check for Linked Stage Graph took 0.3112223148345947s
Understandability | Number of label check for Linked Stage Graph took 0.7778618335723877s
Understandability | URI regex check for Linked Stage Graph took 0.8033978939056396s
Understandability | Vocabs check for Linked Stage Graph took 0.4022328853607178s
Verifiability | Authors check for Linked Stage Graph took 0.305835485458374s
Verifiability | Publishers check for Linked Stage Graph took 0.32502317428588867s
Performance | Throughput check for Linked Stage Graph took 12.03201937675476s
Amount of data | Check the number of entities for Linked Stage Graph took 3.2901763916015625e-05s
Verifiability | Contribs. check for Linked Stage Graph took 0.28983449935913086s
Interlinking | sameAs chians check for Linked Stage Graph took 0.4121971130371094s
Interlinking | skos check for Linked Stage Graph took 0.35712337493896484s
Interlinking | skos check for Linked Stage Graph took 0.2971651554107666s
Timeliness | dataset update frequency check for Linked Stage Graph took 0.47630739212036133s
Currency | Creation date check for Linked Stage Graph took 0.6366915702819824s
Currency | Modification date check for Linked Stage Graph took 0.6210041046142578s
Rep.Conc. | URIs length for Linked Stage Graph took 1.760098934173584s
Interoperability | New vocabularies check for Linked Stage Graph took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Linked Stage Graph took 0.3027682304382324s
Accuracy | Check Functional Property for Linked Stage Graph took 0.508948564529419s
Accuracy | Check Inverse Functional Property for Linked Stage Graph took 0.5285825729370117s
Accuracy | Check Empty annotation labels for Linked Stage Graph took 0.8728358745574951s
Accuracy | Check White space in annotation for Linked Stage Graph took 0.023748397827148438s
Accuracy | Check Datatype consistency for Linked Stage Graph took 0.029570341110229492s
Consistency | Disjoint class check for Linked Stage Graph took 0.2988758087158203s
Consistency | Check Misplaced properties for Linked Stage Graph took 1.185210943222046s
Consistency | Misplaced classes for Linked Stage Graph took 0.6967451572418213s
Consistency | Check Ontology hijacking for Linked Stage Graph took 2.1148808002471924s
Consistency | Check Invalid usage of undefined classes for Linked Stage Graph took 1.3417015075683594s
Consistency | Check Invalid usage of undefined properties for Linked Stage Graph took 1.9503164291381836s
Conciseness | Check Extensional conciseness for Linked Stage Graph took 0.027639389038085938s
Conciseness | Check Intensional conciseness for Linked Stage Graph took 0.6810381412506104s
Security | Sign check for Linked Stage Graph took 0.7067344188690186s
Availability | Check URIs Dereferenciability for Linked Stage Graph took 4601.088914871216s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.3920919895172119s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.02169322967529297s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0010690689086914062s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 6.103515625e-05s
Interoperability | Check the re-using of existing vocabs for Linked Stage Graph took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Stage Graph took 1.4781951904296875e-05s
INFO | --- Analysis for slod took 4676.951774120331s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.654639482498169s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.00038313865661621094s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 99.02821326255798s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.9543614387512207s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 9.172024250030518s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 14.299691200256348s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.25038838386536s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 2.0267152786254883s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.32247042655944824s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 7.358407258987427s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.3949398994445801s
License | MR license check for Smart Points Of Interest @PSNC took 0.9075000286102295s
License | HR license check for Smart Points Of Interest @PSNC took 300.196142911911s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.20649147033691406s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 2.82743239402771s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 1.073486089706421s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.5562982559204102s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.19079256057739258s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.24577927589416504s
Performance | Throughput check for Smart Points Of Interest @PSNC took 11.408015012741089s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 8.225440979003906e-05s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.18395614624023438s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.21651697158813477s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.4732534885406494s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.4258918762207031s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 4.383091688156128s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.4995272159576416s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.25501489639282227s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 149.5388662815094s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.18320012092590332s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.4276580810546875s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.41379833221435547s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 46.93937397003174s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.7026729583740234s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.8044838905334473s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.21374988555908203s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 87.02973508834839s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.6212739944458s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 28.58093762397766s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.5049552917480469s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 87.62180781364441s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.7743403911590576s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.5139882564544678s
Security | Sign check for Smart Points Of Interest @PSNC took 1.5717120170593262s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 9.233614206314087s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.5311977863311768s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.021962642669677734s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.0001666545867919922s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 2.6226043701171875e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 1.0728836059570312e-05s
INFO | --- Analysis for Smart_POI_dataset took 2256.7314777374268s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 5.204306125640869s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0007333755493164062s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.4103224277496338s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.02122187614440918s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.647804260253906e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 1.0728836059570312e-05s
INFO | --- Analysis for smartlink took 13.755779504776001s
Availability | SPARQL endpoint availability check for SNIK took 0.44237351417541504s
Availability | VoID file availability check for SNIK took 0.0004942417144775391s
Extra | Recovery of all triples for SNIK took 3.8911352157592773s
Performance | Total latancy measurement for SNIK took 0.9761407375335693s
Amount of data | Number of triples check for SNIK took 0.20070719718933105s
Interoperability | New terms check for SNIK took 1.5206398963928223s
Versatility | Languages check for SNIK took 0.2839164733886719s
Interpretability | Number of blank nodes check for SNIK took 0.20554423332214355s
Interpretability | RDF structures check for SNIK took 0.24585723876953125s
Versatility | Serialization formats check for SNIK took 0.19524550437927246s
Availability | RDF dump link check for SNIK took 0.18178606033325195s
License | MR license check for SNIK took 0.2364671230316162s
License | HR license check for SNIK took 0.23015499114990234s
Amount of data | Number of property check for SNIK took 0.20583224296569824s
Understandability | Number of label check for SNIK took 0.264080286026001s
Understandability | URI regex check for SNIK took 0.3896803855895996s
Understandability | Vocabs check for SNIK took 0.20005154609680176s
Verifiability | Authors check for SNIK took 0.21109390258789062s
Verifiability | Publishers check for SNIK took 0.18853306770324707s
Performance | Throughput check for SNIK took 11.294970273971558s
Amount of data | Check the number of entities for SNIK took 8.916854858398438e-05s
Verifiability | Contribs. check for SNIK took 0.19678544998168945s
Interlinking | sameAs chians check for SNIK took 0.20285940170288086s
Interlinking | skos check for SNIK took 0.18381810188293457s
Interlinking | skos check for SNIK took 0.19883370399475098s
Timeliness | dataset update frequency check for SNIK took 0.1999666690826416s
Currency | Creation date check for SNIK took 0.39176177978515625s
Currency | Modification date check for SNIK took 0.4051480293273926s
Rep.Conc. | URIs length for SNIK took 1.5743179321289062s
Interoperability | New vocabularies check for SNIK took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.18642354011535645s
Accuracy | Check Functional Property for SNIK took 0.19635939598083496s
Accuracy | Check Inverse Functional Property for SNIK took 0.1983642578125s
Accuracy | Check Empty annotation labels for SNIK took 0.6901545524597168s
Accuracy | Check White space in annotation for SNIK took 0.02750086784362793s
Accuracy | Check Datatype consistency for SNIK took 0.2260599136352539s
Consistency | Disjoint class check for SNIK took 0.1799180507659912s
Consistency | Check Misplaced properties for SNIK took 0.7507455348968506s
Consistency | Misplaced classes for SNIK took 0.686164140701294s
Consistency | Check Ontology hijacking for SNIK took 1.85233473777771s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.3301517963409424s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.5868077278137207s
Conciseness | Check Extensional conciseness for SNIK took 0.15583014488220215s
Conciseness | Check Intensional conciseness for SNIK took 0.321882963180542s
Security | Sign check for SNIK took 0.23461246490478516s
Availability | Check URIs Dereferenciability for SNIK took 9682.637244462967s
Completeness | Calculation of interlinking completeness for SNIK took 0.8632807731628418s
Reputation | Calculation of the PageRank for SNIK took 0.2583162784576416s
Interlinking | Calculation of Degree of Connection for SNIK took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0008223056793212891s
Interlinking | Calculation of Clustering coefficient for SNIK took 8.58306884765625e-05s
Interoperability | Check the re-using of existing vocabs for SNIK took 1.6689300537109375e-06s
Believability | Calculation of trust value for SNIK took 1.0967254638671875e-05s
INFO | --- Analysis for snik took 10069.252247571945s
Availability | SPARQL endpoint availability check for SocialLink took 0.201246976852417s
Availability | VoID file availability check for SocialLink took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for SocialLink took 0.3758246898651123s
Reputation | Calculation of the PageRank for SocialLink took 0.020925521850585938s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for SocialLink took 8.535385131835938e-05s
Believability | Calculation of trust value for SocialLink took 1.1205673217773438e-05s
INFO | --- Analysis for SocialLink took 4.543269634246826s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 9.918212890625e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.36279964447021484s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.020940303802490234s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.528594970703125e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 1.0967254638671875e-05s
INFO | --- Analysis for SocialRoles took 11.410462141036987s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.2196338176727295s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0007195472717285156s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 17.10071301460266s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.4784369468688965s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.21712398529052734s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.6208643913269043s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.37077951431274414s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.18002796173095703s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.35689878463745117s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.12194991111755371s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.1305081844329834s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.7448022365570068s
License | MR license check for Social Semantic Web Thesaurus took 0.12332987785339355s
License | HR license check for Social Semantic Web Thesaurus took 0.11712050437927246s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.1132802963256836s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.11545753479003906s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.18304920196533203s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.11974382400512695s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.1313478946685791s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.12140679359436035s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.61338472366333s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 8.416175842285156e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.12179327011108398s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.11321663856506348s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.12207341194152832s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.09735822677612305s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.08897042274475098s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.17847824096679688s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.21885037422180176s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.9397799968719482s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 2.7842633724212646s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.12070274353027344s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.07934308052062988s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.09426736831665039s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.4799838066101074s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012387275695800781s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.08866000175476074s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.30666208267211914s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.08241486549377441s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.1775527000427246s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.5872015953063965s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.00016260147094726562s
Security | Sign check for Social Semantic Web Thesaurus took 0.07938241958618164s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 115.99482560157776s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.3410370349884033s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.021498441696166992s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.799003601074219e-05s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 3.7915422916412354s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.4781951904296875e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 570.3501205444336s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5479199886322021s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0005609989166259766s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 100.31066489219666s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.0334148406982422s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.005424499511719s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 14.404427766799927s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.22770833969116s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.219381093978882s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3220219612121582s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.308969259262085s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3338174819946289s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.8796937465667725s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.2576355934143s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21715283393859863s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.2588605880737305s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.084360122680664s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5826051235198975s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20147299766540527s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.26188206672668457s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.418676376342773s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.344650268554688e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18584823608398438s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20229005813598633s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4806797504425049s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.419677734375s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.366625070571899s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4941260814666748s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.23398256301879883s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 142.73641395568848s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18195343017578125s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.46207118034362793s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4419534206390381s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 42.60665440559387s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.692413091659546s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.803229331970215s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.194838285446167s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 85.73549389839172s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.66691780090332s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 33.90263915061951s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.5174274444580078s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 86.8492739200592s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.791625738143921s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5077917575836182s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.533189058303833s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 10.627247095108032s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.6370759010314941s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.02296733856201172s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0008256435394287109s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.1484832763671875e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.0994415283203125e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.621246337890625e-05s
INFO | --- Analysis for Soil_maps took 2256.937238931656s
Availability | SPARQL endpoint availability check for terrorrist ontology took 5.459785461425781e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.3403763771057129s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.02117609977722168s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0008349418640136719s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.719329833984375e-05s
Believability | Calculation of trust value for terrorrist ontology took 1.7881393432617188e-05s
INFO | --- Analysis for somya_omer took 3.6260838508605957s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.935264587402344e-05s
Availability | VoID file availability check for Sonclubcx took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.3535177707672119s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020849227905273438s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.33514404296875e-05s
Believability | Calculation of trust value for Sonclubcx took 1.52587890625e-05s
INFO | --- Analysis for sonclubcx took 4.3047919273376465s
Availability | SPARQL endpoint availability check for SORS took 0.000125885009765625s
Availability | VoID file availability check for SORS took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for SORS took 0.4106299877166748s
Reputation | Calculation of the PageRank for SORS took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for SORS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for SORS took 5.1021575927734375e-05s
Believability | Calculation of trust value for SORS took 1.049041748046875e-05s
INFO | --- Analysis for sors took 13.458248615264893s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 0.00013327598571777344s
Availability | VoID file availability check for southampton-ac-uk took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.3436861038208008s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.026096582412719727s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0010066032409667969s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 0.00012803077697753906s
Believability | Calculation of trust value for southampton-ac-uk took 1.4781951904296875e-05s
INFO | --- Analysis for southampton-ac-uk took 4.652824640274048s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.75071382522583s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0007903575897216797s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.3237471580505371s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.020966768264770508s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.266334533691406e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 1.1682510375976562e-05s
INFO | --- Analysis for southampton-ac-uk-apps took 12.466231107711792s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 0.00010251998901367188s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.33730363845825195s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.02124643325805664s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.775161743164062e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.5497207641601562e-05s
INFO | --- Analysis for southampton-ecs-eprints took 3.224294424057007s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.516895055770874s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0005581378936767578s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 160.70439624786377s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.218566656112671s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.315999984741211s
Interoperability | New terms check for Spanish Linguistic Datasets took 3.259392023086548s
Versatility | Languages check for Spanish Linguistic Datasets took 44.767627477645874s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.1701335906982422s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.14507770538330078s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.2882511615753174s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.2934558391571045s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.28579139709472656s
License | MR license check for Spanish Linguistic Datasets took 0.27100634574890137s
License | HR license check for Spanish Linguistic Datasets took 0.3883645534515381s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.27269721031188965s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.323519229888916s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.5555012226104736s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.3050730228424072s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.30293989181518555s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.2872452735900879s
Performance | Throughput check for Spanish Linguistic Datasets took 11.207222700119019s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 8.249282836914062e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.28649234771728516s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.30067920684814453s
Interlinking | skos check for Spanish Linguistic Datasets took 0.28735780715942383s
Interlinking | skos check for Spanish Linguistic Datasets took 0.21491289138793945s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.3061027526855469s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5693516731262207s
Currency | Modification date check for Spanish Linguistic Datasets took 0.57723069190979s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 61.050480127334595s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.2948429584503174s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.2885258197784424s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.277240514755249s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.9945480823516846s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010370016098022461s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.7594010829925537s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.28012657165527344s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.7102720737457275s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.81241750717163s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 45.23042154312134s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.6182091236114502s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.842979907989502s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.9660115242004395s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.30732297897338867s
Security | Sign check for Spanish Linguistic Datasets took 0.2758629322052002s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 9.806084632873535s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.7608456611633301s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.02160358428955078s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 2.6226043701171875e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 1.9550323486328125e-05s
INFO | --- Analysis for spanish-linguistic-datasets took 417.94549584388733s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.08353376388549805s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.324310302734375s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.021151304244995117s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.839897155761719e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 1.5020370483398438e-05s
INFO | --- Analysis for sparql-endpoint-status took 3.4654245376586914s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.887580871582031e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.3297288417816162s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.021091461181640625s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 9.1552734375e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 1.5020370483398438e-05s
INFO | --- Analysis for springernaturescigraph took 3.5916731357574463s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 9.632110595703125e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.377504825592041s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.02126908302307129s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.170967102050781e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.0728836059570312e-05s
INFO | --- Analysis for srcmf took 7.8919150829315186s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.34268617630004883s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0005471706390380859s
Extra | Recovery of all triples for Lexicon of Syntactic and Semantic Framework took 1.0062708854675293s
Performance | Total latancy measurement for Lexicon of Syntactic and Semantic Framework took 0.7444331645965576s
Amount of data | Number of triples check for Lexicon of Syntactic and Semantic Framework took 0.1445462703704834s
Interoperability | New terms check for Lexicon of Syntactic and Semantic Framework took 1.4546220302581787s
Versatility | Languages check for Lexicon of Syntactic and Semantic Framework took 0.17355895042419434s
Interpretability | Number of blank nodes check for Lexicon of Syntactic and Semantic Framework took 0.15239310264587402s
Security | Check HTTPS for Lexicon of Syntactic and Semantic Framework took 0.10162854194641113s
Interpretability | RDF structures check for Lexicon of Syntactic and Semantic Framework took 0.15329623222351074s
Versatility | Serialization formats check for Lexicon of Syntactic and Semantic Framework took 0.16254043579101562s
Availability | RDF dump link check for Lexicon of Syntactic and Semantic Framework took 0.15061354637145996s
License | MR license check for Lexicon of Syntactic and Semantic Framework took 0.17589354515075684s
License | HR license check for Lexicon of Syntactic and Semantic Framework took 0.14747953414916992s
Amount of data | Number of property check for Lexicon of Syntactic and Semantic Framework took 0.1404261589050293s
Understandability | Number of label check for Lexicon of Syntactic and Semantic Framework took 0.1596238613128662s
Understandability | URI regex check for Lexicon of Syntactic and Semantic Framework took 0.3216519355773926s
Understandability | Vocabs check for Lexicon of Syntactic and Semantic Framework took 0.1352553367614746s
Verifiability | Authors check for Lexicon of Syntactic and Semantic Framework took 0.14136910438537598s
Verifiability | Publishers check for Lexicon of Syntactic and Semantic Framework took 0.1522982120513916s
Performance | Throughput check for Lexicon of Syntactic and Semantic Framework took 10.58540415763855s
Amount of data | Check the number of entities for Lexicon of Syntactic and Semantic Framework took 7.987022399902344e-05s
Verifiability | Contribs. check for Lexicon of Syntactic and Semantic Framework took 0.1410386562347412s
Interlinking | sameAs chians check for Lexicon of Syntactic and Semantic Framework took 0.15441393852233887s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.17586398124694824s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.17427992820739746s
Timeliness | dataset update frequency check for Lexicon of Syntactic and Semantic Framework took 0.16499614715576172s
Currency | Creation date check for Lexicon of Syntactic and Semantic Framework took 0.3116738796234131s
Currency | Modification date check for Lexicon of Syntactic and Semantic Framework took 0.30956339836120605s
Rep.Conc. | URIs length for Lexicon of Syntactic and Semantic Framework took 0.5190236568450928s
Interoperability | New vocabularies check for Lexicon of Syntactic and Semantic Framework took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Lexicon of Syntactic and Semantic Framework took 0.15015172958374023s
Accuracy | Check Functional Property for Lexicon of Syntactic and Semantic Framework took 0.15276145935058594s
Accuracy | Check Inverse Functional Property for Lexicon of Syntactic and Semantic Framework took 0.15462613105773926s
Accuracy | Check Empty annotation labels for Lexicon of Syntactic and Semantic Framework took 0.14355778694152832s
Accuracy | Check White space in annotation for Lexicon of Syntactic and Semantic Framework took 0.00030517578125s
Accuracy | Check Datatype consistency for Lexicon of Syntactic and Semantic Framework took 0.033263206481933594s
Consistency | Disjoint class check for Lexicon of Syntactic and Semantic Framework took 0.16292262077331543s
Consistency | Check Misplaced properties for Lexicon of Syntactic and Semantic Framework took 0.29967665672302246s
Consistency | Misplaced classes for Lexicon of Syntactic and Semantic Framework took 0.21149182319641113s
Consistency | Check Ontology hijacking for Lexicon of Syntactic and Semantic Framework took 1.557382583618164s
Consistency | Check Invalid usage of undefined classes for Lexicon of Syntactic and Semantic Framework took 1.3535244464874268s
Consistency | Check Invalid usage of undefined properties for Lexicon of Syntactic and Semantic Framework took 1.5113859176635742s
Conciseness | Check Extensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.020662546157836914s
Conciseness | Check Intensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.1627664566040039s
Security | Sign check for Lexicon of Syntactic and Semantic Framework took 0.1549685001373291s
Availability | Check URIs Dereferenciability for Lexicon of Syntactic and Semantic Framework took 270.45213866233826s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.3759279251098633s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.021306514739990234s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 5.936622619628906e-05s
Interoperability | Check the re-using of existing vocabs for Lexicon of Syntactic and Semantic Framework took 1.9073486328125e-06s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 1.430511474609375e-05s
INFO | --- Analysis for ssf took 312.7761676311493s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 5.0067901611328125e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0007402896881103516s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.3250911235809326s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.020975112915039062s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007605552673339844s
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 9.775161743164062e-06s
INFO | --- Analysis for st-andrews-resource-lists took 4.393936395645142s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 5.340576171875e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.29702186584472656s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.021012306213378906s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.910064697265625e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 9.775161743164062e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 3.696396589279175s
Availability | SPARQL endpoint availability check for Stammbuch took 5.6743621826171875e-05s
Availability | VoID file availability check for Stammbuch took 0.00041103363037109375s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.3304097652435303s
Reputation | Calculation of the PageRank for Stammbuch took 0.021442174911499023s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 3.5762786865234375e-05s
Believability | Calculation of trust value for Stammbuch took 1.4781951904296875e-05s
INFO | --- Analysis for Stammbuch took 3.1144402027130127s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.3688559532165527s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.45627760887145996s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.028523921966552734s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0014340877532958984s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.0001361370086669922s
Believability | Calculation of trust value for statistics.data.gov.uk took 1.0728836059570312e-05s
INFO | --- Analysis for statistics-data-gov-uk took 5.065813779830933s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.863739013671875e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.35183167457580566s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.021083354949951172s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00011181831359863281s
Believability | Calculation of trust value for statusnet-1w6-org took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-1w6-org took 4.788854360580444s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 9.417533874511719e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.3335001468658447s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.020786523818969727s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.246566772460938e-05s
Believability | Calculation of trust value for statusnet-20100-org took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-20100-org took 3.174618721008301s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 0.0001468658447265625s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.3446371555328369s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.021758556365966797s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 7.581710815429688e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-alexandrefranke-com took 3.603524684906006s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 5.7697296142578125e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.346250057220459s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.022289037704467773s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0008141994476318359s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 9.059906005859375e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 1.6450881958007812e-05s
INFO | --- Analysis for statusnet-atari-frosch-de took 3.402174711227417s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 0.0001556873321533203s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0007615089416503906s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.35872793197631836s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.022163867950439453s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.417533874511719e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-belfalas-org took 3.3808071613311768s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 0.00010848045349121094s
Availability | VoID file availability check for statusnet-bka-li took 0.000720977783203125s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.3324148654937744s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00011348724365234375s
Believability | Calculation of trust value for statusnet-bka-li took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-bka-li took 13.351969957351685s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.37254929542541504s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.020979881286621094s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.981590270996094e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 4.393125057220459s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 5.14984130859375e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.000637054443359375s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.34317851066589355s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.021800518035888672s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 5.555152893066406e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-ced117-net took 4.778505325317383s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 0.00010347366333007812s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.35573506355285645s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.021236658096313477s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.7220458984375e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 1.5735626220703125e-05s
INFO | --- Analysis for statusnet-chickenkiller-com took 3.4511401653289795s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 9.632110595703125e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.3354959487915039s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020802021026611328s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011396408081054688s
Believability | Calculation of trust value for statusnet-chromic-org took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-chromic-org took 3.298926591873169s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 5.1975250244140625e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.34859776496887207s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.021633386611938477s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0008656978607177734s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 9.822845458984375e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 1.430511474609375e-05s
INFO | --- Analysis for statusnet-cooleysekula-net took 6.502906322479248s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 0.00010371208190917969s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.34183168411254883s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.841255187988281e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 1.52587890625e-05s
INFO | --- Analysis for statusnet-coreyavis-com took 3.179497718811035s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 5.125999450683594e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.3071775436401367s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.021610260009765625s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 7.510185241699219e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.951204538345337s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 0.00011849403381347656s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.7111110687255859s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.021879911422729492s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010704994201660156s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 1.621246337890625e-05s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 3.878966808319092s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 0.00010037422180175781s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.38008809089660645s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.021097660064697266s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.461143493652344e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 1.5497207641601562e-05s
INFO | --- Analysis for statusnet-deuxpi-ca took 3.187143325805664s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 0.00018906593322753906s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.3618326187133789s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.021175861358642578s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.340576171875e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-doomicile-de took 5.249218225479126s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.32319164276123047s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.021453142166137695s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0008540153503417969s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.604194641113281e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 1.71661376953125e-05s
INFO | --- Analysis for statusnet-dtdns-net took 3.396536350250244s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 0.00010466575622558594s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.35475754737854004s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.02090311050415039s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.838539123535156e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 1.71661376953125e-05s
INFO | --- Analysis for statusnet-equestriarp-net took 3.2016468048095703s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 0.00010848045349121094s
Availability | VoID file availability check for statusnet-exdc-net took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.3633580207824707s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.022393226623535156s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.486343383789062e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-exdc-net took 3.3298287391662598s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 7.963180541992188e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.3488922119140625s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.02132415771484375s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.322166442871094e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-fcac-com took 3.5764975547790527s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 0.00010466575622558594s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0013453960418701172s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.3015115261077881s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.022670269012451172s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 6.008148193359375e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 1.5735626220703125e-05s
INFO | --- Analysis for statusnet-fcestrada-com took 3.8756601810455322s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 0.00010204315185546875s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.3278791904449463s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.02076125144958496s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00018358230590820312s
Believability | Calculation of trust value for statusnet-fragdev-com took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-fragdev-com took 4.073756694793701s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 0.00010132789611816406s
Availability | VoID file availability check for statusnet-freelish-us took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.3494236469268799s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.02124929428100586s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.963180541992188e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 1.621246337890625e-05s
INFO | --- Analysis for statusnet-freelish-us took 4.719926357269287s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 9.584426879882812e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0007843971252441406s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.40044689178466797s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.0209505558013916s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010752677917480469s
Believability | Calculation of trust value for statusnet-gegeweb-org took 1.52587890625e-05s
INFO | --- Analysis for statusnet-gegeweb-org took 3.6356618404388428s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 5.1021575927734375e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.36290407180786133s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.02123427391052246s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 7.271766662597656e-05s
Believability | Calculation of trust value for statusnet-glou-org took 1.5735626220703125e-05s
INFO | --- Analysis for statusnet-glou-org took 3.287623882293701s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.935264587402344e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.38264989852905273s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.02087259292602539s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.0001342296600341797s
Believability | Calculation of trust value for statusnet-gomertronic-com took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-gomertronic-com took 3.1945176124572754s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 0.0001723766326904297s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.342498779296875s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.020946025848388672s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 2.765655517578125e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010657310485839844s
Believability | Calculation of trust value for statusnet-hackerposse-com took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-hackerposse-com took 3.4671003818511963s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 0.00010895729064941406s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.33535265922546387s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.02102828025817871s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.001256704330444336s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 7.367134094238281e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-hii-co-il took 4.1911327838897705s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 0.00010275840759277344s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.3490934371948242s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.020948410034179688s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.179115295410156e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.3378095626831055s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 5.435943603515625e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.4513680934906006s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.022806644439697266s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0012798309326171875s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 9.250640869140625e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-imirhil-fr took 3.3251304626464844s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 5.435943603515625e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.32485413551330566s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.023171186447143555s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 5.269050598144531e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-integralblue-com took 3.3394107818603516s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 9.655952453613281e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0007901191711425781s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.35688018798828125s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.02119612693786621s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 6.4849853515625e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 1.5974044799804688e-05s
INFO | --- Analysis for statusnet-johndrinkwater-name took 23.047294855117798s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.37125563621520996s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.021120548248291016s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0008096694946289062s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.000125885009765625s
Believability | Calculation of trust value for statusnet-jonkman-ca took 3.528594970703125e-05s
INFO | --- Analysis for statusnet-jonkman-ca took 4.069892406463623s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.935264587402344e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.32184338569641113s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.021730899810791016s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0008649826049804688s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 0.00011205673217773438s
Believability | Calculation of trust value for statusnet-kaimi-cc took 1.5735626220703125e-05s
INFO | --- Analysis for statusnet-kaimi-cc took 3.122596025466919s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 0.00010943412780761719s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.3349645137786865s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.021077871322631836s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 6.67572021484375e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 1.621246337890625e-05s
INFO | --- Analysis for statusnet-kathryl-fr took 3.196047067642212s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 0.00010323524475097656s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.3493046760559082s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.02100396156311035s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 4.3392181396484375e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 1.6450881958007812e-05s
INFO | --- Analysis for statusnet-kenzoid-com took 4.379905939102173s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 5.14984130859375e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.3397858142852783s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.021200180053710938s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0008466243743896484s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 8.58306884765625e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-keuser-fr took 3.5968151092529297s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 7.653236389160156e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.3628220558166504s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.02249884605407715s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0008990764617919922s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 5.817413330078125e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 1.52587890625e-05s
INFO | --- Analysis for statusnet-ldn-fai-net took 3.2966270446777344s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 5.412101745605469e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.3318338394165039s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.021869897842407227s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.151199340820312e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-lebsanft-org took 3.2788307666778564s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 5.3882598876953125e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.30062341690063477s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020834684371948242s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.679794311523438e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.5497207641601562e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 3.728217363357544s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 5.030632019042969e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.3580961227416992s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.0209197998046875s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011515617370605469s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-linuxwrangling-com took 3.1726577281951904s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.839897155761719e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0007975101470947266s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.4936411380767822s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02098989486694336s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.626678466796875e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-ludost-net took 4.6519927978515625s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 5.340576171875e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0007750988006591797s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.32801079750061035s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.020945072174072266s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 0.00010752677917480469s
Believability | Calculation of trust value for statusnet-lydiastench-com took 1.5497207641601562e-05s
INFO | --- Analysis for statusnet-lydiastench-com took 3.2312657833099365s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 0.00010156631469726562s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.37391233444213867s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.02070331573486328s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.412101745605469e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 4.150140762329102s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 0.00012063980102539062s
Availability | VoID file availability check for statusnet-macno-org took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.29671239852905273s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020943403244018555s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.0001513957977294922s
Believability | Calculation of trust value for statusnet-macno-org took 1.4066696166992188e-05s
INFO | --- Analysis for statusnet-macno-org took 3.1312100887298584s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 0.00010275840759277344s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.3653542995452881s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.020896434783935547s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.556510925292969e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 3.347882032394409s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 0.00013756752014160156s
Availability | VoID file availability check for statusnet-maymay-net took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.45990777015686035s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.02083301544189453s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.130073547363281e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 1.52587890625e-05s
INFO | --- Analysis for statusnet-maymay-net took 43.45876431465149s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 5.841255187988281e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.3880898952484131s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.020730257034301758s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.0001704692840576172s
Believability | Calculation of trust value for statusnet-morphtown-de took 1.52587890625e-05s
INFO | --- Analysis for statusnet-morphtown-de took 3.2949392795562744s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.863739013671875e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.35717201232910156s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.02245783805847168s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 0.000102996826171875s
Believability | Calculation of trust value for statusnet-mrblog-nl took 1.6450881958007812e-05s
INFO | --- Analysis for statusnet-mrblog-nl took 3.104321241378784s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 9.989738464355469e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.31969380378723145s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.745887756347656e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-mulestable-net took 3.748138904571533s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 8.106231689453125e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.3416883945465088s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.022719860076904297s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.316734313964844e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.6689300537109375e-05s
INFO | --- Analysis for statusnet-my-status-tk took 3.2654693126678467s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.673004150390625e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.3229258060455322s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00011563301086425781s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-opensim-chat-eu took 3.1167097091674805s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 0.00017452239990234375s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.3482496738433838s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.021110057830810547s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 6.651878356933594e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-orangeseeds-org took 3.478118896484375s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 0.00010776519775390625s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.29897046089172363s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.0207674503326416s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.604194641113281e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 1.5974044799804688e-05s
INFO | --- Analysis for statusnet-otbm-fr took 3.39428448677063s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 0.00010704994201660156s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.4124913215637207s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.02273106575012207s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.845329284667969e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 3.2799489498138428s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 0.00010037422180175781s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0007290840148925781s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.706362247467041s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.021676301956176758s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 5.245208740234375e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 1.5735626220703125e-05s
INFO | --- Analysis for statusnet-panda-id-au took 4.463399410247803s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 5.14984130859375e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.37158823013305664s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.021480083465576172s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 0.00010585784912109375s
Believability | Calculation of trust value for statusnet-piana-eu took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-piana-eu took 3.0752711296081543s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 6.246566772460938e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.3722872734069824s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.022609233856201172s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.677078247070312e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 1.621246337890625e-05s
INFO | --- Analysis for statusnet-planet-libre-org took 3.336793899536133s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 0.00010037422180175781s
Availability | VoID file availability check for statusnet-postblue-info took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.3231499195098877s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.021152496337890625s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00023651123046875s
Believability | Calculation of trust value for statusnet-postblue-info took 1.5974044799804688e-05s
INFO | --- Analysis for statusnet-postblue-info took 3.549389600753784s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 0.00011205673217773438s
Availability | VoID file availability check for statusnet-progval-net took 0.0006899833679199219s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.33861279487609863s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.02325129508972168s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 7.176399230957031e-05s
Believability | Calculation of trust value for statusnet-progval-net took 1.52587890625e-05s
INFO | --- Analysis for statusnet-progval-net took 23.217747449874878s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 0.000102996826171875s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.3211944103240967s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.0213620662689209s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00011801719665527344s
Believability | Calculation of trust value for statusnet-qdnx-org took 1.6689300537109375e-05s
INFO | --- Analysis for statusnet-qdnx-org took 3.6119701862335205s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 7.295608520507812e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0007998943328857422s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.3262600898742676s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020930051803588867s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.4849853515625e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-qth-fr took 5.7589452266693115s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 0.00010514259338378906s
Availability | VoID file availability check for statusnet-quitter-se took 0.0008907318115234375s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.32402944564819336s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020877361297607422s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.0002281665802001953s
Believability | Calculation of trust value for statusnet-quitter-se took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-quitter-se took 6.4260101318359375s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.9114227294921875e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.36362314224243164s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.021137475967407227s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010609626770019531s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.52587890625e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 3.6877315044403076s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.863739013671875e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0007679462432861328s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.3751368522644043s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.021111726760864258s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.52587890625e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 6.198883056640625e-05s
Believability | Calculation of trust value for statusnet-recit-org took 1.52587890625e-05s
INFO | --- Analysis for statusnet-recit-org took 13.744903802871704s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 0.00014281272888183594s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.3827812671661377s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.02108025550842285s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.0001583099365234375s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.5974044799804688e-05s
INFO | --- Analysis for statusnet-russwurm-org took 4.165940046310425s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 0.00010156631469726562s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.3239476680755615s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020920276641845703s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.559226989746094e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.52587890625e-05s
INFO | --- Analysis for statusnet-samnoble-org took 5.3188416957855225s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 5.602836608886719e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0004169940948486328s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.33898115158081055s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.021535634994506836s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 9.202957153320312e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 1.8835067749023438e-05s
INFO | --- Analysis for statusnet-schiessle-org took 3.3100836277008057s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 5.984306335449219e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.3489224910736084s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.021119356155395508s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 0.00010013580322265625s
Believability | Calculation of trust value for statusnet-scoffoni-net took 1.5497207641601562e-05s
INFO | --- Analysis for statusnet-scoffoni-net took 3.0581181049346924s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.3034839630126953s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.022672176361083984s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0008466243743896484s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 7.367134094238281e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 1.5735626220703125e-05s
INFO | --- Analysis for statusnet-sebseb01-net took 3.101445436477661s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 9.846687316894531e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0012607574462890625s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.33083200454711914s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.022409439086914062s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.462501525878906e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 1.5497207641601562e-05s
INFO | --- Analysis for statusnet-shnoulle-net took 3.7739369869232178s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 0.00010061264038085938s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.3296694755554199s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.0213162899017334s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00021648406982421875s
Believability | Calculation of trust value for statusnet-skilledtests-com took 1.4543533325195312e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 3.737037181854248s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 0.00010466575622558594s
Availability | VoID file availability check for statusnet-somsants-net took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.3422975540161133s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.02103567123413086s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010943412780761719s
Believability | Calculation of trust value for statusnet-somsants-net took 1.5497207641601562e-05s
INFO | --- Analysis for statusnet-somsants-net took 3.039003849029541s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.6253204345703125e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0006346702575683594s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.3106226921081543s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.021013736724853516s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00014209747314453125s
Believability | Calculation of trust value for statusnet-soucy-cc took 1.5974044799804688e-05s
INFO | --- Analysis for statusnet-soucy-cc took 4.833785772323608s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 9.393692016601562e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.36164331436157227s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.021076440811157227s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.318092346191406e-05s
Believability | Calculation of trust value for statusnet-spip-org took 1.52587890625e-05s
INFO | --- Analysis for statusnet-spip-org took 4.161285400390625s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 6.67572021484375e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.34349775314331055s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.021089792251586914s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.508827209472656e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 1.811981201171875e-05s
INFO | --- Analysis for statusnet-spraci-org took 6.085342884063721s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 7.43865966796875e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.3234117031097412s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.0209658145904541s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00011467933654785156s
Believability | Calculation of trust value for statusnet-ssweeny-net took 1.4781951904296875e-05s
INFO | --- Analysis for statusnet-ssweeny-net took 6.308800935745239s
Availability | SPARQL endpoint availability check for statusnet-status-net took 5.054473876953125e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.3418142795562744s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.0211029052734375s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00023365020751953125s
Believability | Calculation of trust value for statusnet-status-net took 1.5974044799804688e-05s
INFO | --- Analysis for statusnet-status-net took 4.120493412017822s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 0.00010704994201660156s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.3600742816925049s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.02103447914123535s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.888938903808594e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 3.626614570617676s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 0.00011038780212402344s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.306443452835083s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.021260499954223633s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.72747802734375e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-tekk-com-ar took 3.2036454677581787s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 5.340576171875e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0003066062927246094s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.33628106117248535s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.021032094955444336s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00012612342834472656s
Believability | Calculation of trust value for statusnet-thelovebug-org took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-thelovebug-org took 3.348133087158203s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 0.00011444091796875s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.3103444576263428s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.02121424674987793s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.557868957519531e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-thornton2-com took 5.656233549118042s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 6.794929504394531e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0007014274597167969s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.3491640090942383s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.021131277084350586s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00011396408081054688s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 1.621246337890625e-05s
INFO | --- Analysis for statusnet-timttmy-co-uk took 3.4380085468292236s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 5.3882598876953125e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0006470680236816406s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.31923913955688477s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0008585453033447266s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 4.76837158203125e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 1.5735626220703125e-05s
INFO | --- Analysis for statusnet-tl1n-com took 4.355101585388184s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 9.799003601074219e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.39876604080200195s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.022269487380981445s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 7.009506225585938e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 1.6450881958007812e-05s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 3.6303935050964355s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 8.20159912109375e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.35057663917541504s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020818471908569336s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.933906555175781e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 1.6689300537109375e-05s
INFO | --- Analysis for statusnet-uni-siegen-de took 4.175985813140869s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 0.00010251998901367188s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.3745710849761963s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.024715662002563477s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0023293495178222656s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 6.794929504394531e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 1.5735626220703125e-05s
INFO | --- Analysis for steak took 3.59305739402771s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 5.1021575927734375e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.4974968433380127s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.021755218505859375s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.7220458984375e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 1.5735626220703125e-05s
INFO | --- Analysis for stitch-rameau took 5.333876609802246s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.8159284591674805s
Availability | VoID file availability check for Stone Tech Square took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.4090754985809326s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.02133464813232422s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.430511474609375e-05s
Believability | Calculation of trust value for Stone Tech Square took 1.4543533325195312e-05s
INFO | --- Analysis for stone-tech-square-data took 8.159469366073608s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.4739401340484619s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0005574226379394531s
Extra | Recovery of all triples for STW Thesaurus for Economics took 18.501205921173096s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.1522588729858398s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.659529447555542s
Interoperability | New terms check for STW Thesaurus for Economics took 1.7376718521118164s
Versatility | Languages check for STW Thesaurus for Economics took 1.6540164947509766s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.5549087524414062s
Security | Check HTTPS for STW Thesaurus for Economics took 0.14833545684814453s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.2604494094848633s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.23679041862487793s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.25067615509033203s
License | MR license check for STW Thesaurus for Economics took 0.25957536697387695s
License | HR license check for STW Thesaurus for Economics took 2.5382914543151855s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.24979448318481445s
Understandability | Number of label check for STW Thesaurus for Economics took 0.6864778995513916s
Understandability | URI regex check for STW Thesaurus for Economics took 0.5011646747589111s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.25389838218688965s
Verifiability | Authors check for STW Thesaurus for Economics took 0.2694377899169922s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.2264089584350586s
Performance | Throughput check for STW Thesaurus for Economics took 11.038440942764282s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.8089690208435059s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.2613034248352051s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.2268378734588623s
Interlinking | skos check for STW Thesaurus for Economics took 0.3914794921875s
Interlinking | skos check for STW Thesaurus for Economics took 0.3103485107421875s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.25031256675720215s
Currency | Creation date check for STW Thesaurus for Economics took 0.4880533218383789s
Currency | Modification date check for STW Thesaurus for Economics took 0.6127564907073975s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 7.707998275756836s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 3.694901466369629s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.24180245399475098s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.2721371650695801s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.2893526554107666s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 6.215718746185303s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0537409782409668s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.4390993118286133s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.2502617835998535s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.3509495258331299s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 1.8336076736450195s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.4672508239746094s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.595587730407715s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6705131530761719s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.25096869468688965s
Security | Sign check for STW Thesaurus for Economics took 0.24459004402160645s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 4.7154576778411865s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.3227958679199219s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.021542787551879883s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00012373924255371094s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 4.400836944580078s
Believability | Calculation of trust value for STW Thesaurus for Economics took 1.049041748046875e-05s
INFO | --- Analysis for stw-thesaurus-for-economics took 109.92494916915894s
Availability | SPARQL endpoint availability check for SudershanTech took 0.00010347366333007812s
Availability | VoID file availability check for SudershanTech took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.35041379928588867s
Reputation | Calculation of the PageRank for SudershanTech took 0.021036863327026367s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.218650817871094e-05s
Believability | Calculation of trust value for SudershanTech took 1.1205673217773438e-05s
INFO | --- Analysis for SudershanTech took 3.246628999710083s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.8146486282348633s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.441953182220459s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.021436214447021484s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 3.695487976074219e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.982948303222656e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 1.0013580322265625e-05s
INFO | --- Analysis for sudocfr took 8.438396453857422s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 1.018667459487915s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0006823539733886719s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 25.85222101211548s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.6749722957611084s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.4591541290283203s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 2.9904842376708984s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 3.090505361557007s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.160440444946289s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5337996482849121s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5326368808746338s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5377323627471924s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5569210052490234s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 7.721152067184448s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.5977804660797119s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.65521240234375s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.058028221130371s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5277302265167236s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.530658483505249s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5417380332946777s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.887619256973267s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 4.076957702636719e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5517551898956299s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5932838916778564s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5998287200927734s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5822396278381348s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.57232666015625s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.0969398021697998s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.1530091762542725s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 39.39592885971069s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5249876976013184s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5562427043914795s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5509746074676514s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 3.1148455142974854s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.3819565773010254s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.5563488006591797s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 30.769742965698242s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.497968673706055s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.4490120410919s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 25.219215631484985s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 3.1187188625335693s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.9130642414093018s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5383710861206055s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4725.786222457886s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.8435707092285156s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.023346900939941406s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 0.0002002716064453125s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 1.9073486328125e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 1.5497207641601562e-05s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 8292.278534650803s
Availability | SPARQL endpoint availability check for Surge Radio took 9.989738464355469e-05s
Availability | VoID file availability check for Surge Radio took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.32610392570495605s
Reputation | Calculation of the PageRank for Surge Radio took 0.021548748016357422s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 9.608268737792969e-05s
Believability | Calculation of trust value for Surge Radio took 1.430511474609375e-05s
INFO | --- Analysis for surge-radio took 4.302154064178467s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 0.00010347366333007812s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0007228851318359375s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.32223939895629883s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.021279573440551758s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.1948089599609375e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 1.6450881958007812e-05s
INFO | --- Analysis for SWAT took 29.199551105499268s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 5.3882598876953125e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.5053820610046387s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.34509944915771484s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.023421287536621094s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 7.081031799316406e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 1.3589859008789062e-05s
INFO | --- Analysis for swedish-open-cultural-heritage took 7.296832084655762s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.250046730041504s
Availability | VoID file availability check for SweFN-RDF took 0.0007395744323730469s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.3677551746368408s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.021198511123657227s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 4.100799560546875e-05s
Believability | Calculation of trust value for SweFN-RDF took 1.5497207641601562e-05s
INFO | --- Analysis for swefn-rdf took 6.952595472335815s
Availability | SPARQL endpoint availability check for SwetoDblp took 0.00010561943054199219s
Availability | VoID file availability check for SwetoDblp took 0.0007808208465576172s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.3510322570800781s
Reputation | Calculation of the PageRank for SwetoDblp took 0.02275562286376953s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.886222839355469e-05s
Believability | Calculation of trust value for SwetoDblp took 1.5735626220703125e-05s
INFO | --- Analysis for sweto-dblp took 23.775308847427368s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.5686933994293213s
Availability | VoID file availability check for Swift Vocabulary took 0.0006701946258544922s
Extra | Recovery of all triples for Swift Vocabulary took 2.4802393913269043s
Performance | Total latancy measurement for Swift Vocabulary took 0.992753267288208s
Amount of data | Number of triples check for Swift Vocabulary took 0.24732518196105957s
Interoperability | New terms check for Swift Vocabulary took 1.5711076259613037s
Versatility | Languages check for Swift Vocabulary took 0.22577190399169922s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.24649500846862793s
Interpretability | RDF structures check for Swift Vocabulary took 0.2520110607147217s
Versatility | Serialization formats check for Swift Vocabulary took 0.22039175033569336s
Availability | RDF dump link check for Swift Vocabulary took 0.1853468418121338s
License | MR license check for Swift Vocabulary took 0.21979236602783203s
License | HR license check for Swift Vocabulary took 0.20346617698669434s
Amount of data | Number of property check for Swift Vocabulary took 0.20227646827697754s
Understandability | Number of label check for Swift Vocabulary took 0.2075824737548828s
Understandability | URI regex check for Swift Vocabulary took 0.38393068313598633s
Understandability | Vocabs check for Swift Vocabulary took 0.2071361541748047s
Verifiability | Authors check for Swift Vocabulary took 0.2010486125946045s
Verifiability | Publishers check for Swift Vocabulary took 0.2167677879333496s
Performance | Throughput check for Swift Vocabulary took 11.625493049621582s
Amount of data | Check the number of entities for Swift Vocabulary took 8.440017700195312e-05s
Verifiability | Contribs. check for Swift Vocabulary took 0.22809576988220215s
Interlinking | sameAs chians check for Swift Vocabulary took 0.2275400161743164s
Interlinking | skos check for Swift Vocabulary took 0.26413512229919434s
Interlinking | skos check for Swift Vocabulary took 0.2614462375640869s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.24691247940063477s
Currency | Creation date check for Swift Vocabulary took 0.5137968063354492s
Currency | Modification date check for Swift Vocabulary took 0.4959287643432617s
Rep.Conc. | URIs length for Swift Vocabulary took 0.8856847286224365s
Interoperability | New vocabularies check for Swift Vocabulary took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.2666811943054199s
Accuracy | Check Functional Property for Swift Vocabulary took 0.22686076164245605s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.26838135719299316s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.39815545082092285s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.003131866455078125s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.037319183349609375s
Consistency | Disjoint class check for Swift Vocabulary took 0.24277329444885254s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.5481441020965576s
Consistency | Misplaced classes for Swift Vocabulary took 0.2742781639099121s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.6767678260803223s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.3554203510284424s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.5540459156036377s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.027984619140625s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.20286011695861816s
Security | Sign check for Swift Vocabulary took 0.1868114471435547s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 964.0259165763855s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.6808300018310547s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.021830081939697266s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 8.511543273925781e-05s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 1.6689300537109375e-06s
Believability | Calculation of trust value for Swift Vocabulary took 1.6689300537109375e-05s
INFO | --- Analysis for Swift took 1014.3196423053741s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 9.655952453613281e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.001352548599243164s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.3964362144470215s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.02104020118713379s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.361701965332031e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 1.52587890625e-05s
INFO | --- Analysis for symptoms-in-chinese took 53.62247586250305s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.30701494216918945s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0006449222564697266s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.4677910804748535s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.8989048004150391s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 7.65987491607666s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 19.037413120269775s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.17799997329711914s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 3.226238489151001s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.11064839363098145s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.1806809902191162s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.17521071434020996s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.17441010475158691s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.19363737106323242s
License | HR license check for National Digital Data Archive of Hungary (partial) took 53.034887075424194s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.433563232421875s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 32.12768197059631s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.36075592041015625s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.17945432662963867s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.17184853553771973s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.1869795322418213s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.751513481140137s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 0.00011539459228515625s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.78316068649292s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.957747459411621s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.841167688369751s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.899878740310669s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.8542935848236084s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 3.555479049682617s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 3.304194450378418s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 64.51517581939697s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.1782073974609375s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.18654680252075195s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.18886637687683105s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.2503342628479004s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0027577877044677734s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.002615690231323242s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.18543148040771484s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 45.28674030303955s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.2502443790435791s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.664478063583374s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.362384557723999s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 47.47814607620239s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002312898635864258s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.2793433666229248s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.17778468132019043s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 9.69732403755188s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.6263523101806641s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.0211489200592041s
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.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 8.940696716308594e-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.5497207641601562e-05s
INFO | --- Analysis for sztaki-lod took 496.59164690971375s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.00019097328186035156s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.38053274154663086s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.02281975746154785s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0010418891906738281s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 6.389617919921875e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 1.430511474609375e-05s
INFO | --- Analysis for t4gm-info took 3.9374749660491943s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.935264587402344e-05s
Availability | VoID file availability check for tags2con delicious took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.3553586006164551s
Reputation | Calculation of the PageRank for tags2con delicious took 0.020954132080078125s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 5.054473876953125e-05s
Believability | Calculation of trust value for tags2con delicious took 1.7642974853515625e-05s
INFO | --- Analysis for tags2con-delicious took 45.389667987823486s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 263.0067865848541s
Availability | VoID file availability check for Taiwan geographic names took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.44705724716186523s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.022013425827026367s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 6.270408630371094e-05s
Believability | Calculation of trust value for Taiwan geographic names took 1.4066696166992188e-05s
INFO | --- Analysis for taiwan-geographic-names took 669.2545154094696s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 0.00012540817260742188s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0007758140563964844s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.3032662868499756s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.021161317825317383s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.989738464355469e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 1.5497207641601562e-05s
INFO | --- Analysis for talis-openlibrary took 4.387937545776367s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.902691125869751s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.3685758113861084s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.021987438201904297s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.0001285076141357422s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 1.5020370483398438e-05s
INFO | --- Analysis for taxonconcept took 16.036146879196167s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 5.936622619628906e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.320354700088501s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.022611141204833984s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.344650268554688e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.5735626220703125e-05s
INFO | --- Analysis for taxonconcept-assets took 3.4933645725250244s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 9.512901306152344e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.32647156715393066s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.020989656448364258s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.316734313964844e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 1.239776611328125e-05s
INFO | --- Analysis for taxonconcept-occurences took 3.5077967643737793s
Availability | SPARQL endpoint availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.056067943572998s
Availability | VoID file availability check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0006113052368164062s
Extra | Recovery of all triples for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 18.033078908920288s
Performance | Total latancy measurement for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.0886788368225098s
Amount of data | Number of triples check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 15.308308601379395s
Interoperability | New terms check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 5.4802515506744385s
Versatility | Languages check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 62.448370933532715s
Interpretability | Number of blank nodes check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 50.2506537437439s
Interpretability | RDF structures check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 6.676891088485718s
Versatility | Serialization formats check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 9.101949214935303s
Availability | RDF dump link check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 2.3235373497009277s
License | MR license check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 4.521470308303833s
License | HR license check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 62.38174104690552s
Amount of data | Number of property check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.39675354957580566s
Understandability | Number of label check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 22.02084517478943s
Understandability | URI regex check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.5140681266784668s
Understandability | Vocabs check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.20304346084594727s
Verifiability | Authors check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.20844054222106934s
Verifiability | Publishers check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.30364012718200684s
Performance | Throughput check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 11.83819031715393s
Amount of data | Check the number of entities for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.023794889450073242s
Verifiability | Contribs. check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.7844064235687256s
Interlinking | sameAs chians check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 8.508906841278076s
Interlinking | skos check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.32160067558288574s
Interlinking | skos check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.7360501289367676s
Timeliness | dataset update frequency check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.7395737171173096s
Currency | Creation date check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.6175398826599121s
Currency | Modification date check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.2547628879547119s
Rep.Conc. | URIs length for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 32.46979999542236s
Interoperability | New vocabularies check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 24.553080558776855s
Consistency | Deprecated classes/propertiers check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.24713659286499023s
Accuracy | Check Functional Property for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 6.733619928359985s
Accuracy | Check Inverse Functional Property for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.503399133682251s
Accuracy | Check Empty annotation labels for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 8.04304838180542s
Accuracy | Check White space in annotation for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.029764652252197266s
Accuracy | Check Datatype consistency for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.029128074645996094s
Consistency | Disjoint class check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.2503237724304199s
Consistency | Check Misplaced properties for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 12.854899883270264s
Consistency | Misplaced classes for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.43779730796813965s
Consistency | Check Ontology hijacking for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 5.498283386230469s
Consistency | Check Invalid usage of undefined classes for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.3634605407714844s
Consistency | Check Invalid usage of undefined properties for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 18.04583978652954s
Conciseness | Check Extensional conciseness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.033559322357177734s
Conciseness | Check Intensional conciseness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.43898963928222656s
Security | Sign check for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 17.244638681411743s
Availability | Check URIs Dereferenciability for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 24.03434681892395s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.4626927375793457s
Reputation | Calculation of the PageRank for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.02325272560119629s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 0.00011610984802246094s
Interoperability | Check the re-using of existing vocabs for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 27.863741397857666s
Believability | Calculation of trust value for TAXREF-LD: Knowledge Graph of the French taxonomic registery took 1.52587890625e-05s
INFO | --- Analysis for taxref-ld took 1312.9257192611694s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 262.32133197784424s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0007352828979492188s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.4017784595489502s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.021258115768432617s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 4.982948303222656e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.52587890625e-05s
INFO | --- Analysis for tcga took 540.7825880050659s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.40358638763427734s
Availability | VoID file availability check for TCGA Roadmap took 0.0007221698760986328s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.3728756904602051s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.02301502227783203s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0008728504180908203s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 8.749961853027344e-05s
Believability | Calculation of trust value for TCGA Roadmap took 1.5497207641601562e-05s
INFO | --- Analysis for tcga-roadmap took 6.685517311096191s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.1869986057281494s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.3553314208984375s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.021105289459228516s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00010967254638671875s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 1.4781951904296875e-05s
INFO | --- Analysis for tcmgenedit_dataset took 137.54415273666382s
Availability | SPARQL endpoint availability check for TDS took 5.221366882324219e-05s
Availability | VoID file availability check for TDS took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for TDS took 0.31798338890075684s
Reputation | Calculation of the PageRank for TDS took 0.021576642990112305s
Interlinking | Calculation of Degree of Connection for TDS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for TDS took 4.482269287109375e-05s
Believability | Calculation of trust value for TDS took 1.33514404296875e-05s
INFO | --- Analysis for tds took 5.973195552825928s
Availability | SPARQL endpoint availability check for TEKORD took 5.316734313964844e-05s
Availability | VoID file availability check for TEKORD took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for TEKORD took 0.28794384002685547s
Reputation | Calculation of the PageRank for TEKORD took 0.021095991134643555s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.57763671875e-05s
Believability | Calculation of trust value for TEKORD took 1.2159347534179688e-05s
INFO | --- Analysis for tekord took 6.350430727005005s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 1.8634710311889648s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0006649494171142578s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.32860255241394043s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.020714998245239258s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.0001087188720703125s
Believability | Calculation of trust value for Telegraphis Linked Data took 7.62939453125e-06s
INFO | --- Analysis for telegraphis took 8.717534303665161s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 0.00015807151794433594s
Availability | VoID file availability check for Temple ov thee Lemur took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.38094544410705566s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.022980451583862305s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0008285045623779297s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.867813110351562e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 1.621246337890625e-05s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 16.524922609329224s
Availability | SPARQL endpoint availability check for Ontology took 0.00017762184143066406s
Availability | VoID file availability check for Ontology took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for Ontology took 0.3457620143890381s
Reputation | Calculation of the PageRank for Ontology took 0.021805763244628906s
Interlinking | Calculation of Degree of Connection for Ontology took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0008571147918701172s
Interlinking | Calculation of Clustering coefficient for Ontology took 4.029273986816406e-05s
Believability | Calculation of trust value for Ontology took 1.52587890625e-05s
INFO | --- Analysis for Terrorist_attack took 3.590388774871826s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 5.1021575927734375e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.3505246639251709s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.023532390594482422s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0013799667358398438s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 4.3392181396484375e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 1.4543533325195312e-05s
INFO | --- Analysis for Terrorist_Attack_1 took 3.2007908821105957s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0006325244903564453s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.3380165100097656s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.021178007125854492s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.337860107421875e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.3828277587890625e-05s
INFO | --- Analysis for Tesla_Deaths took 4.055857181549072s
Availability | SPARQL endpoint availability check for test took 5.53131103515625e-05s
Availability | VoID file availability check for test took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for test took 0.34688687324523926s
Reputation | Calculation of the PageRank for test took 0.022287845611572266s
Interlinking | Calculation of Degree of Connection for test took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for test took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for test took 3.170967102050781e-05s
Believability | Calculation of trust value for test took 1.2874603271484375e-05s
INFO | --- Analysis for test took 3.33408522605896s
Availability | SPARQL endpoint availability check for Test took 9.989738464355469e-05s
Availability | VoID file availability check for Test took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Test took 0.3106107711791992s
Reputation | Calculation of the PageRank for Test took 0.020991802215576172s
Interlinking | Calculation of Degree of Connection for Test took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Test took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Test took 3.0040740966796875e-05s
Believability | Calculation of trust value for Test took 1.33514404296875e-05s
INFO | --- Analysis for Test took 2.91892671585083s
Availability | SPARQL endpoint availability check for test-svu took 20.220657110214233s
Availability | VoID file availability check for test-svu took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for test-svu took 0.3323817253112793s
Reputation | Calculation of the PageRank for test-svu took 0.02098393440246582s
Interlinking | Calculation of Degree of Connection for test-svu took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for test-svu took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.24249267578125e-05s
Believability | Calculation of trust value for test-svu took 1.5735626220703125e-05s
INFO | --- Analysis for test-svu took 53.324490547180176s
Availability | SPARQL endpoint availability check for Test took 5.340576171875e-05s
Availability | VoID file availability check for Test took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Test took 0.3399839401245117s
Reputation | Calculation of the PageRank for Test took 0.021561145782470703s
Interlinking | Calculation of Degree of Connection for Test took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Test took 0.0008213520050048828s
Interlinking | Calculation of Clustering coefficient for Test took 3.4809112548828125e-05s
Believability | Calculation of trust value for Test took 1.0967254638671875e-05s
INFO | --- Analysis for Test_ took 3.0156044960021973s
Availability | SPARQL endpoint availability check for xxxxx took 262.0568861961365s
Availability | VoID file availability check for xxxxx took 0.0008771419525146484s
Completeness | Calculation of interlinking completeness for xxxxx took 0.43686509132385254s
Reputation | Calculation of the PageRank for xxxxx took 0.0216522216796875s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for xxxxx took 9.822845458984375e-05s
Believability | Calculation of trust value for xxxxx took 1.430511474609375e-05s
INFO | --- Analysis for testee took 799.3507027626038s
Availability | SPARQL endpoint availability check for tharawat magazine took 5.0067901611328125e-05s
Availability | VoID file availability check for tharawat magazine took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.3243441581726074s
Reputation | Calculation of the PageRank for tharawat magazine took 0.02126622200012207s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.0001227855682373047s
Believability | Calculation of trust value for tharawat magazine took 1.3589859008789062e-05s
INFO | --- Analysis for tharawat-magazine-com took 3.990736246109009s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 1.5620214939117432s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.3627612590789795s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.021611690521240234s
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.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.337860107421875e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 1.5020370483398438e-05s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 9.003478288650513s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 3.333345651626587s
Availability | VoID file availability check for The European Library Open Dataset took 0.0008654594421386719s
Extra | Recovery of all triples for The European Library Open Dataset took 7.062035083770752s
Performance | Total latancy measurement for The European Library Open Dataset took 16.03722381591797s
Amount of data | Number of triples check for The European Library Open Dataset took 64.68510794639587s
Interoperability | New terms check for The European Library Open Dataset took 60.61379027366638s
Versatility | Languages check for The European Library Open Dataset took 3.2113595008850098s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 3.1976163387298584s
Interpretability | RDF structures check for The European Library Open Dataset took 3.2015950679779053s
Versatility | Serialization formats check for The European Library Open Dataset took 3.203312873840332s
Availability | RDF dump link check for The European Library Open Dataset took 3.199676036834717s
License | MR license check for The European Library Open Dataset took 3.1989448070526123s
License | HR license check for The European Library Open Dataset took 3.236757278442383s
Amount of data | Number of property check for The European Library Open Dataset took 3.2331295013427734s
Understandability | Number of label check for The European Library Open Dataset took 3.7075154781341553s
Understandability | URI regex check for The European Library Open Dataset took 6.395756006240845s
Understandability | Vocabs check for The European Library Open Dataset took 3.2002222537994385s
Verifiability | Authors check for The European Library Open Dataset took 3.236521005630493s
Verifiability | Publishers check for The European Library Open Dataset took 3.197803020477295s
Performance | Throughput check for The European Library Open Dataset took 32.060787200927734s
Amount of data | Check the number of entities for The European Library Open Dataset took 8.320808410644531e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 3.2072067260742188s
Interlinking | sameAs chians check for The European Library Open Dataset took 3.3313663005828857s
Interlinking | skos check for The European Library Open Dataset took 3.2338263988494873s
Interlinking | skos check for The European Library Open Dataset took 3.2714409828186035s
Timeliness | dataset update frequency check for The European Library Open Dataset took 3.2161612510681152s
Currency | Creation date check for The European Library Open Dataset took 6.399875164031982s
Currency | Modification date check for The European Library Open Dataset took 6.4322497844696045s
Rep.Conc. | URIs length for The European Library Open Dataset took 123.07801604270935s
Interoperability | New vocabularies check for The European Library Open Dataset took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 3.225745916366577s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 3.4989359378814697s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.027211666107177734s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.029775381088256836s
Consistency | Disjoint class check for The European Library Open Dataset took 3.1967132091522217s
Consistency | Check Misplaced properties for The European Library Open Dataset took 67.77904057502747s
Consistency | Misplaced classes for The European Library Open Dataset took 3.288331985473633s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 4.9327309131622314s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.350322961807251s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 65.828125s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03442215919494629s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 3.2178964614868164s
Security | Sign check for The European Library Open Dataset took 3.2052574157714844s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 11.275647401809692s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.5576128959655762s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.02165508270263672s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 7.081031799316406e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 1.5497207641601562e-05s
INFO | --- Analysis for the-european-library-open-dataset took 921.3803741931915s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.04626274108887s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0008084774017333984s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.4334254264831543s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.02199411392211914s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00011730194091796875s
Believability | Calculation of trust value for The Eurostat Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for the-eurostat-linked-data took 243.78654789924622s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 6.246566772460938e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.35257792472839355s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.021593809127807617s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 8.082389831542969e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 1.52587890625e-05s
INFO | --- Analysis for the-living-lod-cloud took 44.2695152759552s
Availability | SPARQL endpoint availability check for The View From took 11.357208251953125s
Availability | VoID file availability check for The View From took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for The View From took 0.35152411460876465s
Reputation | Calculation of the PageRank for The View From took 0.020960092544555664s
Interlinking | Calculation of Degree of Connection for The View From took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for The View From took 9.274482727050781e-05s
Believability | Calculation of trust value for The View From took 1.049041748046875e-05s
INFO | --- Analysis for the-view-from took 18.637566566467285s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.603662967681885s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.41840386390686035s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020986080169677734s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.743171691894531e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.5020370483398438e-05s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 74.19387316703796s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.203774213790894s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0007781982421875s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.3687760829925537s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.021560192108154297s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.719329833984375e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.52587890625e-05s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 103.55067348480225s
Availability | SPARQL endpoint availability check for The Content Wrangler took 0.00017023086547851562s
Availability | VoID file availability check for The Content Wrangler took 0.0010461807250976562s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.3551516532897949s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.022186756134033203s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00010704994201660156s
Believability | Calculation of trust value for The Content Wrangler took 1.5020370483398438e-05s
INFO | --- Analysis for thecontentwrangler-com took 4.08261251449585s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.935264587402344e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.33057212829589844s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020966291427612305s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.075599670410156e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 1.430511474609375e-05s
INFO | --- Analysis for thesaurus-datenwissen took 3.3043315410614014s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.6016907691955566s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.000579833984375s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.29899048805236816s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.021145343780517578s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 8.225440979003906e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 1.2636184692382812e-05s
INFO | --- Analysis for thesaurus-w took 4.7049336433410645s
Availability | SPARQL endpoint availability check for theses.fr took 5.412101745605469e-05s
Availability | VoID file availability check for theses.fr took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for theses.fr took 0.32616186141967773s
Reputation | Calculation of the PageRank for theses.fr took 0.02100348472595215s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for theses.fr took 5.14984130859375e-05s
Believability | Calculation of trust value for theses.fr took 1.3828277587890625e-05s
INFO | --- Analysis for thesesfr took 5.325016021728516s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 5.602836608886719e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.3327009677886963s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.023532390594482422s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.695487976074219e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.5020370483398438e-05s
INFO | --- Analysis for Thinkphile took 3.30003023147583s
Availability | SPARQL endpoint availability check for ThIST took 265.5437390804291s
Availability | VoID file availability check for ThIST took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for ThIST took 0.3606584072113037s
Reputation | Calculation of the PageRank for ThIST took 0.021411895751953125s
Interlinking | Calculation of Degree of Connection for ThIST took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for ThIST took 9.703636169433594e-05s
Believability | Calculation of trust value for ThIST took 1.0013580322265625e-05s
INFO | --- Analysis for thist took 563.2594139575958s
Availability | SPARQL endpoint availability check for TIP took 40.03210163116455s
Availability | VoID file availability check for TIP took 0.0003235340118408203s
Completeness | Calculation of interlinking completeness for TIP took 0.39704155921936035s
Reputation | Calculation of the PageRank for TIP took 0.02154994010925293s
Interlinking | Calculation of Degree of Connection for TIP took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00011587142944335938s
Believability | Calculation of trust value for TIP took 1.5974044799804688e-05s
INFO | --- Analysis for tip took 103.68046808242798s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 5.91278076171875e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0007936954498291016s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.3588600158691406s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.020977497100830078s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.170967102050781e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 1.5735626220703125e-05s
INFO | --- Analysis for TOPMODEL took 27.192273378372192s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.472895860671997s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.3412818908691406s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.020765304565429688s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.5762786865234375e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 1.5497207641601562e-05s
INFO | --- Analysis for TP-data took 8.210160970687866s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.9095432758331299s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.33263731002807617s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.021010398864746094s
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.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.38690185546875e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 1.430511474609375e-05s
INFO | --- Analysis for traditional-korean-medicine took 4.6062352657318115s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.24692726135253906s
Availability | VoID file availability check for Traffic Scotland took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.3171577453613281s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.020917654037475586s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.600120544433594e-05s
Believability | Calculation of trust value for Traffic Scotland took 1.0967254638671875e-05s
INFO | --- Analysis for traffic-scotland took 3.520909070968628s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.09154963493347168s
Availability | VoID file availability check for Transparency International Linked Data took 0.0012707710266113281s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.40583252906799316s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.02165532112121582s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010824203491210938s
Believability | Calculation of trust value for Transparency International Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for transparency-linked-data took 3.4912703037261963s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.764805793762207s
Availability | VoID file availability check for transport.data.gov.uk took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.3574225902557373s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.0210723876953125s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.560585021972656e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 1.049041748046875e-05s
INFO | --- Analysis for transport-data-gov-uk took 4.860640048980713s
Availability | SPARQL endpoint availability check for Trelios took 5.1021575927734375e-05s
Availability | VoID file availability check for Trelios took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Trelios took 0.4835968017578125s
Reputation | Calculation of the PageRank for Trelios took 0.020861387252807617s
Interlinking | Calculation of Degree of Connection for Trelios took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.6450881958007812e-05s
Believability | Calculation of trust value for Trelios took 1.0967254638671875e-05s
INFO | --- Analysis for Trelios took 3.112955093383789s
Availability | SPARQL endpoint availability check for Twarql took 10.600823163986206s
Availability | VoID file availability check for Twarql took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Twarql took 0.37781476974487305s
Reputation | Calculation of the PageRank for Twarql took 0.022396326065063477s
Interlinking | Calculation of Degree of Connection for Twarql took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Twarql took 7.2479248046875e-05s
Believability | Calculation of trust value for Twarql took 1.430511474609375e-05s
INFO | --- Analysis for twarql took 13.72635793685913s
Availability | SPARQL endpoint availability check for TWC Data-gov took 5.030632019042969e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.3646368980407715s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.02107381820678711s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 4.029273986816406e-05s
Believability | Calculation of trust value for TWC Data-gov took 1.0728836059570312e-05s
INFO | --- Analysis for twc-data-gov took 13.628767251968384s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.13891983032226562s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.3617262840270996s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.020858287811279297s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 3.695487976074219e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 1.049041748046875e-05s
INFO | --- Analysis for twc-healthdata took 15.03844404220581s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.0198400020599365s
Availability | VoID file availability check for Instance Hub (all) took 0.00039005279541015625s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.30582642555236816s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.021272659301757812s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 7.152557373046875e-05s
Believability | Calculation of trust value for Instance Hub (all) took 1.4066696166992188e-05s
INFO | --- Analysis for twc-hub took 79.4302248954773s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.13746356964111328s
Availability | VoID file availability check for IEEE VIS Source Data took 0.000324249267578125s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.5358686447143555s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.02105093002319336s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00011277198791503906s
Believability | Calculation of trust value for IEEE VIS Source Data took 1.2159347534179688e-05s
INFO | --- Analysis for twc-ieeevis took 112.79942178726196s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 9.942054748535156e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.34035563468933105s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.02105998992919922s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0008153915405273438s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 9.822845458984375e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 1.1682510375976562e-05s
INFO | --- Analysis for twc-logd took 3.6404972076416016s
Availability | SPARQL endpoint availability check for twc-opendap took 0.12339401245117188s
Availability | VoID file availability check for twc-opendap took 0.00034332275390625s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.3438260555267334s
Reputation | Calculation of the PageRank for twc-opendap took 0.021369457244873047s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0008642673492431641s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 9.822845458984375e-05s
Believability | Calculation of trust value for twc-opendap took 1.621246337890625e-05s
INFO | --- Analysis for twc-opendap took 64.19686651229858s
Availability | SPARQL endpoint availability check for typepad took 5.078315734863281e-05s
Availability | VoID file availability check for typepad took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for typepad took 0.5066049098968506s
Reputation | Calculation of the PageRank for typepad took 0.020934104919433594s
Interlinking | Calculation of Degree of Connection for typepad took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for typepad took 5.221366882324219e-05s
Believability | Calculation of trust value for typepad took 1.5497207641601562e-05s
INFO | --- Analysis for typepad took 4.280564308166504s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 1.0500104427337646s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.3566446304321289s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.022791147232055664s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.267692565917969e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.33514404296875e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 5.952152490615845s
Availability | SPARQL endpoint availability check for Uberblic.org took 0.08577156066894531s
Availability | VoID file availability check for Uberblic.org took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.3267247676849365s
Reputation | Calculation of the PageRank for Uberblic.org took 0.021712779998779297s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0009593963623046875s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00013494491577148438s
Believability | Calculation of trust value for Uberblic.org took 1.4781951904296875e-05s
INFO | --- Analysis for uberblic took 4.033571004867554s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.6296777725219727s
Availability | VoID file availability check for UDante in LiLa took 0.0007333755493164062s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.3550300598144531s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.020935535430908203s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 3.886222839355469e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.5020370483398438e-05s
INFO | --- Analysis for UDante took 4.814436435699463s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 5.965612888336182s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.40667104721069336s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.022737979888916016s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0010848045349121094s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 4.935264587402344e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 1.4781951904296875e-05s
INFO | --- Analysis for ufo took 10.551692724227905s
Availability | SPARQL endpoint availability check for Uganda Disasters took 9.942054748535156e-05s
Availability | VoID file availability check for Uganda Disasters took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.3324105739593506s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.02088785171508789s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0008552074432373047s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 5.1975250244140625e-05s
Believability | Calculation of trust value for Uganda Disasters took 1.0967254638671875e-05s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 3.395993232727051s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.061232805252075195s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.2976977825164795s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.02096867561340332s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0008244514465332031s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.00010538101196289062s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for uis-linked-data took 3.021000623703003s
Availability | SPARQL endpoint availability check for UK Legislation took 9.989738464355469e-05s
Availability | VoID file availability check for UK Legislation took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.34989476203918457s
Reputation | Calculation of the PageRank for UK Legislation took 0.020938634872436523s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 9.441375732421875e-05s
Believability | Calculation of trust value for UK Legislation took 1.0251998901367188e-05s
INFO | --- Analysis for uk-legislation-api took 4.177983999252319s
Availability | SPARQL endpoint availability check for UK Postcodes took 5.6743621826171875e-05s
Availability | VoID file availability check for UK Postcodes took 0.0007278919219970703s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.348355770111084s
Reputation | Calculation of the PageRank for UK Postcodes took 0.02123713493347168s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.793571472167969e-05s
Believability | Calculation of trust value for UK Postcodes took 9.775161743164062e-06s
INFO | --- Analysis for uk-postcodes took 23.098944187164307s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 5.1021575927734375e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0006797313690185547s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.3365945816040039s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.022826671600341797s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0009324550628662109s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00015664100646972656s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.4543533325195312e-05s
INFO | --- Analysis for umbel took 7.129477024078369s
Availability | SPARQL endpoint availability check for German environmental thesaurus UMTHES took 6.318092346191406e-05s
Availability | VoID file availability check for German environmental thesaurus UMTHES took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for German environmental thesaurus UMTHES took 0.36666202545166016s
Reputation | Calculation of the PageRank for German environmental thesaurus UMTHES took 0.021956920623779297s
Interlinking | Calculation of Degree of Connection for German environmental thesaurus UMTHES took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for German environmental thesaurus UMTHES took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for German environmental thesaurus UMTHES took 6.341934204101562e-05s
Believability | Calculation of trust value for German environmental thesaurus UMTHES took 7.867813110351562e-06s
INFO | --- Analysis for umthes took 4.053629159927368s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 1.9922163486480713s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.00093841552734375s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.3956472873687744s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.025496721267700195s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0013968944549560547s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 5.5789947509765625e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 7.867813110351562e-06s
INFO | --- Analysis for un-hazardous-numbers took 12.30954098701477s
Availability | SPARQL endpoint availability check for UniProt took 3.466491222381592s
Availability | VoID file availability check for UniProt took 0.00038909912109375s
Extra | Recovery of all triples for UniProt took 17.971503973007202s
Performance | Total latancy measurement for UniProt took 7.166505575180054s
Amount of data | Number of triples check for UniProt took 0.7699794769287109s
Interoperability | New terms check for UniProt took 1.8271870613098145s
Versatility | Languages check for UniProt took 1.7679424285888672s
Interpretability | Number of blank nodes check for UniProt took 3.304887533187866s
Interpretability | RDF structures check for UniProt took 1.6355600357055664s
Versatility | Serialization formats check for UniProt took 2.2231764793395996s
Availability | RDF dump link check for UniProt took 0.3296353816986084s
License | MR license check for UniProt took 1.3515844345092773s
License | HR license check for UniProt took 300.0964183807373s
Amount of data | Number of property check for UniProt took 0.11908674240112305s
Understandability | Number of label check for UniProt took 48.408652782440186s
Understandability | URI regex check for UniProt took 0.8517880439758301s
Understandability | Vocabs check for UniProt took 0.8748002052307129s
Verifiability | Authors check for UniProt took 1.9482758045196533s
Verifiability | Publishers check for UniProt took 1.1897969245910645s
Performance | Throughput check for UniProt took 35.80022597312927s
Amount of data | Check the number of entities for UniProt took 9.608268737792969e-05s
Verifiability | Contribs. check for UniProt took 0.8543648719787598s
Interlinking | sameAs chians check for UniProt took 0.532473087310791s
Interlinking | skos check for UniProt took 1.2711334228515625s
Interlinking | skos check for UniProt took 0.11041259765625s
Timeliness | dataset update frequency check for UniProt took 1.4825658798217773s
Currency | Creation date check for UniProt took 1.8549256324768066s
Currency | Modification date check for UniProt took 1.6817317008972168s
Rep.Conc. | URIs length for UniProt took 121.48603224754333s
Interoperability | New vocabularies check for UniProt took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for UniProt took 0.3894648551940918s
Accuracy | Check Functional Property for UniProt took 0.3769371509552002s
Accuracy | Check Inverse Functional Property for UniProt took 0.4898231029510498s
Accuracy | Check Empty annotation labels for UniProt took 11.320301055908203s
Accuracy | Check White space in annotation for UniProt took 2.5443172454833984s
Accuracy | Check Datatype consistency for UniProt took 7.602017641067505s
Consistency | Disjoint class check for UniProt took 0.38689422607421875s
Consistency | Check Misplaced properties for UniProt took 2.8044960498809814s
Consistency | Check Ontology hijacking for UniProt took 9.381124258041382s
Consistency | Check Invalid usage of undefined classes for UniProt took 24874.699671268463s
Consistency | Check Invalid usage of undefined properties for UniProt took 2.233290910720825s
Conciseness | Check Extensional conciseness for UniProt took 2.729076623916626s
Conciseness | Check Intensional conciseness for UniProt took 0.9583549499511719s
Security | Sign check for UniProt took 1.2103490829467773s
Availability | Check URIs Dereferenciability for UniProt took 5.138270139694214s
Completeness | Calculation of interlinking completeness for UniProt took 1.027785301208496s
Reputation | Calculation of the PageRank for UniProt took 0.023633956909179688s
Interlinking | Calculation of Degree of Connection for UniProt took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0008437633514404297s
Interlinking | Calculation of Clustering coefficient for UniProt took 6.103515625e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 6.198883056640625e-06s
Believability | Calculation of trust value for UniProt took 1.5497207641601562e-05s
INFO | --- Analysis for UniProt took 25906.90581893921s
Availability | SPARQL endpoint availability check for UniProt took 3.767794132232666s
Availability | VoID file availability check for UniProt took 0.0006580352783203125s
Extra | Recovery of all triples for UniProt took 19.720616579055786s
Performance | Total latancy measurement for UniProt took 8.158800840377808s
Amount of data | Number of triples check for UniProt took 0.8574020862579346s
Versatility | Languages check for UniProt took 1.9783403873443604s
Interpretability | Number of blank nodes check for UniProt took 3.411503314971924s
Security | Check HTTPS for UniProt took 3.3939521312713623s
Interpretability | RDF structures check for UniProt took 0.2201228141784668s
Versatility | Serialization formats check for UniProt took 0.22433924674987793s
Availability | RDF dump link check for UniProt took 0.20151615142822266s
License | MR license check for UniProt took 0.2256937026977539s
License | HR license check for UniProt took 0.22699451446533203s
Amount of data | Number of property check for UniProt took 0.19815397262573242s
Understandability | Number of label check for UniProt took 0.23708295822143555s
Understandability | URI regex check for UniProt took 0.4177103042602539s
Understandability | Vocabs check for UniProt took 0.24340415000915527s
Verifiability | Authors check for UniProt took 0.2239234447479248s
Verifiability | Publishers check for UniProt took 0.2149817943572998s
Performance | Throughput check for UniProt took 33.64496660232544s
Amount of data | Check the number of entities for UniProt took 0.00016689300537109375s
Verifiability | Contribs. check for UniProt took 0.28578853607177734s
Interlinking | sameAs chians check for UniProt took 0.19527125358581543s
Interlinking | skos check for UniProt took 0.22452187538146973s
Interlinking | skos check for UniProt took 0.202040433883667s
Timeliness | dataset update frequency check for UniProt took 0.22410058975219727s
Currency | Creation date check for UniProt took 0.46078014373779297s
Currency | Modification date check for UniProt took 0.41976451873779297s
Rep.Conc. | URIs length for UniProt took 126.32020211219788s
Interoperability | New vocabularies check for UniProt took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.20278525352478027s
Accuracy | Check Datatype consistency for UniProt took 7.520825147628784s
Consistency | Disjoint class check for UniProt took 0.21047472953796387s
Consistency | Check Ontology hijacking for UniProt took 0.21153712272644043s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.7978549003601074s
Conciseness | Check Extensional conciseness for UniProt took 2.740952491760254s
Security | Sign check for UniProt took 0.23150968551635742s
Availability | Check URIs Dereferenciability for UniProt took 4.6448657512664795s
Completeness | Calculation of interlinking completeness for UniProt took 0.42076992988586426s
Reputation | Calculation of the PageRank for UniProt took 0.028254032135009766s
Interlinking | Calculation of Degree of Connection for UniProt took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for UniProt took 6.031990051269531e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 7.152557373046875e-07s
Believability | Calculation of trust value for UniProt took 1.239776611328125e-05s
INFO | --- Analysis for uniprot took 765.5534374713898s
Availability | SPARQL endpoint availability check for uniprot-metadata took 9.274482727050781e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.6180739402770996s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.020889759063720703s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 7.677078247070312e-05s
Believability | Calculation of trust value for uniprot-metadata took 1.4781951904296875e-05s
INFO | --- Analysis for uniprot-metadata took 5.359041929244995s
Availability | SPARQL endpoint availability check for UniProtKB took 3.3940813541412354s
Availability | VoID file availability check for UniProtKB took 0.0005905628204345703s
Extra | Recovery of all triples for UniProtKB took 19.53072500228882s
Performance | Total latancy measurement for UniProtKB took 7.234019041061401s
Amount of data | Number of triples check for UniProtKB took 0.6824800968170166s
Interoperability | New terms check for UniProtKB took 2.1384451389312744s
Versatility | Languages check for UniProtKB took 2.654264211654663s
Interpretability | Number of blank nodes check for UniProtKB took 3.2770349979400635s
Interpretability | RDF structures check for UniProtKB took 1.7540504932403564s
Versatility | Serialization formats check for UniProtKB took 2.3039302825927734s
Availability | RDF dump link check for UniProtKB took 0.42455148696899414s
License | MR license check for UniProtKB took 1.2605066299438477s
License | HR license check for UniProtKB took 300.1747329235077s
Amount of data | Number of property check for UniProtKB took 0.16080260276794434s
Understandability | Number of label check for UniProtKB took 56.53242540359497s
Understandability | URI regex check for UniProtKB took 0.9368321895599365s
Understandability | Vocabs check for UniProtKB took 1.24898362159729s
Verifiability | Authors check for UniProtKB took 1.5461742877960205s
Verifiability | Publishers check for UniProtKB took 1.2577335834503174s
Performance | Throughput check for UniProtKB took 38.458152770996094s
Amount of data | Check the number of entities for UniProtKB took 6.651878356933594e-05s
Verifiability | Contribs. check for UniProtKB took 0.7430195808410645s
Interlinking | sameAs chians check for UniProtKB took 0.5802915096282959s
Interlinking | skos check for UniProtKB took 1.3193020820617676s
Interlinking | skos check for UniProtKB took 0.10846710205078125s
Timeliness | dataset update frequency check for UniProtKB took 1.3990581035614014s
Currency | Creation date check for UniProtKB took 1.6069636344909668s
Currency | Modification date check for UniProtKB took 2.08031964302063s
Rep.Conc. | URIs length for UniProtKB took 123.01367139816284s
Interoperability | New vocabularies check for UniProtKB took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.4040248394012451s
Accuracy | Check Functional Property for UniProtKB took 0.49393248558044434s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.4528391361236572s
Accuracy | Check Empty annotation labels for UniProtKB took 36.53742003440857s
Accuracy | Check White space in annotation for UniProtKB took 2.5295605659484863s
Accuracy | Check Datatype consistency for UniProtKB took 7.585142612457275s
Consistency | Disjoint class check for UniProtKB took 0.5798783302307129s
Consistency | Check Misplaced properties for UniProtKB took 2.54187273979187s
Consistency | Check Ontology hijacking for UniProtKB took 8.910502433776855s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 25192.56419491768s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 2.2578063011169434s
Conciseness | Check Extensional conciseness for UniProtKB took 2.766075849533081s
Conciseness | Check Intensional conciseness for UniProtKB took 0.8208446502685547s
Security | Sign check for UniProtKB took 1.097895622253418s
Availability | Check URIs Dereferenciability for UniProtKB took 4.925030708312988s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.9769117832183838s
Reputation | Calculation of the PageRank for UniProtKB took 0.022148847579956055s
Interlinking | Calculation of Degree of Connection for UniProtKB took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 7.128715515136719e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 2.1457672119140625e-06s
Believability | Calculation of trust value for UniProtKB took 1.1682510375976562e-05s
INFO | --- Analysis for uniprotkb took 26263.356297254562s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 0.00011229515075683594s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0007505416870117188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.32994818687438965s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.020918607711791992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 14.798780679702759s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.601478576660156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.32553744316101074s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.02225971221923828s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0008091926574707031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.5974044799804688e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 4.69684910774231s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 0.00010395050048828125s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0007648468017578125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.394362211227417s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.021188735961914062s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.88109564781189s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 0.00015163421630859375s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0007455348968505859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.3339731693267822s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.020766735076904297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0010714530944824219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 5.0067901611328125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 1.4543533325195312e-05s
INFO | --- Analysis for universal-dependencies-treebank-basque took 14.103268146514893s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 5.316734313964844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0007750988006591797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.3476686477661133s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.022833824157714844s
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.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 1.4543533325195312e-05s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 14.019485712051392s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 0.00011730194091796875s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0007333755493164062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.36507105827331543s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.02094411849975586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 1.52587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 14.10206913948059s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 9.846687316894531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.3444480895996094s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 4.594290733337402s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 0.00010991096496582031s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0008454322814941406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.39522624015808105s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.020732641220092773s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 1.5497207641601562e-05s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 14.21959114074707s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 0.00014853477478027344s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0007548332214355469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.33790087699890137s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.02241802215576172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 1.52587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 14.312374591827393s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.839897155761719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0007283687591552734s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.3728199005126953s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.02082061767578125s
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.0007638931274414062s
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.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.938812255859375s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 6.198883056640625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.333057165145874s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.0208282470703125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 13.873603582382202s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 0.0001876354217529297s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.36295104026794434s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.021075725555419922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0008952617645263672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.601478576660156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 1.5020370483398438e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 13.839689493179321s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 5.793571472167969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.34946560859680176s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.020875930786132812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-danish took 4.552975654602051s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 5.2928924560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0007712841033935547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.36998891830444336s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.0207822322845459s
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.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.91533350944519s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 5.817413330078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.33992528915405273s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.020741939544677734s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 1.4543533325195312e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 13.854584217071533s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 5.1975250244140625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.41605710983276367s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.021377086639404297s
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.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-english took 14.2518949508667s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 5.245208740234375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0007958412170410156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.4449589252471924s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.02278900146484375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.790051460266113s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 9.942054748535156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0007748603820800781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.3389897346496582s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.02071690559387207s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 13.914767980575562s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 9.751319885253906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0008103847503662109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.40488481521606445s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.021348237991333008s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.5974044799804688e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 14.118020296096802s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 5.054473876953125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.36057257652282715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020860671997070312s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 4.768845319747925s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 5.14984130859375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.3566110134124756s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.02228999137878418s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 4.220008850097656e-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.768224716186523s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 8.344650268554688e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.3833949565887451s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.02256608009338379s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 1.71661376953125e-05s
INFO | --- Analysis for universal-dependencies-treebank-french took 14.234119176864624s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 0.00010442733764648438s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0007331371307373047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.7408819198608398s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.022190332412719727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 1.5020370483398438e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician took 14.461982727050781s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 0.00012087821960449219s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.5493903160095215s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.020752429962158203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 4.887590169906616s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 0.0001010894775390625s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.36470985412597656s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.02081608772277832s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-german took 8.019744634628296s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 5.507469177246094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.6598916053771973s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.020783424377441406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 1.52587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 4.868950366973877s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 8.630752563476562e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.3245089054107666s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.025805234909057617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0008425712585449219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 4.57763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-greek took 4.693938970565796s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 0.00010657310485839844s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.36539411544799805s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.02091813087463379s
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.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 14.090693235397339s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 5.2928924560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0007312297821044922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.3471977710723877s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.023004770278930664s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.837608337402344s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 5.5789947509765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.727938175201416s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.020955562591552734s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 1.52587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 5.320452451705933s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 5.0067901611328125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0007398128509521484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.34354734420776367s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.02122330665588379s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 5.221366882324219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 14.081298351287842s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 9.799003601074219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.31366491317749023s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.020963668823242188s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-irish took 4.762856960296631s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 5.14984130859375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.34537267684936523s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.020987510681152344s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-italian took 14.025086879730225s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 0.00010347366333007812s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0007228851318359375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.3468000888824463s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.023022890090942383s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0009429454803466797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 5.030632019042969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.911610126495361s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 0.0001266002655029297s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.6549303531646729s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.021942853927612305s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 4.8958985805511475s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 6.222724914550781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0009565353393554688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.3813457489013672s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.02112579345703125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 5.14984130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 14.11768126487732s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 5.221366882324219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.37560057640075684s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.020814895629882812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin took 4.552587270736694s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 9.822845458984375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0008227825164794922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.394193172454834s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.021179676055908203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 5.2928924560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 14.223242282867432s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.982948303222656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0007710456848144531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.3689308166503906s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.02111649513244629s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 13.715368747711182s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 5.316734313964844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.3231043815612793s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.02089238166809082s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 1.621246337890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.980615854263306s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 9.703636169433594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0008099079132080078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.3653237819671631s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.021788358688354492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0011737346649169922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 5.1975250244140625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.52587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 13.852655410766602s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.00012612342834472656s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007638931274414062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.42006468772888184s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 1.52587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 14.57288670539856s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 9.989738464355469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.3497426509857178s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.021013975143432617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 1.5020370483398438e-05s
INFO | --- Analysis for universal-dependencies-treebank-persian took 4.63815975189209s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 0.00012183189392089844s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0008006095886230469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.39458179473876953s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.02109551429748535s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 4.935264587402344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 1.4781951904296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-polish took 14.05736231803894s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 5.125999450683594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0007722377777099609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.4940521717071533s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.021304845809936523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 1.5020370483398438e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 13.80794358253479s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 5.5789947509765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0009036064147949219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.35230183601379395s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.935264587402344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 1.4781951904296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 13.946889638900757s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 5.793571472167969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.00067138671875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.36425113677978516s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.02243328094482422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 13.96445369720459s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 0.0001938343048095703s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0007278919219970703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.33141303062438965s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.02097630500793457s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.4781951904296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 14.009676933288574s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 5.3882598876953125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.3399684429168701s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.020998716354370117s
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.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 1.5735626220703125e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian took 14.069026231765747s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.00010180473327636719s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.34636902809143066s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.021093130111694336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 4.364891052246094s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 5.412101745605469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.33907556533813477s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.02090144157409668s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 4.863739013671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 14.034646034240723s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 5.340576171875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0007708072662353516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.36164116859436035s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.02100348472595215s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 1.5020370483398438e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.882324695587158s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 0.0001819133758544922s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.3652820587158203s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.020998239517211914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.974088907241821s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 5.316734313964844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0008113384246826172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.34795355796813965s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.02083611488342285s
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.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 14.001010179519653s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 5.817413330078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.5452108383178711s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.021290063858032227s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 14.260618686676025s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 0.00011944770812988281s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.3538186550140381s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.020929336547851562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 9.298324584960938e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 13.710455179214478s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 0.00010395050048828125s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.36353015899658203s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.02078723907470703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 4.799937009811401s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 5.3882598876953125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.00040984153747558594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.33748674392700195s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 4.671952486038208s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 9.298324584960938e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0008192062377929688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.3429551124572754s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.021022319793701172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 1.5497207641601562e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 14.10924482345581s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 9.894371032714844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.4069681167602539s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020954608917236328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.986234426498413s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 0.0001239776611328125s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0008320808410644531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.38559794425964355s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.021157026290893555s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 4.792213439941406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 1.4543533325195312e-05s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.789437770843506s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 9.822845458984375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0007829666137695312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.5620231628417969s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.02086663246154785s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 14.598226547241211s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 5.245208740234375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0007834434509277344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.3553485870361328s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.021819353103637695s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 1.4781951904296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 14.967812061309814s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 0.0001685619354248047s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.37398862838745117s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.02101421356201172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.934039115905762s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 5.888938903808594e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.38348984718322754s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.022327423095703125s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.985664367675781e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 1.5974044799804688e-05s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 4.576295614242554s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 9.965896606445312e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.34165191650390625s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.021049976348876953s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 5.793571472167969e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.4781951904296875e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 3.7558820247650146s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 0.00017499923706054688s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0006253719329833984s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.3322460651397705s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.022623538970947266s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0008449554443359375s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 4.00543212890625e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 1.3828277587890625e-05s
INFO | --- Analysis for university-sussex-reading-lists took 3.450890064239502s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 7.437677621841431s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.3910942077636719s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.02268075942993164s
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.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 7.343292236328125e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 1.0728836059570312e-05s
INFO | --- Analysis for unodc took 20.5187509059906s
Availability | SPARQL endpoint availability check for Super Ontology took 5.316734313964844e-05s
Availability | VoID file availability check for Super Ontology took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.3737602233886719s
Reputation | Calculation of the PageRank for Super Ontology took 0.02139902114868164s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 8.821487426757812e-05s
Believability | Calculation of trust value for Super Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for upper-ontology took 4.558562517166138s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 1.5505003929138184s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.3382749557495117s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.021198034286499023s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.552436828613281e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for Upper_Ontology took 5.677385330200195s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 6.937980651855469e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.0003178119659423828s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.3222782611846924s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.021109342575073242s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 3.147125244140625e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 1.811981201171875e-05s
INFO | --- Analysis for Urban_Atlas_ took 3.1851634979248047s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 0.6598842144012451s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.0005872249603271484s
Extra | Recovery of all triples for Urban Atlas dataset @PSNC took 100.83983039855957s
Performance | Total latancy measurement for Urban Atlas dataset @PSNC took 0.9647612571716309s
Amount of data | Number of triples check for Urban Atlas dataset @PSNC took 9.04136323928833s
Interoperability | New terms check for Urban Atlas dataset @PSNC took 14.304022312164307s
Versatility | Languages check for Urban Atlas dataset @PSNC took 300.1794250011444s
Interpretability | Number of blank nodes check for Urban Atlas dataset @PSNC took 2.082639217376709s
Interpretability | RDF structures check for Urban Atlas dataset @PSNC took 0.2993776798248291s
Versatility | Serialization formats check for Urban Atlas dataset @PSNC took 12.327023029327393s
Availability | RDF dump link check for Urban Atlas dataset @PSNC took 0.3665013313293457s
License | MR license check for Urban Atlas dataset @PSNC took 0.677666425704956s
License | HR license check for Urban Atlas dataset @PSNC took 300.25818490982056s
Amount of data | Number of property check for Urban Atlas dataset @PSNC took 0.20753908157348633s
Understandability | Number of label check for Urban Atlas dataset @PSNC took 1.861708164215088s
Understandability | URI regex check for Urban Atlas dataset @PSNC took 1.0227069854736328s
Understandability | Vocabs check for Urban Atlas dataset @PSNC took 0.6176300048828125s
Verifiability | Authors check for Urban Atlas dataset @PSNC took 0.22020459175109863s
Verifiability | Publishers check for Urban Atlas dataset @PSNC took 0.24381375312805176s
Performance | Throughput check for Urban Atlas dataset @PSNC took 11.220046758651733s
Amount of data | Check the number of entities for Urban Atlas dataset @PSNC took 9.012222290039062e-05s
Verifiability | Contribs. check for Urban Atlas dataset @PSNC took 0.20254206657409668s
Interlinking | sameAs chians check for Urban Atlas dataset @PSNC took 0.19644999504089355s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.42726635932922363s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.42880821228027344s
Timeliness | dataset update frequency check for Urban Atlas dataset @PSNC took 5.503740310668945s
Currency | Creation date check for Urban Atlas dataset @PSNC took 0.466996431350708s
Currency | Modification date check for Urban Atlas dataset @PSNC took 0.2432713508605957s
Rep.Conc. | URIs length for Urban Atlas dataset @PSNC took 155.57676720619202s
Interoperability | New vocabularies check for Urban Atlas dataset @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Urban Atlas dataset @PSNC took 0.19774699211120605s
Accuracy | Check Functional Property for Urban Atlas dataset @PSNC took 0.29297447204589844s
Accuracy | Check Inverse Functional Property for Urban Atlas dataset @PSNC took 0.27555203437805176s
Accuracy | Check Empty annotation labels for Urban Atlas dataset @PSNC took 36.041369915008545s
Accuracy | Check White space in annotation for Urban Atlas dataset @PSNC took 2.6728148460388184s
Accuracy | Check Datatype consistency for Urban Atlas dataset @PSNC took 2.758352756500244s
Consistency | Disjoint class check for Urban Atlas dataset @PSNC took 0.17633605003356934s
Consistency | Check Misplaced properties for Urban Atlas dataset @PSNC took 87.08410716056824s
Consistency | Misplaced classes for Urban Atlas dataset @PSNC took 8.762324094772339s
Consistency | Check Ontology hijacking for Urban Atlas dataset @PSNC took 40.85601735115051s
Consistency | Check Invalid usage of undefined classes for Urban Atlas dataset @PSNC took 1.5014152526855469s
Consistency | Check Invalid usage of undefined properties for Urban Atlas dataset @PSNC took 87.5519368648529s
Conciseness | Check Extensional conciseness for Urban Atlas dataset @PSNC took 2.8547091484069824s
Conciseness | Check Intensional conciseness for Urban Atlas dataset @PSNC took 0.6219651699066162s
Security | Sign check for Urban Atlas dataset @PSNC took 1.3586914539337158s
Availability | Check URIs Dereferenciability for Urban Atlas dataset @PSNC took 10.022027730941772s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.6279709339141846s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.021773338317871094s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Urban Atlas dataset @PSNC took 2.6226043701171875e-06s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 1.5735626220703125e-05s
INFO | --- Analysis for Urban_Atlas_Dataset took 2277.3332307338715s
Availability | SPARQL endpoint availability check for URIBurner took 0.9859426021575928s
Availability | VoID file availability check for URIBurner took 0.0006182193756103516s
Extra | Recovery of all triples for URIBurner took 121.4842312335968s
Performance | Total latancy measurement for URIBurner took 2.6378891468048096s
Amount of data | Number of triples check for URIBurner took 3.5260934829711914s
Interoperability | New terms check for URIBurner took 38.46291208267212s
Versatility | Languages check for URIBurner took 123.49665856361389s
Interpretability | Number of blank nodes check for URIBurner took 1.8692045211791992s
Security | Check HTTPS for URIBurner took 0.867642879486084s
Interpretability | RDF structures check for URIBurner took 0.7989423274993896s
Versatility | Serialization formats check for URIBurner took 6.093223571777344s
Availability | RDF dump link check for URIBurner took 45.33875846862793s
License | MR license check for URIBurner took 0.8302860260009766s
License | HR license check for URIBurner took 122.73654246330261s
Amount of data | Number of property check for URIBurner took 0.7576746940612793s
Understandability | Number of label check for URIBurner took 2.994763135910034s
Understandability | URI regex check for URIBurner took 1.2506024837493896s
Understandability | Vocabs check for URIBurner took 0.6447386741638184s
Verifiability | Authors check for URIBurner took 0.7400553226470947s
Verifiability | Publishers check for URIBurner took 0.5984940528869629s
Performance | Throughput check for URIBurner took 10.912156105041504s
Amount of data | Check the number of entities for URIBurner took 0.00010538101196289062s
Verifiability | Contribs. check for URIBurner took 0.6017539501190186s
Interlinking | sameAs chians check for URIBurner took 0.997065544128418s
Interlinking | skos check for URIBurner took 0.5844879150390625s
Interlinking | skos check for URIBurner took 0.5133633613586426s
Timeliness | dataset update frequency check for URIBurner took 0.9884233474731445s
Currency | Creation date check for URIBurner took 2.998396158218384s
Currency | Modification date check for URIBurner took 0.6013739109039307s
Rep.Conc. | URIs length for URIBurner took 112.83418130874634s
Interoperability | New vocabularies check for URIBurner took 40.48845410346985s
Consistency | Deprecated classes/propertiers check for URIBurner took 0.6310806274414062s
Accuracy | Check Functional Property for URIBurner took 0.6126594543457031s
Accuracy | Check Inverse Functional Property for URIBurner took 0.61814284324646s
Accuracy | Check Empty annotation labels for URIBurner took 56.03432297706604s
Accuracy | Check White space in annotation for URIBurner took 0.1911482810974121s
Consistency | Disjoint class check for URIBurner took 0.5712282657623291s
Consistency | Check Misplaced properties for URIBurner took 314.8581166267395s
Consistency | Misplaced classes for URIBurner took 55.6187379360199s
Consistency | Check Ontology hijacking for URIBurner took 57.61065077781677s
Consistency | Check Invalid usage of undefined properties for URIBurner took 56.93344736099243s
Conciseness | Check Extensional conciseness for URIBurner took 0.0001659393310546875s
Conciseness | Check Intensional conciseness for URIBurner took 107.97400307655334s
Security | Sign check for URIBurner took 0.8227388858795166s
Completeness | Calculation of interlinking completeness for URIBurner took 0.8575112819671631s
Reputation | Calculation of the PageRank for URIBurner took 0.02216053009033203s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for URIBurner took 0.00011181831359863281s
Interoperability | Check the re-using of existing vocabs for URIBurner took 40.99202108383179s
Believability | Calculation of trust value for URIBurner took 1.5974044799804688e-05s
INFO | --- Analysis for uriburner took 15161.758506536484s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0001010894775390625s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.3249471187591553s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.021178722381591797s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0009760856628417969s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.1961669921875e-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 urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 2.934802293777466s
Availability | SPARQL endpoint availability check for Legija Stranaca took 9.489059448242188e-05s
Availability | VoID file availability check for Legija Stranaca took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.29995179176330566s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.02111220359802246s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 3.1948089599609375e-05s
Believability | Calculation of trust value for Legija Stranaca took 1.4543533325195312e-05s
INFO | --- Analysis for Uros_Legija_Susa took 2.8402304649353027s
Availability | SPARQL endpoint availability check for Legija took 0.0001323223114013672s
Availability | VoID file availability check for Legija took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Legija took 0.32818603515625s
Reputation | Calculation of the PageRank for Legija took 0.020865201950073242s
Interlinking | Calculation of Degree of Connection for Legija took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Legija took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Legija took 3.147125244140625e-05s
Believability | Calculation of trust value for Legija took 9.5367431640625e-06s
INFO | --- Analysis for Uros_Susa took 3.03617787361145s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.5159990787506104s
Availability | VoID file availability check for USAGE review corpus took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.469501256942749s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.020771265029907227s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.1948089599609375e-05s
Believability | Calculation of trust value for USAGE review corpus took 1.049041748046875e-05s
INFO | --- Analysis for usage-review-corpus took 4.295873641967773s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 3.9483752250671387s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.3655662536621094s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.022632360458374023s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.724761962890625e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 1.52587890625e-05s
INFO | --- Analysis for utpl-lod took 10.891901969909668s
Availability | SPARQL endpoint availability check for terrorist attack took 5.1975250244140625e-05s
Availability | VoID file availability check for terrorist attack took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.3547043800354004s
Reputation | Calculation of the PageRank for terrorist attack took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 3.0517578125e-05s
Believability | Calculation of trust value for terrorist attack took 1.430511474609375e-05s
INFO | --- Analysis for varsha took 4.983856201171875s
Availability | SPARQL endpoint availability check for VA took 5.030632019042969e-05s
Availability | VoID file availability check for VA took 0.0004146099090576172s
Completeness | Calculation of interlinking completeness for VA took 0.32674288749694824s
Reputation | Calculation of the PageRank for VA took 0.02091050148010254s
Interlinking | Calculation of Degree of Connection for VA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VA took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for VA took 3.24249267578125e-05s
Believability | Calculation of trust value for VA took 1.52587890625e-05s
INFO | --- Analysis for Vehicule_Autonome took 3.1724495887756348s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 0.5966348648071289s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.31566572189331055s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.020966529846191406s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for VelezIndexTotiusArtis took 4.652372360229492s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 6.578382968902588s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.2898731231689453s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.02107381820678711s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 0.00011444091796875s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 1.0013580322265625e-05s
INFO | --- Analysis for verrijktkoninkrijk took 15.341640710830688s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 0.00011134147644042969s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.32761383056640625s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.021135568618774414s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00017642974853515625s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.4543533325195312e-05s
INFO | --- Analysis for viaf took 21.44370985031128s
Availability | SPARQL endpoint availability check for Vihar Exports took 9.584426879882812e-05s
Availability | VoID file availability check for Vihar Exports took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.300457239151001s
Reputation | Calculation of the PageRank for Vihar Exports took 0.021840810775756836s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 3.24249267578125e-05s
Believability | Calculation of trust value for Vihar Exports took 1.0251998901367188e-05s
INFO | --- Analysis for Vihar_Exports took 2.973344087600708s
Availability | SPARQL endpoint availability check for VIVO took 0.00010061264038085938s
Availability | VoID file availability check for VIVO took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for VIVO took 0.34186816215515137s
Reputation | Calculation of the PageRank for VIVO took 0.020850181579589844s
Interlinking | Calculation of Degree of Connection for VIVO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for VIVO took 6.699562072753906e-05s
Believability | Calculation of trust value for VIVO took 1.52587890625e-05s
INFO | --- Analysis for vivo took 5.880279064178467s
Availability | SPARQL endpoint availability check for VIVO Cornell took 0.00010204315185546875s
Availability | VoID file availability check for VIVO Cornell took 0.0007610321044921875s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.29073309898376465s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.021098852157592773s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.392333984375e-05s
Believability | Calculation of trust value for VIVO Cornell took 1.239776611328125e-05s
INFO | --- Analysis for vivo-cornell-university took 7.209767818450928s
Availability | SPARQL endpoint availability check for VIVO Indiana took 5.817413330078125e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.2853658199310303s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.021214008331298828s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 8.630752563476562e-05s
Believability | Calculation of trust value for VIVO Indiana took 1.1920928955078125e-05s
INFO | --- Analysis for vivo-indiana-university took 3.6615421772003174s
Availability | SPARQL endpoint availability check for VIVO Ponce took 5.364418029785156e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.3287482261657715s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.021581649780273438s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.719329833984375e-05s
Believability | Calculation of trust value for VIVO Ponce took 1.621246337890625e-05s
INFO | --- Analysis for vivo-ponce took 3.4617509841918945s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 9.655952453613281e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0007536411285400391s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.33985400199890137s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.021178722381591797s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 4.029273986816406e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 1.4781951904296875e-05s
INFO | --- Analysis for vivo-scripps-research-institute took 3.4150314331054688s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 0.000125885009765625s
Availability | VoID file availability check for VIVO University of Florida took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.32508182525634766s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.020928382873535156s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.703636169433594e-05s
Believability | Calculation of trust value for VIVO University of Florida took 1.1205673217773438e-05s
INFO | --- Analysis for vivo-university-of-florida took 3.1111605167388916s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 8.440017700195312e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0006740093231201172s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.2850310802459717s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.02071690559387207s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 4.458427429199219e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 1.2874603271484375e-05s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 3.165623664855957s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 0.00016164779663085938s
Availability | VoID file availability check for VIVO WUSTL took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.3240492343902588s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.021288394927978516s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 4.172325134277344e-05s
Believability | Calculation of trust value for VIVO WUSTL took 1.5497207641601562e-05s
INFO | --- Analysis for vivo-wustl took 3.2963521480560303s
Availability | SPARQL endpoint availability check for vivo2doi took 0.00010371208190917969s
Availability | VoID file availability check for vivo2doi took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.3290114402770996s
Reputation | Calculation of the PageRank for vivo2doi took 0.02069568634033203s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.315376281738281e-05s
Believability | Calculation of trust value for vivo2doi took 1.1920928955078125e-05s
INFO | --- Analysis for vivo2doi took 26.39038324356079s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 9.894371032714844e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0008003711700439453s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.32033562660217285s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.961822509765625e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 1.5974044799804688e-05s
INFO | --- Analysis for vu-wordnet took 16.120620250701904s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.13368654251098633s
Availability | VoID file availability check for vulnerapedia took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.3131906986236572s
Reputation | Calculation of the PageRank for vulnerapedia took 0.023034095764160156s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 7.009506225585938e-05s
Believability | Calculation of trust value for vulnerapedia took 1.5020370483398438e-05s
INFO | --- Analysis for vulnerapedia took 3.586305856704712s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 4.839897155761719e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.3130331039428711s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.020930767059326172s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.2636184692382812e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.0967254638671875e-05s
INFO | --- Analysis for VVASIAK took 2.775139808654785s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 0.00010204315185546875s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.3207712173461914s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.020724058151245117s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.0040740966796875e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 1.1444091796875e-05s
INFO | --- Analysis for Vyvasta took 2.9380533695220947s
Availability | SPARQL endpoint availability check for W3C took 6.151199340820312e-05s
Availability | VoID file availability check for W3C took 0.0003597736358642578s
Completeness | Calculation of interlinking completeness for W3C took 0.3065965175628662s
Reputation | Calculation of the PageRank for W3C took 0.021001815795898438s
Interlinking | Calculation of Degree of Connection for W3C took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for W3C took 0.00013947486877441406s
Believability | Calculation of trust value for W3C took 1.1205673217773438e-05s
INFO | --- Analysis for w3c took 3.247053623199463s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 0.00010585784912109375s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.3378758430480957s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.02130603790283203s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00012230873107910156s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 1.3828277587890625e-05s
INFO | --- Analysis for w3c-wordnet took 3.8601009845733643s
Availability | SPARQL endpoint availability check for WarSampo took 0.3730034828186035s
Availability | VoID file availability check for WarSampo took 0.0006742477416992188s
Extra | Recovery of all triples for WarSampo took 25.985111474990845s
Performance | Total latancy measurement for WarSampo took 0.8342535495758057s
Amount of data | Number of triples check for WarSampo took 18.756681203842163s
Interoperability | New terms check for WarSampo took 4.1636834144592285s
Versatility | Languages check for WarSampo took 51.10344910621643s
Interpretability | Number of blank nodes check for WarSampo took 18.429546356201172s
Security | Check HTTPS for WarSampo took 0.3857133388519287s
Interpretability | RDF structures check for WarSampo took 0.20247530937194824s
Versatility | Serialization formats check for WarSampo took 0.22280168533325195s
Availability | RDF dump link check for WarSampo took 0.8088746070861816s
License | MR license check for WarSampo took 0.19922828674316406s
License | HR license check for WarSampo took 47.51631736755371s
Amount of data | Number of property check for WarSampo took 0.20598912239074707s
Understandability | Number of label check for WarSampo took 9.505996465682983s
Understandability | URI regex check for WarSampo took 0.3558330535888672s
Understandability | Vocabs check for WarSampo took 0.1614842414855957s
Verifiability | Authors check for WarSampo took 0.20079827308654785s
Verifiability | Publishers check for WarSampo took 0.19180941581726074s
Performance | Throughput check for WarSampo took 11.005396127700806s
Amount of data | Check the number of entities for WarSampo took 17.011869430541992s
Verifiability | Contribs. check for WarSampo took 0.19226741790771484s
Interlinking | sameAs chians check for WarSampo took 0.19469499588012695s
Interlinking | skos check for WarSampo took 0.20212745666503906s
Interlinking | skos check for WarSampo took 0.16488409042358398s
Timeliness | dataset update frequency check for WarSampo took 0.16361618041992188s
Currency | Creation date check for WarSampo took 0.34827136993408203s
Currency | Modification date check for WarSampo took 0.3648672103881836s
Rep.Conc. | URIs length for WarSampo took 51.37305164337158s
Interoperability | New vocabularies check for WarSampo took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.2001180648803711s
Accuracy | Check Functional Property for WarSampo took 0.19887781143188477s
Accuracy | Check Inverse Functional Property for WarSampo took 0.16073036193847656s
Accuracy | Check Empty annotation labels for WarSampo took 11.842015027999878s
Accuracy | Check White space in annotation for WarSampo took 2.2608556747436523s
Accuracy | Check Datatype consistency for WarSampo took 5.474349498748779s
Consistency | Disjoint class check for WarSampo took 0.20027732849121094s
Consistency | Check Misplaced properties for WarSampo took 20.460681438446045s
Consistency | Check Ontology hijacking for WarSampo took 20.189371824264526s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.636876106262207s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.8200898170471191s
Conciseness | Check Extensional conciseness for WarSampo took 2.9105641841888428s
Conciseness | Check Intensional conciseness for WarSampo took 0.2824530601501465s
Security | Sign check for WarSampo took 0.17973089218139648s
Availability | Check URIs Dereferenciability for WarSampo took 2.622593641281128s
Completeness | Calculation of interlinking completeness for WarSampo took 0.6556129455566406s
Reputation | Calculation of the PageRank for WarSampo took 0.02182769775390625s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for WarSampo took 9.131431579589844e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 1.9073486328125e-06s
Believability | Calculation of trust value for WarSampo took 1.4543533325195312e-05s
INFO | --- Analysis for warsampo took 983.4224152565002s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.369197368621826s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.3266170024871826s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.02093815803527832s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 9.131431579589844e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 1.5735626220703125e-05s
INFO | --- Analysis for wasabi took 55.5124249458313s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 0.4974246025085449s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.0005223751068115234s
Extra | Recovery of all triples for FAO water areas classification as linked data @PSNC took 100.59837174415588s
Performance | Total latancy measurement for FAO water areas classification as linked data @PSNC took 0.9880430698394775s
Amount of data | Number of triples check for FAO water areas classification as linked data @PSNC took 9.278470993041992s
Interoperability | New terms check for FAO water areas classification as linked data @PSNC took 14.237597942352295s
Versatility | Languages check for FAO water areas classification as linked data @PSNC took 300.16137433052063s
Interpretability | Number of blank nodes check for FAO water areas classification as linked data @PSNC took 1.9881281852722168s
Interpretability | RDF structures check for FAO water areas classification as linked data @PSNC took 0.3261146545410156s
Versatility | Serialization formats check for FAO water areas classification as linked data @PSNC took 9.179601907730103s
Availability | RDF dump link check for FAO water areas classification as linked data @PSNC took 0.2774009704589844s
License | MR license check for FAO water areas classification as linked data @PSNC took 0.628817081451416s
License | HR license check for FAO water areas classification as linked data @PSNC took 300.20725440979004s
Amount of data | Number of property check for FAO water areas classification as linked data @PSNC took 0.23124051094055176s
Understandability | Number of label check for FAO water areas classification as linked data @PSNC took 3.0635600090026855s
Understandability | URI regex check for FAO water areas classification as linked data @PSNC took 1.2838873863220215s
Understandability | Vocabs check for FAO water areas classification as linked data @PSNC took 0.752147912979126s
Verifiability | Authors check for FAO water areas classification as linked data @PSNC took 0.2236628532409668s
Verifiability | Publishers check for FAO water areas classification as linked data @PSNC took 0.26954174041748047s
Performance | Throughput check for FAO water areas classification as linked data @PSNC took 11.10526967048645s
Amount of data | Check the number of entities for FAO water areas classification as linked data @PSNC took 5.698204040527344e-05s
Verifiability | Contribs. check for FAO water areas classification as linked data @PSNC took 0.18517732620239258s
Interlinking | sameAs chians check for FAO water areas classification as linked data @PSNC took 0.20108795166015625s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.500983715057373s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.4270143508911133s
Timeliness | dataset update frequency check for FAO water areas classification as linked data @PSNC took 4.767482757568359s
Currency | Creation date check for FAO water areas classification as linked data @PSNC took 0.48998117446899414s
Currency | Modification date check for FAO water areas classification as linked data @PSNC took 0.23948097229003906s
Rep.Conc. | URIs length for FAO water areas classification as linked data @PSNC took 153.28209972381592s
Interoperability | New vocabularies check for FAO water areas classification as linked data @PSNC took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for FAO water areas classification as linked data @PSNC took 0.2248094081878662s
Accuracy | Check Functional Property for FAO water areas classification as linked data @PSNC took 0.4417433738708496s
Accuracy | Check Inverse Functional Property for FAO water areas classification as linked data @PSNC took 0.4188215732574463s
Accuracy | Check Empty annotation labels for FAO water areas classification as linked data @PSNC took 34.982271909713745s
Accuracy | Check White space in annotation for FAO water areas classification as linked data @PSNC took 2.6881346702575684s
Accuracy | Check Datatype consistency for FAO water areas classification as linked data @PSNC took 2.7624943256378174s
Consistency | Disjoint class check for FAO water areas classification as linked data @PSNC took 0.21114110946655273s
Consistency | Check Misplaced properties for FAO water areas classification as linked data @PSNC took 87.94576454162598s
Consistency | Misplaced classes for FAO water areas classification as linked data @PSNC took 8.632721662521362s
Consistency | Check Ontology hijacking for FAO water areas classification as linked data @PSNC took 34.3519070148468s
Consistency | Check Invalid usage of undefined classes for FAO water areas classification as linked data @PSNC took 1.4981763362884521s
Consistency | Check Invalid usage of undefined properties for FAO water areas classification as linked data @PSNC took 87.35438942909241s
Conciseness | Check Extensional conciseness for FAO water areas classification as linked data @PSNC took 2.803407669067383s
Conciseness | Check Intensional conciseness for FAO water areas classification as linked data @PSNC took 0.659555196762085s
Security | Sign check for FAO water areas classification as linked data @PSNC took 1.2909398078918457s
Availability | Check URIs Dereferenciability for FAO water areas classification as linked data @PSNC took 18.20213770866394s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.5862090587615967s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.021860599517822266s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 5.269050598144531e-05s
Interoperability | Check the re-using of existing vocabs for FAO water areas classification as linked data @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 1.52587890625e-05s
INFO | --- Analysis for Water_Areas_Classification took 2275.495628595352s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 0.17951011657714844s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.0005340576171875s
Extra | Recovery of all triples for Water buffer dataset from Czech Republic @PSNC took 122.76216268539429s
Performance | Total latancy measurement for Water buffer dataset from Czech Republic @PSNC took 0.9674968719482422s
Amount of data | Number of triples check for Water buffer dataset from Czech Republic @PSNC took 9.061514854431152s
Interoperability | New terms check for Water buffer dataset from Czech Republic @PSNC took 14.269327640533447s
Versatility | Languages check for Water buffer dataset from Czech Republic @PSNC took 300.23324489593506s
Interpretability | Number of blank nodes check for Water buffer dataset from Czech Republic @PSNC took 2.283463954925537s
Interpretability | RDF structures check for Water buffer dataset from Czech Republic @PSNC took 0.31826233863830566s
Versatility | Serialization formats check for Water buffer dataset from Czech Republic @PSNC took 10.611916065216064s
Availability | RDF dump link check for Water buffer dataset from Czech Republic @PSNC took 0.3388545513153076s
License | MR license check for Water buffer dataset from Czech Republic @PSNC took 0.8598504066467285s
License | HR license check for Water buffer dataset from Czech Republic @PSNC took 300.1471781730652s
Amount of data | Number of property check for Water buffer dataset from Czech Republic @PSNC took 0.21412920951843262s
Understandability | Number of label check for Water buffer dataset from Czech Republic @PSNC took 2.7891781330108643s
Understandability | URI regex check for Water buffer dataset from Czech Republic @PSNC took 1.2018866539001465s
Understandability | Vocabs check for Water buffer dataset from Czech Republic @PSNC took 0.5905969142913818s
Verifiability | Authors check for Water buffer dataset from Czech Republic @PSNC took 0.21033930778503418s
Verifiability | Publishers check for Water buffer dataset from Czech Republic @PSNC took 0.22668194770812988s
Performance | Throughput check for Water buffer dataset from Czech Republic @PSNC took 11.499171733856201s
Amount of data | Check the number of entities for Water buffer dataset from Czech Republic @PSNC took 9.202957153320312e-05s
Verifiability | Contribs. check for Water buffer dataset from Czech Republic @PSNC took 0.1875019073486328s
Interlinking | sameAs chians check for Water buffer dataset from Czech Republic @PSNC took 0.20337986946105957s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.5441000461578369s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.4593541622161865s
Timeliness | dataset update frequency check for Water buffer dataset from Czech Republic @PSNC took 4.865130424499512s
Currency | Creation date check for Water buffer dataset from Czech Republic @PSNC took 0.46219515800476074s
Currency | Modification date check for Water buffer dataset from Czech Republic @PSNC took 0.22309398651123047s
Rep.Conc. | URIs length for Water buffer dataset from Czech Republic @PSNC took 152.35164165496826s
Interoperability | New vocabularies check for Water buffer dataset from Czech Republic @PSNC took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Water buffer dataset from Czech Republic @PSNC took 0.18296480178833008s
Accuracy | Check Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.4723236560821533s
Accuracy | Check Inverse Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.45906686782836914s
Accuracy | Check Empty annotation labels for Water buffer dataset from Czech Republic @PSNC took 35.27222561836243s
Accuracy | Check White space in annotation for Water buffer dataset from Czech Republic @PSNC took 2.6960084438323975s
Accuracy | Check Datatype consistency for Water buffer dataset from Czech Republic @PSNC took 2.790292978286743s
Consistency | Disjoint class check for Water buffer dataset from Czech Republic @PSNC took 0.20418667793273926s
Consistency | Check Misplaced properties for Water buffer dataset from Czech Republic @PSNC took 88.66234612464905s
Consistency | Misplaced classes for Water buffer dataset from Czech Republic @PSNC took 8.555477619171143s
Consistency | Check Ontology hijacking for Water buffer dataset from Czech Republic @PSNC took 34.6912841796875s
Consistency | Check Invalid usage of undefined classes for Water buffer dataset from Czech Republic @PSNC took 1.4623918533325195s
Consistency | Check Invalid usage of undefined properties for Water buffer dataset from Czech Republic @PSNC took 88.21631050109863s
Conciseness | Check Extensional conciseness for Water buffer dataset from Czech Republic @PSNC took 2.880136013031006s
Conciseness | Check Intensional conciseness for Water buffer dataset from Czech Republic @PSNC took 0.5317234992980957s
Security | Sign check for Water buffer dataset from Czech Republic @PSNC took 1.367192029953003s
Availability | Check URIs Dereferenciability for Water buffer dataset from Czech Republic @PSNC took 9.683936834335327s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.5546665191650391s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.022143125534057617s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 4.363059997558594e-05s
Interoperability | Check the re-using of existing vocabs for Water buffer dataset from Czech Republic @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 1.6927719116210938e-05s
INFO | --- Analysis for Water_Buffer took 2286.5914447307587s
Availability | SPARQL endpoint availability check for WebIsALOD took 0.21640872955322266s
Availability | VoID file availability check for WebIsALOD took 0.0004661083221435547s
Extra | Recovery of all triples for WebIsALOD took 1.1156642436981201s
Performance | Total latancy measurement for WebIsALOD took 0.4300510883331299s
Amount of data | Number of triples check for WebIsALOD took 20.66207718849182s
Interoperability | New terms check for WebIsALOD took 20.654534101486206s
Versatility | Languages check for WebIsALOD took 60.950207471847534s
Interpretability | Number of blank nodes check for WebIsALOD took 0.10634541511535645s
Interpretability | RDF structures check for WebIsALOD took 0.19927573204040527s
Versatility | Serialization formats check for WebIsALOD took 0.11806178092956543s
Availability | RDF dump link check for WebIsALOD took 1.354905128479004s
License | MR license check for WebIsALOD took 0.10221219062805176s
License | HR license check for WebIsALOD took 18.681902408599854s
Amount of data | Number of property check for WebIsALOD took 0.13100385665893555s
Understandability | Number of label check for WebIsALOD took 0.2572922706604004s
Understandability | URI regex check for WebIsALOD took 0.17896556854248047s
Understandability | Vocabs check for WebIsALOD took 0.14057040214538574s
Verifiability | Authors check for WebIsALOD took 0.13442516326904297s
Verifiability | Publishers check for WebIsALOD took 0.11845779418945312s
Performance | Throughput check for WebIsALOD took 10.465535640716553s
Amount of data | Check the number of entities for WebIsALOD took 5.793571472167969e-05s
Verifiability | Contribs. check for WebIsALOD took 0.1309652328491211s
Interlinking | sameAs chians check for WebIsALOD took 0.14760184288024902s
Interlinking | skos check for WebIsALOD took 0.13040971755981445s
Interlinking | skos check for WebIsALOD took 0.07493209838867188s
Timeliness | dataset update frequency check for WebIsALOD took 0.09235119819641113s
Currency | Creation date check for WebIsALOD took 0.23259544372558594s
Currency | Modification date check for WebIsALOD took 0.21781158447265625s
Rep.Conc. | URIs length for WebIsALOD took 79.46085524559021s
Interoperability | New vocabularies check for WebIsALOD took 17.8531391620636s
Consistency | Deprecated classes/propertiers check for WebIsALOD took 0.11317920684814453s
Accuracy | Check Functional Property for WebIsALOD took 0.12916088104248047s
Accuracy | Check Inverse Functional Property for WebIsALOD took 0.09132623672485352s
Accuracy | Check Empty annotation labels for WebIsALOD took 0.40860533714294434s
Accuracy | Check White space in annotation for WebIsALOD took 0.030093669891357422s
Accuracy | Check Datatype consistency for WebIsALOD took 0.03138160705566406s
Consistency | Disjoint class check for WebIsALOD took 0.1110219955444336s
Consistency | Check Misplaced properties for WebIsALOD took 61.642632246017456s
Consistency | Misplaced classes for WebIsALOD took 0.31057286262512207s
Consistency | Check Ontology hijacking for WebIsALOD took 2.216249942779541s
Consistency | Check Invalid usage of undefined classes for WebIsALOD took 1.8213107585906982s
Consistency | Check Invalid usage of undefined properties for WebIsALOD took 62.97643423080444s
Conciseness | Check Extensional conciseness for WebIsALOD took 0.034058570861816406s
Conciseness | Check Intensional conciseness for WebIsALOD took 0.14815926551818848s
Security | Sign check for WebIsALOD took 0.09231925010681152s
Availability | Check URIs Dereferenciability for WebIsALOD took 9.52791452407837s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.4395167827606201s
Reputation | Calculation of the PageRank for WebIsALOD took 0.02263188362121582s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 8.7738037109375e-05s
Interoperability | Check the re-using of existing vocabs for WebIsALOD took 15.290936708450317s
Believability | Calculation of trust value for WebIsALOD took 1.5497207641601562e-05s
INFO | --- Analysis for webisalod took 574.8688893318176s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 0.00010776519775390625s
Availability | VoID file availability check for webnmasunotraveler took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.32671427726745605s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.02125072479248047s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0008409023284912109s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 4.3392181396484375e-05s
Believability | Calculation of trust value for webnmasunotraveler took 1.430511474609375e-05s
INFO | --- Analysis for webnmasunotraveler took 9.528615713119507s
Availability | SPARQL endpoint availability check for Whisky Circle took 0.000102996826171875s
Availability | VoID file availability check for Whisky Circle took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.3208181858062744s
Reputation | Calculation of the PageRank for Whisky Circle took 0.022307872772216797s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0008285045623779297s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00012445449829101562s
Believability | Calculation of trust value for Whisky Circle took 1.430511474609375e-05s
INFO | --- Analysis for whisky-circle-info took 3.632849931716919s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 13.616142749786377s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.00091552734375s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.320690393447876s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.022538423538208008s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 3.552436828613281e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 1.4543533325195312e-05s
INFO | --- Analysis for WHOnto took 33.897520542144775s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 0.0001480579376220703s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0007598400115966797s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.35457873344421387s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.021296262741088867s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for whonto took 8.783164978027344s
Availability | SPARQL endpoint availability check for Wikidata took 0.7326552867889404s
Availability | VoID file availability check for Wikidata took 0.0006730556488037109s
Extra | Recovery of all triples for Wikidata took 56.480414390563965s
Performance | Total latancy measurement for Wikidata took 1.14276123046875s
Amount of data | Number of triples check for Wikidata took 65.16863870620728s
Interoperability | New terms check for Wikidata took 2.1103930473327637s
Versatility | Languages check for Wikidata took 65.16850972175598s
Interpretability | Number of blank nodes check for Wikidata took 65.2455403804779s
Interpretability | RDF structures check for Wikidata took 0.18514657020568848s
Versatility | Serialization formats check for Wikidata took 0.1876983642578125s
Availability | RDF dump link check for Wikidata took 0.15833473205566406s
License | MR license check for Wikidata took 0.6615934371948242s
License | HR license check for Wikidata took 65.18768000602722s
Amount of data | Number of property check for Wikidata took 0.4524192810058594s
Understandability | Number of label check for Wikidata took 60.262983560562134s
Understandability | URI regex check for Wikidata took 0.4297780990600586s
Understandability | Vocabs check for Wikidata took 0.1585700511932373s
Verifiability | Authors check for Wikidata took 0.1872704029083252s
Verifiability | Publishers check for Wikidata took 0.1839280128479004s
Amount of data | Check the number of entities for Wikidata took 7.748603820800781e-05s
Verifiability | Contribs. check for Wikidata took 0.18384742736816406s
Interlinking | sameAs chians check for Wikidata took 22.81349205970764s
Interlinking | skos check for Wikidata took 0.22226905822753906s
Interlinking | skos check for Wikidata took 0.20122432708740234s
Timeliness | dataset update frequency check for Wikidata took 0.19500517845153809s
Currency | Creation date check for Wikidata took 0.3756904602050781s
Currency | Modification date check for Wikidata took 0.38761186599731445s
Rep.Conc. | URIs length for Wikidata took 36.10089921951294s
Interoperability | New vocabularies check for Wikidata took 5.9604644775390625e-06s
Consistency | Deprecated classes/propertiers check for Wikidata took 0.17023992538452148s
Accuracy | Check Empty annotation labels for Wikidata took 12.733278512954712s
Accuracy | Check White space in annotation for Wikidata took 2.6884238719940186s
Accuracy | Check Datatype consistency for Wikidata took 4.689088821411133s
Consistency | Disjoint class check for Wikidata took 0.18244504928588867s
Consistency | Check Misplaced properties for Wikidata took 13.588394165039062s
Consistency | Misplaced classes for Wikidata took 9.049779653549194s
Consistency | Check Ontology hijacking for Wikidata took 33.032830238342285s
Consistency | Check Invalid usage of undefined classes for Wikidata took 1.4934158325195312s
Consistency | Check Invalid usage of undefined properties for Wikidata took 3.3165669441223145s
Conciseness | Check Extensional conciseness for Wikidata took 2.877702474594116s
Conciseness | Check Intensional conciseness for Wikidata took 1.63401460647583s
Security | Sign check for Wikidata took 0.2162494659423828s
Availability | Check URIs Dereferenciability for Wikidata took 8.67833399772644s
Completeness | Calculation of interlinking completeness for Wikidata took 0.6779394149780273s
Reputation | Calculation of the PageRank for Wikidata took 0.02190685272216797s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.00029540061950683594s
Interoperability | Check the re-using of existing vocabs for Wikidata took 1.1920928955078125e-06s
Believability | Calculation of trust value for Wikidata took 1.1444091796875e-05s
INFO | --- Analysis for wikidata took 901.7516067028046s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 5.936622619628906e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.3344767093658447s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.022983074188232422s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 8.034706115722656e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 1.430511474609375e-05s
INFO | --- Analysis for wikilinks-rdf-nif took 3.746316909790039s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.2838304042816162s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.31723904609680176s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.02098560333251953s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 9.298324584960938e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 1.5020370483398438e-05s
INFO | --- Analysis for wiktionary-dbpedia-org took 4.799909830093384s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2499666213989258s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.3174605369567871s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.02088475227355957s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.0279159545898438e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 1.52587890625e-05s
INFO | --- Analysis for wl-kg took 4.630951881408691s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 9.918212890625e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007436275482177734s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.37220215797424316s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.02111959457397461s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 7.605552673339844e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 1.621246337890625e-05s
INFO | --- Analysis for wn-wiki-instances took 3.7327194213867188s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.30891966819763184s
Availability | VoID file availability check for World Loanword Database took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.34273362159729004s
Reputation | Calculation of the PageRank for World Loanword Database took 0.02091073989868164s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 7.748603820800781e-05s
Believability | Calculation of trust value for World Loanword Database took 1.5974044799804688e-05s
INFO | --- Analysis for wold took 3.500112533569336s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 5.1975250244140625e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.294783353805542s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.026680946350097656s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0015139579772949219s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 4.792213439941406e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.5020370483398438e-05s
INFO | --- Analysis for woodtrick took 3.8171989917755127s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 0.47661519050598145s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.00078582763671875s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.3120591640472412s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.021043777465820312s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 4.3392181396484375e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 1.5497207641601562e-05s
INFO | --- Analysis for WordFormationLatin took 4.324044227600098s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 0.0001766681671142578s
Availability | VoID file availability check for WordLift Blog EN took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.2800297737121582s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.02120184898376465s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.00011110305786132812s
Believability | Calculation of trust value for WordLift Blog EN took 1.3589859008789062e-05s
INFO | --- Analysis for wordlift-io-blog-en took 3.5045535564422607s
Availability | SPARQL endpoint availability check for WordLift IT took 5.078315734863281e-05s
Availability | VoID file availability check for WordLift IT took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.2946610450744629s
Reputation | Calculation of the PageRank for WordLift IT took 0.02117919921875s
Interlinking | Calculation of Degree of Connection for WordLift IT took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for WordLift IT took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00011301040649414062s
Believability | Calculation of trust value for WordLift IT took 1.5735626220703125e-05s
INFO | --- Analysis for wordlift-io-blog-it took 3.365313768386841s
Availability | SPARQL endpoint availability check for WordNet-RDF took 0.00010609626770019531s
Availability | VoID file availability check for WordNet-RDF took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.31104493141174316s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.021927595138549805s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.369850158691406e-05s
Believability | Calculation of trust value for WordNet-RDF took 1.5497207641601562e-05s
INFO | --- Analysis for wordnet-rdf took 2.926217794418335s
Availability | SPARQL endpoint availability check for wordpress took 6.246566772460938e-05s
Availability | VoID file availability check for wordpress took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for wordpress took 0.323352575302124s
Reputation | Calculation of the PageRank for wordpress took 0.022928237915039062s
Interlinking | Calculation of Degree of Connection for wordpress took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for wordpress took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.749961853027344e-05s
Believability | Calculation of trust value for wordpress took 1.4781951904296875e-05s
INFO | --- Analysis for wordpress took 3.001190185546875s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 0.12374353408813477s
Availability | VoID file availability check for World Bank Linked Data took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.276824951171875s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.021700382232666016s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00012445449829101562s
Believability | Calculation of trust value for World Bank Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for world-bank-linked-data took 2.9661736488342285s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 0.9825439453125s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.338270902633667s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.021285295486450195s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.96453857421875e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 1.52587890625e-05s
INFO | --- Analysis for world-factbook-fu-berlin took 5.723623037338257s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 9.894371032714844e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0007588863372802734s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.3416600227355957s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.021059274673461914s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.845329284667969e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 1.049041748046875e-05s
INFO | --- Analysis for world-wide-web-foundation took 6.189091920852661s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.33401989936828613s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0006649494171142578s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 3.5260939598083496s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.796684741973877s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.24128246307373047s
Interoperability | New terms check for World War 1 as Linked Open Data took 2.0932681560516357s
Versatility | Languages check for World War 1 as Linked Open Data took 0.43289995193481445s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.23773884773254395s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.42060232162475586s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.5730199813842773s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.2549753189086914s
Availability | RDF dump link check for World War 1 as Linked Open Data took 7.107771635055542s
License | MR license check for World War 1 as Linked Open Data took 0.25335121154785156s
License | HR license check for World War 1 as Linked Open Data took 1.6590442657470703s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.1930556297302246s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.5193288326263428s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.36966490745544434s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.23510169982910156s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.18399691581726074s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.20625567436218262s
Performance | Throughput check for World War 1 as Linked Open Data took 11.063290119171143s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.07781195640563965s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.18485116958618164s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.5150327682495117s
Interlinking | skos check for World War 1 as Linked Open Data took 0.19401788711547852s
Interlinking | skos check for World War 1 as Linked Open Data took 0.16488289833068848s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.1954331398010254s
Currency | Creation date check for World War 1 as Linked Open Data took 0.3952615261077881s
Currency | Modification date check for World War 1 as Linked Open Data took 0.19724106788635254s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 1.9907455444335938s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 27.875714778900146s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.24500703811645508s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.19043922424316406s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.16699814796447754s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.195826768875122s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.05079030990600586s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.32245969772338867s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.18355679512023926s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.5909988880157471s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.1278936862945557s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.3513798713684082s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.6025002002716064s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.19611811637878418s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.825059175491333s
Security | Sign check for World War 1 as Linked Open Data took 0.19189095497131348s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1579.0939724445343s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.555917501449585s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.023720741271972656s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0008640289306640625s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 0.0001621246337890625s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 21.28365683555603s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 2.5033950805664062e-05s
INFO | --- Analysis for ww1lod took 1699.6043679714203s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.34023475646972656s
Availability | VoID file availability check for xLiD-Lexica took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.34168386459350586s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.020990371704101562s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 4.076957702636719e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 7.05718994140625e-05s
Believability | Calculation of trust value for xLiD-Lexica took 7.62939453125e-06s
INFO | --- Analysis for xlid-lexica took 4.598013639450073s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 5.125999450683594e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.3093552589416504s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.02075052261352539s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.8623809814453125e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 1.5020370483398438e-05s
INFO | --- Analysis for xwn took 3.417531728744507s
Availability | SPARQL endpoint availability check for xxx took 0.00010442733764648438s
Availability | VoID file availability check for xxx took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for xxx took 0.2920191287994385s
Reputation | Calculation of the PageRank for xxx took 0.021689414978027344s
Interlinking | Calculation of Degree of Connection for xxx took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for xxx took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for xxx took 3.170967102050781e-05s
Believability | Calculation of trust value for xxx took 1.4543533325195312e-05s
INFO | --- Analysis for xx took 2.816917896270752s
Availability | SPARQL endpoint availability check for YAGO took 9.751319885253906e-05s
Availability | VoID file availability check for YAGO took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for YAGO took 0.3344700336456299s
Reputation | Calculation of the PageRank for YAGO took 0.021941661834716797s
Interlinking | Calculation of Degree of Connection for YAGO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.00013494491577148438s
Believability | Calculation of trust value for YAGO took 1.52587890625e-05s
INFO | --- Analysis for yago took 5.033398866653442s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 2.6844844818115234s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.32637882232666016s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.02084803581237793s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 8.058547973632812e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 1.4543533325195312e-05s
INFO | --- Analysis for yahoo_geoplanet took 14.833443641662598s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.13806486129760742s
Availability | VoID file availability check for Yale Senselab took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.30419397354125977s
Reputation | Calculation of the PageRank for Yale Senselab took 0.020915746688842773s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 3.147125244140625e-05s
Believability | Calculation of trust value for Yale Senselab took 1.4781951904296875e-05s
INFO | --- Analysis for yale_senselab took 15.362836599349976s
Availability | SPARQL endpoint availability check for test-dapp-2 took 0.00010323524475097656s
Availability | VoID file availability check for test-dapp-2 took 0.0005967617034912109s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.5242898464202881s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.021474599838256836s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 3.409385681152344e-05s
Believability | Calculation of trust value for test-dapp-2 took 1.5020370483398438e-05s
INFO | --- Analysis for yordhis took 3.261493682861328s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 0.8430814743041992s
Availability | VoID file availability check for Yovisto - academic video search took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.3267948627471924s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.020961999893188477s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 7.843971252441406e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 1.1205673217773438e-05s
INFO | --- Analysis for yovisto took 24.725426197052002s
Availability | SPARQL endpoint availability check for YSA - General Finnish Thesaurus took 5.269050598144531e-05s
Availability | VoID file availability check for YSA - General Finnish Thesaurus took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for YSA - General Finnish Thesaurus took 0.3405897617340088s
Reputation | Calculation of the PageRank for YSA - General Finnish Thesaurus took 0.02085280418395996s
Interlinking | Calculation of Degree of Connection for YSA - General Finnish Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for YSA - General Finnish Thesaurus took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for YSA - General Finnish Thesaurus took 3.7670135498046875e-05s
Believability | Calculation of trust value for YSA - General Finnish Thesaurus took 1.4543533325195312e-05s
INFO | --- Analysis for ysa took 4.285607814788818s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 9.894371032714844e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.3297538757324219s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.02178049087524414s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.602836608886719e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 1.4066696166992188e-05s
INFO | --- Analysis for yso took 4.535603284835815s
Availability | SPARQL endpoint availability check for yso-fi-allars took 5.0067901611328125e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0008127689361572266s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.3208000659942627s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.0209197998046875s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.4809112548828125e-05s
Believability | Calculation of trust value for yso-fi-allars took 1.3828277587890625e-05s
INFO | --- Analysis for yso-fi-allars took 3.5946898460388184s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 0.00010418891906738281s
Availability | VoID file availability check for yso-fi-ysa took 0.0008985996246337891s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.5391662120819092s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.02108597755432129s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.552436828613281e-05s
Believability | Calculation of trust value for yso-fi-ysa took 1.8596649169921875e-05s
INFO | --- Analysis for yso-fi-ysa took 3.542003631591797s
Availability | SPARQL endpoint availability check for YSO places took 0.6601014137268066s
Availability | VoID file availability check for YSO places took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for YSO places took 0.30101990699768066s
Reputation | Calculation of the PageRank for YSO places took 0.02072739601135254s
Interlinking | Calculation of Degree of Connection for YSO places took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for YSO places took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for YSO places took 3.337860107421875e-05s
Believability | Calculation of trust value for YSO places took 1.430511474609375e-05s
INFO | --- Analysis for yso-paikat took 4.606796026229858s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 6.341934204101562e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0008368492126464844s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.37068843841552734s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.021881580352783203s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.838539123535156e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 1.049041748046875e-05s
INFO | --- Analysis for zaragoza-datosabiertos took 7.856290817260742s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 5.245208740234375e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.3341691493988037s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.022108793258666992s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.886222839355469e-05s
Believability | Calculation of trust value for zaragoza_turruta took 1.4543533325195312e-05s
INFO | --- Analysis for zaragoza_turruta took 3.0851736068725586s
Availability | SPARQL endpoint availability check for ZBW Labs took 0.000194549560546875s
Availability | VoID file availability check for ZBW Labs took 0.0007226467132568359s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.3762803077697754s
Reputation | Calculation of the PageRank for ZBW Labs took 0.021109342575073242s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 7.081031799316406e-05s
Believability | Calculation of trust value for ZBW Labs took 1.5974044799804688e-05s
INFO | --- Analysis for zbw-labs took 3.9663238525390625s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.17345476150512695s
Availability | VoID file availability check for 20th Century Press Archives took 0.0006797313690185547s
Extra | Recovery of all triples for 20th Century Press Archives took 0.12627410888671875s
Performance | Total latancy measurement for 20th Century Press Archives took 0.789423942565918s
Amount of data | Number of triples check for 20th Century Press Archives took 1.1665005683898926s
Interoperability | New terms check for 20th Century Press Archives took 1.7342112064361572s
Versatility | Languages check for 20th Century Press Archives took 3.4242465496063232s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.9340238571166992s
Interpretability | RDF structures check for 20th Century Press Archives took 0.14884471893310547s
Versatility | Serialization formats check for 20th Century Press Archives took 0.14263582229614258s
Availability | RDF dump link check for 20th Century Press Archives took 0.15190720558166504s
License | MR license check for 20th Century Press Archives took 0.17325735092163086s
License | HR license check for 20th Century Press Archives took 5.6646833419799805s
Amount of data | Number of property check for 20th Century Press Archives took 0.1559455394744873s
Understandability | Number of label check for 20th Century Press Archives took 0.5718278884887695s
Understandability | URI regex check for 20th Century Press Archives took 0.28443050384521484s
Understandability | Vocabs check for 20th Century Press Archives took 0.15664434432983398s
Verifiability | Authors check for 20th Century Press Archives took 0.1263875961303711s
Verifiability | Publishers check for 20th Century Press Archives took 0.1383199691772461s
Performance | Throughput check for 20th Century Press Archives took 10.513179063796997s
Amount of data | Check the number of entities for 20th Century Press Archives took 0.000118255615234375s
Verifiability | Contribs. check for 20th Century Press Archives took 0.13869380950927734s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.13168907165527344s
Interlinking | skos check for 20th Century Press Archives took 0.1807246208190918s
Interlinking | skos check for 20th Century Press Archives took 0.20160198211669922s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.14247822761535645s
Currency | Creation date check for 20th Century Press Archives took 0.27261948585510254s
Currency | Modification date check for 20th Century Press Archives took 0.3100104331970215s
Rep.Conc. | URIs length for 20th Century Press Archives took 11.629562139511108s
Interoperability | New vocabularies check for 20th Century Press Archives took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.1764051914215088s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.15002846717834473s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.16358232498168945s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 4.1663877964019775s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8911457061767578s
Consistency | Disjoint class check for 20th Century Press Archives took 0.16155338287353516s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.516413927078247s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.889862298965454s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.7355310916900635s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 0.00016069412231445312s
Security | Sign check for 20th Century Press Archives took 0.15534186363220215s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 1058.946739912033s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.5246169567108154s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.022325992584228516s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00011277198791503906s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 5.0067901611328125e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 1.5020370483398438e-05s
INFO | --- Analysis for zbw-pressemappe20 took 1133.0410151481628s
Availability | SPARQL endpoint availability check for zhishi.lemon took 0.00013709068298339844s
Availability | VoID file availability check for zhishi.lemon took 0.0007243156433105469s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.4971482753753662s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.021054744720458984s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0008282661437988281s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 5.030632019042969e-05s
Believability | Calculation of trust value for zhishi.lemon took 1.4543533325195312e-05s
INFO | --- Analysis for zhishi-lemon took 25.207154035568237s
Availability | SPARQL endpoint availability check for Zhishi.me took 5.777681827545166s
Availability | VoID file availability check for Zhishi.me took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.32317066192626953s
Reputation | Calculation of the PageRank for Zhishi.me took 0.02117753028869629s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0008378028869628906s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 7.653236389160156e-05s
Believability | Calculation of trust value for Zhishi.me took 1.5020370483398438e-05s
INFO | --- Analysis for zhishi-me took 11.500139236450195s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.839897155761719e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.3372802734375s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.0209500789642334s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 7.891654968261719e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 1.430511474609375e-05s
INFO | --- Analysis for zitgist-musicbrainz took 3.423764944076538s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 0.00010442733764648438s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.29099488258361816s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.02162766456604004s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007984638214111328s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 3.62396240234375e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 1.430511474609375e-05s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 3.0144283771514893s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.6771583557128906s
Availability | VoID file availability check for performing-arts.ch took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.29907941818237305s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.02100539207458496s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.3589859008789062e-05s
Believability | Calculation of trust value for performing-arts.ch took 1.9073486328125e-05s
INFO | --- Analysis for performing-arts.ch took 4.977905511856079s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.867464303970337s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.33166956901550293s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.021270751953125s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.3828277587890625e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 1.430511474609375e-05s
INFO | --- Analysis for The-AA-Thesaurus took 9.033948421478271s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.7516164779663086s
Availability | VoID file availability check for MiMoTextBase took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.39089465141296387s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.021149873733520508s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.5735626220703125e-05s
Believability | Calculation of trust value for MiMoTextBase took 1.6689300537109375e-05s
INFO | --- Analysis for MiMoTextBase took 7.038098096847534s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.5502893924713135s
Availability | VoID file availability check for National Library of Sweden took 0.0006084442138671875s
Extra | Recovery of all triples for National Library of Sweden took 6.70081090927124s
Performance | Total latancy measurement for National Library of Sweden took 1.0410854816436768s
Amount of data | Number of triples check for National Library of Sweden took 19.161511659622192s
Interoperability | New terms check for National Library of Sweden took 18.049235105514526s
Versatility | Languages check for National Library of Sweden took 0.22596979141235352s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.1999936103821s
Interpretability | RDF structures check for National Library of Sweden took 0.2813124656677246s
Versatility | Serialization formats check for National Library of Sweden took 0.22669768333435059s
Availability | RDF dump link check for National Library of Sweden took 0.20303106307983398s
License | MR license check for National Library of Sweden took 0.23344755172729492s
License | HR license check for National Library of Sweden took 0.2067713737487793s
Amount of data | Number of property check for National Library of Sweden took 0.2308793067932129s
Understandability | Number of label check for National Library of Sweden took 0.22835135459899902s
Understandability | URI regex check for National Library of Sweden took 0.40796613693237305s
Understandability | Vocabs check for National Library of Sweden took 0.21580958366394043s
Verifiability | Authors check for National Library of Sweden took 0.22864770889282227s
Verifiability | Publishers check for National Library of Sweden took 0.20342707633972168s
Performance | Throughput check for National Library of Sweden took 10.591501712799072s
Amount of data | Check the number of entities for National Library of Sweden took 0.00010371208190917969s
Verifiability | Contribs. check for National Library of Sweden took 0.23034048080444336s
Interlinking | sameAs chians check for National Library of Sweden took 0.20584702491760254s
Interlinking | skos check for National Library of Sweden took 0.20720171928405762s
Interlinking | skos check for National Library of Sweden took 0.21348905563354492s
Timeliness | dataset update frequency check for National Library of Sweden took 0.22919487953186035s
Currency | Creation date check for National Library of Sweden took 0.4207158088684082s
Currency | Modification date check for National Library of Sweden took 0.42251014709472656s
Rep.Conc. | URIs length for National Library of Sweden took 91.9449872970581s
Interoperability | New vocabularies check for National Library of Sweden took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.22722363471984863s
Accuracy | Check Functional Property for National Library of Sweden took 0.21399617195129395s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.2243196964263916s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.27956223487854004s
Consistency | Disjoint class check for National Library of Sweden took 0.2149369716644287s
Consistency | Check Misplaced properties for National Library of Sweden took 70.91302156448364s
Consistency | Misplaced classes for National Library of Sweden took 1.1527564525604248s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.2929282188415527s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.3468070030212402s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 71.74365234375s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.29480886459350586s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.36452221870422363s
Security | Sign check for National Library of Sweden took 0.22691130638122559s
Availability | Check URIs Dereferenciability for National Library of Sweden took 9.955772638320923s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.6151602268218994s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.021204710006713867s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 6.961822509765625e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.430511474609375e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.5497207641601562e-05s
INFO | --- Analysis for NLS took 1404.6072976589203s
Availability | SPARQL endpoint availability check for Japan Search took 1.1888439655303955s
Availability | VoID file availability check for Japan Search took 0.0005490779876708984s
Extra | Recovery of all triples for Japan Search took 3.440670967102051s
Performance | Total latancy measurement for Japan Search took 2.4184072017669678s
Amount of data | Number of triples check for Japan Search took 5.694881916046143s
Interoperability | New terms check for Japan Search took 4.169628858566284s
Versatility | Languages check for Japan Search took 0.26412224769592285s
Interpretability | Number of blank nodes check for Japan Search took 13.393970012664795s
Interpretability | RDF structures check for Japan Search took 0.4307398796081543s
Versatility | Serialization formats check for Japan Search took 0.43369293212890625s
Availability | RDF dump link check for Japan Search took 0.7896416187286377s
License | MR license check for Japan Search took 1.0830423831939697s
License | HR license check for Japan Search took 91.24150848388672s
Amount of data | Number of property check for Japan Search took 0.765251636505127s
Understandability | Number of label check for Japan Search took 3.250333786010742s
Understandability | URI regex check for Japan Search took 0.5465703010559082s
Understandability | Vocabs check for Japan Search took 0.7603659629821777s
Verifiability | Authors check for Japan Search took 0.3595426082611084s
Verifiability | Publishers check for Japan Search took 0.2843620777130127s
Performance | Throughput check for Japan Search took 11.285070657730103s
Amount of data | Check the number of entities for Japan Search took 4.696846008300781e-05s
Verifiability | Contribs. check for Japan Search took 0.2613790035247803s
Interlinking | sameAs chians check for Japan Search took 0.2893831729888916s
Interlinking | skos check for Japan Search took 0.35509157180786133s
Interlinking | skos check for Japan Search took 0.3068554401397705s
Timeliness | dataset update frequency check for Japan Search took 0.3892800807952881s
Currency | Creation date check for Japan Search took 0.5676701068878174s
Currency | Modification date check for Japan Search took 0.5654313564300537s
Rep.Conc. | URIs length for Japan Search took 29.99459743499756s
Interoperability | New vocabularies check for Japan Search took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.7131876945495605s
Accuracy | Check Empty annotation labels for Japan Search took 2.217937469482422s
Accuracy | Check White space in annotation for Japan Search took 0.029603242874145508s
Accuracy | Check Datatype consistency for Japan Search took 0.030585050582885742s
Consistency | Disjoint class check for Japan Search took 0.31227898597717285s
Consistency | Check Misplaced properties for Japan Search took 26.739550828933716s
Consistency | Misplaced classes for Japan Search took 1.083296298980713s
Consistency | Check Ontology hijacking for Japan Search took 3.5625855922698975s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.3603236675262451s
Consistency | Check Invalid usage of undefined properties for Japan Search took 28.450753688812256s
Conciseness | Check Extensional conciseness for Japan Search took 0.037307024002075195s
Conciseness | Check Intensional conciseness for Japan Search took 0.5394449234008789s
Security | Sign check for Japan Search took 0.3042259216308594s
Availability | Check URIs Dereferenciability for Japan Search took 8.431948900222778s
Completeness | Calculation of interlinking completeness for Japan Search took 0.45318007469177246s
Reputation | Calculation of the PageRank for Japan Search took 0.02173781394958496s
Interlinking | Calculation of Degree of Connection for Japan Search took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for Japan Search took 2.4557113647460938e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 1.6689300537109375e-06s
Believability | Calculation of trust value for Japan Search took 1.0728836059570312e-05s
INFO | --- Analysis for Japan-Search took 639.4474453926086s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.0968554019927979s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0003273487091064453s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.34670567512512207s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.02135610580444336s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.3113021850585938e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.4781951904296875e-05s
INFO | --- Analysis for Rijksmuseum took 5.364983797073364s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.8882360458374023s
Availability | VoID file availability check for Finnish Public Libraries took 0.0007050037384033203s
Extra | Recovery of all triples for Finnish Public Libraries took 67.17937874794006s
Performance | Total latancy measurement for Finnish Public Libraries took 1.0615129470825195s
Amount of data | Number of triples check for Finnish Public Libraries took 60.13187265396118s
Interoperability | New terms check for Finnish Public Libraries took 17.224714279174805s
Versatility | Languages check for Finnish Public Libraries took 60.33616781234741s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 57.19631767272949s
Interpretability | RDF structures check for Finnish Public Libraries took 0.45276856422424316s
Versatility | Serialization formats check for Finnish Public Libraries took 0.33389925956726074s
Availability | RDF dump link check for Finnish Public Libraries took 0.10987234115600586s
License | MR license check for Finnish Public Libraries took 0.2395007610321045s
License | HR license check for Finnish Public Libraries took 34.963621377944946s
Amount of data | Number of property check for Finnish Public Libraries took 0.33040547370910645s
Understandability | Number of label check for Finnish Public Libraries took 12.988792419433594s
Understandability | URI regex check for Finnish Public Libraries took 0.4579010009765625s
Understandability | Vocabs check for Finnish Public Libraries took 0.12184023857116699s
Verifiability | Authors check for Finnish Public Libraries took 0.29935550689697266s
Verifiability | Publishers check for Finnish Public Libraries took 0.1362595558166504s
Performance | Throughput check for Finnish Public Libraries took 11.072798013687134s
Amount of data | Check the number of entities for Finnish Public Libraries took 8.177757263183594e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.16179203987121582s
Interlinking | sameAs chians check for Finnish Public Libraries took 12.660799503326416s
Interlinking | skos check for Finnish Public Libraries took 0.15505290031433105s
Interlinking | skos check for Finnish Public Libraries took 0.1250779628753662s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.13080930709838867s
Currency | Creation date check for Finnish Public Libraries took 0.2739756107330322s
Currency | Modification date check for Finnish Public Libraries took 0.33499717712402344s
Rep.Conc. | URIs length for Finnish Public Libraries took 106.37034702301025s
Interoperability | New vocabularies check for Finnish Public Libraries took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.43640947341918945s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 8.005393266677856s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.251185894012451s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.570316314697266s
Consistency | Disjoint class check for Finnish Public Libraries took 0.2224273681640625s
Consistency | Check Misplaced properties for Finnish Public Libraries took 60.63059949874878s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 14.937479734420776s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.6446609497070312s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 61.8139853477478s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.8055732250213623s
Security | Sign check for Finnish Public Libraries took 0.3994119167327881s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 0.8537845611572266s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.7163164615631104s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.022281408309936523s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0008368492126464844s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.52587890625e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 2.384185791015625e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 1.5974044799804688e-05s
INFO | --- Analysis for FI-Library took 1332.431468963623s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 2.4314558506011963s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0005071163177490234s
Extra | Recovery of all triples for Shanghai Library Open Data Platform took 10.564758062362671s
Performance | Total latancy measurement for Shanghai Library Open Data Platform took 3.444669008255005s
Amount of data | Number of triples check for Shanghai Library Open Data Platform took 2.2458713054656982s
Interoperability | New terms check for Shanghai Library Open Data Platform took 4.863336086273193s
Versatility | Languages check for Shanghai Library Open Data Platform took 60.69304132461548s
Interpretability | Number of blank nodes check for Shanghai Library Open Data Platform took 2.0010323524475098s
Interpretability | RDF structures check for Shanghai Library Open Data Platform took 1.0766313076019287s
Versatility | Serialization formats check for Shanghai Library Open Data Platform took 0.8351130485534668s
Availability | RDF dump link check for Shanghai Library Open Data Platform took 0.7728004455566406s
License | MR license check for Shanghai Library Open Data Platform took 1.0814251899719238s
License | HR license check for Shanghai Library Open Data Platform took 31.913389444351196s
Amount of data | Number of property check for Shanghai Library Open Data Platform took 0.6792924404144287s
Understandability | Number of label check for Shanghai Library Open Data Platform took 1.2743175029754639s
Understandability | URI regex check for Shanghai Library Open Data Platform took 1.50754976272583s
Understandability | Vocabs check for Shanghai Library Open Data Platform took 0.749652624130249s
Verifiability | Authors check for Shanghai Library Open Data Platform took 0.8114538192749023s
Verifiability | Publishers check for Shanghai Library Open Data Platform took 0.7773995399475098s
Performance | Throughput check for Shanghai Library Open Data Platform took 13.623822689056396s
Amount of data | Check the number of entities for Shanghai Library Open Data Platform took 7.724761962890625e-05s
Verifiability | Contribs. check for Shanghai Library Open Data Platform took 0.7257390022277832s
Interlinking | sameAs chians check for Shanghai Library Open Data Platform took 0.7211716175079346s
Interlinking | skos check for Shanghai Library Open Data Platform took 0.99735426902771s
Interlinking | skos check for Shanghai Library Open Data Platform took 0.7227687835693359s
Timeliness | dataset update frequency check for Shanghai Library Open Data Platform took 0.7882211208343506s
Currency | Creation date check for Shanghai Library Open Data Platform took 1.481170654296875s
Currency | Modification date check for Shanghai Library Open Data Platform took 1.4904942512512207s
Rep.Conc. | URIs length for Shanghai Library Open Data Platform took 11.491822481155396s
Interoperability | New vocabularies check for Shanghai Library Open Data Platform took 5.9604644775390625e-06s
Consistency | Deprecated classes/propertiers check for Shanghai Library Open Data Platform took 0.6963834762573242s
Accuracy | Check Functional Property for Shanghai Library Open Data Platform took 0.7128660678863525s
Accuracy | Check Inverse Functional Property for Shanghai Library Open Data Platform took 0.6998827457427979s
Accuracy | Check Empty annotation labels for Shanghai Library Open Data Platform took 2.859452486038208s
Accuracy | Check White space in annotation for Shanghai Library Open Data Platform took 0.06654071807861328s
Accuracy | Check Datatype consistency for Shanghai Library Open Data Platform took 0.14313745498657227s
Consistency | Disjoint class check for Shanghai Library Open Data Platform took 0.8404760360717773s
Consistency | Check Misplaced properties for Shanghai Library Open Data Platform took 6.221233129501343s
Consistency | Misplaced classes for Shanghai Library Open Data Platform took 1.307612419128418s
Consistency | Check Ontology hijacking for Shanghai Library Open Data Platform took 4.859530687332153s
Consistency | Check Invalid usage of undefined classes for Shanghai Library Open Data Platform took 1.5789072513580322s
Consistency | Check Invalid usage of undefined properties for Shanghai Library Open Data Platform took 7.164211988449097s
Conciseness | Check Extensional conciseness for Shanghai Library Open Data Platform took 0.15685319900512695s
Conciseness | Check Intensional conciseness for Shanghai Library Open Data Platform took 1.1270792484283447s
Security | Sign check for Shanghai Library Open Data Platform took 0.9153478145599365s
Availability | Check URIs Dereferenciability for Shanghai Library Open Data Platform took 9.923534393310547s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.5825352668762207s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.024005889892578125s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.8835067749023438e-05s
Interoperability | Check the re-using of existing vocabs for Shanghai Library Open Data Platform took 2.1457672119140625e-06s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 1.52587890625e-05s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 299.31553077697754s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.37748384475708s
Availability | VoID file availability check for National Library Netherlands took 0.0006623268127441406s
Extra | Recovery of all triples for National Library Netherlands took 0.6321823596954346s
Performance | Total latancy measurement for National Library Netherlands took 0.7506136894226074s
Amount of data | Number of triples check for National Library Netherlands took 0.14845776557922363s
Interoperability | New terms check for National Library Netherlands took 1.5603201389312744s
Versatility | Languages check for National Library Netherlands took 58.14909267425537s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.15401339530944824s
Interpretability | RDF structures check for National Library Netherlands took 0.16919398307800293s
Versatility | Serialization formats check for National Library Netherlands took 0.14355683326721191s
Availability | RDF dump link check for National Library Netherlands took 0.1546468734741211s
License | MR license check for National Library Netherlands took 0.18699026107788086s
License | HR license check for National Library Netherlands took 0.20192241668701172s
Amount of data | Number of property check for National Library Netherlands took 0.13486289978027344s
Understandability | Number of label check for National Library Netherlands took 0.15000081062316895s
Understandability | URI regex check for National Library Netherlands took 0.33256077766418457s
Understandability | Vocabs check for National Library Netherlands took 0.16022467613220215s
Verifiability | Authors check for National Library Netherlands took 0.16157293319702148s
Verifiability | Publishers check for National Library Netherlands took 0.15474200248718262s
Performance | Throughput check for National Library Netherlands took 10.399014711380005s
Amount of data | Check the number of entities for National Library Netherlands took 8.344650268554688e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.1355607509613037s
Interlinking | sameAs chians check for National Library Netherlands took 0.1430373191833496s
Interlinking | skos check for National Library Netherlands took 0.14429450035095215s
Interlinking | skos check for National Library Netherlands took 0.14708900451660156s
Timeliness | dataset update frequency check for National Library Netherlands took 0.15854811668395996s
Currency | Creation date check for National Library Netherlands took 0.284623384475708s
Currency | Modification date check for National Library Netherlands took 0.2904508113861084s
Rep.Conc. | URIs length for National Library Netherlands took 0.6594033241271973s
Interoperability | New vocabularies check for National Library Netherlands took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.14888763427734375s
Accuracy | Check Functional Property for National Library Netherlands took 0.14394855499267578s
Accuracy | Check Inverse Functional Property for National Library Netherlands took 0.14669442176818848s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.4983859062194824s
Accuracy | Check White space in annotation for National Library Netherlands took 0.027580976486206055s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.02879166603088379s
Consistency | Disjoint class check for National Library Netherlands took 0.15616083145141602s
Consistency | Check Misplaced properties for National Library Netherlands took 0.34253573417663574s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.9141178131103516s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 1.516106128692627s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.689544916152954s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.031052589416503906s
Security | Sign check for National Library Netherlands took 0.14675354957580566s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1716.2811794281006s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.62615966796875s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.02682638168334961s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 2.4080276489257812e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Library Netherlands took 1.4066696166992188e-05s
INFO | --- Analysis for National-Library-Netherlands took 1822.050103187561s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.5745728015899658s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.3733999729156494s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.021528005599975586s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.4066696166992188e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.5020370483398438e-05s
INFO | --- Analysis for Antique-Renaissance took 6.736250400543213s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 6.530436754226685s
Availability | VoID file availability check for ARTSDATA.CA took 0.0009286403656005859s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.34162282943725586s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.020941495895385742s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.3113021850585938e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 1.4543533325195312e-05s
INFO | --- Analysis for ARTSDATA-CA took 12.675801277160645s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.25678563117980957s
Availability | VoID file availability check for Architecture of Knowledge took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.30394816398620605s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.02083563804626465s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.33514404296875e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 8.344650268554688e-06s
INFO | --- Analysis for ArCo took 4.511657238006592s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.3763575553894043s
Availability | VoID file availability check for ConfermentSampo took 0.0005221366882324219s
Extra | Recovery of all triples for ConfermentSampo took 21.6479172706604s
Performance | Total latancy measurement for ConfermentSampo took 0.8270852565765381s
Amount of data | Number of triples check for ConfermentSampo took 9.186220407485962s
Interoperability | New terms check for ConfermentSampo took 2.54957914352417s
Versatility | Languages check for ConfermentSampo took 26.99001383781433s
Interpretability | Number of blank nodes check for ConfermentSampo took 8.441414594650269s
Security | Check HTTPS for ConfermentSampo took 0.4133768081665039s
Interpretability | RDF structures check for ConfermentSampo took 0.20830702781677246s
Versatility | Serialization formats check for ConfermentSampo took 0.21354460716247559s
Availability | RDF dump link check for ConfermentSampo took 3.042634963989258s
License | MR license check for ConfermentSampo took 0.20998692512512207s
License | HR license check for ConfermentSampo took 0.23620939254760742s
Amount of data | Number of property check for ConfermentSampo took 0.18613934516906738s
Understandability | Number of label check for ConfermentSampo took 5.60326623916626s
Understandability | URI regex check for ConfermentSampo took 0.3832981586456299s
Understandability | Vocabs check for ConfermentSampo took 0.17041802406311035s
Verifiability | Authors check for ConfermentSampo took 0.2359328269958496s
Verifiability | Publishers check for ConfermentSampo took 0.2060837745666504s
Performance | Throughput check for ConfermentSampo took 11.106796741485596s
Amount of data | Check the number of entities for ConfermentSampo took 4.427722692489624s
Verifiability | Contribs. check for ConfermentSampo took 0.16021513938903809s
Interlinking | sameAs chians check for ConfermentSampo took 0.4650301933288574s
Interlinking | skos check for ConfermentSampo took 0.1658327579498291s
Interlinking | skos check for ConfermentSampo took 0.16547369956970215s
Timeliness | dataset update frequency check for ConfermentSampo took 0.16681885719299316s
Currency | Creation date check for ConfermentSampo took 0.3667030334472656s
Currency | Modification date check for ConfermentSampo took 0.3475685119628906s
Rep.Conc. | URIs length for ConfermentSampo took 35.404542684555054s
Interoperability | New vocabularies check for ConfermentSampo took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.1988687515258789s
Accuracy | Check Functional Property for ConfermentSampo took 0.19536566734313965s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.16451525688171387s
Accuracy | Check Empty annotation labels for ConfermentSampo took 15.38793683052063s
Accuracy | Check White space in annotation for ConfermentSampo took 3.0385990142822266s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.372330904006958s
Consistency | Disjoint class check for ConfermentSampo took 0.1686091423034668s
Consistency | Check Misplaced properties for ConfermentSampo took 6.5470757484436035s
Consistency | Check Ontology hijacking for ConfermentSampo took 15.350766897201538s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.543215274810791s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.676957130432129s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.912813186645508s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.2009563446044922s
Security | Sign check for ConfermentSampo took 0.17197155952453613s
Availability | Check URIs Dereferenciability for ConfermentSampo took 1402.0828449726105s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.820451021194458s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.026502370834350586s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.7642974853515625e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 2.6226043701171875e-06s
Believability | Calculation of trust value for ConfermentSampo took 1.6450881958007812e-05s
INFO | --- Analysis for ConfermentSampo took 1710.1590206623077s
Availability | SPARQL endpoint availability check for Museum Finland took 0.6233019828796387s
Availability | VoID file availability check for Museum Finland took 0.0005459785461425781s
Extra | Recovery of all triples for Museum Finland took 6.340074300765991s
Performance | Total latancy measurement for Museum Finland took 0.8110411167144775s
Amount of data | Number of triples check for Museum Finland took 0.34699034690856934s
Interoperability | New terms check for Museum Finland took 1.83990478515625s
Versatility | Languages check for Museum Finland took 0.6816515922546387s
Interpretability | Number of blank nodes check for Museum Finland took 0.4328131675720215s
Security | Check HTTPS for Museum Finland took 0.24426555633544922s
Interpretability | RDF structures check for Museum Finland took 0.3063654899597168s
Versatility | Serialization formats check for Museum Finland took 0.20734000205993652s
Availability | RDF dump link check for Museum Finland took 0.16912412643432617s
License | MR license check for Museum Finland took 0.1961376667022705s
License | HR license check for Museum Finland took 0.3855116367340088s
Amount of data | Number of property check for Museum Finland took 0.19524264335632324s
Understandability | Number of label check for Museum Finland took 0.3156254291534424s
Understandability | URI regex check for Museum Finland took 0.32268595695495605s
Understandability | Vocabs check for Museum Finland took 0.15350818634033203s
Verifiability | Authors check for Museum Finland took 0.1831812858581543s
Verifiability | Publishers check for Museum Finland took 0.15350914001464844s
Performance | Throughput check for Museum Finland took 11.13388204574585s
Amount of data | Check the number of entities for Museum Finland took 4.00543212890625e-05s
Verifiability | Contribs. check for Museum Finland took 0.15910983085632324s
Interlinking | sameAs chians check for Museum Finland took 0.17481231689453125s
Interlinking | skos check for Museum Finland took 0.16850614547729492s
Interlinking | skos check for Museum Finland took 0.16392111778259277s
Timeliness | dataset update frequency check for Museum Finland took 0.16707825660705566s
Currency | Creation date check for Museum Finland took 0.34940147399902344s
Currency | Modification date check for Museum Finland took 0.3746774196624756s
Rep.Conc. | URIs length for Museum Finland took 3.5494399070739746s
Interoperability | New vocabularies check for Museum Finland took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.19101190567016602s
Accuracy | Check Functional Property for Museum Finland took 0.15871238708496094s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.16010069847106934s
Accuracy | Check Empty annotation labels for Museum Finland took 1.0278778076171875s
Accuracy | Check White space in annotation for Museum Finland took 0.062332868576049805s
Accuracy | Check Datatype consistency for Museum Finland took 0.9818804264068604s
Consistency | Disjoint class check for Museum Finland took 0.16324782371520996s
Consistency | Check Misplaced properties for Museum Finland took 0.5952939987182617s
Consistency | Check Ontology hijacking for Museum Finland took 2.4013381004333496s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.719857931137085s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.9335510730743408s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6813151836395264s
Conciseness | Check Intensional conciseness for Museum Finland took 0.28101015090942383s
Security | Sign check for Museum Finland took 0.16074800491333008s
Availability | Check URIs Dereferenciability for Museum Finland took 2597.4517920017242s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.47226977348327637s
Reputation | Calculation of the PageRank for Museum Finland took 0.023386001586914062s
Interlinking | Calculation of Degree of Connection for Museum Finland took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 2.5272369384765625e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 2.6226043701171875e-06s
Believability | Calculation of trust value for Museum Finland took 1.71661376953125e-05s
INFO | --- Analysis for FI-Museum took 2655.419777393341s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.20293927192687988s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0007028579711914062s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 15.929922819137573s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.7988755702972412s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 30.97815728187561s
Interoperability | New terms check for Mapping Manuscript Migrations took 5.422960519790649s
Versatility | Languages check for Mapping Manuscript Migrations took 75.472900390625s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 29.208553075790405s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.39329028129577637s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.19218039512634277s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.1993708610534668s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.1589062213897705s
License | MR license check for Mapping Manuscript Migrations took 0.19905519485473633s
License | HR license check for Mapping Manuscript Migrations took 1.8277409076690674s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.1909010410308838s
Understandability | Number of label check for Mapping Manuscript Migrations took 8.765586614608765s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.3513050079345703s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.16814494132995605s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.19155335426330566s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.19080543518066406s
Performance | Throughput check for Mapping Manuscript Migrations took 11.045853614807129s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.1654436588287354s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.16048836708068848s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.5190200805664062s
Interlinking | skos check for Mapping Manuscript Migrations took 0.1608142852783203s
Interlinking | skos check for Mapping Manuscript Migrations took 0.16591453552246094s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.16048121452331543s
Currency | Creation date check for Mapping Manuscript Migrations took 0.36713361740112305s
Currency | Modification date check for Mapping Manuscript Migrations took 0.19887447357177734s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 48.51831769943237s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.16045856475830078s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.15205979347229004s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.16695499420166016s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 11.029691934585571s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.47139573097229s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.860077381134033s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.19333910942077637s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 23.060180187225342s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 16.836508750915527s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.7197625637054443s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.6946616172790527s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.936033248901367s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.19994044303894043s
Security | Sign check for Mapping Manuscript Migrations took 0.15984153747558594s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 21.71590542793274s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.3460993766784668s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.02149486541748047s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.3828277587890625e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 8.821487426757812e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 1.5497207641601562e-05s
INFO | --- Analysis for MMM took 526.4050235748291s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.2967205047607422s
Availability | VoID file availability check for Semantic Kalevala took 0.0005354881286621094s
Extra | Recovery of all triples for Semantic Kalevala took 8.392442226409912s
Performance | Total latancy measurement for Semantic Kalevala took 0.8446614742279053s
Amount of data | Number of triples check for Semantic Kalevala took 0.4190030097961426s
Interoperability | New terms check for Semantic Kalevala took 2.0673141479492188s
Versatility | Languages check for Semantic Kalevala took 0.9352216720581055s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.37860894203186035s
Security | Check HTTPS for Semantic Kalevala took 0.24257588386535645s
Interpretability | RDF structures check for Semantic Kalevala took 0.361461877822876s
Versatility | Serialization formats check for Semantic Kalevala took 0.20144009590148926s
Availability | RDF dump link check for Semantic Kalevala took 0.17232131958007812s
License | MR license check for Semantic Kalevala took 0.236191987991333s
License | HR license check for Semantic Kalevala took 0.9946568012237549s
Amount of data | Number of property check for Semantic Kalevala took 0.18999075889587402s
Understandability | Number of label check for Semantic Kalevala took 0.6487429141998291s
Understandability | URI regex check for Semantic Kalevala took 0.32793283462524414s
Understandability | Vocabs check for Semantic Kalevala took 0.16193938255310059s
Verifiability | Authors check for Semantic Kalevala took 0.16066503524780273s
Verifiability | Publishers check for Semantic Kalevala took 0.1685323715209961s
Performance | Throughput check for Semantic Kalevala took 11.07731580734253s
Amount of data | Check the number of entities for Semantic Kalevala took 7.724761962890625e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.1737067699432373s
Interlinking | sameAs chians check for Semantic Kalevala took 0.19085288047790527s
Interlinking | skos check for Semantic Kalevala took 0.27159738540649414s
Interlinking | skos check for Semantic Kalevala took 0.15723848342895508s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.15822458267211914s
Currency | Creation date check for Semantic Kalevala took 0.3360574245452881s
Currency | Modification date check for Semantic Kalevala took 0.35656213760375977s
Rep.Conc. | URIs length for Semantic Kalevala took 5.061459541320801s
Interoperability | New vocabularies check for Semantic Kalevala took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.20737862586975098s
Accuracy | Check Functional Property for Semantic Kalevala took 0.1829071044921875s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.15973186492919922s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.9338645935058594s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.2991678714752197s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.4193480014801025s
Consistency | Disjoint class check for Semantic Kalevala took 0.15974831581115723s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.7474832534790039s
Consistency | Check Ontology hijacking for Semantic Kalevala took 4.145524978637695s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.5676805973052979s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.7671425342559814s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.9127247333526611s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.27710390090942383s
Security | Sign check for Semantic Kalevala took 0.1667461395263672s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 2294.93186211586s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.34629082679748535s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.67671799659729s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.5020370483398438e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 1.6689300537109375e-06s
Believability | Calculation of trust value for Semantic Kalevala took 1.9073486328125e-05s
INFO | --- Analysis for Semantic-Kalevala took 2362.089420080185s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.9224591255187988s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0006327629089355469s
Extra | Recovery of all triples for Smithsonian American Art Museum took 278.5753757953644s
Performance | Total latancy measurement for Smithsonian American Art Museum took 2.944962978363037s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5641112327575684s
Interoperability | New terms check for Smithsonian American Art Museum took 3.645458698272705s
Versatility | Languages check for Smithsonian American Art Museum took 27.822055101394653s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.5882689952850342s
Security | Check HTTPS for Smithsonian American Art Museum took 0.36492156982421875s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.6320102214813232s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.6301290988922119s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.5727269649505615s
License | MR license check for Smithsonian American Art Museum took 0.5915627479553223s
License | HR license check for Smithsonian American Art Museum took 17.902256727218628s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5652191638946533s
Understandability | Number of label check for Smithsonian American Art Museum took 0.5888111591339111s
Understandability | URI regex check for Smithsonian American Art Museum took 1.1461114883422852s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.5970156192779541s
Verifiability | Authors check for Smithsonian American Art Museum took 0.5776007175445557s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.5857963562011719s
Performance | Throughput check for Smithsonian American Art Museum took 11.609875440597534s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 8.153915405273438e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.6003665924072266s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.5765745639801025s
Interlinking | skos check for Smithsonian American Art Museum took 0.5761034488677979s
Interlinking | skos check for Smithsonian American Art Museum took 0.5692391395568848s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.5904695987701416s
Currency | Creation date check for Smithsonian American Art Museum took 1.1741547584533691s
Currency | Modification date check for Smithsonian American Art Museum took 1.157299280166626s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 104.0440239906311s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.5640079975128174s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 19.32922863960266s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.5013141632080078s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.364947319030762s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5641939640045166s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 6.03404688835144s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 101.36409997940063s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.76883864402771s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 5.97720742225647s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.9519383907318115s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.6132490634918213s
Security | Sign check for Smithsonian American Art Museum took 0.5820009708404541s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.196747541427612s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.508570671081543s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.02131366729736328s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.3828277587890625e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 2.1457672119140625e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 1.4781951904296875e-05s
INFO | --- Analysis for Smithsonian took 705.5375771522522s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.21483254432678223s
Availability | VoID file availability check for Zeri Photo Archive took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.3363316059112549s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.020664453506469727s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.33514404296875e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 1.5974044799804688e-05s
INFO | --- Analysis for Zeri-Photo-Archive took 6.247897624969482s
Availability | SPARQL endpoint availability check for Archives Hub took 21.35175108909607s
Availability | VoID file availability check for Archives Hub took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.3095052242279053s
Reputation | Calculation of the PageRank for Archives Hub took 0.021131515502929688s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.3828277587890625e-05s
Believability | Calculation of trust value for Archives Hub took 1.5974044799804688e-05s
INFO | --- Analysis for Archives-Hub took 55.07201957702637s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.6773569583892822s
Availability | VoID file availability check for Yale centre of British Art took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.3061220645904541s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.021205902099609375s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.2874603271484375e-05s
Believability | Calculation of trust value for Yale centre of British Art took 1.5497207641601562e-05s
INFO | --- Analysis for Yale took 5.990198850631714s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 262.49021339416504s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.3310072422027588s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.022939682006835938s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.7642974853515625e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 1.4543533325195312e-05s
INFO | --- Analysis for ADL took 537.5799515247345s
Availability | SPARQL endpoint availability check for MusicKG took 0.7974255084991455s
Availability | VoID file availability check for MusicKG took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for MusicKG took 0.4062161445617676s
Reputation | Calculation of the PageRank for MusicKG took 0.02221393585205078s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.2636184692382812e-05s
Believability | Calculation of trust value for MusicKG took 1.5735626220703125e-05s
INFO | --- Analysis for MusicKG took 5.159574508666992s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.8348069190979004s
Availability | VoID file availability check for CIDOC-CRM took 0.0007488727569580078s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.5970766544342041s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.021053791046142578s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.8358230590820312e-05s
Believability | Calculation of trust value for CIDOC-CRM took 1.3828277587890625e-05s
INFO | --- Analysis for CIDOC-CRM took 4.997525691986084s
Availability | SPARQL endpoint availability check for Mondis took 9.485507011413574s
Availability | VoID file availability check for Mondis took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Mondis took 0.33182406425476074s
Reputation | Calculation of the PageRank for Mondis took 0.02092576026916504s
Interlinking | Calculation of Degree of Connection for Mondis took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.3828277587890625e-05s
Believability | Calculation of trust value for Mondis took 1.5735626220703125e-05s
INFO | --- Analysis for Mondis took 13.408863067626953s
Availability | SPARQL endpoint availability check for DigitalNZ took 3.626863956451416s
Availability | VoID file availability check for DigitalNZ took 0.0007305145263671875s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.33469581604003906s
Reputation | Calculation of the PageRank for DigitalNZ took 0.020928144454956055s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.430511474609375e-05s
Believability | Calculation of trust value for DigitalNZ took 1.4543533325195312e-05s
INFO | --- Analysis for DigitalNZ took 8.41628384590149s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.1586909294128418s
Availability | VoID file availability check for Fondazione Zeri took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.29712748527526855s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.021214008331298828s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.52587890625e-05s
Believability | Calculation of trust value for Fondazione Zeri took 1.621246337890625e-05s
INFO | --- Analysis for Fondazione-Zeri took 4.09449315071106s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.19831013679504395s
Availability | VoID file availability check for Digital Public Library of America took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.28539180755615234s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.0209808349609375s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.4066696166992188e-05s
Believability | Calculation of trust value for Digital Public Library of America took 1.6927719116210938e-05s
INFO | --- Analysis for Library-of-America took 4.608696222305298s
Availability | SPARQL endpoint availability check for Auckland Museum took 1.5620343685150146s
Availability | VoID file availability check for Auckland Museum took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.31157827377319336s
Reputation | Calculation of the PageRank for Auckland Museum took 0.021064043045043945s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.3113021850585938e-05s
Believability | Calculation of trust value for Auckland Museum took 1.5497207641601562e-05s
INFO | --- Analysis for Auckland-Museum took 7.343973159790039s
Availability | SPARQL endpoint availability check for National Library of Spain took 2.1222593784332275s
Availability | VoID file availability check for National Library of Spain took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.331770658493042s
Reputation | Calculation of the PageRank for National Library of Spain took 0.0209047794342041s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.430511474609375e-05s
Believability | Calculation of trust value for National Library of Spain took 8.106231689453125e-06s
INFO | --- Analysis for BNE took 5.7412614822387695s
Availability | SPARQL endpoint availability check for National Library of Korea took 1.6529574394226074s
Availability | VoID file availability check for National Library of Korea took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.3137192726135254s
Reputation | Calculation of the PageRank for National Library of Korea took 0.021602869033813477s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.430511474609375e-05s
Believability | Calculation of trust value for National Library of Korea took 1.4543533325195312e-05s
INFO | --- Analysis for Korea-Library took 5.10227370262146s
Availability | SPARQL endpoint availability check for The State Russian Museum took 1.606879472732544s
Availability | VoID file availability check for The State Russian Museum took 0.0003235340118408203s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.30770111083984375s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.02416229248046875s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 3.409385681152344e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0016863346099853516s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 2.384185791015625e-05s
Believability | Calculation of trust value for The State Russian Museum took 1.430511474609375e-05s
INFO | --- Analysis for Russian-Museum took 5.441389560699463s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.1742274761199951s
Availability | VoID file availability check for National Library of Scotland took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.33582139015197754s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.023195981979370117s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 2.6226043701171875e-05s
Believability | Calculation of trust value for National Library of Scotland took 1.5497207641601562e-05s
INFO | --- Analysis for National-Library-of-Scotland took 7.623817682266235s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 1.3693046569824219s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.5057272911071777s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.02108025550842285s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.52587890625e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 1.5497207641601562e-05s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 7.777672290802002s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.19022011756896973s
Availability | VoID file availability check for OntoComedySources took 0.0007007122039794922s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.32314062118530273s
Reputation | Calculation of the PageRank for OntoComedySources took 0.02296304702758789s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.52587890625e-05s
Believability | Calculation of trust value for OntoComedySources took 1.52587890625e-05s
INFO | --- Analysis for OntoComedySources took 4.583806753158569s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.20316457748413086s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0007684230804443359s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.29004549980163574s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.020940780639648438s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.52587890625e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 1.5020370483398438e-05s
INFO | --- Analysis for OntoCeramic-2.0 took 4.71892523765564s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.14312338829040527s
Availability | VoID file availability check for SaintGall Ontology took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.4177534580230713s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.022408485412597656s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.4781951904296875e-05s
Believability | Calculation of trust value for SaintGall Ontology took 1.5497207641601562e-05s
INFO | --- Analysis for SaintGall-Ontology took 4.0554680824279785s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.7065544128417969s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.3343062400817871s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.02101731300354004s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.5020370483398438e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 1.5020370483398438e-05s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 14.275349140167236s
Availability | SPARQL endpoint availability check for ICON took 0.276531457901001s
Availability | VoID file availability check for ICON took 0.0008857250213623047s
Completeness | Calculation of interlinking completeness for ICON took 0.31934261322021484s
Reputation | Calculation of the PageRank for ICON took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for ICON took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for ICON took 1.3589859008789062e-05s
Believability | Calculation of trust value for ICON took 1.6927719116210938e-05s
INFO | --- Analysis for ICON took 5.201610565185547s
Availability | SPARQL endpoint availability check for Polifonia took 0.25643372535705566s
Availability | VoID file availability check for Polifonia took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for Polifonia took 0.40330052375793457s
Reputation | Calculation of the PageRank for Polifonia took 0.02082967758178711s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.430511474609375e-05s
Believability | Calculation of trust value for Polifonia took 1.5020370483398438e-05s
INFO | --- Analysis for Polifonia took 4.817902565002441s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.2658655643463135s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0007364749908447266s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.34029245376586914s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.021131515502929688s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.3828277587890625e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 1.4781951904296875e-05s
INFO | --- Analysis for Atlas-of-Paths took 4.78333306312561s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.20079445838928223s
Availability | VoID file availability check for Music Note Ontology took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.33251476287841797s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.021116256713867188s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.4543533325195312e-05s
Believability | Calculation of trust value for Music Note Ontology took 1.430511474609375e-05s
INFO | --- Analysis for Music-Note-Ontology took 8.373070240020752s
Availability | SPARQL endpoint availability check for HaMSE took 0.21505475044250488s
Availability | VoID file availability check for HaMSE took 0.0007393360137939453s
Completeness | Calculation of interlinking completeness for HaMSE took 0.33312439918518066s
Reputation | Calculation of the PageRank for HaMSE took 0.021761417388916016s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.33514404296875e-05s
Believability | Calculation of trust value for HaMSE took 1.621246337890625e-05s
INFO | --- Analysis for HaMSE took 5.180278301239014s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.13201093673706055s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.30812931060791016s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.020918607711791992s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0008087158203125s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.3589859008789062e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 1.811981201171875e-05s
INFO | --- Analysis for FOod took 5.241003036499023s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.731116771697998s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0007736682891845703s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.3775637149810791s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.021325111389160156s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.52587890625e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 1.1205673217773438e-05s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 5.2983903884887695s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.449153184890747s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.31864094734191895s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.0226438045501709s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.3828277587890625e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 1.4781951904296875e-05s
INFO | --- Analysis for ARIADNE took 6.248621702194214s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.315976619720459s
Availability | VoID file availability check for Odeuropa Ontology took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.29995226860046387s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.021028757095336914s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.4543533325195312e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 1.71661376953125e-05s
INFO | --- Analysis for Odeuropa took 4.092067003250122s

--- Total time for analysis:494272.9615125656s ---
--- Total time for analysis:137.29804486460156 hours ---