Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 5.14984130859375e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0010361671447753906s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.25300002098083496s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.4897420406341553s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.00067138671875s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.7642974853515625e-05s
INFO | --- Analysis for 0080-3626 took 6.013545989990234s
Availability | SPARQL endpoint availability check for 土地利用图 took 5.0067901611328125e-05s
Availability | VoID file availability check for 土地利用图 took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.2724881172180176s
Reputation | Calculation of the PageRank for 土地利用图 took 0.021266937255859375s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 4.553794860839844e-05s
Believability | Calculation of trust value for 土地利用图 took 1.5735626220703125e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 2.8573849201202393s
Availability | SPARQL endpoint availability check for 113322 took 4.9114227294921875e-05s
Availability | VoID file availability check for 113322 took 0.0007469654083251953s
Completeness | Calculation of interlinking completeness for 113322 took 0.2670717239379883s
Reputation | Calculation of the PageRank for 113322 took 0.02136397361755371s
Interlinking | Calculation of Degree of Connection for 113322 took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for 113322 took 4.553794860839844e-05s
Believability | Calculation of trust value for 113322 took 1.621246337890625e-05s
INFO | --- Analysis for 11 took 4.104846715927124s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 8.296966552734375e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.25069284439086914s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.02223372459411621s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 4.4345855712890625e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.1444091796875e-05s
INFO | --- Analysis for 12323 took 2.3128063678741455s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.06540966033935547s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.2662966251373291s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020999431610107422s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 0.00010824203491210938s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.5974044799804688e-05s
INFO | --- Analysis for 2000-us-census-rdf took 2.4096341133117676s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 2.2780916690826416s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.2623574733734131s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.02126145362854004s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 5.412101745605469e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 1.0967254638671875e-05s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 6.607430696487427s
Availability | SPARQL endpoint availability check for Open Data Web took 18.085482597351074s
Availability | VoID file availability check for Open Data Web took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.25317978858947754s
Reputation | Calculation of the PageRank for Open Data Web took 0.021634578704833984s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.2901763916015625e-05s
Believability | Calculation of trust value for Open Data Web took 1.0728836059570312e-05s
INFO | --- Analysis for _data.odw.tw took 22.033127546310425s
Availability | SPARQL endpoint availability check for 土地利用 took 7.033348083496094e-05s
Availability | VoID file availability check for 土地利用 took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.24807453155517578s
Reputation | Calculation of the PageRank for 土地利用 took 0.022081375122070312s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.147125244140625e-05s
Believability | Calculation of trust value for 土地利用 took 1.0013580322265625e-05s
INFO | --- Analysis for _data1.odw.tw took 2.3676645755767822s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.8160552978515625e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.25952911376953125s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 3.0279159545898438e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.0251998901367188e-05s
INFO | --- Analysis for _data2.odw.tw took 5.3400843143463135s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.511543273925781e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.233750581741333s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.022702455520629883s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.147125244140625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.0728836059570312e-05s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 4.871960639953613s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.5299530029296875e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.00038743019104003906s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.26194262504577637s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.1948089599609375e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.049041748046875e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 3.034424304962158s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 9.34600830078125e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.2691471576690674s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.361701965332031e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 8.821487426757812e-06s
INFO | --- Analysis for A1 took 2.8383989334106445s
Availability | SPARQL endpoint availability check for SummerOlympics took 2.062295436859131s
Availability | VoID file availability check for SummerOlympics took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.2516908645629883s
Reputation | Calculation of the PageRank for SummerOlympics took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.365776062011719e-05s
Believability | Calculation of trust value for SummerOlympics took 1.2159347534179688e-05s
INFO | --- Analysis for abc took 7.756613254547119s
Availability | SPARQL endpoint availability check for Test_m took 4.315376281738281e-05s
Availability | VoID file availability check for Test_m took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Test_m took 0.26662492752075195s
Reputation | Calculation of the PageRank for Test_m took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for Test_m took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.170967102050781e-05s
Believability | Calculation of trust value for Test_m took 1.049041748046875e-05s
INFO | --- Analysis for ABC took 2.483680248260498s
Availability | SPARQL endpoint availability check for my intro took 4.267692565917969e-05s
Availability | VoID file availability check for my intro took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for my intro took 0.24786710739135742s
Reputation | Calculation of the PageRank for my intro took 0.021107196807861328s
Interlinking | Calculation of Degree of Connection for my intro took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for my intro took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for my intro took 2.9325485229492188e-05s
Believability | Calculation of trust value for my intro took 9.298324584960938e-06s
INFO | --- Analysis for abhay_intro took 2.374875783920288s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.1199033260345459s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.27566957473754883s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 9.846687316894531e-05s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for abs-linked-data took 2.5575342178344727s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 0.00011372566223144531s
Availability | VoID file availability check for Academic Offer of UNL took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.27986764907836914s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.02096271514892578s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 4.100799560546875e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 1.239776611328125e-05s
INFO | --- Analysis for academic-offer-of-unl took 2.8930130004882812s
Availability | SPARQL endpoint availability check for AcadOnto took 0.00011849403381347656s
Availability | VoID file availability check for AcadOnto took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.24779057502746582s
Reputation | Calculation of the PageRank for AcadOnto took 0.020905256271362305s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0009679794311523438s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.910064697265625e-05s
Believability | Calculation of trust value for AcadOnto took 1.1682510375976562e-05s
INFO | --- Analysis for acadonto took 2.874472141265869s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.382077932357788s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007066726684570312s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.2603585720062256s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.020235538482666016s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.838539123535156e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.298324584960938e-06s
INFO | --- Analysis for acorn-sat took 36.971744537353516s
Availability | SPARQL endpoint availability check for Addgene took 8.630752563476562e-05s
Availability | VoID file availability check for Addgene took 0.0009171962738037109s
Completeness | Calculation of interlinking completeness for Addgene took 0.25739598274230957s
Reputation | Calculation of the PageRank for Addgene took 0.021013498306274414s
Interlinking | Calculation of Degree of Connection for Addgene took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0008449554443359375s
Interlinking | Calculation of Clustering coefficient for Addgene took 4.124641418457031e-05s
Believability | Calculation of trust value for Addgene took 1.2874603271484375e-05s
INFO | --- Analysis for addgene took 16.063451051712036s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.291534423828125e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.2562398910522461s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.02036738395690918s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.441375732421875e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.1444091796875e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 9.77156138420105s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.7987196445465088s
Availability | VoID file availability check for AEMET metereological dataset took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.2538323402404785s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.02229475975036621s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.457069396972656e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 1.3589859008789062e-05s
INFO | --- Analysis for aemet took 5.736500978469849s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.38690185546875e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.2624695301055908s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02028203010559082s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 2.8371810913085938e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 1.0728836059570312e-05s
INFO | --- Analysis for agenda-de-zaragoza took 2.8701589107513428s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.03874683380126953s
Availability | VoID file availability check for AgriNepalData took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.27145838737487793s
Reputation | Calculation of the PageRank for AgriNepalData took 0.02024984359741211s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 6.866455078125e-05s
Believability | Calculation of trust value for AgriNepalData took 9.298324584960938e-06s
INFO | --- Analysis for agrinepaldata took 2.49467396736145s
Availability | SPARQL endpoint availability check for AGRIS took 261.86747765541077s
Availability | VoID file availability check for AGRIS took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for AGRIS took 0.24388766288757324s
Reputation | Calculation of the PageRank for AGRIS took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.557868957519531e-05s
Believability | Calculation of trust value for AGRIS took 1.1682510375976562e-05s
INFO | --- Analysis for agris took 554.9991898536682s
Availability | SPARQL endpoint availability check for AGROVOC took 0.18092036247253418s
Availability | VoID file availability check for AGROVOC took 0.00030231475830078125s
Extra | Recovery of all triples for AGROVOC took 59.485913038253784s
Performance | Total latancy measurement for AGROVOC took 0.46953248977661133s
Amount of data | Number of triples check for AGROVOC took 163.98554491996765s
Interoperability | New terms check for AGROVOC took 3.9475817680358887s
Versatility | Languages check for AGROVOC took 247.52389669418335s
Interpretability | Number of blank nodes check for AGROVOC took 112.80890464782715s
Interpretability | RDF structures check for AGROVOC took 0.09981751441955566s
Versatility | Serialization formats check for AGROVOC took 0.09958934783935547s
Availability | RDF dump link check for AGROVOC took 0.0858304500579834s
License | MR license check for AGROVOC took 0.08818197250366211s
License | HR license check for AGROVOC took 0.655646800994873s
Amount of data | Number of property check for AGROVOC took 0.07579874992370605s
Understandability | Number of label check for AGROVOC took 84.58146643638611s
Understandability | URI regex check for AGROVOC took 0.17647480964660645s
Understandability | Vocabs check for AGROVOC took 0.08647823333740234s
Verifiability | Authors check for AGROVOC took 0.13289809226989746s
Verifiability | Publishers check for AGROVOC took 0.10306024551391602s
Performance | Throughput check for AGROVOC took 10.540114164352417s
Amount of data | Check the number of entities for AGROVOC took 6.937980651855469e-05s
Verifiability | Contribs. check for AGROVOC took 0.09633779525756836s
Interlinking | sameAs chians check for AGROVOC took 0.09803462028503418s
Interlinking | skos check for AGROVOC took 1.5475850105285645s
Interlinking | skos check for AGROVOC took 0.9181382656097412s
Timeliness | dataset update frequency check for AGROVOC took 0.08754992485046387s
Currency | Creation date check for AGROVOC took 0.19045758247375488s
Currency | Modification date check for AGROVOC took 0.17313861846923828s
Rep.Conc. | URIs length for AGROVOC took 125.75833201408386s
Interoperability | New vocabularies check for AGROVOC took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.08465147018432617s
Accuracy | Check Functional Property for AGROVOC took 0.0884697437286377s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.07499241828918457s
Accuracy | Check Empty annotation labels for AGROVOC took 23.321943044662476s
Accuracy | Check White space in annotation for AGROVOC took 2.94807505607605s
Accuracy | Check Datatype consistency for AGROVOC took 4.470619201660156s
Consistency | Disjoint class check for AGROVOC took 0.09455680847167969s
Consistency | Check Misplaced properties for AGROVOC took 25.669668197631836s
Consistency | Check Ontology hijacking for AGROVOC took 112.24703884124756s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.4913063049316406s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 25.589205980300903s
Conciseness | Check Extensional conciseness for AGROVOC took 2.5470080375671387s
Conciseness | Check Intensional conciseness for AGROVOC took 0.09973454475402832s
Security | Sign check for AGROVOC took 0.0899968147277832s
Availability | Check URIs Dereferenciability for AGROVOC took 2267.2359824180603s
Completeness | Calculation of interlinking completeness for AGROVOC took 1.4854872226715088s
Reputation | Calculation of the PageRank for AGROVOC took 0.021779298782348633s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00012731552124023438s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.6689300537109375e-06s
Believability | Calculation of trust value for AGROVOC took 7.152557373046875e-06s
INFO | --- Analysis for agrovoc took 3411.9474306106567s
Availability | SPARQL endpoint availability check for AGROVOC took 6.723403930664062e-05s
Availability | VoID file availability check for AGROVOC took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.29258060455322266s
Reputation | Calculation of the PageRank for AGROVOC took 0.021352291107177734s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.745887756347656e-05s
Believability | Calculation of trust value for AGROVOC took 6.9141387939453125e-06s
INFO | --- Analysis for agrovoc-skos took 3.2534587383270264s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.7459430694580078s
Availability | VoID file availability check for Analytics India Magazine took 0.0004642009735107422s
Extra | Recovery of all triples for Analytics India Magazine took 3.4064252376556396s
Performance | Total latancy measurement for Analytics India Magazine took 2.9132583141326904s
Amount of data | Number of triples check for Analytics India Magazine took 1.752979040145874s
Versatility | Languages check for Analytics India Magazine took 1.7117283344268799s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.346900463104248s
Interpretability | RDF structures check for Analytics India Magazine took 1.6357331275939941s
Versatility | Serialization formats check for Analytics India Magazine took 1.706709384918213s
Availability | RDF dump link check for Analytics India Magazine took 1.628014087677002s
License | MR license check for Analytics India Magazine took 1.653731346130371s
License | HR license check for Analytics India Magazine took 1.4253895282745361s
Amount of data | Number of property check for Analytics India Magazine took 1.4480478763580322s
Understandability | Number of label check for Analytics India Magazine took 1.5266292095184326s
Understandability | URI regex check for Analytics India Magazine took 3.017322063446045s
Understandability | Vocabs check for Analytics India Magazine took 1.9354438781738281s
Verifiability | Authors check for Analytics India Magazine took 1.6499836444854736s
Verifiability | Publishers check for Analytics India Magazine took 1.574157476425171s
Performance | Throughput check for Analytics India Magazine took 17.376823902130127s
Amount of data | Check the number of entities for Analytics India Magazine took 0.00010514259338378906s
Verifiability | Contribs. check for Analytics India Magazine took 1.2725417613983154s
Interlinking | sameAs chians check for Analytics India Magazine took 1.5550572872161865s
Interlinking | skos check for Analytics India Magazine took 1.315528154373169s
Interlinking | skos check for Analytics India Magazine took 0.11066150665283203s
Timeliness | dataset update frequency check for Analytics India Magazine took 1.568446159362793s
Currency | Creation date check for Analytics India Magazine took 3.499643325805664s
Currency | Modification date check for Analytics India Magazine took 3.1333348751068115s
Rep.Conc. | URIs length for Analytics India Magazine took 3.625490427017212s
Interoperability | New vocabularies check for Analytics India Magazine took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 1.4909038543701172s
Consistency | Disjoint class check for Analytics India Magazine took 1.198819637298584s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.514552116394043s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 2.8102469444274902s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.00014543533325195312s
Security | Sign check for Analytics India Magazine took 1.2589659690856934s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.6936688423156738s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 2.8848648071289062e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 1.430511474609375e-06s
Believability | Calculation of trust value for Analytics India Magazine took 1.1205673217773438e-05s
INFO | --- Analysis for AIM took 116.59349250793457s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 4.3392181396484375e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.25252747535705566s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020198345184326172s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 2.8848648071289062e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.2159347534179688e-05s
INFO | --- Analysis for AISHE took 2.3100874423980713s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.1961669921875e-05s
Availability | VoID file availability check for  equipment ontology took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.23138093948364258s
Reputation | Calculation of the PageRank for  equipment ontology took 0.020337820053100586s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 2.8371810913085938e-05s
Believability | Calculation of trust value for  equipment ontology took 7.152557373046875e-06s
INFO | --- Analysis for akash took 2.6354401111602783s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.172325134277344e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.25995421409606934s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.022882938385009766s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 2.7894973754882812e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 1.1920928955078125e-05s
INFO | --- Analysis for aksworg took 2.8191006183624268s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.0531158447265625e-05s
Availability | VoID file availability check for AlchemyAPI took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.25505661964416504s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 3.170967102050781e-05s
Believability | Calculation of trust value for AlchemyAPI took 1.2636184692382812e-05s
INFO | --- Analysis for alchemyapi took 2.8109874725341797s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 4.100799560546875e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.2369835376739502s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.021584033966064453s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.001046895980834961s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 3.528594970703125e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 1.0967254638671875e-05s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.8401687145233154s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.3758718967437744s
Availability | VoID file availability check for aliada-scanbit-net took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.26225924491882324s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020337820053100586s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00010943412780761719s
Believability | Calculation of trust value for aliada-scanbit-net took 1.0967254638671875e-05s
INFO | --- Analysis for aliada-scanbit-net took 4.813933610916138s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 5.316734313964844e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.27230095863342285s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.020459413528442383s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 3.0040740966796875e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 1.2636184692382812e-05s
INFO | --- Analysis for allen-brain-atlas took 2.8096115589141846s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 1.439986228942871s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006396770477294922s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 107.02026987075806s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.6735713481903076s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.5575435161590576s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.44115948677063s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.1035649776459s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.427032232284546s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8997993469238281s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.564835786819458s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.6993491649627686s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5379154682159424s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.5657968521118164s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 33.84521293640137s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5505220890045166s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 1.563323736190796s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.500967264175415s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.5470659732818604s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6466326713562012s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5308947563171387s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.673208713531494s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 0.0001251697540283203s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5443150997161865s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.545811653137207s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.56475830078125s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.552772045135498s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.542694091796875s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.0803804397583008s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.0656371116638184s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 42.19283652305603s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 1.4460749626159668s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5358929634094238s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.624180793762207s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6101288795471191s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 23.66321635246277s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.023444652557373s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.617957830429077s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.5772755146026611s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.633014440536499s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.826875686645508s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 22.72567915916443s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.318711519241333s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.397284507751465s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.6955490112304688s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8697211742401123s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5494999885559082s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 12856.871851444244s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 1.197892427444458s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.023833036422729492s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 5.650520324707031e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0008206367492675781s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 0.0001442432403564453s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 1.730342149734497s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.3113021850585938e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 13543.364835739136s
Availability | SPARQL endpoint availability check for Alojamientos took 8.654594421386719e-05s
Availability | VoID file availability check for Alojamientos took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.26224684715270996s
Reputation | Calculation of the PageRank for Alojamientos took 0.020970821380615234s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.361701965332031e-05s
Believability | Calculation of trust value for Alojamientos took 1.3113021850585938e-05s
INFO | --- Analysis for alojamientos-zaragoza took 3.241582155227661s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.31077027320861816s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.24296998977661133s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.020392179489135742s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 4.124641418457031e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.1444091796875e-05s
INFO | --- Analysis for alpino-rdf took 3.8509085178375244s
Availability | SPARQL endpoint availability check for AAT-atawil took 9.894371032714844e-05s
Availability | VoID file availability check for AAT-atawil took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.2863774299621582s
Reputation | Calculation of the PageRank for AAT-atawil took 0.023757457733154297s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.409385681152344e-05s
Believability | Calculation of trust value for AAT-atawil took 1.1920928955078125e-05s
INFO | --- Analysis for Altawil took 2.3613955974578857s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 8.606910705566406e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.2527434825897217s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.023393630981445312s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0008356571197509766s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 3.4332275390625e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 1.2159347534179688e-05s
INFO | --- Analysis for am-collections-online took 2.8485279083251953s
Availability | SPARQL endpoint availability check for Amer Nejma took 8.893013000488281e-05s
Availability | VoID file availability check for Amer Nejma took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.2788841724395752s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.0994415283203125e-05s
Believability | Calculation of trust value for Amer Nejma took 1.2636184692382812e-05s
INFO | --- Analysis for Amer_Nejma took 2.303919553756714s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0009276866912841797s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.24271726608276367s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020896196365356445s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 2.7894973754882812e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.239776611328125e-05s
INFO | --- Analysis for amon took 2.774442434310913s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7880151271820068s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.274247407913208s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00010037422180175781s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.239776611328125e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 13.891793251037598s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 4.2438507080078125e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.2521936893463135s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.022216796875s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.24249267578125e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 1.2159347534179688e-05s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.8843867778778076s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.267692565917969e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.2635684013366699s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.02237391471862793s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 3.552436828613281e-05s
Believability | Calculation of trust value for Animal Diversity Web took 1.1682510375976562e-05s
INFO | --- Analysis for animal-diversity-web took 2.8213279247283936s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.458427429199219e-05s
Availability | VoID file availability check for Anime Dataset took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.25998759269714355s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020882606506347656s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 3.3855438232421875e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0023336410522460938s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 6.985664367675781e-05s
Believability | Calculation of trust value for Anime Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for Anime took 4.412083387374878s
Availability | SPARQL endpoint availability check for ANNO took 4.291534423828125e-05s
Availability | VoID file availability check for ANNO took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for ANNO took 0.2766437530517578s
Reputation | Calculation of the PageRank for ANNO took 0.02076125144958496s
Interlinking | Calculation of Degree of Connection for ANNO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.528594970703125e-05s
Believability | Calculation of trust value for ANNO took 1.049041748046875e-05s
INFO | --- Analysis for anno took 7.843032360076904s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 8.940696716308594e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.2578310966491699s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020696163177490234s
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.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.724761962890625e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 9.5367431640625e-06s
INFO | --- Analysis for AntiqueCarsCollection took 3.8261373043060303s
Availability | SPARQL endpoint availability check for apache took 4.267692565917969e-05s
Availability | VoID file availability check for apache took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for apache took 0.28795599937438965s
Reputation | Calculation of the PageRank for apache took 0.020321369171142578s
Interlinking | Calculation of Degree of Connection for apache took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for apache took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for apache took 5.555152893066406e-05s
Believability | Calculation of trust value for apache took 1.0251998901367188e-05s
INFO | --- Analysis for apache took 3.3328070640563965s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF took 0.01833796501159668s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.2546238899230957s
Reputation | Calculation of the PageRank for Apertium RDF took 0.023052453994750977s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf took 7.419341564178467s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 9.012222290039062e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.2621588706970215s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.02128767967224121s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.792213439941406e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 5.685837745666504s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.25177645683288574s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020410537719726562s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 5.56608510017395s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.25801539421081543s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 9.775161743164062e-06s
INFO | --- Analysis for apertium-rdf-en-es took 5.473969459533691s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.25238728523254395s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 9.965896606445312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 9.298324584960938e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 5.538479566574097s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 9.369850158691406e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0007007122039794922s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.25029683113098145s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020871877670288086s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007915496826171875s
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.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.454049348831177s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 5.364418029785156e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.2542243003845215s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02254343032836914s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.7206878662109375e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 6.0558319091796875e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 5.527084827423096s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 5.841255187988281e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.29334187507629395s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020775556564331055s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.172325134277344e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 5.570897102355957s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 9.036064147949219e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0003750324249267578s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.2606935501098633s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.02022695541381836s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.461186408996582s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 7.605552673339844e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.273754358291626s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020387649536132812s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 6.198883056640625e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-es-an took 5.559189796447754s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 9.036064147949219e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.2415156364440918s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020175933837890625s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.100799560546875e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 5.574732065200806s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 8.726119995117188e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.24559378623962402s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.7206878662109375e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 24.786554098129272s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 8.749961853027344e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.24675345420837402s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.022485017776489258s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 5.14984130859375e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 5.545147180557251s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 8.845329284667969e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.25113368034362793s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020490169525146484s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.744529724121094e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 9.059906005859375e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.479820251464844s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 9.083747863769531e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.2642347812652588s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.020906925201416016s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 5.540729999542236s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 9.179115295410156e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.2517988681793213s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.673004150390625e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 9.775161743164062e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 5.500720024108887s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 9.298324584960938e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.26317405700683594s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.02144145965576172s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 9.775161743164062e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 5.791622161865234s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.24339866638183594s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020828723907470703s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.4958953857421875s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 8.845329284667969e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.2648797035217285s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.021751880645751953s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 9.298324584960938e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 6.019832611083984s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.982948303222656e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.2471475601196289s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.0013580322265625e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.416172742843628s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 8.749961853027344e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2630326747894287s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020359039306640625s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 5.470560550689697s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.27506017684936523s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020699739456176758s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.8160552978515625e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 6.063076972961426s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 8.797645568847656e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.2731499671936035s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.021854162216186523s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 5.173683166503906e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.774087190628052s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.8011863231658936s
Availability | VoID file availability check for AragoDBPedia took 0.0005817413330078125s
Extra | Recovery of all triples for AragoDBPedia took 3.3571577072143555s
Performance | Total latancy measurement for AragoDBPedia took 1.9008970260620117s
Amount of data | Number of triples check for AragoDBPedia took 0.7468156814575195s
Interoperability | New terms check for AragoDBPedia took 2.038209915161133s
Versatility | Languages check for AragoDBPedia took 60.47279667854309s
Interpretability | Number of blank nodes check for AragoDBPedia took 4.4546003341674805s
Security | Check HTTPS for AragoDBPedia took 0.2774641513824463s
Interpretability | RDF structures check for AragoDBPedia took 0.5384869575500488s
Versatility | Serialization formats check for AragoDBPedia took 0.9336380958557129s
Availability | RDF dump link check for AragoDBPedia took 0.3516991138458252s
License | MR license check for AragoDBPedia took 0.5057251453399658s
License | HR license check for AragoDBPedia took 6.273060083389282s
Amount of data | Number of property check for AragoDBPedia took 0.4055328369140625s
Understandability | Number of label check for AragoDBPedia took 0.4877767562866211s
Understandability | URI regex check for AragoDBPedia took 0.8358995914459229s
Understandability | Vocabs check for AragoDBPedia took 0.4052917957305908s
Verifiability | Authors check for AragoDBPedia took 0.42651963233947754s
Verifiability | Publishers check for AragoDBPedia took 0.3910384178161621s
Performance | Throughput check for AragoDBPedia took 11.518482208251953s
Amount of data | Check the number of entities for AragoDBPedia took 8.392333984375e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.4538421630859375s
Interlinking | sameAs chians check for AragoDBPedia took 0.374692440032959s
Interlinking | skos check for AragoDBPedia took 0.5092747211456299s
Interlinking | skos check for AragoDBPedia took 0.3659369945526123s
Timeliness | dataset update frequency check for AragoDBPedia took 0.45165562629699707s
Currency | Creation date check for AragoDBPedia took 1.2523226737976074s
Currency | Modification date check for AragoDBPedia took 0.420900821685791s
Rep.Conc. | URIs length for AragoDBPedia took 6.176937103271484s
Interoperability | New vocabularies check for AragoDBPedia took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.3547630310058594s
Accuracy | Check Functional Property for AragoDBPedia took 0.46720170974731445s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.44156861305236816s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.2479307651519775s
Accuracy | Check White space in annotation for AragoDBPedia took 0.030677080154418945s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.027338266372680664s
Consistency | Disjoint class check for AragoDBPedia took 0.4069206714630127s
Consistency | Check Misplaced properties for AragoDBPedia took 4.50439977645874s
Consistency | Misplaced classes for AragoDBPedia took 0.5849292278289795s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.4979982376098633s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.236487865447998s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.235337257385254s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.031879425048828125s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.4975438117980957s
Security | Sign check for AragoDBPedia took 0.5308918952941895s
Availability | Check URIs Dereferenciability for AragoDBPedia took 2966.9022011756897s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 1.472080945968628s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.02135920524597168s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 6.0558319091796875e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for AragoDBPedia took 8.821487426757812e-06s
INFO | --- Analysis for aragodbpedia took 3247.7589721679688s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.433676719665527s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0007357597351074219s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.25907182693481445s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020540714263916016s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 4.982948303222656e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.8596649169921875e-05s
INFO | --- Analysis for archiveshub-linkeddata took 83.38821482658386s
Availability | SPARQL endpoint availability check for Archivi ISMA took 9.036064147949219e-05s
Availability | VoID file availability check for Archivi ISMA took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.2595832347869873s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 3.170967102050781e-05s
Believability | Calculation of trust value for Archivi ISMA took 1.049041748046875e-05s
INFO | --- Analysis for archivio-isma took 3.2938477993011475s
Availability | SPARQL endpoint availability check for ARIADNE took 4.5299530029296875e-05s
Availability | VoID file availability check for ARIADNE took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.26658082008361816s
Reputation | Calculation of the PageRank for ARIADNE took 0.02078700065612793s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 3.266334533691406e-05s
Believability | Calculation of trust value for ARIADNE took 1.0013580322265625e-05s
INFO | --- Analysis for ariadne took 2.8594188690185547s
Availability | SPARQL endpoint availability check for Aristotle University took 6.699562072753906e-05s
Availability | VoID file availability check for Aristotle University took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.27567529678344727s
Reputation | Calculation of the PageRank for Aristotle University took 0.020781755447387695s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 3.147125244140625e-05s
Believability | Calculation of trust value for Aristotle University took 9.5367431640625e-06s
INFO | --- Analysis for aristotle-university took 2.872699022293091s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 5.123246908187866s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.25671982765197754s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.02232813835144043s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.218650817871094e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 9.059906005859375e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 20.762322664260864s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.172325134277344e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.2707827091217041s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.0013580322265625e-05s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 2.7873620986938477s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.9222443103790283s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.2726759910583496s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.021930456161499023s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0008537769317626953s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.935264587402344e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.1682510375976562e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 16.61911392211914s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.553794860839844e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.2590763568878174s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010776519775390625s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.1205673217773438e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 81.10703635215759s
Availability | SPARQL endpoint availability check for Arthroscopy community took 9.202957153320312e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.27960872650146484s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010395050048828125s
Believability | Calculation of trust value for Arthroscopy community took 1.239776611328125e-05s
INFO | --- Analysis for arthroscopy took 14.548190355300903s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.8053419589996338s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0005943775177001953s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 22.66096591949463s
Performance | Total latancy measurement for Wikidata entry for Art × Science International took 1.2921409606933594s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 65.18860936164856s
Interoperability | New terms check for Wikidata entry for Art × Science International took 1.9558584690093994s
Versatility | Languages check for Wikidata entry for Art × Science International took 60.38141632080078s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 65.20581340789795s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.2802910804748535s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.2285144329071045s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.3320791721343994s
License | MR license check for Wikidata entry for Art × Science International took 0.21173548698425293s
License | HR license check for Wikidata entry for Art × Science International took 65.19423794746399s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.45316481590270996s
Understandability | Number of label check for Wikidata entry for Art × Science International took 65.20716762542725s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.43505048751831055s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.21635866165161133s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.217512845993042s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.23330044746398926s
Performance | Throughput check for Wikidata entry for Art × Science International took 11.441712856292725s
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.3301997184753418s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 14.884437561035156s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.21709394454956055s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.21775221824645996s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.22795867919921875s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.4372398853302002s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.45962023735046387s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 44.62445044517517s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.20204639434814453s
Accuracy | Check Empty annotation labels for Wikidata entry for Art × Science International took 12.474042892456055s
Accuracy | Check White space in annotation for Wikidata entry for Art × Science International took 2.6631219387054443s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.628479719161987s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.21333050727844238s
Consistency | Check Misplaced properties for Wikidata entry for Art × Science International took 9.842854499816895s
Consistency | Misplaced classes for Wikidata entry for Art × Science International took 8.814555168151855s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 33.96187615394592s
Consistency | Check Invalid usage of undefined classes for Wikidata entry for Art × Science International took 1.3852007389068604s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 2.3512444496154785s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.784294843673706s
Conciseness | Check Intensional conciseness for Wikidata entry for Art × Science International took 1.6998510360717773s
Security | Sign check for Wikidata entry for Art × Science International took 0.20141196250915527s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 14.60554814338684s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.7777788639068604s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.02128314971923828s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.4066696166992188e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 1.9073486328125e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 1.2874603271484375e-05s
INFO | --- Analysis for artxscienceinternational-wikidata took 942.0579543113708s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 4.273061513900757s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.2555985450744629s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.021373271942138672s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.869171142578125e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.239776611328125e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 13.988163471221924s
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.4065499305725098s
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.0006196498870849609s
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.2801675796508789s
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.020609617233276367s
Interlinking | Calculation of Degree of Connection for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.0007462501525878906s
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.654594421386719e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 11.174444198608398s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.3859305381774902s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.2597672939300537s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.00013875961303710938s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 12.14765477180481s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.3996872901916504s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.23787450790405273s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.076957702636719e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.2636184692382812e-05s
INFO | --- Analysis for ASCDC-CRB took 14.373667478561401s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.4218857288360596s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.2516632080078125s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.02035808563232422s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.1552734375e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 11.600471019744873s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.397211790084839s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.2526412010192871s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.021273136138916016s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-DQOT took 12.643817901611328s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.4396603107452393s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.25861048698425293s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.02226734161376953s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.867813110351562e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.777063846588135s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.444450855255127s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.27486610412597656s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020526409149169922s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.034706115722656e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.2874603271484375e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 15.453924655914307s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.3852922916412354s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.2504889965057373s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.021599769592285156s
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.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.221366882324219e-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.4781951904296875e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 11.562743902206421s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.3856117725372314s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.25298237800598145s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.022300243377685547s
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.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.364418029785156e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 11.56876277923584s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.9988667964935303s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.2616612911224365s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020645618438720703s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 5.435943603515625e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 16.02758526802063s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.3926098346710205s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.00036406517028808594s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.24726319313049316s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020703792572021484s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.557868957519531e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 11.068856954574585s
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.3799877166748047s
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.00035381317138671875s
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.24551749229431152s
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.020528554916381836s
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 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.724761962890625e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.604583024978638s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.378847360610962s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.000370025634765625s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.24460363388061523s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.38690185546875e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC_-_DNB took 10.983628749847412s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.315376281738281e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.000301361083984375s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.24598431587219238s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020885944366455078s
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.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.771087646484375e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.5735626220703125e-05s
INFO | --- Analysis for asit took 8.67089557647705s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.601478576660156e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.25751829147338867s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.020540714263916016s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.719329833984375e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.1682510375976562e-05s
INFO | --- Analysis for asjp took 5.870683193206787s
Availability | SPARQL endpoint availability check for ASN:US took 3.3770041465759277s
Availability | VoID file availability check for ASN:US took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for ASN:US took 0.24897527694702148s
Reputation | Calculation of the PageRank for ASN:US took 0.021085500717163086s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for ASN:US took 7.462501525878906e-05s
Believability | Calculation of trust value for ASN:US took 5.0067901611328125e-06s
INFO | --- Analysis for asn-us took 13.83879542350769s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.553794860839844e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.2600085735321045s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0009593963623046875s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.4809112548828125e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 4.76837158203125e-06s
INFO | --- Analysis for aspire-mmu took 4.467083692550659s
Availability | SPARQL endpoint availability check for associations took 5.0067901611328125e-05s
Availability | VoID file availability check for associations took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for associations took 0.2524886131286621s
Reputation | Calculation of the PageRank for associations took 0.020705699920654297s
Interlinking | Calculation of Degree of Connection for associations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for associations took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for associations took 7.462501525878906e-05s
Believability | Calculation of trust value for associations took 1.0967254638671875e-05s
INFO | --- Analysis for associations took 8.629327535629272s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.458427429199219e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.2660245895385742s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.022199392318725586s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 3.0994415283203125e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 7.152557373046875e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 2.8354392051696777s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 0.00011181831359863281s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.042290687561035156s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.2475719451904297s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.96453857421875e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.1682510375976562e-05s
INFO | --- Analysis for athelia-rfid took 7.22554087638855s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 8.320808410644531e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.2513916492462158s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.02114725112915039s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 3.361701965332031e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 1.1444091796875e-05s
INFO | --- Analysis for aueb-linked-open-data took 2.8297524452209473s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.6793832778930664s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0007333755493164062s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.2593729496002197s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.340576171875e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for AugustiniConfessiones took 4.241455316543579s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.5607593059539795s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.25670695304870605s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.022502422332763672s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.179115295410156e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.1444091796875e-05s
INFO | --- Analysis for austrian_ski_racers took 3.635784149169922s
Availability | SPARQL endpoint availability check for AVsOnto took 8.845329284667969e-05s
Availability | VoID file availability check for AVsOnto took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.24758434295654297s
Reputation | Calculation of the PageRank for AVsOnto took 0.02248358726501465s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.457069396972656e-05s
Believability | Calculation of trust value for AVsOnto took 1.0013580322265625e-05s
INFO | --- Analysis for AVsOnto took 3.0952932834625244s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5738484859466553s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005428791046142578s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 170.67033219337463s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.4861772060394287s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.06947088241577s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 191.6860692501068s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0756425857544s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0064055919647s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.6126494407653809s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.25477075576782227s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17969727516174316s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11204195022583008s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 57.167929887771606s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0385797023773s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11945080757141113s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.06606435775757s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20286011695861816s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09998416900634766s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14650583267211914s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14134740829467773s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.842341423034668s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.224082946777344e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09377264976501465s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0150554180145s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17798185348510742s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.18030166625976562s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10703396797180176s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.21632647514343262s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24399137496948242s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 893.956930398941s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13284802436828613s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.571422815322876s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.1963865756988525s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.737872362136841s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11771965026855469s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.25723338127136s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 411.8885042667389s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.4132351875305176s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.4092707633972s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.815171241760254s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15317726135253906s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.0451266765594482s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.224912166595459s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021755695343017578s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.271766662597656e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6689300537109375e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.059906005859375e-06s
INFO | --- Analysis for b3kat took 6040.233585357666s
Availability | SPARQL endpoint availability check for BabelNet took 0.536280632019043s
Availability | VoID file availability check for BabelNet took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for BabelNet took 0.28113865852355957s
Reputation | Calculation of the PageRank for BabelNet took 0.020904541015625s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001609325408935547s
Believability | Calculation of trust value for BabelNet took 1.0251998901367188e-05s
INFO | --- Analysis for babelnet took 6.53485369682312s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 8.797645568847656e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.2344808578491211s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.021220684051513672s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bacevicius.lt took 9.775161743164062e-06s
INFO | --- Analysis for Bacevicius.lt took 2.686427593231201s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.5394895076751709s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.2758800983428955s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.022359132766723633s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.363059997558594e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.049041748046875e-05s
INFO | --- Analysis for bag took 4.656892538070679s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 2.4591760635375977s
Availability | VoID file availability check for 红色经典歌曲 took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.25209832191467285s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02041149139404297s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.1948089599609375e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.33514404296875e-05s
INFO | --- Analysis for baixue took 4.778991937637329s
Availability | SPARQL endpoint availability check for baixue composer took 4.2438507080078125e-05s
Availability | VoID file availability check for baixue composer took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for baixue composer took 0.2754971981048584s
Reputation | Calculation of the PageRank for baixue composer took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for baixue composer took 2.9802322387695312e-05s
Believability | Calculation of trust value for baixue composer took 1.1920928955078125e-05s
INFO | --- Analysis for baixue_composer took 3.1992948055267334s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.3392181396484375e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.26604461669921875s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02184891700744629s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.0994415283203125e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1920928955078125e-05s
INFO | --- Analysis for baixue_imagery took 2.7696280479431152s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 8.916854858398438e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.26359128952026367s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.021294355392456055s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.314018249511719e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1920928955078125e-05s
INFO | --- Analysis for baixue_imagery1 took 4.131033420562744s
Availability | SPARQL endpoint availability check for BAMS took 4.076957702636719e-05s
Availability | VoID file availability check for BAMS took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for BAMS took 0.24422335624694824s
Reputation | Calculation of the PageRank for BAMS took 0.020899295806884766s
Interlinking | Calculation of Degree of Connection for BAMS took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0009481906890869141s
Interlinking | Calculation of Clustering coefficient for BAMS took 4.100799560546875e-05s
Believability | Calculation of trust value for BAMS took 1.2874603271484375e-05s
INFO | --- Analysis for bams took 2.830843687057495s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 8.702278137207031e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.25542783737182617s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.02087235450744629s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.4345855712890625e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.1920928955078125e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 2.854749917984009s
Availability | SPARQL endpoint availability check for BBC Music took 0.5452125072479248s
Availability | VoID file availability check for BBC Music took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for BBC Music took 0.2780473232269287s
Reputation | Calculation of the PageRank for BBC Music took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00012683868408203125s
Believability | Calculation of trust value for BBC Music took 1.1444091796875e-05s
INFO | --- Analysis for bbc-music took 3.5932414531707764s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.21903729438781738s
Availability | VoID file availability check for BBC Programmes took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.2847721576690674s
Reputation | Calculation of the PageRank for BBC Programmes took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0009338855743408203s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00011587142944335938s
Believability | Calculation of trust value for BBC Programmes took 1.1920928955078125e-05s
INFO | --- Analysis for bbc-programmes took 11.073092460632324s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.21206068992614746s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.2530853748321533s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010395050048828125s
Believability | Calculation of trust value for BBC Wildlife Finder took 1.2636184692382812e-05s
INFO | --- Analysis for bbc-wildlife-finder took 9.744903087615967s
Availability | SPARQL endpoint availability check for BBOP took 8.58306884765625e-05s
Availability | VoID file availability check for BBOP took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for BBOP took 0.2646164894104004s
Reputation | Calculation of the PageRank for BBOP took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for BBOP took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0008335113525390625s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.361701965332031e-05s
Believability | Calculation of trust value for BBOP took 1.0728836059570312e-05s
INFO | --- Analysis for bbop took 2.8668270111083984s
Availability | SPARQL endpoint availability check for BBOP took 4.458427429199219e-05s
Availability | VoID file availability check for BBOP took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for BBOP took 0.2854926586151123s
Reputation | Calculation of the PageRank for BBOP took 0.02097010612487793s
Interlinking | Calculation of Degree of Connection for BBOP took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.7670135498046875e-05s
Believability | Calculation of trust value for BBOP took 6.9141387939453125e-06s
INFO | --- Analysis for bbop-selected took 19.92526865005493s
Availability | SPARQL endpoint availability check for Bdgp took 1.272301197052002s
Availability | VoID file availability check for Bdgp took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Bdgp took 0.24654459953308105s
Reputation | Calculation of the PageRank for Bdgp took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bdgp took 8.58306884765625e-06s
INFO | --- Analysis for bdgp took 5.1718831062316895s
Availability | SPARQL endpoint availability check for Bendev Junior took 8.654594421386719e-05s
Availability | VoID file availability check for Bendev Junior took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.249298095703125s
Reputation | Calculation of the PageRank for Bendev Junior took 0.021865129470825195s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 2.8133392333984375e-05s
Believability | Calculation of trust value for Bendev Junior took 1.0967254638671875e-05s
INFO | --- Analysis for bendevoficial took 3.8551840782165527s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 5.694072008132935s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.2650723457336426s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.0205380916595459s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.389617919921875e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 8.58306884765625e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 15.34268569946289s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.315376281738281e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.27745914459228516s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.02063298225402832s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 2.8848648071289062e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 1.1205673217773438e-05s
INFO | --- Analysis for berlin-offener-haushalt took 2.892390012741089s
Availability | SPARQL endpoint availability check for berlios took 4.172325134277344e-05s
Availability | VoID file availability check for berlios took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for berlios took 0.2554199695587158s
Reputation | Calculation of the PageRank for berlios took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for berlios took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for berlios took 8.869171142578125e-05s
Believability | Calculation of trust value for berlios took 1.2159347534179688e-05s
INFO | --- Analysis for berlios took 3.050311326980591s
Availability | SPARQL endpoint availability check for Between Our Worlds took 7.033348083496094e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0006642341613769531s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.30948853492736816s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.02236461639404297s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0010330677032470703s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 9.1552734375e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.239776611328125e-05s
INFO | --- Analysis for betweenourworlds took 8.79780387878418s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.11406373977661133s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.26023244857788086s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020706653594970703s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.96453857421875e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for bfs-linked-data took 2.553868055343628s
Availability | SPARQL endpoint availability check for BibBase took 0.07474875450134277s
Availability | VoID file availability check for BibBase took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for BibBase took 0.26622819900512695s
Reputation | Calculation of the PageRank for BibBase took 0.021024703979492188s
Interlinking | Calculation of Degree of Connection for BibBase took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for BibBase took 0.00010013580322265625s
Believability | Calculation of trust value for BibBase took 1.049041748046875e-05s
INFO | --- Analysis for bibbase took 2.5441555976867676s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.3392181396484375e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0007927417755126953s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.26245570182800293s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 9.822845458984375e-05s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.0728836059570312e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 9.21546220779419s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 8.678436279296875e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.26352667808532715s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.020671367645263672s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010013580322265625s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.1444091796875e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 10.212144136428833s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.291534423828125e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.23830556869506836s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.02084207534790039s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.4332275390625e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.1205673217773438e-05s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.7816271781921387s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 9.131431579589844e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.26109933853149414s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.886222839355469e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.2159347534179688e-05s
INFO | --- Analysis for BibSonomy took 10.312893152236938s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.1484832763671875e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.26197218894958496s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.021823406219482422s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.266334533691406e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 9.775161743164062e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 5.406286239624023s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 6.866455078125e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.2355954647064209s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020913124084472656s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.170967102050781e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.0728836059570312e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.575995922088623s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.25694870948791504s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.021183013916015625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 3.218650817871094e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-acfsid took 2.8683085441589355s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 2.199763536453247s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.00037741661071777344s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 20.271920204162598s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.4767780303955078s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 44.07911491394043s
Interoperability | New terms check for Bio2RDF::Affymetrix took 41.47497200965881s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.089542865753174s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.11531329154968262s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.7799007892608643s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.1645963191986084s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 2.2373995780944824s
License | MR license check for Bio2RDF::Affymetrix took 0.30606698989868164s
License | HR license check for Bio2RDF::Affymetrix took 60.09671902656555s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.1107027530670166s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.68600058555603s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.3153057098388672s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.11058449745178223s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.11558270454406738s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.10536766052246094s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.644646167755127s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 74.95797085762024s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 1.5549743175506592s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.21156978607177734s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.8629248142242432s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.18604540824890137s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.11375284194946289s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.22633790969848633s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.20488548278808594s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 109.59751653671265s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 13.321671962738037s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.2780182361602783s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.13454532623291016s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.1352217197418213s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 7.019965171813965s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8833348751068115s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6360874176025391s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.2930574417114258s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 65.21867322921753s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.215646266937256s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.435048580169678s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.2501294612884521s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.38270401954651s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7096726894378662s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.3070108890533447s
Security | Sign check for Bio2RDF::Affymetrix took 0.11525177955627441s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 16.579195022583008s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.9920392036437988s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.02164769172668457s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010704994201660156s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 13.190200805664062s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1035.5960929393768s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.6091792583465576s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0006678104400634766s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 19.459904193878174s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2759172916412354s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 43.468817472457886s
Interoperability | New terms check for Bio2RDF::Biomodels took 40.11421871185303s
Versatility | Languages check for Bio2RDF::Biomodels took 60.25694561004639s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.26393747329711914s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.15576791763305664s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.5955069065093994s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.32323122024536133s
Availability | RDF dump link check for Bio2RDF::Biomodels took 2.3855655193328857s
License | MR license check for Bio2RDF::Biomodels took 0.52445387840271s
License | HR license check for Bio2RDF::Biomodels took 60.25727963447571s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.25876688957214355s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.256224393844604s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5992074012756348s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2659327983856201s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.25046682357788086s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.27368903160095215s
Performance | Throughput check for Bio2RDF::Biomodels took 11.019690036773682s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 73.81713104248047s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.7052304744720459s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.34471988677978516s
Interlinking | skos check for Bio2RDF::Biomodels took 0.7684683799743652s
Interlinking | skos check for Bio2RDF::Biomodels took 0.33301448822021484s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2492058277130127s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5286576747894287s
Currency | Modification date check for Bio2RDF::Biomodels took 0.4992024898529053s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 108.18813872337341s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 14.033884763717651s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.4243595600128174s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.28165769577026367s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.28530454635620117s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 7.024709939956665s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.886737585067749s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6537246704101562s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.4977600574493408s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.02508330345154s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.426297426223755s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 5.883255958557129s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.2919189929962158s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.53393816947937s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.697157621383667s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.45324087142944336s
Security | Sign check for Bio2RDF::Biomodels took 0.26552414894104004s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 15.407164573669434s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 1.2694447040557861s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.02076101303100586s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011873245239257812s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 12.7434401512146s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1035.5694348812103s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 7.462501525878906e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.2752368450164795s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.022531986236572266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.790855407714844e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 3.7124826908111572s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 1.410656213760376s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.00030350685119628906s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 20.553422212600708s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.1903724670410156s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 43.76931166648865s
Interoperability | New terms check for Bio2RDF::Bioportal took 39.695680379867554s
Versatility | Languages check for Bio2RDF::Bioportal took 60.2682991027832s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.25922346115112305s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.17590570449829102s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.7924895286560059s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.3388862609863281s
Availability | RDF dump link check for Bio2RDF::Bioportal took 2.1983044147491455s
License | MR license check for Bio2RDF::Bioportal took 0.4871244430541992s
License | HR license check for Bio2RDF::Bioportal took 60.254128217697144s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.23568391799926758s
Understandability | Number of label check for Bio2RDF::Bioportal took 9.832029104232788s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.579150915145874s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2615017890930176s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.24608302116394043s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.27034640312194824s
Performance | Throughput check for Bio2RDF::Bioportal took 11.67732858657837s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 76.09369277954102s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.6906304359436035s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.38264918327331543s
Interlinking | skos check for Bio2RDF::Bioportal took 0.7693667411804199s
Interlinking | skos check for Bio2RDF::Bioportal took 0.5605382919311523s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.2713441848754883s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5136268138885498s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5153319835662842s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 108.49241328239441s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 13.778942108154297s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.4175689220428467s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.2766697406768799s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.2880129814147949s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 6.877256393432617s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8911833763122559s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6490688323974609s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.4228172302246094s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 64.85336351394653s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.39809250831604s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.538535833358765s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.2631120681762695s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.53094673156738s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.6951134204864502s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.43277525901794434s
Security | Sign check for Bio2RDF::Bioportal took 0.2670609951019287s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 15.972742557525635s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.3750176429748535s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004341602325439453s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 12.764300346374512s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1046.4014143943787s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.1473217010498047s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.2679760456085205s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.023122787475585938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.2928924560546875e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-chembl took 15.736108541488647s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.6042037010192871s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.000553131103515625s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 19.02280354499817s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2837293148040771s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 43.815778970718384s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 41.32583737373352s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.22834849357605s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.2624800205230713s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.1533644199371338s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.7637968063354492s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.3219130039215088s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 2.5209479331970215s
License | MR license check for Bio2RDF::Clinicaltrials took 0.471923828125s
License | HR license check for Bio2RDF::Clinicaltrials took 60.249160289764404s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.25554895401000977s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.013052701950073s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5903210639953613s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.23459172248840332s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2667679786682129s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.2504878044128418s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.009264707565308s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 75.45189666748047s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.6768941879272461s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.37927889823913574s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.9805631637573242s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.34075212478637695s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.2523486614227295s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5037953853607178s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5189623832702637s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 109.89714026451111s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 13.057133913040161s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.42713189125061035s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.26250505447387695s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.27199625968933105s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 6.893670082092285s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8828186988830566s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.644909143447876s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.41370439529418945s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.05768990516663s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.390678644180298s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.7923972606658936s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.2891130447387695s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.50805926322937s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.6976158618927002s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.4371798038482666s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.26621413230895996s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 15.506409406661987s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.30496883392333984s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020467758178710938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.14984130859375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 14.05850076675415s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1037.3724839687347s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 2.214210033416748s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0005707740783691406s
Extra | Recovery of all triples for Bio2RDF::Ctd took 18.976407527923584s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2033722400665283s
Amount of data | Number of triples check for Bio2RDF::Ctd took 44.702585220336914s
Interoperability | New terms check for Bio2RDF::Ctd took 42.12215995788574s
Versatility | Languages check for Bio2RDF::Ctd took 60.25934958457947s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.26380014419555664s
Security | Check HTTPS for Bio2RDF::Ctd took 0.15395283699035645s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.8295724391937256s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.34355807304382324s
Availability | RDF dump link check for Bio2RDF::Ctd took 2.426241636276245s
License | MR license check for Bio2RDF::Ctd took 0.4518885612487793s
License | HR license check for Bio2RDF::Ctd took 60.25512361526489s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2654547691345215s
Understandability | Number of label check for Bio2RDF::Ctd took 10.590635299682617s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5908663272857666s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.24088597297668457s
Verifiability | Authors check for Bio2RDF::Ctd took 0.26571202278137207s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.26094651222229004s
Performance | Throughput check for Bio2RDF::Ctd took 11.473996639251709s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 71.98062515258789s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.8402953147888184s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.39306044578552246s
Interlinking | skos check for Bio2RDF::Ctd took 0.9481630325317383s
Interlinking | skos check for Bio2RDF::Ctd took 0.35646557807922363s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.25867486000061035s
Currency | Creation date check for Bio2RDF::Ctd took 0.7935476303100586s
Currency | Modification date check for Bio2RDF::Ctd took 0.5220999717712402s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 107.69686341285706s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 12.731532573699951s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4228084087371826s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.2714207172393799s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.27721166610717773s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 7.47024941444397s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8890407085418701s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6489920616149902s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.4683260917663574s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.31676173210144s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.408494234085083s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.017266750335693s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.2901065349578857s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.55916690826416s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.6877949237823486s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.40198683738708496s
Security | Sign check for Bio2RDF::Ctd took 0.2603886127471924s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 18.182586193084717s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.37187910079956055s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.02065730094909668s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0008096694946289062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.628036499023438e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 13.178991794586182s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-ctd took 1047.4435245990753s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.363059997558594e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.003414630889892578s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.2529580593109131s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.021402835845947266s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.412101745605469e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.0251998901367188e-05s
INFO | --- Analysis for bio2rdf-dataset took 2.979907989501953s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.5978882312774658s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0006103515625s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 18.307032346725464s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.299217700958252s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 43.58930706977844s
Interoperability | New terms check for Bio2RDF::Dbsnp took 40.356306314468384s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.25485849380493s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.28683900833129883s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.17064499855041504s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.9953861236572266s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.3146543502807617s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 2.2652344703674316s
License | MR license check for Bio2RDF::Dbsnp took 0.5064725875854492s
License | HR license check for Bio2RDF::Dbsnp took 60.2334361076355s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.27243757247924805s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.11984133720398s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5653197765350342s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.2712433338165283s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2645845413208008s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.24777626991271973s
Performance | Throughput check for Bio2RDF::Dbsnp took 11.121464252471924s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 74.41719794273376s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.7215983867645264s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.3548426628112793s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.7335414886474609s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.3469102382659912s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.2738223075866699s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.48187708854675293s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.49648618698120117s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 108.46706247329712s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 13.376514434814453s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4236001968383789s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.27310705184936523s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.26020097732543945s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 6.877589464187622s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8897271156311035s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6665160655975342s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.48986005783081055s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.41698217391968s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.371044158935547s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.410632610321045s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.2862887382507324s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.484001874923706s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7055091857910156s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.4263880252838135s
Security | Sign check for Bio2RDF::Dbsnp took 0.265352725982666s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 15.343298435211182s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.4007995128631592s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020760059356689453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.200241088867188e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 12.571819305419922s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 1034.5268466472626s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.6105210781097412s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0006282329559326172s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 18.5404953956604s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.235825777053833s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 43.17482376098633s
Interoperability | New terms check for Bio2RDF::Drugbank took 40.45328211784363s
Versatility | Languages check for Bio2RDF::Drugbank took 60.24065923690796s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.26760387420654297s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.16768312454223633s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 1.0773680210113525s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3349151611328125s
Availability | RDF dump link check for Bio2RDF::Drugbank took 2.6444523334503174s
License | MR license check for Bio2RDF::Drugbank took 0.5763325691223145s
License | HR license check for Bio2RDF::Drugbank took 60.24731492996216s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.27037787437438965s
Understandability | Number of label check for Bio2RDF::Drugbank took 9.804932594299316s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.6012389659881592s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.273296594619751s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.2704923152923584s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.2725350856781006s
Performance | Throughput check for Bio2RDF::Drugbank took 11.250041484832764s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 73.57730221748352s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 2.1514952182769775s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.3377964496612549s
Interlinking | skos check for Bio2RDF::Drugbank took 0.8207137584686279s
Interlinking | skos check for Bio2RDF::Drugbank took 0.3889598846435547s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2519710063934326s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5051708221435547s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5171849727630615s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 108.21619033813477s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 13.082529544830322s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4503755569458008s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.2695119380950928s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.29607558250427246s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 7.427971124649048s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8855040073394775s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6549639701843262s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.43528151512145996s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.03018450737s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.367638349533081s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 5.9570348262786865s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.2918040752410889s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.531713247299194s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.6939530372619629s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.4263143539428711s
Security | Sign check for Bio2RDF::Drugbank took 0.2628645896911621s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 16.71430778503418s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 1.0642609596252441s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.02048516273498535s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00010919570922851562s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 13.005307674407959s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-drugbank took 1037.5582082271576s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.5959906578063965s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006401538848876953s
Extra | Recovery of all triples for Bio2RDF::Genage took 18.658267498016357s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.1998076438903809s
Amount of data | Number of triples check for Bio2RDF::Genage took 44.333775758743286s
Interoperability | New terms check for Bio2RDF::Genage took 40.52019000053406s
Versatility | Languages check for Bio2RDF::Genage took 60.26538634300232s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.25658559799194336s
Security | Check HTTPS for Bio2RDF::Genage took 0.15379548072814941s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.8485534191131592s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.33856630325317383s
Availability | RDF dump link check for Bio2RDF::Genage took 2.226038932800293s
License | MR license check for Bio2RDF::Genage took 0.579096794128418s
License | HR license check for Bio2RDF::Genage took 60.22763633728027s
Amount of data | Number of property check for Bio2RDF::Genage took 0.27236485481262207s
Understandability | Number of label check for Bio2RDF::Genage took 9.883011817932129s
Understandability | URI regex check for Bio2RDF::Genage took 0.5526034832000732s
Understandability | Vocabs check for Bio2RDF::Genage took 0.25617527961730957s
Verifiability | Authors check for Bio2RDF::Genage took 0.26642346382141113s
Verifiability | Publishers check for Bio2RDF::Genage took 0.2619292736053467s
Performance | Throughput check for Bio2RDF::Genage took 11.2022066116333s
Amount of data | Check the number of entities for Bio2RDF::Genage took 76.20483350753784s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.7138218879699707s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.3555619716644287s
Interlinking | skos check for Bio2RDF::Genage took 0.7919316291809082s
Interlinking | skos check for Bio2RDF::Genage took 0.5312726497650146s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2508409023284912s
Currency | Creation date check for Bio2RDF::Genage took 0.5213277339935303s
Currency | Modification date check for Bio2RDF::Genage took 0.5100617408752441s
Rep.Conc. | URIs length for Bio2RDF::Genage took 108.73829770088196s
Interoperability | New vocabularies check for Bio2RDF::Genage took 20.30098247528076s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.43044376373291016s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.28896641731262207s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.29280948638916016s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 6.858750343322754s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8972113132476807s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6659190654754639s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.42887067794799805s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.30994486808777s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.399479389190674s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 5.892829656600952s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.2792813777923584s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.55455422401428s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7173061370849609s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.4263951778411865s
Security | Sign check for Bio2RDF::Genage took 0.26704931259155273s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 15.57651948928833s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 1.2814695835113525s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.0207517147064209s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.000682830810546875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 21.62706685066223s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-genage took 1054.7317848205566s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 6.747245788574219e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.27230310440063477s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.020653486251831055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 6.0558319091796875e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-genbank took 2.979212760925293s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.5974583625793457s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006623268127441406s
Extra | Recovery of all triples for Bio2RDF::Gendr took 18.51287579536438s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.233339548110962s
Amount of data | Number of triples check for Bio2RDF::Gendr took 43.34187030792236s
Interoperability | New terms check for Bio2RDF::Gendr took 41.037439584732056s
Versatility | Languages check for Bio2RDF::Gendr took 60.23847961425781s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.2864522933959961s
Security | Check HTTPS for Bio2RDF::Gendr took 0.15543341636657715s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.7127077579498291s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.3709592819213867s
Availability | RDF dump link check for Bio2RDF::Gendr took 2.1979458332061768s
License | MR license check for Bio2RDF::Gendr took 0.5040647983551025s
License | HR license check for Bio2RDF::Gendr took 60.236435651779175s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.2694258689880371s
Understandability | Number of label check for Bio2RDF::Gendr took 9.366341352462769s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5958859920501709s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.2655482292175293s
Verifiability | Authors check for Bio2RDF::Gendr took 0.25559282302856445s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2603724002838135s
Performance | Throughput check for Bio2RDF::Gendr took 11.488303661346436s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 74.58501863479614s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.6887087821960449s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.332263708114624s
Interlinking | skos check for Bio2RDF::Gendr took 0.7090675830841064s
Interlinking | skos check for Bio2RDF::Gendr took 0.34264683723449707s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.261096715927124s
Currency | Creation date check for Bio2RDF::Gendr took 0.5160458087921143s
Currency | Modification date check for Bio2RDF::Gendr took 0.5061328411102295s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 106.97324252128601s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 14.548866748809814s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.43798255920410156s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.28556108474731445s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2877349853515625s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.215690851211548s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8875021934509277s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6574389934539795s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.43001747131347656s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 64.94407248497009s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.4027292728424072s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.123300075531006s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.2947320938110352s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.525585651397705s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.6948878765106201s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.43657755851745605s
Security | Sign check for Bio2RDF::Gendr took 0.288257360458374s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 16.726634979248047s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.8267476558685303s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020960569381713867s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 6.4849853515625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 13.020881175994873s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-gendr took 1039.099881887436s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.6181731224060059s
Availability | VoID file availability check for Bio2RDF::Goa took 0.000682830810546875s
Extra | Recovery of all triples for Bio2RDF::Goa took 18.723830223083496s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2516984939575195s
Amount of data | Number of triples check for Bio2RDF::Goa took 43.786274909973145s
Interoperability | New terms check for Bio2RDF::Goa took 41.19188404083252s
Versatility | Languages check for Bio2RDF::Goa took 60.2566351890564s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.25771474838256836s
Security | Check HTTPS for Bio2RDF::Goa took 0.15499186515808105s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.37365055084228516s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.2985706329345703s
Availability | RDF dump link check for Bio2RDF::Goa took 2.2239091396331787s
License | MR license check for Bio2RDF::Goa took 0.49266862869262695s
License | HR license check for Bio2RDF::Goa took 60.264479875564575s
Amount of data | Number of property check for Bio2RDF::Goa took 0.2472703456878662s
Understandability | Number of label check for Bio2RDF::Goa took 9.351408004760742s
Understandability | URI regex check for Bio2RDF::Goa took 0.5825819969177246s
Understandability | Vocabs check for Bio2RDF::Goa took 0.2549552917480469s
Verifiability | Authors check for Bio2RDF::Goa took 0.2460036277770996s
Verifiability | Publishers check for Bio2RDF::Goa took 0.2506582736968994s
Performance | Throughput check for Bio2RDF::Goa took 11.033456802368164s
Amount of data | Check the number of entities for Bio2RDF::Goa took 71.48334908485413s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.6860959529876709s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.3735067844390869s
Interlinking | skos check for Bio2RDF::Goa took 0.8954339027404785s
Interlinking | skos check for Bio2RDF::Goa took 0.3442721366882324s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.24876642227172852s
Currency | Creation date check for Bio2RDF::Goa took 0.523418664932251s
Currency | Modification date check for Bio2RDF::Goa took 0.5079140663146973s
Rep.Conc. | URIs length for Bio2RDF::Goa took 106.90075635910034s
Interoperability | New vocabularies check for Bio2RDF::Goa took 13.438601732254028s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.42842745780944824s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.30034875869750977s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.2959768772125244s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 6.989862442016602s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8944797515869141s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6425790786743164s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.4153566360473633s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.02342081069946s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.341982126235962s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.398395776748657s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.2960789203643799s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.49299597740173s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.6905670166015625s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.4045882225036621s
Security | Sign check for Bio2RDF::Goa took 0.25036072731018066s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 15.814069986343384s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.32586121559143066s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.318092346191406e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 17.947953462600708s
Believability | Calculation of trust value for Bio2RDF::Goa took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-goa took 1040.9206972122192s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 1.3938806056976318s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0006873607635498047s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 18.36311411857605s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2446045875549316s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 43.56312704086304s
Interoperability | New terms check for Bio2RDF::Hgnc took 39.8782103061676s
Versatility | Languages check for Bio2RDF::Hgnc took 60.24018120765686s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.26381397247314453s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.15540599822998047s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.644878625869751s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.3377857208251953s
Availability | RDF dump link check for Bio2RDF::Hgnc took 2.407167911529541s
License | MR license check for Bio2RDF::Hgnc took 0.4526681900024414s
License | HR license check for Bio2RDF::Hgnc took 60.24169635772705s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.26627254486083984s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.360710144042969s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.6215178966522217s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.24898219108581543s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.25446557998657227s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.2739272117614746s
Performance | Throughput check for Bio2RDF::Hgnc took 11.268432378768921s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 74.91269969940186s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.8944308757781982s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.3763773441314697s
Interlinking | skos check for Bio2RDF::Hgnc took 1.055288314819336s
Interlinking | skos check for Bio2RDF::Hgnc took 0.3861730098724365s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2740755081176758s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5188727378845215s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5025014877319336s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 107.5211181640625s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 12.71575379371643s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.4216787815093994s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.2783772945404053s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.2784607410430908s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.28757119178772s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8840405941009521s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6472423076629639s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.4266173839569092s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.06959414482117s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.3574118614196777s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 5.999435663223267s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.2724685668945312s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.5469970703125s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7197856903076172s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.4275212287902832s
Security | Sign check for Bio2RDF::Hgnc took 0.27298951148986816s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 21.734706163406372s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 1.1056327819824219s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00012683868408203125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 13.755554676055908s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1043.0060296058655s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.6146845817565918s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0005841255187988281s
Extra | Recovery of all triples for Bio2RDF::Homologene took 19.744029760360718s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2311651706695557s
Amount of data | Number of triples check for Bio2RDF::Homologene took 43.5767183303833s
Interoperability | New terms check for Bio2RDF::Homologene took 40.581700563430786s
Versatility | Languages check for Bio2RDF::Homologene took 60.25787591934204s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.2649860382080078s
Security | Check HTTPS for Bio2RDF::Homologene took 0.15621638298034668s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.7844362258911133s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.30074048042297363s
Availability | RDF dump link check for Bio2RDF::Homologene took 2.149325370788574s
License | MR license check for Bio2RDF::Homologene took 0.4749724864959717s
License | HR license check for Bio2RDF::Homologene took 60.24143147468567s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.26921963691711426s
Understandability | Number of label check for Bio2RDF::Homologene took 10.581378698348999s
Understandability | URI regex check for Bio2RDF::Homologene took 0.58829665184021s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.24834012985229492s
Verifiability | Authors check for Bio2RDF::Homologene took 0.2631337642669678s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.25441789627075195s
Performance | Throughput check for Bio2RDF::Homologene took 11.25183892250061s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 73.80005621910095s
Verifiability | Contribs. check for Bio2RDF::Homologene took 1.1861517429351807s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.3514585494995117s
Interlinking | skos check for Bio2RDF::Homologene took 0.6872410774230957s
Interlinking | skos check for Bio2RDF::Homologene took 0.354036808013916s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.24592947959899902s
Currency | Creation date check for Bio2RDF::Homologene took 0.49887609481811523s
Currency | Modification date check for Bio2RDF::Homologene took 0.5138499736785889s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 108.41688752174377s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 14.005820989608765s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.4262080192565918s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.2530205249786377s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.2824137210845947s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 6.512958526611328s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8960318565368652s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6551849842071533s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.38512492179870605s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.00851726531982s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.376553773880005s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.2273194789886475s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.2772765159606934s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.4991557598114s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7072978019714355s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.40261411666870117s
Security | Sign check for Bio2RDF::Homologene took 0.28006458282470703s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 15.292285203933716s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.8022446632385254s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 13.600695133209229s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-homologene took 1037.7382106781006s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 8.463859558105469e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.6733458042144775s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.022888660430908203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 3.457069396972656e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-inoh took 4.961442232131958s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.6033015251159668s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.06411194801330566s
Extra | Recovery of all triples for Bio2RDF::Interpro took 18.816445112228394s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2653555870056152s
Amount of data | Number of triples check for Bio2RDF::Interpro took 43.50602173805237s
Interoperability | New terms check for Bio2RDF::Interpro took 40.54573178291321s
Versatility | Languages check for Bio2RDF::Interpro took 60.24552297592163s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.25599169731140137s
Security | Check HTTPS for Bio2RDF::Interpro took 0.16580581665039062s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.6238067150115967s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.3274374008178711s
Availability | RDF dump link check for Bio2RDF::Interpro took 2.3615598678588867s
License | MR license check for Bio2RDF::Interpro took 0.48351573944091797s
License | HR license check for Bio2RDF::Interpro took 60.24373650550842s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2690587043762207s
Understandability | Number of label check for Bio2RDF::Interpro took 10.2139253616333s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5989034175872803s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.24887299537658691s
Verifiability | Authors check for Bio2RDF::Interpro took 0.2603142261505127s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.26217174530029297s
Performance | Throughput check for Bio2RDF::Interpro took 11.204913854598999s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 74.41623139381409s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.8756890296936035s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.34581851959228516s
Interlinking | skos check for Bio2RDF::Interpro took 0.7539258003234863s
Interlinking | skos check for Bio2RDF::Interpro took 0.3388998508453369s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.26210975646972656s
Currency | Creation date check for Bio2RDF::Interpro took 0.5270586013793945s
Currency | Modification date check for Bio2RDF::Interpro took 0.4935135841369629s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 106.97632908821106s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 12.550663948059082s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.426715612411499s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.27039051055908203s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.27173495292663574s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 6.901995897293091s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8861627578735352s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6453981399536133s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.4254627227783203s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.39677882194519s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.417222261428833s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.49885106086731s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.259878396987915s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.495627880096436s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.6899170875549316s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.392777681350708s
Security | Sign check for Bio2RDF::Interpro took 0.2672584056854248s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 16.86874556541443s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 1.4867770671844482s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.021747589111328125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0011277198791503906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00011944770812988281s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 12.692378520965576s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-interpro took 1035.8460841178894s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.15404748916625977s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.25243449211120605s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.021793603897094727s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.534027099609375e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-iproclass took 17.984244108200073s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.6037638187408447s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0006227493286132812s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 18.129023790359497s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2510647773742676s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 43.06214118003845s
Interoperability | New terms check for Bio2RDF::Irefindex took 41.44206261634827s
Versatility | Languages check for Bio2RDF::Irefindex took 60.240662574768066s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.27715539932250977s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.15706825256347656s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.8017613887786865s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.31061434745788574s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.392656087875366s
License | MR license check for Bio2RDF::Irefindex took 0.48613953590393066s
License | HR license check for Bio2RDF::Irefindex took 60.25187683105469s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.26441526412963867s
Understandability | Number of label check for Bio2RDF::Irefindex took 10.103907585144043s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.5902562141418457s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.26215124130249023s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.2510707378387451s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.2540147304534912s
Performance | Throughput check for Bio2RDF::Irefindex took 11.09788727760315s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 76.3291277885437s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.6898901462554932s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.3714027404785156s
Interlinking | skos check for Bio2RDF::Irefindex took 1.094139814376831s
Interlinking | skos check for Bio2RDF::Irefindex took 0.3381516933441162s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.26635169982910156s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5044171810150146s
Currency | Modification date check for Bio2RDF::Irefindex took 0.504692554473877s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 107.73865365982056s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 14.614512205123901s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.4147326946258545s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2786874771118164s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.2660374641418457s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 7.139136552810669s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8922076225280762s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6638145446777344s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.4064807891845703s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.12746214866638s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.4073424339294434s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.739037275314331s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.3229868412017822s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.51443338394165s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7131688594818115s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.42775654792785645s
Security | Sign check for Bio2RDF::Irefindex took 0.25899267196655273s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 15.123257160186768s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.8097400665283203s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.273124694824219e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 12.821422576904297s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1035.2143075466156s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.7187366485595703s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.021179914474487305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.604194641113281e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-kegg took 4.710724353790283s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.6939547061920166s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.021982908248901367s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.8623809814453125e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-kegg-biopax took 4.1195595264434814s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.15959453582763672s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.25287389755249023s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-linkedspl took 9.832879066467285s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.5879042148590088s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0005805492401123047s
Extra | Recovery of all triples for Bio2RDF::Lsr took 18.783302545547485s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.216557502746582s
Amount of data | Number of triples check for Bio2RDF::Lsr took 43.486409425735474s
Interoperability | New terms check for Bio2RDF::Lsr took 41.73592233657837s
Versatility | Languages check for Bio2RDF::Lsr took 60.26065754890442s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.25116443634033203s
Security | Check HTTPS for Bio2RDF::Lsr took 0.1457228660583496s
Interpretability | RDF structures check for Bio2RDF::Lsr took 1.1602137088775635s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.3395054340362549s
Availability | RDF dump link check for Bio2RDF::Lsr took 2.3991143703460693s
License | MR license check for Bio2RDF::Lsr took 0.48948192596435547s
License | HR license check for Bio2RDF::Lsr took 60.259297132492065s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.27876877784729004s
Understandability | Number of label check for Bio2RDF::Lsr took 10.489812135696411s
Understandability | URI regex check for Bio2RDF::Lsr took 0.6145563125610352s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.24849581718444824s
Verifiability | Authors check for Bio2RDF::Lsr took 0.26848864555358887s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.24878811836242676s
Performance | Throughput check for Bio2RDF::Lsr took 11.709217071533203s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 77.64579153060913s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.9548404216766357s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3768277168273926s
Interlinking | skos check for Bio2RDF::Lsr took 0.7689449787139893s
Interlinking | skos check for Bio2RDF::Lsr took 0.34169983863830566s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.27541375160217285s
Currency | Creation date check for Bio2RDF::Lsr took 0.4930858612060547s
Currency | Modification date check for Bio2RDF::Lsr took 0.506967306137085s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 107.04803562164307s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 12.130196332931519s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.3993396759033203s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.2797720432281494s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.27720069885253906s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 7.479053974151611s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8814888000488281s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6550648212432861s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.4369819164276123s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 64.83414340019226s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.386443614959717s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.010726451873779s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.2629218101501465s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.47787952423096s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.6935238838195801s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.4470336437225342s
Security | Sign check for Bio2RDF::Lsr took 0.26680922508239746s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 16.283862829208374s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.5983848571777344s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.020441532135009766s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0008709430694580078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.626678466796875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 12.436069965362549s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-lsr took 1040.1456444263458s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.5817291736602783s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.000614166259765625s
Extra | Recovery of all triples for Bio2RDF::Mesh took 19.188493013381958s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.269599437713623s
Amount of data | Number of triples check for Bio2RDF::Mesh took 44.00157642364502s
Interoperability | New terms check for Bio2RDF::Mesh took 42.922473669052124s
Versatility | Languages check for Bio2RDF::Mesh took 60.24798393249512s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.27359986305236816s
Security | Check HTTPS for Bio2RDF::Mesh took 0.15552449226379395s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.7544329166412354s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.3101043701171875s
Availability | RDF dump link check for Bio2RDF::Mesh took 2.398947238922119s
License | MR license check for Bio2RDF::Mesh took 0.4794485569000244s
License | HR license check for Bio2RDF::Mesh took 60.24874186515808s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.2538778781890869s
Understandability | Number of label check for Bio2RDF::Mesh took 10.209001302719116s
Understandability | URI regex check for Bio2RDF::Mesh took 0.6047897338867188s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.2470228672027588s
Verifiability | Authors check for Bio2RDF::Mesh took 0.26985931396484375s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.25607752799987793s
Performance | Throughput check for Bio2RDF::Mesh took 11.411983728408813s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 72.5152633190155s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.7104063034057617s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.3682749271392822s
Interlinking | skos check for Bio2RDF::Mesh took 0.9515841007232666s
Interlinking | skos check for Bio2RDF::Mesh took 0.3732938766479492s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.27836060523986816s
Currency | Creation date check for Bio2RDF::Mesh took 0.5071158409118652s
Currency | Modification date check for Bio2RDF::Mesh took 0.531653642654419s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 107.3669319152832s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 12.258094549179077s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.4389479160308838s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.27512097358703613s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.27289748191833496s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 6.993603944778442s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8979091644287109s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6706686019897461s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.45139002799987793s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.25576639175415s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.401676893234253s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 5.915359020233154s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.2928354740142822s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.47524833679199s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.6863760948181152s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.4081401824951172s
Security | Sign check for Bio2RDF::Mesh took 0.26337623596191406s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 16.274308443069458s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.8674829006195068s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020306825637817383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 8.034706115722656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 12.877252578735352s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-mesh took 1037.8833258152008s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 1.409759759902954s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0007643699645996094s
Extra | Recovery of all triples for Bio2RDF::Mgi took 19.144014358520508s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2352893352508545s
Amount of data | Number of triples check for Bio2RDF::Mgi took 43.15064978599548s
Interoperability | New terms check for Bio2RDF::Mgi took 41.201000452041626s
Versatility | Languages check for Bio2RDF::Mgi took 60.25482797622681s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.2775864601135254s
Security | Check HTTPS for Bio2RDF::Mgi took 0.16711091995239258s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.7261605262756348s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.3078434467315674s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.3510642051696777s
License | MR license check for Bio2RDF::Mgi took 0.44840264320373535s
License | HR license check for Bio2RDF::Mgi took 60.2417151927948s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.2649707794189453s
Understandability | Number of label check for Bio2RDF::Mgi took 10.114627838134766s
Understandability | URI regex check for Bio2RDF::Mgi took 0.568260908126831s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.24485564231872559s
Verifiability | Authors check for Bio2RDF::Mgi took 0.24900078773498535s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.2549881935119629s
Performance | Throughput check for Bio2RDF::Mgi took 10.568715572357178s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 76.58761143684387s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.8820655345916748s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.38639330863952637s
Interlinking | skos check for Bio2RDF::Mgi took 0.9284265041351318s
Interlinking | skos check for Bio2RDF::Mgi took 0.35361742973327637s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.24503469467163086s
Currency | Creation date check for Bio2RDF::Mgi took 0.5272467136383057s
Currency | Modification date check for Bio2RDF::Mgi took 0.5036823749542236s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 109.97084069252014s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 26.02788233757019s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.48566484451293945s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.27173352241516113s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.2641410827636719s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.766523361206055s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.900794267654419s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6721947193145752s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.4377715587615967s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 64.94767832756042s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.3986713886260986s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.496554851531982s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.2636830806732178s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.542640209198s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7169568538665771s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.41988635063171387s
Security | Sign check for Bio2RDF::Mgi took 0.26166677474975586s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 18.643577814102173s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 1.1657311916351318s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02406787872314453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.34600830078125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 11.611103057861328s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-mgi took 1058.907250881195s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.5908021926879883s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0005629062652587891s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 18.77888059616089s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2651021480560303s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 43.16157126426697s
Interoperability | New terms check for Bio2RDF::Ncbigene took 40.624770164489746s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.23887491226196s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.2483351230621338s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.1713249683380127s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.9449985027313232s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.3421776294708252s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 2.2003605365753174s
License | MR license check for Bio2RDF::Ncbigene took 0.5875983238220215s
License | HR license check for Bio2RDF::Ncbigene took 60.23996710777283s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.26996564865112305s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.544779300689697s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.7140376567840576s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.26146650314331055s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.2500486373901367s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.2570936679840088s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.721805334091187s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 73.38085293769836s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.700186014175415s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.3874633312225342s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.9776515960693359s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.40863537788391113s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.26767420768737793s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5283041000366211s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5000200271606445s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 107.74366188049316s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 14.748474836349487s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.436082124710083s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2786862850189209s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.2831752300262451s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.502291917800903s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8930532932281494s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6548817157745361s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.47535085678100586s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.0719997882843s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.411703109741211s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 5.978605508804321s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.257347583770752s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.50269174575806s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.6996450424194336s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.4342329502105713s
Security | Sign check for Bio2RDF::Ncbigene took 0.2764091491699219s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 16.00250506401062s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.44760799407958984s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.02039337158203125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.0001308917999267578s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 13.967637538909912s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1044.3817791938782s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 1.406801700592041s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0007073879241943359s
Extra | Recovery of all triples for Bio2RDF::Ndc took 18.091631412506104s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2592155933380127s
Amount of data | Number of triples check for Bio2RDF::Ndc took 42.8705849647522s
Interoperability | New terms check for Bio2RDF::Ndc took 40.485644578933716s
Versatility | Languages check for Bio2RDF::Ndc took 60.24430060386658s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.25568580627441406s
Security | Check HTTPS for Bio2RDF::Ndc took 0.15719079971313477s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.756948709487915s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.47637367248535156s
Availability | RDF dump link check for Bio2RDF::Ndc took 2.292736530303955s
License | MR license check for Bio2RDF::Ndc took 0.4753425121307373s
License | HR license check for Bio2RDF::Ndc took 60.2544150352478s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.2482130527496338s
Understandability | Number of label check for Bio2RDF::Ndc took 9.23898458480835s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5909080505371094s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.2345438003540039s
Verifiability | Authors check for Bio2RDF::Ndc took 0.2564547061920166s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.25516343116760254s
Performance | Throughput check for Bio2RDF::Ndc took 11.023150205612183s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 77.20232582092285s
Verifiability | Contribs. check for Bio2RDF::Ndc took 1.5979773998260498s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.35726165771484375s
Interlinking | skos check for Bio2RDF::Ndc took 1.076094627380371s
Interlinking | skos check for Bio2RDF::Ndc took 0.34723830223083496s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.30344104766845703s
Currency | Creation date check for Bio2RDF::Ndc took 0.48334622383117676s
Currency | Modification date check for Bio2RDF::Ndc took 0.5051400661468506s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 108.74620056152344s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 14.071024417877197s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.3965137004852295s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.28699398040771484s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.2683382034301758s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 6.894704103469849s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8990895748138428s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6697323322296143s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.39086031913757324s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.0640115737915s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.435607671737671s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.343328237533569s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.302593469619751s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.54614567756653s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7298438549041748s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.4297306537628174s
Security | Sign check for Bio2RDF::Ndc took 0.26134467124938965s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 17.746386528015137s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 1.4749560356140137s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020539045333862305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.817413330078125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 13.216159105300903s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-ndc took 1042.7943596839905s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 8.440017700195312e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.28840208053588867s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.02112746238708496s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.337860107421875e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-netpath took 5.105664014816284s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.14571714401245117s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.2646517753601074s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.023246288299560547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 2.8848648071289062e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-nextprot took 4.24244499206543s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.6219727993011475s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0005581378936767578s
Extra | Recovery of all triples for Bio2RDF::Omim took 19.020987510681152s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.1999852657318115s
Amount of data | Number of triples check for Bio2RDF::Omim took 43.67691445350647s
Interoperability | New terms check for Bio2RDF::Omim took 42.379722356796265s
Versatility | Languages check for Bio2RDF::Omim took 60.256481409072876s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.27782583236694336s
Security | Check HTTPS for Bio2RDF::Omim took 0.15706729888916016s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.5617008209228516s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.32617640495300293s
Availability | RDF dump link check for Bio2RDF::Omim took 2.3594298362731934s
License | MR license check for Bio2RDF::Omim took 0.5135104656219482s
License | HR license check for Bio2RDF::Omim took 60.240718841552734s
Amount of data | Number of property check for Bio2RDF::Omim took 0.23609447479248047s
Understandability | Number of label check for Bio2RDF::Omim took 9.77063536643982s
Understandability | URI regex check for Bio2RDF::Omim took 0.5727880001068115s
Understandability | Vocabs check for Bio2RDF::Omim took 0.2508823871612549s
Verifiability | Authors check for Bio2RDF::Omim took 0.28310394287109375s
Verifiability | Publishers check for Bio2RDF::Omim took 0.2654728889465332s
Performance | Throughput check for Bio2RDF::Omim took 11.274309158325195s
Amount of data | Check the number of entities for Bio2RDF::Omim took 77.55581212043762s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.674511194229126s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.3732748031616211s
Interlinking | skos check for Bio2RDF::Omim took 0.7860162258148193s
Interlinking | skos check for Bio2RDF::Omim took 0.33124303817749023s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.2827901840209961s
Currency | Creation date check for Bio2RDF::Omim took 0.5092179775238037s
Currency | Modification date check for Bio2RDF::Omim took 0.5032908916473389s
Rep.Conc. | URIs length for Bio2RDF::Omim took 111.00268721580505s
Interoperability | New vocabularies check for Bio2RDF::Omim took 20.567200183868408s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.408876895904541s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.2615694999694824s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.27662181854248047s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 7.071726322174072s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8926100730895996s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6435728073120117s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.3986072540283203s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 64.85991740226746s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.375746488571167s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.678455829620361s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.2876920700073242s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.549116134643555s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7213926315307617s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.42665576934814453s
Security | Sign check for Bio2RDF::Omim took 0.27382874488830566s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 17.95696997642517s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.8805720806121826s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.02061295509338379s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00014019012451171875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 14.792045831680298s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-omim took 1054.7554440498352s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.3392181396484375e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.2778465747833252s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.02231884002685547s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.7670135498046875e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 4.050034284591675s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.611522912979126s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0005233287811279297s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 18.158619165420532s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.246410846710205s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 43.711881160736084s
Interoperability | New terms check for Bio2RDF::Orphanet took 40.0884644985199s
Versatility | Languages check for Bio2RDF::Orphanet took 60.265135526657104s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.2561795711517334s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.15359807014465332s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.5241384506225586s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.29895496368408203s
Availability | RDF dump link check for Bio2RDF::Orphanet took 2.2242565155029297s
License | MR license check for Bio2RDF::Orphanet took 0.45643186569213867s
License | HR license check for Bio2RDF::Orphanet took 60.255581855773926s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.27399110794067383s
Understandability | Number of label check for Bio2RDF::Orphanet took 9.894314527511597s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5646648406982422s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.23776006698608398s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.2773864269256592s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.2676277160644531s
Performance | Throughput check for Bio2RDF::Orphanet took 11.466468811035156s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 76.77443957328796s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.8574790954589844s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.3517014980316162s
Interlinking | skos check for Bio2RDF::Orphanet took 0.715731143951416s
Interlinking | skos check for Bio2RDF::Orphanet took 0.41379475593566895s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.24840021133422852s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5268039703369141s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5044093132019043s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 110.60655760765076s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 21.12980318069458s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.46476006507873535s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2855863571166992s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2896578311920166s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 6.8611836433410645s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8911535739898682s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6605618000030518s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.39710402488708496s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 64.97455906867981s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.3889808654785156s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.684609651565552s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.2666757106781006s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.5053870677948s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.6958739757537842s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.41280317306518555s
Security | Sign check for Bio2RDF::Orphanet took 0.26628589630126953s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 18.40392804145813s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 1.2234165668487549s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.020249366760253906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 7.748603820800781e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 13.112618684768677s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1054.1877307891846s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.15380597114562988s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.25705718994140625s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020194530487060547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.62396240234375e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 9.528303623199463s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.5945677757263184s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0005526542663574219s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 20.544386625289917s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.227797031402588s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 45.75260066986084s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 45.22202658653259s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.26159930229187s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.2684476375579834s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.16472625732421875s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.9949824810028076s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.30887913703918457s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 2.331291437149048s
License | MR license check for Bio2RDF::Pharmgkb took 0.4719839096069336s
License | HR license check for Bio2RDF::Pharmgkb took 60.2432279586792s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.2591850757598877s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 9.690216302871704s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5676138401031494s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.2603635787963867s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.26760339736938477s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.252915620803833s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.418549299240112s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 75.49938178062439s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.6896350383758545s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.34433984756469727s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.75960373878479s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.36567139625549316s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.25933408737182617s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5110304355621338s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.498279333114624s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 108.36846947669983s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 14.3464994430542s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.4204998016357422s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.26470136642456055s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.26239538192749023s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 7.680277585983276s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8900461196899414s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6638484001159668s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.4162576198577881s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.4397246837616s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.3784966468811035s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.506970643997192s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.291313648223877s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.56550192832947s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7145142555236816s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.39868855476379395s
Security | Sign check for Bio2RDF::Pharmgkb took 0.3120594024658203s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 17.29203152656555s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.403714656829834s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 8.368492126464844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 13.623107671737671s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 1053.2983474731445s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.26468706130981445s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.021800518035888672s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 3.7312021255493164s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.029273986816406e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.7028541564941406s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.170967102050781e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-pid took 3.3421072959899902s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 4.267692565917969e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.00048828125s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.2930777072906494s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.022245168685913086s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-pubchem-2 took 3.697661876678467s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.5991725921630859s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0004985332489013672s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 18.619207620620728s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2328953742980957s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 44.95783042907715s
Interoperability | New terms check for Bio2RDF::Pubmed took 40.10427165031433s
Versatility | Languages check for Bio2RDF::Pubmed took 60.24421143531799s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.27316832542419434s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.16750335693359375s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.6171567440032959s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.3122527599334717s
Availability | RDF dump link check for Bio2RDF::Pubmed took 2.4823713302612305s
License | MR license check for Bio2RDF::Pubmed took 0.4745512008666992s
License | HR license check for Bio2RDF::Pubmed took 60.26495957374573s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.2551760673522949s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.838445901870728s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5865359306335449s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.2543768882751465s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.24869656562805176s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.25539708137512207s
Performance | Throughput check for Bio2RDF::Pubmed took 10.987998247146606s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 78.0076551437378s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.9138119220733643s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.344280481338501s
Interlinking | skos check for Bio2RDF::Pubmed took 0.7318611145019531s
Interlinking | skos check for Bio2RDF::Pubmed took 0.3424680233001709s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2699406147003174s
Currency | Creation date check for Bio2RDF::Pubmed took 0.48568058013916016s
Currency | Modification date check for Bio2RDF::Pubmed took 0.48685359954833984s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 107.65537643432617s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 13.500297546386719s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.4410572052001953s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.286052942276001s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.26306700706481934s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 6.962266445159912s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.9063107967376709s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6544480323791504s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.43265342712402344s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.58139204978943s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.8082473278045654s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.40989351272583s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.2543132305145264s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.51368689537048s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.6904222965240479s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.4241325855255127s
Security | Sign check for Bio2RDF::Pubmed took 0.2598385810852051s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 18.60857391357422s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.42430734634399414s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020902633666992188s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00014209747314453125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 16.54043173789978s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-pubmed took 1046.6942582130432s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 4.4345855712890625e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.24734711647033691s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020205020904541016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 9.870529174804688e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-reactome took 3.259270668029785s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.0531158447265625e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.26450252532958984s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.221366882324219e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-rhea took 3.2508904933929443s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.15261411666870117s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0003790855407714844s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.2698335647583008s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020201444625854492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.43865966796875e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-sabiork took 8.700368881225586s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.5997822284698486s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0003247261047363281s
Extra | Recovery of all triples for Bio2RDF::Sgd took 18.994080066680908s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.5840997695922852s
Amount of data | Number of triples check for Bio2RDF::Sgd took 44.14922523498535s
Interoperability | New terms check for Bio2RDF::Sgd took 40.49050569534302s
Versatility | Languages check for Bio2RDF::Sgd took 60.26336455345154s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.2719416618347168s
Security | Check HTTPS for Bio2RDF::Sgd took 0.15588617324829102s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.8914837837219238s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.337799072265625s
Availability | RDF dump link check for Bio2RDF::Sgd took 2.309290885925293s
License | MR license check for Bio2RDF::Sgd took 0.5400724411010742s
License | HR license check for Bio2RDF::Sgd took 60.234373807907104s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.2610950469970703s
Understandability | Number of label check for Bio2RDF::Sgd took 10.802358150482178s
Understandability | URI regex check for Bio2RDF::Sgd took 0.6109161376953125s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.26744747161865234s
Verifiability | Authors check for Bio2RDF::Sgd took 0.25051212310791016s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.2626211643218994s
Performance | Throughput check for Bio2RDF::Sgd took 10.966952800750732s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 76.25178289413452s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.6964266300201416s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.3616328239440918s
Interlinking | skos check for Bio2RDF::Sgd took 0.8143377304077148s
Interlinking | skos check for Bio2RDF::Sgd took 0.3380424976348877s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.25939106941223145s
Currency | Creation date check for Bio2RDF::Sgd took 0.5367522239685059s
Currency | Modification date check for Bio2RDF::Sgd took 0.502483606338501s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 107.6790132522583s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 12.379769563674927s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.3970978260040283s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2656092643737793s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.2746741771697998s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.892657518386841s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.8929018974304199s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6504063606262207s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.4289078712463379s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 64.75934767723083s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.441511392593384s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.725974798202515s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.2986414432525635s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.482282400131226s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.699774980545044s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.4210059642791748s
Security | Sign check for Bio2RDF::Sgd took 0.2684638500213623s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 17.80450129508972s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.4123570919036865s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020322799682617188s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00011539459228515625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 12.66896677017212s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-sgd took 1038.8757507801056s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.3392181396484375e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.25380825996398926s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.02324676513671875s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 4.124641418457031e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 4.021683216094971s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.5789833068847656s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0006442070007324219s
Extra | Recovery of all triples for Bio2RDF::Sider took 19.58199191093445s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2252097129821777s
Amount of data | Number of triples check for Bio2RDF::Sider took 42.9544358253479s
Interoperability | New terms check for Bio2RDF::Sider took 42.8713960647583s
Versatility | Languages check for Bio2RDF::Sider took 60.24514293670654s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.26594042778015137s
Security | Check HTTPS for Bio2RDF::Sider took 0.1443462371826172s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.8191573619842529s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.29291749000549316s
Availability | RDF dump link check for Bio2RDF::Sider took 2.346498727798462s
License | MR license check for Bio2RDF::Sider took 0.5159385204315186s
License | HR license check for Bio2RDF::Sider took 60.25184416770935s
Amount of data | Number of property check for Bio2RDF::Sider took 0.2624843120574951s
Understandability | Number of label check for Bio2RDF::Sider took 10.68208360671997s
Understandability | URI regex check for Bio2RDF::Sider took 0.590674638748169s
Understandability | Vocabs check for Bio2RDF::Sider took 0.2556643486022949s
Verifiability | Authors check for Bio2RDF::Sider took 0.2453908920288086s
Verifiability | Publishers check for Bio2RDF::Sider took 0.25475311279296875s
Performance | Throughput check for Bio2RDF::Sider took 11.235974550247192s
Amount of data | Check the number of entities for Bio2RDF::Sider took 74.69999122619629s
Verifiability | Contribs. check for Bio2RDF::Sider took 1.4942502975463867s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.3561747074127197s
Interlinking | skos check for Bio2RDF::Sider took 0.8273346424102783s
Interlinking | skos check for Bio2RDF::Sider took 0.3356130123138428s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.2411513328552246s
Currency | Creation date check for Bio2RDF::Sider took 0.4960968494415283s
Currency | Modification date check for Bio2RDF::Sider took 0.5212311744689941s
Rep.Conc. | URIs length for Bio2RDF::Sider took 108.4746150970459s
Interoperability | New vocabularies check for Bio2RDF::Sider took 13.143593072891235s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.4137246608734131s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.27608776092529297s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2679431438446045s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 6.952639102935791s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8850438594818115s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6487045288085938s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.4731125831604004s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 64.91191029548645s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.3950140476226807s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.156105995178223s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.3156914710998535s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.53025794029236s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7090563774108887s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.44417428970336914s
Security | Sign check for Bio2RDF::Sider took 0.2576582431793213s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 18.86984896659851s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 1.114074945449829s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.363059997558594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 13.393804788589478s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-sider took 1048.8373000621796s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 5.1021575927734375e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.7100322246551514s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.020299434661865234s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-spike took 4.565039157867432s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 7.62939453125e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0003142356872558594s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.23333215713500977s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.0531158447265625e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.5497207641601562e-05s
INFO | --- Analysis for bio2rdf-taxon took 2.5946850776672363s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.5835573673248291s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0005991458892822266s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 19.711484909057617s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2642221450805664s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 43.26426029205322s
Interoperability | New terms check for Bio2RDF::Taxonomy took 41.768166303634644s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.23540115356445s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.24935054779052734s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.16701507568359375s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 1.0172626972198486s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.3217630386352539s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 2.33939266204834s
License | MR license check for Bio2RDF::Taxonomy took 0.42209887504577637s
License | HR license check for Bio2RDF::Taxonomy took 60.24901819229126s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.26117992401123047s
Understandability | Number of label check for Bio2RDF::Taxonomy took 9.424380540847778s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.6084709167480469s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.24543094635009766s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.25952839851379395s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.2639915943145752s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.520750522613525s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 77.34842658042908s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 1.5266807079315186s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.3518247604370117s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.6823699474334717s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.34594297409057617s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.2651205062866211s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.4892098903656006s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5429985523223877s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 108.4415991306305s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 21.084529876708984s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4227468967437744s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.28769469261169434s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.2675449848175049s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 6.69146990776062s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8942861557006836s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6709797382354736s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.41296911239624023s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 64.9158284664154s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.367500066757202s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.798292398452759s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.290903091430664s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.51981234550476s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7025401592254639s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.43528294563293457s
Security | Sign check for Bio2RDF::Taxonomy took 0.25945472717285156s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 21.404385805130005s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.38069820404052734s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010609626770019531s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 14.038936376571655s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.3589859008789062e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 1059.5000491142273s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.14778804779052734s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.2667374610900879s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020236492156982422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 4.482269287109375e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 16.672866106033325s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.5888724327087402s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0005669593811035156s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 22.78086805343628s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.2665941715240479s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 43.866596937179565s
Interoperability | New terms check for Bio2RDF::Wormbase took 41.041621923446655s
Versatility | Languages check for Bio2RDF::Wormbase took 60.25207209587097s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.25716543197631836s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.165069580078125s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.7300825119018555s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.31412267684936523s
Availability | RDF dump link check for Bio2RDF::Wormbase took 2.3897440433502197s
License | MR license check for Bio2RDF::Wormbase took 0.4455525875091553s
License | HR license check for Bio2RDF::Wormbase took 60.234885454177856s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.26868319511413574s
Understandability | Number of label check for Bio2RDF::Wormbase took 10.152518272399902s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.5741469860076904s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.2568967342376709s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.258558988571167s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.23261570930480957s
Performance | Throughput check for Bio2RDF::Wormbase took 11.02452540397644s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 75.39706921577454s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.705859899520874s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.34509944915771484s
Interlinking | skos check for Bio2RDF::Wormbase took 0.9892439842224121s
Interlinking | skos check for Bio2RDF::Wormbase took 0.3300018310546875s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.2420337200164795s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5092871189117432s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5084407329559326s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 106.92329335212708s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 19.15097451210022s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.4380347728729248s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.2653999328613281s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.27771496772766113s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 6.947232007980347s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8916337490081787s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6529827117919922s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.394744873046875s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 64.92841696739197s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.3329505920410156s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.542515516281128s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.2567014694213867s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.50585699081421s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.6994144916534424s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.45694661140441895s
Security | Sign check for Bio2RDF::Wormbase took 0.28746533393859863s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 17.96083688735962s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 1.4110057353973389s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.02053213119506836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.845329284667969e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 12.603956699371338s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-wormbase took 1053.8015308380127s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 4.5299530029296875e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.23949527740478516s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.2636184692382812e-05s
Believability | Calculation of trust value for Biografías y Vidas took 1.1205673217773438e-05s
INFO | --- Analysis for biografiasyvidas took 5.270525693893433s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.831413984298706s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.2643768787384033s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.0205233097076416s
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.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.797645568847656e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 1.0251998901367188e-05s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.7099738121032715s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0002522468566894531s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.2758908271789551s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.020740985870361328s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 3.314018249511719e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for biolit took 2.8164868354797363s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 9.036064147949219e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.37874698638916016s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020882368087768555s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.673004150390625e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.0728836059570312e-05s
INFO | --- Analysis for biolod-pdb took 7.852831602096558s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.5988445281982422s
Availability | VoID file availability check for BioModels RDF took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.26223325729370117s
Reputation | Calculation of the PageRank for BioModels RDF took 0.021044015884399414s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 4.100799560546875e-05s
Believability | Calculation of trust value for BioModels RDF took 1.239776611328125e-05s
INFO | --- Analysis for biomodels-rdf took 4.137356281280518s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.9508161544799805s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2365250587463379s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.1948089599609375e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0728836059570312e-05s
INFO | --- Analysis for Biop took 5.860566139221191s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.9114227294921875e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.23719120025634766s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007462501525878906s
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 9.775161743164062e-06s
INFO | --- Analysis for Bioportal took 2.339914560317993s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 9.274482727050781e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.24376535415649414s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020490407943725586s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006377696990966797s
Believability | Calculation of trust value for Amphibian gross anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-aao took 4.758971929550171s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.363059997558594e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.2628765106201172s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.021691560745239258s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00029468536376953125s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-aba took 4.255646705627441s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2376558780670166s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.021531105041503906s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015785694122314453s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-acgt took 4.513753890991211s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.792213439941406e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.25093770027160645s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020614147186279297s
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.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003197193145751953s
Believability | Calculation of trust value for Animal natural history and life history took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-adw took 3.7706120014190674s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.26006174087524414s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004534721374511719s
Believability | Calculation of trust value for Anatomical Entity Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-aeo took 3.9995276927948s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.2507359981536865s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.020292997360229492s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009813308715820312s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-aero took 4.265620231628418s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.38690185546875e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.24849915504455566s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020655393600463867s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.00040459632873535156s
Believability | Calculation of trust value for AI/RHEUM took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-air took 4.262312412261963s
Availability | SPARQL endpoint availability check for Amino Acid took 4.220008850097656e-05s
Availability | VoID file availability check for Amino Acid took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.24348187446594238s
Reputation | Calculation of the PageRank for Amino Acid took 0.02088332176208496s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00025725364685058594s
Believability | Calculation of trust value for Amino Acid took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-amino-acid took 4.143795013427734s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.25276708602905273s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020514249801635742s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.00028324127197265625s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-apo took 4.127230405807495s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.363059997558594e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.2524995803833008s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00024008750915527344s
Believability | Calculation of trust value for African Traditional Medicine took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-atmo took 3.9152767658233643s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 8.749961853027344e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.24437880516052246s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.298324584960938e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ato took 4.254803419113159s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 9.72747802734375e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.2557947635650635s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.001314401626586914s
Believability | Calculation of trust value for BioAssay Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bao took 3.915834903717041s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 0.00014638900756835938s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.2727644443511963s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.022426605224609375s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003762245178222656s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 3.9868898391723633s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.2606797218322754s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.021172285079956055s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003147125244140625s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bcgo took 4.180010557174683s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.25364089012145996s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020367145538330078s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0013730525970458984s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bdo took 4.1757001876831055s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 7.534027099609375e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.23398971557617188s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.021882295608520508s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004885196685791016s
Believability | Calculation of trust value for Basic Formal Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bfo took 7.225858926773071s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 8.487701416015625e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.25119924545288086s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020460844039916992s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007233619689941406s
Believability | Calculation of trust value for Bleeding History Phenotype took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bho took 4.0122106075286865s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.2706716060638428s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004246234893798828s
Believability | Calculation of trust value for Bilateria anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-bila took 4.100753545761108s
Availability | SPARQL endpoint availability check for BIRNLex took 9.036064147949219e-05s
Availability | VoID file availability check for BIRNLex took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.26134490966796875s
Reputation | Calculation of the PageRank for BIRNLex took 0.022205829620361328s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014913082122802734s
Believability | Calculation of trust value for BIRNLex took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-birnlex took 4.16015887260437s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2736032009124756s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02027726173400879s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007238388061523438s
Believability | Calculation of trust value for Gene Regulation Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bootstrep took 3.88932466506958s
Availability | SPARQL endpoint availability check for BioPAX took 4.2438507080078125e-05s
Availability | VoID file availability check for BioPAX took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for BioPAX took 0.2509474754333496s
Reputation | Calculation of the PageRank for BioPAX took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.00010061264038085938s
Believability | Calculation of trust value for BioPAX took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bp took 4.1494224071502686s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.264132022857666s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.021169185638427734s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003287792205810547s
Believability | Calculation of trust value for Biomedical Resource Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-bro_x1 took 3.8635971546173096s
Availability | SPARQL endpoint availability check for Spatial Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.26277685165405273s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.000213623046875s
Believability | Calculation of trust value for Spatial Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bspo took 3.9779131412506104s
Availability | SPARQL endpoint availability check for BioTop took 4.291534423828125e-05s
Availability | VoID file availability check for BioTop took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for BioTop took 0.27321553230285645s
Reputation | Calculation of the PageRank for BioTop took 0.021524429321289062s
Interlinking | Calculation of Degree of Connection for BioTop took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006473064422607422s
Believability | Calculation of trust value for BioTop took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bt took 4.1551878452301025s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.220008850097656e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.25639772415161133s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020410537719726562s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008990764617919922s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bto took 4.193312883377075s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3011362552642822s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020770788192749023s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.001844644546508789s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-canco took 4.517781019210815s
Availability | SPARQL endpoint availability check for CAO took 4.291534423828125e-05s
Availability | VoID file availability check for CAO took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for CAO took 0.26203155517578125s
Reputation | Calculation of the PageRank for CAO took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for CAO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006177425384521484s
Believability | Calculation of trust value for CAO took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cao took 4.22367525100708s
Availability | SPARQL endpoint availability check for CareLex took 4.220008850097656e-05s
Availability | VoID file availability check for CareLex took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for CareLex took 0.26396965980529785s
Reputation | Calculation of the PageRank for CareLex took 0.02076435089111328s
Interlinking | Calculation of Degree of Connection for CareLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.9591064453125e-05s
Believability | Calculation of trust value for CareLex took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-carelex took 3.92647385597229s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.26003432273864746s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007793903350830078s
Believability | Calculation of trust value for Cell Cycle Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-cco took 3.7480244636535645s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.25131797790527344s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00025582313537597656s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cdao took 4.175106525421143s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.267692565917969e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2530522346496582s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.02084493637084961s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007891654968261719s
Believability | Calculation of trust value for Chemical entities of biological interest took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-chebi took 4.117899179458618s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 8.845329284667969e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.24327945709228516s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.021893024444580078s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002532005310058594s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 4.068966388702393s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 8.392333984375e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.24511194229125977s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020871400833129883s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007472038269042969s
Believability | Calculation of trust value for Chemical Information Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-cheminf took 4.063751935958862s
Availability | SPARQL endpoint availability check for Cell type took 9.012222290039062e-05s
Availability | VoID file availability check for Cell type took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Cell type took 0.25167131423950195s
Reputation | Calculation of the PageRank for Cell type took 0.020676851272583008s
Interlinking | Calculation of Degree of Connection for Cell type took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.00037741661071777344s
Believability | Calculation of trust value for Cell type took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-cl took 4.212118864059448s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.27263689041137695s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008153915405273438s
Believability | Calculation of trust value for Cell Line Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-clo took 4.2258594036102295s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.2598896026611328s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.021645307540893555s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.0001690387725830078s
Believability | Calculation of trust value for Clinical Measurement Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cmo took 4.031016826629639s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 8.416175842285156e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.2728421688079834s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.021857500076293945s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00020265579223632812s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-cno took 4.170631170272827s
Availability | SPARQL endpoint availability check for Wheat trait took 4.291534423828125e-05s
Availability | VoID file availability check for Wheat trait took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.26184678077697754s
Reputation | Calculation of the PageRank for Wheat trait took 0.020629167556762695s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.435943603515625e-05s
Believability | Calculation of trust value for Wheat trait took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-co_wheat took 4.0700061321258545s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.220008850097656e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.2557687759399414s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003612041473388672s
Believability | Calculation of trust value for Cognitive Atlas took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-cogat took 4.085628032684326s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.2496500015258789s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020277023315429688s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007421970367431641s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-cogpo took 4.024867296218872s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.2438507080078125e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.25211358070373535s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020279645919799805s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004258155822753906s
Believability | Calculation of trust value for Current Procedural Terminology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cpt took 4.050763845443726s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 0.00010156631469726562s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.36686110496520996s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020914077758789062s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017588138580322266s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-csp took 4.70946192741394s
Availability | SPARQL endpoint availability check for COSTART took 6.4849853515625e-05s
Availability | VoID file availability check for COSTART took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for COSTART took 0.25820469856262207s
Reputation | Calculation of the PageRank for COSTART took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for COSTART took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009932518005371094s
Believability | Calculation of trust value for COSTART took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-cst took 4.130102872848511s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.410743713378906e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.27092671394348145s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020612239837646484s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005812644958496094s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ctcae took 4.202962398529053s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.649162292480469e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.2649664878845215s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.02058100700378418s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004558563232421875s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ctx took 5.095052719116211s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.124641418457031e-05s
Availability | VoID file availability check for Dendritic cell took 0.0003228187561035156s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.26451945304870605s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020205974578857422s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00028777122497558594s
Believability | Calculation of trust value for Dendritic cell took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-dc_cl took 3.8689582347869873s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.172325134277344e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.266080379486084s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.845329284667969e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ddanat took 4.001752614974976s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 5.1975250244140625e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.259549617767334s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020179271697998047s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009710788726806641s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ddi took 4.210381269454956s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.2623577117919922s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.797645568847656e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-diagnosticont took 3.8423044681549072s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 7.557868957519531e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0007405281066894531s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.26218414306640625s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020832538604736328s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00015616416931152344s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 4.126919507980347s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Human disease ontology took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2551565170288086s
Reputation | Calculation of the PageRank for Human disease ontology took 0.02068948745727539s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006654262542724609s
Believability | Calculation of trust value for Human disease ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-doid took 3.904496192932129s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.24828290939331055s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.021152496337890625s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008575916290283203s
Believability | Calculation of trust value for Electrocardiography Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ecg took 3.990891933441162s
Availability | SPARQL endpoint availability check for Evidence codes took 4.38690185546875e-05s
Availability | VoID file availability check for Evidence codes took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2778139114379883s
Reputation | Calculation of the PageRank for Evidence codes took 0.021009206771850586s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.0994415283203125e-05s
Believability | Calculation of trust value for Evidence codes took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-eco took 3.944241523742676s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 7.009506225585938e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0003800392150878906s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3224673271179199s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017282962799072266s
Believability | Calculation of trust value for Experimental Factor Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-efo took 4.46065616607666s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.220008850097656e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.254504919052124s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011565685272216797s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ehda took 4.14698338508606s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 8.869171142578125e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.24748563766479492s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020871639251708984s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0006978511810302734s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ehdaa took 3.9465246200561523s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.267692565917969e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.2715306282043457s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005252361297607422s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 3.924417018890381s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 7.033348083496094e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.2415452003479004s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.021806001663208008s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.528594970703125e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-emap took 3.8389294147491455s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Environment Ontology took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.23613476753234863s
Reputation | Calculation of the PageRank for Environment Ontology took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00040912628173828125s
Believability | Calculation of trust value for Environment Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-envo took 3.7398204803466797s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.792213439941406e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0007469654083251953s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.26575803756713867s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.02121567726135254s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00031113624572753906s
Believability | Calculation of trust value for Plant environmental conditions took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-eo took 5.965333938598633s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.2729957103729248s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.02030491828918457s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012249946594238281s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ep took 3.990551710128784s
Availability | SPARQL endpoint availability check for Epilepsy took 4.315376281738281e-05s
Availability | VoID file availability check for Epilepsy took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.2587273120880127s
Reputation | Calculation of the PageRank for Epilepsy took 0.021796703338623047s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001392364501953125s
Believability | Calculation of trust value for Epilepsy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-epileponto took 4.091247797012329s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 7.462501525878906e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.2860755920410156s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.02039337158203125s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.001173257827758789s
Believability | Calculation of trust value for eagle-i research resource ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ero took 4.3548712730407715s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.649162292480469e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.26012134552001953s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.021398544311523438s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011696815490722656s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ev took 3.835076093673706s
Availability | SPARQL endpoint availability check for ExO took 4.696846008300781e-05s
Availability | VoID file availability check for ExO took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for ExO took 0.2732658386230469s
Reputation | Calculation of the PageRank for ExO took 0.02199101448059082s
Interlinking | Calculation of Degree of Connection for ExO took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00026869773864746094s
Believability | Calculation of trust value for ExO took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-exo took 3.8964247703552246s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 5.173683166503906e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.2609274387359619s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.023235082626342773s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00012421607971191406s
Believability | Calculation of trust value for Fungal gross anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-fao took 4.006729364395142s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.553794860839844e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.2570223808288574s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020834684371948242s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.0002048015594482422s
Believability | Calculation of trust value for Biological imaging methods took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-fbbi took 4.2058680057525635s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 9.322166442871094e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.24100184440612793s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.021758317947387695s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006413459777832031s
Believability | Calculation of trust value for Drosophila gross anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-fbbt took 3.9636197090148926s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.601478576660156e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.24553918838500977s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.020751476287841797s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004134178161621094s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fbcv took 4.073906898498535s
Availability | SPARQL endpoint availability check for Drosophila development took 8.845329284667969e-05s
Availability | VoID file availability check for Drosophila development took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2817370891571045s
Reputation | Calculation of the PageRank for Drosophila development took 0.021411418914794922s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.9114227294921875e-05s
Believability | Calculation of trust value for Drosophila development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fbdv took 3.897364854812622s
Availability | SPARQL endpoint availability check for Fly taxonomy took 5.412101745605469e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.26175355911254883s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.000377655029296875s
Believability | Calculation of trust value for Fly taxonomy took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-fbsp took 4.209382772445679s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 5.6743621826171875e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.25320935249328613s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020848989486694336s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.0002319812774658203s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 3.723012685775757s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.00048828125s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.26640844345092773s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020635128021240234s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.00040650367736816406s
Believability | Calculation of trust value for Family Health History Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-fhho took 3.8931872844696045s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Influenza Ontology took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.26908254623413086s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.021016836166381836s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010783672332763672s
Believability | Calculation of trust value for Influenza Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-flu took 3.811450242996216s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.553794860839844e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.25835442543029785s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020578622817993164s
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.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.818771362304688e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-fma took 3.7961339950561523s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 9.942054748535156e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.2571249008178711s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.02113032341003418s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00013184547424316406s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-fypo took 4.0211005210876465s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.25452637672424316s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.02088618278503418s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 0.00011587142944335938s
Believability | Calculation of trust value for GeoSpecies Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-geospecies took 4.227543115615845s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.2403104305267334s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.02077794075012207s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.0001671314239501953s
Believability | Calculation of trust value for General Formal Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-gfo took 4.002845764160156s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.553794860839844e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.24745535850524902s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006008148193359375s
Believability | Calculation of trust value for General Formal Ontology: Biology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gfo-bio took 4.1563873291015625s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 7.605552673339844e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.22658610343933105s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.021042823791503906s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008654594421386719s
Believability | Calculation of trust value for Gene Ontology Extension took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-go_x1 took 4.108558893203735s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Gene Ontology took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2535109519958496s
Reputation | Calculation of the PageRank for Gene Ontology took 0.021027803421020508s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008330345153808594s
Believability | Calculation of trust value for Gene Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-go_x2 took 3.869016647338867s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.696846008300781e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.00037479400634765625s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.25777316093444824s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.020717382431030273s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.170967102050781e-05s
Believability | Calculation of trust value for Cereal Plant Development took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-gro took 4.029848098754883s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.76837158203125e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.2697415351867676s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020832061767578125s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004246234893798828s
Believability | Calculation of trust value for Cereal plant gross anatomy took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-gro_x1 took 3.782686948776245s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.00034689903259277344s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2707822322845459s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020746707916259766s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007295608520507812s
Believability | Calculation of trust value for Gene Regulation Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-gro_x2 took 4.009523153305054s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 8.0108642578125e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2530326843261719s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.021153926849365234s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005502700805664062s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-hao took 3.8128271102905273s
Availability | SPARQL endpoint availability check for HCPCS took 4.2438507080078125e-05s
Availability | VoID file availability check for HCPCS took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for HCPCS took 0.2777583599090576s
Reputation | Calculation of the PageRank for HCPCS took 0.020965099334716797s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002269744873046875s
Believability | Calculation of trust value for HCPCS took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-hcpcs took 4.056650161743164s
Availability | SPARQL endpoint availability check for Health Level Seven took 5.054473876953125e-05s
Availability | VoID file availability check for Health Level Seven took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.2560570240020752s
Reputation | Calculation of the PageRank for Health Level Seven took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012907981872558594s
Believability | Calculation of trust value for Health Level Seven took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hl7 took 3.7820229530334473s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.482269287109375e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2613992691040039s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020833253860473633s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003466606140136719s
Believability | Calculation of trust value for HEALTH_INDICATORS took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hlth_indics took 3.8928723335266113s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0003921985626220703s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.25461626052856445s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.021018028259277344s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.266334533691406e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-hom took 3.7994844913482666s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.2438507080078125e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.00040411949157714844s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.2662041187286377s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.0994415283203125e-05s
Believability | Calculation of trust value for HOM-HARVARD took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-hom_harvard took 3.8161888122558594s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.26166319847106934s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.02087116241455078s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006842613220214844s
Believability | Calculation of trust value for Human Phenotype Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-hp_x1 took 3.875438690185547s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0007085800170898438s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.258455753326416s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.021659135818481445s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010786056518554688s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-hpio took 4.2404563426971436s
Availability | SPARQL endpoint availability check for HUGO took 0.00012111663818359375s
Availability | VoID file availability check for HUGO took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for HUGO took 0.28858304023742676s
Reputation | Calculation of the PageRank for HUGO took 0.02095508575439453s
Interlinking | Calculation of Degree of Connection for HUGO took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0008113384246826172s
Interlinking | Calculation of Clustering coefficient for HUGO took 9.417533874511719e-05s
Believability | Calculation of trust value for HUGO took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hugo took 3.9069626331329346s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 6.699562072753906e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.2687075138092041s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020798683166503906s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006551742553710938s
Believability | Calculation of trust value for Information Artifact Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-iao took 4.001865863800049s
Availability | SPARQL endpoint availability check for ICD10 took 8.893013000488281e-05s
Availability | VoID file availability check for ICD10 took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for ICD10 took 0.261136531829834s
Reputation | Calculation of the PageRank for ICD10 took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008413791656494141s
Believability | Calculation of trust value for ICD10 took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-icd10 took 4.034013748168945s
Availability | SPARQL endpoint availability check for ICD10CM took 4.3392181396484375e-05s
Availability | VoID file availability check for ICD10CM took 0.0007319450378417969s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.25031304359436035s
Reputation | Calculation of the PageRank for ICD10CM took 0.020284175872802734s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006222724914550781s
Believability | Calculation of trust value for ICD10CM took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-icd10cm took 4.317065000534058s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 8.749961853027344e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.24451875686645508s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020414352416992188s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00016069412231445312s
Believability | Calculation of trust value for ICD-10-PCS took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-icd10pcs took 4.038791656494141s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 9.34600830078125e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.26654577255249023s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020682811737060547s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006399154663085938s
Believability | Calculation of trust value for International Classification of Diseases took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-icd9cm took 4.072033405303955s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 6.866455078125e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.000705718994140625s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.24326109886169434s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.00045108795166015625s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-icf_x1 took 4.154831409454346s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.1961669921875e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.2797660827636719s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02188253402709961s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012323856353759766s
Believability | Calculation of trust value for International Classification for Nursing Practice took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icnp took 4.195135116577148s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 0.00012302398681640625s
Availability | VoID file availability check for International Classification of Primary Care took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.25307250022888184s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004432201385498047s
Believability | Calculation of trust value for International Classification of Primary Care took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icpc took 4.128700494766235s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 8.320808410644531e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0007748603820800781s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2659757137298584s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008962154388427734s
Believability | Calculation of trust value for ICPC-2 PLUS took 3.218650817871094e-05s
INFO | --- Analysis for bioportal-icpc2p took 3.8379263877868652s
Availability | SPARQL endpoint availability check for ICPS Network took 8.344650268554688e-05s
Availability | VoID file availability check for ICPS Network took 0.0007476806640625s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.2540428638458252s
Reputation | Calculation of the PageRank for ICPS Network took 0.020445823669433594s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00022745132446289062s
Believability | Calculation of trust value for ICPS Network took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-icps took 5.590851306915283s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0008065700531005859s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.2744464874267578s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020900487899780273s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.00084686279296875s
Believability | Calculation of trust value for Infectious Disease Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ido took 4.126027345657349s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0008180141448974609s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2720789909362793s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011432170867919922s
Believability | Calculation of trust value for Brucellosis Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-idobru took 4.061506032943726s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.25313687324523926s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0012896060943603516s
Believability | Calculation of trust value for Malaria Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-idomal took 4.285261869430542s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 8.797645568847656e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0007328987121582031s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.2557947635650635s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020705699920654297s
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.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.00033164024353027344s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-iev took 3.9839022159576416s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 8.845329284667969e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.27506375312805176s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00016045570373535156s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-imgt took 4.205191135406494s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.363059997558594e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.25342750549316406s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020864486694335938s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005288124084472656s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-imr took 4.096320390701294s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.026010990142822266s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.26200056076049805s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020643949508666992s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007996559143066406s
Believability | Calculation of trust value for Interaction Network Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ino took 6.962087869644165s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.863739013671875e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.28010034561157227s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.266334533691406e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-invertebrata took 5.396111488342285s
Availability | SPARQL endpoint availability check for IxnO took 6.651878356933594e-05s
Availability | VoID file availability check for IxnO took 0.0008065700531005859s
Completeness | Calculation of interlinking completeness for IxnO took 0.27690672874450684s
Reputation | Calculation of the PageRank for IxnO took 0.02141094207763672s
Interlinking | Calculation of Degree of Connection for IxnO took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.0002143383026123047s
Believability | Calculation of trust value for IxnO took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ixno took 4.247311353683472s
Availability | SPARQL endpoint availability check for SysMO-JERM took 5.7220458984375e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0008094310760498047s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.2772202491760254s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020612239837646484s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.00037932395935058594s
Believability | Calculation of trust value for SysMO-JERM took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-jerm took 5.207455635070801s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 5.030632019042969e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.25202012062072754s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.021544218063354492s
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.0008089542388916016s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 4.220008850097656e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-kisao took 3.8515632152557373s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.9591064453125e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0009305477142333984s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.2491440773010254s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.0002105236053466797s
Believability | Calculation of trust value for Loggerhead nesting took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-lhn took 4.174075365066528s
Availability | SPARQL endpoint availability check for Lipid Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.2633025646209717s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020777225494384766s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.0002143383026123047s
Believability | Calculation of trust value for Lipid Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-lipro took 3.955331325531006s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 5.459785461425781e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0008428096771240234s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.3055102825164795s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018200874328613281s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-lnc took 4.7220635414123535s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 9.083747863769531e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.000812530517578125s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.23598599433898926s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020529508590698242s
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.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006496906280517578s
Believability | Calculation of trust value for Mouse adult gross anatomy took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ma took 4.142789840698242s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.8160552978515625e-05s
Availability | VoID file availability check for Multiple alignment took 0.0008156299591064453s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.25287628173828125s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00020837783813476562s
Believability | Calculation of trust value for Multiple alignment took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mao took 4.10753059387207s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.506111145019531e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0008382797241210938s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.28092312812805176s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007035732269287109s
Believability | Calculation of trust value for Minimal anatomical terminology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-mat took 4.07989239692688s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 6.866455078125e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0007357597351074219s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.24720287322998047s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020766258239746094s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004379749298095703s
Believability | Calculation of trust value for Breast tissue cell lines took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mcbcc took 4.1840643882751465s
Availability | SPARQL endpoint availability check for Cell line ontology took 7.128715515136719e-05s
Availability | VoID file availability check for Cell line ontology took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.26837778091430664s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007541179656982422s
Believability | Calculation of trust value for Cell line ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mccl took 4.259486675262451s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Cell line ontology took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2416830062866211s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02104043960571289s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0009970664978027344s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0015769004821777344s
Believability | Calculation of trust value for Cell line ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-mccl_x1 took 4.013605356216431s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 9.632110595703125e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0007171630859375s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.27581071853637695s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002465248107910156s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-mcv took 3.996926784515381s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.601478576660156e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0003879070281982422s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.26518964767456055s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020593643188476562s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.0001838207244873047s
Believability | Calculation of trust value for Master Drug Data Base took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mddb took 4.280940055847168s
Availability | SPARQL endpoint availability check for MedDRA took 0.00010085105895996094s
Availability | VoID file availability check for MedDRA took 0.0008771419525146484s
Completeness | Calculation of interlinking completeness for MedDRA took 0.24198532104492188s
Reputation | Calculation of the PageRank for MedDRA took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011358261108398438s
Believability | Calculation of trust value for MedDRA took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mdr took 4.030275106430054s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.076957702636719e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.2447643280029297s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008902549743652344s
Believability | Calculation of trust value for MedlinePlus Health Topics took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-medlineplus took 4.1309545040130615s
Availability | SPARQL endpoint availability check for MeGO took 0.00010037422180175781s
Availability | VoID file availability check for MeGO took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for MeGO took 0.23428988456726074s
Reputation | Calculation of the PageRank for MeGO took 0.022064208984375s
Interlinking | Calculation of Degree of Connection for MeGO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014972686767578125s
Believability | Calculation of trust value for MeGO took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mego took 3.8187174797058105s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.2438507080078125e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.2967185974121094s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018320083618164062s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mesh-owl took 4.50308895111084s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.26096582412719727s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.02148580551147461s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006153583526611328s
Believability | Calculation of trust value for Mental Functioning Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mf took 4.4994282722473145s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 9.036064147949219e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.2523970603942871s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.02101445198059082s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005376338958740234s
Believability | Calculation of trust value for Medaka fish anatomy and development took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mfo took 4.1806159019470215s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2662360668182373s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020205974578857422s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007534027099609375s
Believability | Calculation of trust value for Emotion Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mfoem took 3.907982349395752s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.2749805450439453s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00011801719665527344s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mhc took 3.921088457107544s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 8.797645568847656e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.2724730968475342s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020554542541503906s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006971359252929688s
Believability | Calculation of trust value for Protein-protein interaction took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mi took 4.4076128005981445s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 9.417533874511719e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.25603747367858887s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.021280527114868164s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0010678768157958984s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0008876323699951172s
Believability | Calculation of trust value for Mosquito insecticide resistance took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-miro took 4.061195135116577s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0006730556488037109s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.29361486434936523s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.021869182586669922s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00014281272888183594s
Believability | Calculation of trust value for Measurement Method Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mmo took 5.185036659240723s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for MGED Ontology took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.24563145637512207s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020783662796020508s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.00038433074951171875s
Believability | Calculation of trust value for MGED Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mo took 3.945432186126709s
Availability | SPARQL endpoint availability check for Protein modification took 4.315376281738281e-05s
Availability | VoID file availability check for Protein modification took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Protein modification took 0.26206278800964355s
Reputation | Calculation of the PageRank for Protein modification took 0.02205657958984375s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002338886260986328s
Believability | Calculation of trust value for Protein modification took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mod took 4.166605710983276s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 9.083747863769531e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.24902915954589844s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020669937133789062s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006542205810546875s
Believability | Calculation of trust value for Mammalian phenotype took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mp took 4.108709335327148s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.2438507080078125e-05s
Availability | VoID file availability check for Mouse pathology took 0.0007262229919433594s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.2880849838256836s
Reputation | Calculation of the PageRank for Mouse pathology took 0.020865201950073242s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004782676696777344s
Believability | Calculation of trust value for Mouse pathology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mpath took 4.2573487758636475s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.315376281738281e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.25144314765930176s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020704984664916992s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003600120544433594s
Believability | Calculation of trust value for Mass spectrometry took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ms took 4.186665296554565s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 8.487701416015625e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.30164361000061035s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020903348922729492s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018854141235351562s
Believability | Calculation of trust value for Medical Subject Headings took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-msh took 4.5662267208099365s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.124641418457031e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2569084167480469s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020514965057373047s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00017404556274414062s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mthch took 4.137593746185303s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.25684475898742676s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007779598236083984s
Believability | Calculation of trust value for Natural Products Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-natpro took 4.083342552185059s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.220008850097656e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.28741908073425293s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020608186721801758s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0007958412170410156s
Believability | Calculation of trust value for NCBI organismal classification took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 4.009068012237549s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 9.226799011230469e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0007424354553222656s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.34345006942749023s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.021184682846069336s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.001987457275390625s
Believability | Calculation of trust value for NCI Thesaurus took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ncit took 7.815220594406128s
Availability | SPARQL endpoint availability check for National Drug Data File took 9.655952453613281e-05s
Availability | VoID file availability check for National Drug Data File took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.2591702938079834s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020952224731445312s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006415843963623047s
Believability | Calculation of trust value for National Drug Data File took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-nddf took 3.969710350036621s
Availability | SPARQL endpoint availability check for National Drug File took 5.745887756347656e-05s
Availability | VoID file availability check for National Drug File took 0.0007913112640380859s
Completeness | Calculation of interlinking completeness for National Drug File took 0.2652573585510254s
Reputation | Calculation of the PageRank for National Drug File took 0.02194046974182129s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012614727020263672s
Believability | Calculation of trust value for National Drug File took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ndfrt took 4.156959295272827s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.410743713378906e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.26514506340026855s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02059316635131836s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0012049674987792969s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 4.118251800537109s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.9591064453125e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.2811715602874756s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.02028822898864746s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006518363952636719s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-neomark took 4.210574150085449s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0007932186126708984s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.2780027389526367s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.02161574363708496s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0010523796081542969s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.0001659393310546875s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-neomarkontology took 4.185986518859863s
Availability | SPARQL endpoint availability check for NIFSTD took 4.267692565917969e-05s
Availability | VoID file availability check for NIFSTD took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.2992360591888428s
Reputation | Calculation of the PageRank for NIFSTD took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0018982887268066406s
Believability | Calculation of trust value for NIFSTD took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-nif took 4.677259206771851s
Availability | SPARQL endpoint availability check for NIF Cell took 8.511543273925781e-05s
Availability | VoID file availability check for NIF Cell took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.24402070045471191s
Reputation | Calculation of the PageRank for NIF Cell took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013151168823242188s
Believability | Calculation of trust value for NIF Cell took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-nif_cell took 4.158386945724487s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.172325134277344e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.2583286762237549s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014164447784423828s
Believability | Calculation of trust value for NIF Dysfunction took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 3.914608955383301s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 6.67572021484375e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0011641979217529297s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.2378227710723877s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.020372867584228516s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005609989166259766s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-nigo took 3.9896867275238037s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.172325134277344e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.25350069999694824s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020221948623657227s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005497932434082031s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-nmr took 3.866884708404541s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.23375678062438965s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.0001087188720703125s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-nonrctontology took 4.094358444213867s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0003437995910644531s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.24580836296081543s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011837482452392578s
Believability | Calculation of trust value for NanoParticle Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-npo took 4.279141664505005s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.124641418457031e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.26180410385131836s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.02028179168701172s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0008189678192138672s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007443428039550781s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-oae took 4.068304538726807s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 5.4836273193359375e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.271756649017334s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.001424551010131836s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-obi took 4.195899248123169s
Availability | SPARQL endpoint availability check for OBOE took 8.440017700195312e-05s
Availability | VoID file availability check for OBOE took 0.0006103515625s
Completeness | Calculation of interlinking completeness for OBOE took 0.27300238609313965s
Reputation | Calculation of the PageRank for OBOE took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for OBOE took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007987022399902344s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011968612670898438s
Believability | Calculation of trust value for OBOE took 7.62939453125e-06s
INFO | --- Analysis for bioportal-oboe took 3.9390528202056885s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.1961669921875e-05s
Availability | VoID file availability check for OBOE SBC took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.26221227645874023s
Reputation | Calculation of the PageRank for OBOE SBC took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007598400115966797s
Believability | Calculation of trust value for OBOE SBC took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 3.947563409805298s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0003204345703125s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.24548864364624023s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020534038543701172s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005726814270019531s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ocre took 3.978436231613159s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.458427429199219e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.2477586269378662s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008864402770996094s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-odgi took 3.8158583641052246s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.00040984153747558594s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.25504612922668457s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020255327224731445s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008795261383056641s
Believability | Calculation of trust value for Ontology for Genetic Interval took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ogi took 4.073506116867065s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 7.462501525878906e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.23515963554382324s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0002880096435546875s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ogmd took 3.87570858001709s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.076957702636719e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.26708030700683594s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.022122859954833984s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0007150173187255859s
Believability | Calculation of trust value for Ontology for General Medical Science took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ogms took 4.074366569519043s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 8.440017700195312e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.2631378173828125s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.02020120620727539s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011169910430908203s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 3.814697265625e-06s
INFO | --- Analysis for bioportal-omim took 3.9658572673797607s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.6253204345703125e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0007343292236328125s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.28521275520324707s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020316600799560547s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003669261932373047s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-omit took 3.8759303092956543s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.076957702636719e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0002117156982421875s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.27002644538879395s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.02030777931213379s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005872249603271484s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-omrse took 2.3779537677764893s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 8.487701416015625e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.2634706497192383s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.02037215232849121s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007739067077636719s
Believability | Calculation of trust value for Ontology of Data Mining took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ontodm took 4.15018892288208s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.26386141777038574s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002391338348388672s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ontodt took 3.952021837234497s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 5.269050598144531e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.2675149440765381s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.02030801773071289s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.000591278076171875s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ontoorpha took 3.9673118591308594s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 5.53131103515625e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.24991369247436523s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020325422286987305s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009045600891113281s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-opl took 4.025543451309204s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.172325134277344e-05s
Availability | VoID file availability check for Phenotypic quality took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.2378065586090088s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008523464202880859s
Believability | Calculation of trust value for Phenotypic quality took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-pato took 3.8295581340789795s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.220008850097656e-05s
Availability | VoID file availability check for Physician Data Query took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.2443678379058838s
Reputation | Calculation of the PageRank for Physician Data Query took 0.02035236358642578s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.000797271728515625s
Believability | Calculation of trust value for Physician Data Query took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-pdq took 4.037807941436768s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.267692565917969e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.2659614086151123s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020678043365478516s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007879734039306641s
Believability | Calculation of trust value for Pediatric Terminology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pedterm took 4.106884956359863s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.2481989860534668s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020808696746826172s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.0002200603485107422s
Believability | Calculation of trust value for Parasite Experiment Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-peo took 4.1302220821380615s
Availability | SPARQL endpoint availability check for PHARE took 4.506111145019531e-05s
Availability | VoID file availability check for PHARE took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for PHARE took 0.28081297874450684s
Reputation | Calculation of the PageRank for PHARE took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for PHARE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006308555603027344s
Believability | Calculation of trust value for PHARE took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-phare took 4.13685417175293s
Availability | SPARQL endpoint availability check for PKO_Re took 8.893013000488281e-05s
Availability | VoID file availability check for PKO_Re took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.2341935634613037s
Reputation | Calculation of the PageRank for PKO_Re took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0001685619354248047s
Believability | Calculation of trust value for PKO_Re took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-pko took 4.469287395477295s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.315376281738281e-05s
Availability | VoID file availability check for PMA 2010 took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.24277496337890625s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.000885009765625s
Believability | Calculation of trust value for PMA 2010 took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-pma took 4.031347751617432s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.291534423828125e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.24310922622680664s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.02057933807373047s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00018310546875s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 7.62939453125e-06s
INFO | --- Analysis for bioportal-pmr took 4.111455917358398s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.57763671875e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0004093647003173828s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.284121036529541s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.021460533142089844s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00037598609924316406s
Believability | Calculation of trust value for Plant Anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-po took 3.9776227474212646s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 0.0001556873321533203s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.26456594467163086s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020910978317260742s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.628036499023438e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-po_x1 took 4.252471923828125s
Availability | SPARQL endpoint availability check for Plant Ontology took 8.487701416015625e-05s
Availability | VoID file availability check for Plant Ontology took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.27289271354675293s
Reputation | Calculation of the PageRank for Plant Ontology took 0.021200895309448242s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.000431060791015625s
Believability | Calculation of trust value for Plant Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-po_x2 took 4.061365127563477s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 8.535385131835938e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.2592456340789795s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020233154296875s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006670951843261719s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-pr took 4.151238203048706s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.1961669921875e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.24416685104370117s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.02080702781677246s
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.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002892017364501953s
Believability | Calculation of trust value for Proteomics data and process provenance took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-propreo took 3.943390369415283s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Pathway ontology took 0.0007860660552978516s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.24763751029968262s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020509004592895508s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012612342834472656s
Believability | Calculation of trust value for Pathway ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-pw took 3.8956069946289062s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 9.5367431640625e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.2509593963623047s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 2.9325485229492188e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-qibo took 3.8283584117889404s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.3392181396484375e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3153257369995117s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017735958099365234s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-rcd took 4.830239772796631s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.27161407470703125s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00014901161193847656s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-rctontology took 4.120164632797241s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.2531318664550781s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.0214841365814209s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 2.8133392333984375e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.298324584960938e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-repo took 5.22059965133667s
Availability | SPARQL endpoint availability check for Physico-chemical process took 0.00010323524475097656s
Availability | VoID file availability check for Physico-chemical process took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.2557861804962158s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.02043628692626953s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00019979476928710938s
Believability | Calculation of trust value for Physico-chemical process took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-rex took 4.9148664474487305s
Availability | SPARQL endpoint availability check for RadLex took 4.887580871582031e-05s
Availability | VoID file availability check for RadLex took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for RadLex took 0.26180243492126465s
Reputation | Calculation of the PageRank for RadLex took 0.020729780197143555s
Interlinking | Calculation of Degree of Connection for RadLex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RadLex took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0014986991882324219s
Believability | Calculation of trust value for RadLex took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-rid took 3.9640493392944336s
Availability | SPARQL endpoint availability check for RNA ontology took 9.894371032714844e-05s
Availability | VoID file availability check for RNA ontology took 0.0007328987121582031s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2517588138580322s
Reputation | Calculation of the PageRank for RNA ontology took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005645751953125s
Believability | Calculation of trust value for RNA ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-rnao took 3.797268867492676s
Availability | SPARQL endpoint availability check for Role Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Role Ontology took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2401878833770752s
Reputation | Calculation of the PageRank for Role Ontology took 0.020493745803833008s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00019884109497070312s
Believability | Calculation of trust value for Role Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-roleo took 3.836731195449829s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.26705384254455566s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00017690658569335938s
Believability | Calculation of trust value for Rat Strain Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-rs took 4.053067684173584s
Availability | SPARQL endpoint availability check for RxNORM took 8.58306884765625e-05s
Availability | VoID file availability check for RxNORM took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for RxNORM took 0.22881150245666504s
Reputation | Calculation of the PageRank for RxNORM took 0.020336389541625977s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006184577941894531s
Believability | Calculation of trust value for RxNORM took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-rxnorm took 4.045289516448975s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.363059997558594e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.272890567779541s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010266304016113281s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-sao took 4.1971471309661865s
Availability | SPARQL endpoint availability check for Systems Biology took 6.818771362304688e-05s
Availability | VoID file availability check for Systems Biology took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.24258923530578613s
Reputation | Calculation of the PageRank for Systems Biology took 0.02044844627380371s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.00046539306640625s
Believability | Calculation of trust value for Systems Biology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sbo took 4.0579822063446045s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.2522144317626953s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.021106958389282227s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00011110305786132812s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sbro took 4.058576345443726s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 5.936622619628906e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.2844674587249756s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013394355773925781s
Believability | Calculation of trust value for Sleep Domain Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-sdo took 3.874319553375244s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.8160552978515625e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2598745822906494s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.0203549861907959s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003800392150878906s
Believability | Calculation of trust value for Sample processing and separation techniques took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-sep took 4.69530177116394s
Availability | SPARQL endpoint availability check for Student Health Record took 4.8160552978515625e-05s
Availability | VoID file availability check for Student Health Record took 0.0007336139678955078s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.25793027877807617s
Reputation | Calculation of the PageRank for Student Health Record took 0.020610809326171875s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004572868347167969s
Believability | Calculation of trust value for Student Health Record took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-shr took 4.761548042297363s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0006773471832275391s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.2381281852722168s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.021840810775756836s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012788772583007812s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sio took 5.057639122009277s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.4345855712890625e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0007755756378173828s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.2734498977661133s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020589828491210938s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00019860267639160156s
Believability | Calculation of trust value for Situation-Based Access Control took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-sitbac took 3.8815412521362305s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.267692565917969e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.31729578971862793s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020820140838623047s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 3.0279159545898438e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019109249114990234s
Believability | Calculation of trust value for SNOMED Clinical Terms took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-snomedct took 4.722834825515747s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for SNP-Ontology took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.2609376907348633s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006902217864990234s
Believability | Calculation of trust value for SNP-Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-snpo took 4.05121111869812s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.38690185546875e-05s
Availability | VoID file availability check for Sequence types and features took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.267244815826416s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0006403923034667969s
Believability | Calculation of trust value for Sequence types and features took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-so_x1 took 4.076091527938843s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 8.58306884765625e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.31559133529663086s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.02159738540649414s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.001600503921508789s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-sopharm took 4.579469919204712s
Availability | SPARQL endpoint availability check for SoyOntology took 0.0001049041748046875s
Availability | VoID file availability check for SoyOntology took 0.0007886886596679688s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.2657463550567627s
Reputation | Calculation of the PageRank for SoyOntology took 0.0206301212310791s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00012540817260742188s
Believability | Calculation of trust value for SoyOntology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-soy took 4.16712760925293s
Availability | SPARQL endpoint availability check for Spider Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for Spider Ontology took 0.0007770061492919922s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.2517552375793457s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020538806915283203s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00032210350036621094s
Believability | Calculation of trust value for Spider Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-spd took 4.185996770858765s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0007464885711669922s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.26908254623413086s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.022095203399658203s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00027751922607421875s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-spto took 4.205885171890259s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 8.940696716308594e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.2386031150817871s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.02033209800720215s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004401206970214844s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-sso took 4.165481805801392s
Availability | SPARQL endpoint availability check for Software Ontology took 8.845329284667969e-05s
Availability | VoID file availability check for Software Ontology took 0.0007333755493164062s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.2490246295928955s
Reputation | Calculation of the PageRank for Software Ontology took 0.020453214645385742s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0004038810729980469s
Believability | Calculation of trust value for Software Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-swo took 4.16967511177063s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.410743713378906e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.24991893768310547s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.02337193489074707s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00023412704467773438s
Believability | Calculation of trust value for Tick gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-tads took 3.9540727138519287s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.27873802185058594s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.020706653594970703s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008602142333984375s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-tao took 3.916890859603882s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.267692565917969e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.264815092086792s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.02059149742126465s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 9.369850158691406e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-taxrank took 4.163882255554199s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.291534423828125e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.26545095443725586s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.021004199981689453s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.271766662597656e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-teddy took 4.106659650802612s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.2511279582977295s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020537853240966797s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008165836334228516s
Believability | Calculation of trust value for Time Event Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-teo took 7.266043186187744s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.124641418457031e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.25965332984924316s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020423173904418945s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0003802776336669922s
Believability | Calculation of trust value for Mosquito gross anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-tgma took 4.175248384475708s
Availability | SPARQL endpoint availability check for thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for thesaurus took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for thesaurus took 0.26920652389526367s
Reputation | Calculation of the PageRank for thesaurus took 0.020531654357910156s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.747245788574219e-05s
Believability | Calculation of trust value for thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-thesaurus took 4.138333320617676s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 9.679794311523438e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.26120567321777344s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003387928009033203s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 3.932783603668213s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0008113384246826172s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.24190115928649902s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020844459533691406s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008864402770996094s
Believability | Calculation of trust value for Translational Medicine Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-tmo took 4.104385852813721s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 6.532669067382812e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.2644944190979004s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.02072763442993164s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.0001583099365234375s
Believability | Calculation of trust value for Plant Trait Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-to took 3.87154483795166s
Availability | SPARQL endpoint availability check for TOK_Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.24466681480407715s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020740032196044922s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00018739700317382812s
Believability | Calculation of trust value for TOK_Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-tok took 4.216419458389282s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.482269287109375e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.2586793899536133s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00019788742065429688s
Believability | Calculation of trust value for Teleost taxonomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-tto took 4.334958076477051s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.2507777214050293s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.02036762237548828s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010340213775634766s
Believability | Calculation of trust value for Uber anatomy ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-uberon took 3.8511993885040283s
Availability | SPARQL endpoint availability check for Units Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Units Ontology took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.25914955139160156s
Reputation | Calculation of the PageRank for Units Ontology took 0.02293872833251953s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00022363662719726562s
Believability | Calculation of trust value for Units Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-unitsontology took 4.165022134780884s
Availability | SPARQL endpoint availability check for Units of measurement took 4.2438507080078125e-05s
Availability | VoID file availability check for Units of measurement took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.26490116119384766s
Reputation | Calculation of the PageRank for Units of measurement took 0.02226114273071289s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0008051395416259766s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00028133392333984375s
Believability | Calculation of trust value for Units of measurement took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-uo took 3.8679611682891846s
Availability | SPARQL endpoint availability check for VANDF took 9.942054748535156e-05s
Availability | VoID file availability check for VANDF took 0.00034999847412109375s
Completeness | Calculation of interlinking completeness for VANDF took 0.2816019058227539s
Reputation | Calculation of the PageRank for VANDF took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for VANDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006778240203857422s
Believability | Calculation of trust value for VANDF took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-vandf took 4.086365222930908s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.24545693397521973s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020772933959960938s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004203319549560547s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-vao took 3.9745702743530273s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.2438507080078125e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.24579071998596191s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.02043294906616211s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006194114685058594s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-vhog took 4.087256193161011s
Availability | SPARQL endpoint availability check for VIVO took 8.893013000488281e-05s
Availability | VoID file availability check for VIVO took 0.0007996559143066406s
Completeness | Calculation of interlinking completeness for VIVO took 0.2663142681121826s
Reputation | Calculation of the PageRank for VIVO took 0.02095317840576172s
Interlinking | Calculation of Degree of Connection for VIVO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.00035452842712402344s
Believability | Calculation of trust value for VIVO took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-vivo took 4.085686683654785s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.26534199714660645s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.02045130729675293s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012524127960205078s
Believability | Calculation of trust value for Vaccine Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-vo took 4.15033221244812s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.26046228408813477s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.022638797760009766s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020956993103027344s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-vt took 4.182581424713135s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.1961669921875e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.26560163497924805s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020450353622436523s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0004901885986328125s
Believability | Calculation of trust value for C. elegans gross anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-wbbt took 4.113945484161377s
Availability | SPARQL endpoint availability check for C. elegans development took 4.1484832763671875e-05s
Availability | VoID file availability check for C. elegans development took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.2490828037261963s
Reputation | Calculation of the PageRank for C. elegans development took 0.021612882614135742s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.553794860839844e-05s
Believability | Calculation of trust value for C. elegans development took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-wbls took 4.104909658432007s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 8.821487426757812e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0007474422454833984s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.26584649085998535s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.021265029907226562s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 9.441375732421875e-05s
Believability | Calculation of trust value for C. elegans phenotype took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-wbphenotype took 4.16961669921875s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.4345855712890625e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.25824761390686035s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020267009735107422s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006229877471923828s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-who took 3.9610440731048584s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 6.318092346191406e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2615365982055664s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.00069427490234375s
Believability | Calculation of trust value for Xenopus anatomy and development took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-xao took 4.154559135437012s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.24887537956237793s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020319700241088867s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00024175643920898438s
Believability | Calculation of trust value for Experimental Conditions Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-xco took 4.540789365768433s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.315376281738281e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.24355745315551758s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020266056060791016s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00027871131896972656s
Believability | Calculation of trust value for Yeast phenotypes took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ypo took 4.057360887527466s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.363059997558594e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.27725934982299805s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.02043008804321289s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007450580596923828s
Believability | Calculation of trust value for Zebrafish anatomy and development took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-zfa took 4.070200681686401s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.1961669921875e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.25078320503234863s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020725011825561523s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 6.4373016357421875e-06s
INFO | --- Analysis for Bioportal_link took 3.168098211288452s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.4519162178039551s
Availability | VoID file availability check for BioSamples RDF took 0.0003924369812011719s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.26874256134033203s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.5762786865234375e-05s
Believability | Calculation of trust value for BioSamples RDF took 6.198883056640625e-06s
INFO | --- Analysis for biosamples-rdf took 3.476200580596924s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.09840965270996094s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.2400374412536621s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011134147644042969s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.4543533325195312e-05s
INFO | --- Analysis for bis-linked-data took 2.4262242317199707s
Availability | SPARQL endpoint availability check for Bitzi took 7.104873657226562e-05s
Availability | VoID file availability check for Bitzi took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Bitzi took 0.24727725982666016s
Reputation | Calculation of the PageRank for Bitzi took 0.02059149742126465s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Bitzi took 3.3855438232421875e-05s
Believability | Calculation of trust value for Bitzi took 7.152557373046875e-06s
INFO | --- Analysis for bitzi took 2.884366273880005s
Availability | SPARQL endpoint availability check for BizkaiSense took 4.1484832763671875e-05s
Availability | VoID file availability check for BizkaiSense took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.2447221279144287s
Reputation | Calculation of the PageRank for BizkaiSense took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.0040740966796875e-05s
Believability | Calculation of trust value for BizkaiSense took 7.3909759521484375e-06s
INFO | --- Analysis for bizkaisense took 2.770317316055298s
Availability | SPARQL endpoint availability check for blabla.itemlist took 7.510185241699219e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2520310878753662s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.02050948143005371s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.0994415283203125e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.867813110351562e-06s
INFO | --- Analysis for blabla-itemlist took 2.971942901611328s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.029273986816406e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2568531036376953s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.0204315185546875s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.9087066650390625e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.62939453125e-06s
INFO | --- Analysis for blabla_itemlist took 2.7573037147521973s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 7.081031799316406e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0003407001495361328s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.25661396980285645s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 3.9577484130859375e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for bll-thesaurus took 3.5136351585388184s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.2179679870605469s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0003573894500732422s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.25615620613098145s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.02033519744873047s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.508827209472656e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 8.106231689453125e-06s
INFO | --- Analysis for bluk-bnb took 11.194563865661621s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.3178749084472656s
Availability | VoID file availability check for Thesaurus BNCF took 0.0003628730773925781s
Extra | Recovery of all triples for Thesaurus BNCF took 47.6907262802124s
Performance | Total latancy measurement for Thesaurus BNCF took 0.5710222721099854s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6030287742614746s
Interoperability | New terms check for Thesaurus BNCF took 1.458606243133545s
Versatility | Languages check for Thesaurus BNCF took 6.507690906524658s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.7805674076080322s
Security | Check HTTPS for Thesaurus BNCF took 0.07330083847045898s
Interpretability | RDF structures check for Thesaurus BNCF took 0.11411309242248535s
Versatility | Serialization formats check for Thesaurus BNCF took 0.09144759178161621s
Availability | RDF dump link check for Thesaurus BNCF took 0.09512782096862793s
License | MR license check for Thesaurus BNCF took 0.09037017822265625s
License | HR license check for Thesaurus BNCF took 0.22445416450500488s
Amount of data | Number of property check for Thesaurus BNCF took 0.0967109203338623s
Understandability | Number of label check for Thesaurus BNCF took 0.2349686622619629s
Understandability | URI regex check for Thesaurus BNCF took 0.17711257934570312s
Understandability | Vocabs check for Thesaurus BNCF took 0.09075069427490234s
Verifiability | Authors check for Thesaurus BNCF took 0.09481549263000488s
Verifiability | Publishers check for Thesaurus BNCF took 0.09029459953308105s
Performance | Throughput check for Thesaurus BNCF took 10.56715726852417s
Amount of data | Check the number of entities for Thesaurus BNCF took 0.00013709068298339844s
Verifiability | Contribs. check for Thesaurus BNCF took 0.09519672393798828s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.09769368171691895s
Interlinking | skos check for Thesaurus BNCF took 0.1568741798400879s
Interlinking | skos check for Thesaurus BNCF took 0.15713286399841309s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.10073685646057129s
Currency | Creation date check for Thesaurus BNCF took 0.1914656162261963s
Currency | Modification date check for Thesaurus BNCF took 0.19671392440795898s
Rep.Conc. | URIs length for Thesaurus BNCF took 25.80581307411194s
Interoperability | New vocabularies check for Thesaurus BNCF took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.09870553016662598s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.09382343292236328s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.1355907917022705s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 12.711982250213623s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5066730976104736s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.918388605117798s
Consistency | Disjoint class check for Thesaurus BNCF took 0.09523797035217285s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.7979745864868164s
Consistency | Misplaced classes for Thesaurus BNCF took 6.669437885284424s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 8.417806386947632s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4870514869689941s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.2506260871887207s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.3897266387939453s
Security | Sign check for Thesaurus BNCF took 0.09517669677734375s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 21.90903639793396s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.4417111873626709s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 9.655952453613281e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.1920928955078125e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 6.4373016357421875e-06s
INFO | --- Analysis for bncf-ns took 185.89954829216003s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5409173965454102s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006728172302246094s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.4333837032318115s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.010040044784546s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.067401885986328s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.2247772216796875s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.4036180973053s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.274153232574463s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2906968593597412s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.41860103607177734s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.527625322341919s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.44545602798461914s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5823936462402344s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.464452266693115s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3766343593597412s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8596220016479492s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7790422439575195s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.468120813369751s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5431032180786133s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4166374206542969s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.23832631111145s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.506111145019531e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36275434494018555s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3593559265136719s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.359100341796875s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3584611415863037s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.45685410499572754s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7218880653381348s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3842747211456299s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 17.452966928482056s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.40270352363586426s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35013270378112793s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3326144218444824s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7718136310577393s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030836105346679688s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.028629302978515625s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3655111789703369s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.935730695724487s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.47325754165649414s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.192110300064087s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.5313169956207275s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.061801195144653s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030928850173950195s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5132451057434082s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3536803722381592s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 20.440794706344604s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.9351775646209717s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.021537065505981445s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.937980651855469e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6689300537109375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.33514404296875e-05s
INFO | --- Analysis for bpr took 406.8977255821228s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.458427429199219e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.6732945442199707s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.02288532257080078s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.104873657226562e-05s
Believability | Calculation of trust value for Brazilian Politicians took 8.106231689453125e-06s
INFO | --- Analysis for brazilian-politicians took 4.699889421463013s
Availability | SPARQL endpoint availability check for BrazilianCities took 8.678436279296875e-05s
Availability | VoID file availability check for BrazilianCities took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.2782163619995117s
Reputation | Calculation of the PageRank for BrazilianCities took 0.020392179489135742s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.24249267578125e-05s
Believability | Calculation of trust value for BrazilianCities took 1.2159347534179688e-05s
INFO | --- Analysis for braziliancities took 2.9307963848114014s
Availability | SPARQL endpoint availability check for Bricklink took 4.6587975025177s
Availability | VoID file availability check for Bricklink took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Bricklink took 0.2396707534790039s
Reputation | Calculation of the PageRank for Bricklink took 0.02309393882751465s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.723403930664062e-05s
Believability | Calculation of trust value for Bricklink took 1.2636184692382812e-05s
INFO | --- Analysis for bricklink took 16.5588321685791s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.28978443145752s
Availability | VoID file availability check for British Museum Collection took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.25071191787719727s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.647804260253906e-05s
Believability | Calculation of trust value for British Museum Collection took 1.1682510375976562e-05s
INFO | --- Analysis for british-museum-collection took 73.10530114173889s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 7.43865966796875e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.2479710578918457s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 3.9577484130859375e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.0728836059570312e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.936345100402832s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 9.560585021972656e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.2514641284942627s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.02054738998413086s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 3.0994415283203125e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 1.0728836059570312e-05s
INFO | --- Analysis for bsv took 2.8469252586364746s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.40647435188293457s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006856918334960938s
Extra | Recovery of all triples for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 11.717889785766602s
Performance | Total latancy measurement for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.603217601776123s
Amount of data | Number of triples check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2500934600830078s
Interoperability | New terms check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.884185791015625s
Versatility | Languages check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.802831172943115s
Interpretability | Number of blank nodes check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.8889238834381104s
Interpretability | RDF structures check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1149442195892334s
Versatility | Serialization formats check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11508321762084961s
Availability | RDF dump link check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12008428573608398s
License | MR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1289670467376709s
License | HR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 23.610432624816895s
Amount of data | Number of property check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12156081199645996s
Understandability | Number of label check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.17617058753967285s
Understandability | URI regex check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.23635339736938477s
Understandability | Vocabs check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13070344924926758s
Verifiability | Authors check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11429738998413086s
Verifiability | Publishers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1312558650970459s
Performance | Throughput check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.86797571182251s
Amount of data | Check the number of entities for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.723403930664062e-05s
Verifiability | Contribs. check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1206669807434082s
Interlinking | sameAs chians check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1146078109741211s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12858915328979492s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12079191207885742s
Timeliness | dataset update frequency check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1212000846862793s
Currency | Creation date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2502329349517822s
Currency | Modification date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.25096750259399414s
Rep.Conc. | URIs length for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 11.037088871002197s
Interoperability | New vocabularies check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13186168670654297s
Accuracy | Check Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.14312219619750977s
Accuracy | Check Inverse Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12056589126586914s
Accuracy | Check Empty annotation labels for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.1863322257995605s
Accuracy | Check White space in annotation for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24844598770141602s
Accuracy | Check Datatype consistency for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.540611982345581s
Consistency | Disjoint class check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12225866317749023s
Consistency | Check Misplaced properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.301074504852295s
Consistency | Check Ontology hijacking for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.253250598907471s
Consistency | Check Invalid usage of undefined classes for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.279470443725586s
Consistency | Check Invalid usage of undefined properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.5632998943328857s
Conciseness | Check Extensional conciseness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.7093942165374756s
Security | Sign check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1203157901763916s
Availability | Check URIs Dereferenciability for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3566.156635761261s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.5634510517120361s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.021027088165283203s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.103515625e-05s
Interoperability | Check the re-using of existing vocabs for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.0067901611328125e-06s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.00011563301086425781s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 3682.71191239357s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 8.821487426757812e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.7017936706542969s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.022194862365722656s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0008215904235839844s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 3.62396240234375e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 1.2874603271484375e-05s
INFO | --- Analysis for bund-offener-haushalt took 3.8793840408325195s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 8.606910705566406e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.26952362060546875s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 3.0517578125e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 9.298324584960938e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 3.736870050430298s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.34415316581726074s
Availability | VoID file availability check for business.data.gov.uk took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.2604506015777588s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.0204160213470459s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.054473876953125e-05s
Believability | Calculation of trust value for business.data.gov.uk took 8.58306884765625e-06s
INFO | --- Analysis for business-data-gov-uk took 3.267503499984741s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 1.8223209381103516s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.001127481460571289s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 13.260766506195068s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 4.71491003036499s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 2.2743396759033203s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 2.4091882705688477s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 60.77590250968933s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.36078810691833496s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.18707656860351562s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.47435760498046875s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.36904048919677734s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.29791688919067383s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.518951416015625s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 21.536559104919434s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.38866496086120605s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.7251770496368408s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.8452668190002441s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.3279306888580322s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.5495927333831787s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.5148186683654785s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.98770809173584s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.772445678710938e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.37248897552490234s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.3455812931060791s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.4432363510131836s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.4664316177368164s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.5312449932098389s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 1.124826431274414s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.8623867034912109s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 6.459564447402954s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.5629580020904541s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.7224206924438477s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.6718559265136719s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 2.3361685276031494s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03369569778442383s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.028823137283325195s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.42241454124450684s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.7528293132781982s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.471372127532959s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 3.3481059074401855s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2941253185272217s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.655120849609375s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03213644027709961s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.36057090759277344s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.3229339122772217s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1872.0461702346802s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 1.4856488704681396s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.021541118621826172s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.650520324707031e-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.2636184692382812e-05s
INFO | --- Analysis for BVMC took 2060.5768427848816s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.1484832763671875e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.24927377700805664s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.02024078369140625s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 4.029273986816406e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 1.1682510375976562e-05s
INFO | --- Analysis for cabbage took 3.2958483695983887s
Availability | SPARQL endpoint availability check for cablegate took 1.7300658226013184s
Availability | VoID file availability check for cablegate took 0.0007791519165039062s
Completeness | Calculation of interlinking completeness for cablegate took 0.26064467430114746s
Reputation | Calculation of the PageRank for cablegate took 0.022216320037841797s
Interlinking | Calculation of Degree of Connection for cablegate took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0008976459503173828s
Interlinking | Calculation of Clustering coefficient for cablegate took 8.344650268554688e-05s
Believability | Calculation of trust value for cablegate took 1.239776611328125e-05s
INFO | --- Analysis for cablegate took 16.922548532485962s
Availability | SPARQL endpoint availability check for Calames took 4.2438507080078125e-05s
Availability | VoID file availability check for Calames took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Calames took 0.2517282962799072s
Reputation | Calculation of the PageRank for Calames took 0.020850658416748047s
Interlinking | Calculation of Degree of Connection for Calames took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Calames took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Calames took 3.695487976074219e-05s
Believability | Calculation of trust value for Calames took 1.1920928955078125e-05s
INFO | --- Analysis for calames took 3.907158613204956s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.4277160167694092s
Availability | VoID file availability check for CaLiGraph took 0.0004894733428955078s
Extra | Recovery of all triples for CaLiGraph took 1.160581350326538s
Performance | Total latancy measurement for CaLiGraph took 1.162010908126831s
Amount of data | Number of triples check for CaLiGraph took 12.451698064804077s
Interoperability | New terms check for CaLiGraph took 1.9303886890411377s
Versatility | Languages check for CaLiGraph took 60.30357336997986s
Interpretability | Number of blank nodes check for CaLiGraph took 0.2453310489654541s
Security | Check HTTPS for CaLiGraph took 0.15127801895141602s
Interpretability | RDF structures check for CaLiGraph took 0.2586379051208496s
Versatility | Serialization formats check for CaLiGraph took 0.24940013885498047s
Availability | RDF dump link check for CaLiGraph took 0.24991774559020996s
License | MR license check for CaLiGraph took 0.2800588607788086s
License | HR license check for CaLiGraph took 60.2851939201355s
Amount of data | Number of property check for CaLiGraph took 0.22102952003479004s
Understandability | Number of label check for CaLiGraph took 3.2124578952789307s
Understandability | URI regex check for CaLiGraph took 0.5497093200683594s
Understandability | Vocabs check for CaLiGraph took 0.33202266693115234s
Verifiability | Authors check for CaLiGraph took 0.23416876792907715s
Verifiability | Publishers check for CaLiGraph took 0.28966450691223145s
Performance | Throughput check for CaLiGraph took 11.4191255569458s
Amount of data | Check the number of entities for CaLiGraph took 0.015915393829345703s
Verifiability | Contribs. check for CaLiGraph took 0.24780583381652832s
Interlinking | sameAs chians check for CaLiGraph took 0.6835494041442871s
Interlinking | skos check for CaLiGraph took 0.3342142105102539s
Interlinking | skos check for CaLiGraph took 0.2666318416595459s
Timeliness | dataset update frequency check for CaLiGraph took 0.3224046230316162s
Currency | Creation date check for CaLiGraph took 0.49686169624328613s
Currency | Modification date check for CaLiGraph took 0.4975852966308594s
Rep.Conc. | URIs length for CaLiGraph took 61.06387376785278s
Interoperability | New vocabularies check for CaLiGraph took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.25623250007629395s
Accuracy | Check Functional Property for CaLiGraph took 0.2837390899658203s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2960069179534912s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5568346977233887s
Accuracy | Check White space in annotation for CaLiGraph took 0.026287317276000977s
Accuracy | Check Datatype consistency for CaLiGraph took 0.05030369758605957s
Consistency | Disjoint class check for CaLiGraph took 0.29137277603149414s
Consistency | Check Misplaced properties for CaLiGraph took 61.05220627784729s
Consistency | Misplaced classes for CaLiGraph took 0.4625661373138428s
Consistency | Check Ontology hijacking for CaLiGraph took 2.2048604488372803s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2929224967956543s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.59665012359619s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03277325630187988s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.44533205032348633s
Security | Sign check for CaLiGraph took 0.3157188892364502s
Availability | Check URIs Dereferenciability for CaLiGraph took 18.49883246421814s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.35507893562316895s
Reputation | Calculation of the PageRank for CaLiGraph took 0.021221637725830078s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.6689300537109375e-06s
Believability | Calculation of trust value for CaLiGraph took 1.3113021850585938e-05s
INFO | --- Analysis for CaLiGraph took 1496.3445184230804s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.22905516624450684s
Availability | VoID file availability check for CaLiGraph took 0.0006849765777587891s
Extra | Recovery of all triples for CaLiGraph took 1.1903510093688965s
Performance | Total latancy measurement for CaLiGraph took 1.1006147861480713s
Amount of data | Number of triples check for CaLiGraph took 12.420356035232544s
Interoperability | New terms check for CaLiGraph took 1.887092113494873s
Versatility | Languages check for CaLiGraph took 60.2786431312561s
Interpretability | Number of blank nodes check for CaLiGraph took 0.2208864688873291s
Security | Check HTTPS for CaLiGraph took 0.17965292930603027s
Interpretability | RDF structures check for CaLiGraph took 0.23389959335327148s
Versatility | Serialization formats check for CaLiGraph took 0.23122644424438477s
Availability | RDF dump link check for CaLiGraph took 0.23638081550598145s
License | MR license check for CaLiGraph took 0.24498701095581055s
License | HR license check for CaLiGraph took 60.357943534851074s
Amount of data | Number of property check for CaLiGraph took 0.24535226821899414s
Understandability | Number of label check for CaLiGraph took 3.090385913848877s
Understandability | URI regex check for CaLiGraph took 0.45891284942626953s
Understandability | Vocabs check for CaLiGraph took 0.22602295875549316s
Verifiability | Authors check for CaLiGraph took 0.2386622428894043s
Verifiability | Publishers check for CaLiGraph took 0.23603081703186035s
Performance | Throughput check for CaLiGraph took 11.536048889160156s
Amount of data | Check the number of entities for CaLiGraph took 0.01352548599243164s
Verifiability | Contribs. check for CaLiGraph took 0.22660207748413086s
Interlinking | sameAs chians check for CaLiGraph took 0.6437032222747803s
Interlinking | skos check for CaLiGraph took 0.24483323097229004s
Interlinking | skos check for CaLiGraph took 0.2343430519104004s
Timeliness | dataset update frequency check for CaLiGraph took 0.2551534175872803s
Currency | Creation date check for CaLiGraph took 0.544485330581665s
Currency | Modification date check for CaLiGraph took 0.5069317817687988s
Rep.Conc. | URIs length for CaLiGraph took 60.997387170791626s
Interoperability | New vocabularies check for CaLiGraph took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.22881579399108887s
Accuracy | Check Functional Property for CaLiGraph took 0.2324681282043457s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.22972822189331055s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5705618858337402s
Accuracy | Check White space in annotation for CaLiGraph took 0.027053356170654297s
Accuracy | Check Datatype consistency for CaLiGraph took 0.0505986213684082s
Consistency | Disjoint class check for CaLiGraph took 0.24539589881896973s
Consistency | Check Misplaced properties for CaLiGraph took 60.882384300231934s
Consistency | Misplaced classes for CaLiGraph took 0.571890115737915s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9570059776306152s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.281686782836914s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.52621102333069s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.029610157012939453s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4483208656311035s
Security | Sign check for CaLiGraph took 0.23079562187194824s
Availability | Check URIs Dereferenciability for CaLiGraph took 18.610113382339478s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.9809744358062744s
Reputation | Calculation of the PageRank for CaLiGraph took 0.022518157958984375s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 9.179115295410156e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.1920928955078125e-06s
Believability | Calculation of trust value for CaLiGraph took 1.0967254638671875e-05s
INFO | --- Analysis for caligraph took 1498.6897814273834s
Availability | SPARQL endpoint availability check for can-link took 6.771087646484375e-05s
Availability | VoID file availability check for can-link took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for can-link took 0.6989984512329102s
Reputation | Calculation of the PageRank for can-link took 0.02118515968322754s
Interlinking | Calculation of Degree of Connection for can-link took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for can-link took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for can-link took 3.5762786865234375e-05s
Believability | Calculation of trust value for can-link took 1.2636184692382812e-05s
INFO | --- Analysis for can-link took 5.545473337173462s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.016031742095947266s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.25343894958496094s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020503520965576172s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.0013580322265625e-05s
INFO | --- Analysis for cap-italy-rdf took 3.203350067138672s
Availability | SPARQL endpoint availability check for person took 4.458427429199219e-05s
Availability | VoID file availability check for person took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for person took 0.25110363960266113s
Reputation | Calculation of the PageRank for person took 0.021715402603149414s
Interlinking | Calculation of Degree of Connection for person took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for person took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for person took 2.956390380859375e-05s
Believability | Calculation of trust value for person took 1.1444091796875e-05s
INFO | --- Analysis for card took 3.174038887023926s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.3392181396484375e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.24832582473754883s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020777225494384766s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.0251998901367188e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 2.8492207527160645s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.4345855712890625e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.2529919147491455s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.02076435089111328s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.0517578125e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 1.049041748046875e-05s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 3.2379324436187744s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.7296435832977295s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.00048089027404785156s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 115.47791790962219s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 0.9169154167175293s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 10.514203071594238s
Interoperability | New terms check for Norway catch records dataset @PSNC took 14.500123739242554s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.21494483947754s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 2.3337974548339844s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.31645822525024414s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 8.189343929290771s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.31000661849975586s
License | MR license check for Norway catch records dataset @PSNC took 0.7508440017700195s
License | HR license check for Norway catch records dataset @PSNC took 300.2361476421356s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.18587970733642578s
Understandability | Number of label check for Norway catch records dataset @PSNC took 1.510249376296997s
Understandability | URI regex check for Norway catch records dataset @PSNC took 0.899996280670166s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.4876673221588135s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.1840670108795166s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.24465370178222656s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.694008111953735s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 8.535385131835938e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.1806502342224121s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.18294858932495117s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4970715045928955s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4163210391998291s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 4.213665962219238s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.4720151424407959s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.24211764335632324s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 149.76591992378235s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.20514941215515137s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.24121880531311035s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.3908963203430176s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 39.902503967285156s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.6491127014160156s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.6153619289398193s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.20644831657409668s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 87.35261511802673s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.335272073745728s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 37.73953986167908s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.394012451171875s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 88.61210131645203s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.6728270053863525s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.5690009593963623s
Security | Sign check for Norway catch records dataset @PSNC took 1.0346264839172363s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 20.22988986968994s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.5334935188293457s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.026259422302246094s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 5.3882598876953125e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 7.62939453125e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2293.156773328781s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.2438507080078125e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.29024529457092285s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020972251892089844s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0001087188720703125s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.049041748046875e-05s
INFO | --- Analysis for ce4r took 37.93258500099182s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.447948694229126s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005500316619873047s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.0381050109863281s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.7664356231689453s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.31783151626586914s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6378669738769531s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.14726233482361s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1711890697479248s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.31295037269592285s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.158921480178833s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16354799270629883s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24350881576538086s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3118882179260254s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1571788787841797s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.28319692611694336s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3306872844696045s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1668252944946289s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20833683013916016s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18230438232421875s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.711100578308105s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.557868957519531e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2797994613647461s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4328024387359619s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 1.0443475246429443s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15787887573242188s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17775368690490723s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.7092118263244629s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4839198589324951s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.100137710571289s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17679977416992188s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.3161437511444092s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.31772685050964355s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6428356170654297s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.028769493103027344s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.02759408950805664s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4329843521118164s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.2016456127166748s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.887420415878296s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.2457842826843262s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.5069866180419922s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.029987812042236328s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.21858453750610352s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17118525505065918s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2747.3695769309998s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.8129339218139648s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020761966705322266s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.57763671875e-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.33514404296875e-05s
INFO | --- Analysis for ceo took 2875.438798427582s
Availability | SPARQL endpoint availability check for Charging Stations took 4.1484832763671875e-05s
Availability | VoID file availability check for Charging Stations took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.7116384506225586s
Reputation | Calculation of the PageRank for Charging Stations took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.24249267578125e-05s
Believability | Calculation of trust value for Charging Stations took 1.239776611328125e-05s
INFO | --- Analysis for charging-stations took 4.08945107460022s
Availability | SPARQL endpoint availability check for Chat Game corpus took 8.96453857421875e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0006976127624511719s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.6843380928039551s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020604848861694336s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.5762786865234375e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.0967254638671875e-05s
INFO | --- Analysis for chat-game-corpus took 13.022915601730347s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 8.249282836914062e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.25448036193847656s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.0207369327545166s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.790855407714844e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 1.0251998901367188e-05s
INFO | --- Analysis for chebi took 2.8166749477386475s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 8.58306884765625e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0007848739624023438s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.7802712917327881s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.022222518920898438s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 6.580352783203125e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.2874603271484375e-05s
INFO | --- Analysis for chem2bio2rdf took 136.1710546016693s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.6907494068145752s
Availability | VoID file availability check for ChEMBL RDF took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.26198863983154297s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020734548568725586s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.316734313964844e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.1682510375976562e-05s
INFO | --- Analysis for chembl-rdf took 4.623400926589966s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.0842838287353516s
Availability | VoID file availability check for chemdb  dataset took 0.0004749298095703125s
Extra | Recovery of all triples for chemdb  dataset took 4.971969366073608s
Performance | Total latancy measurement for chemdb  dataset took 2.5000171661376953s
Amount of data | Number of triples check for chemdb  dataset took 0.5255355834960938s
Interoperability | New terms check for chemdb  dataset took 3.4037325382232666s
Versatility | Languages check for chemdb  dataset took 29.767281770706177s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.49395251274108887s
Interpretability | RDF structures check for chemdb  dataset took 1.854787826538086s
Versatility | Serialization formats check for chemdb  dataset took 1.439439296722412s
Availability | RDF dump link check for chemdb  dataset took 0.8204967975616455s
License | MR license check for chemdb  dataset took 4.293375492095947s
License | HR license check for chemdb  dataset took 4.594242334365845s
Amount of data | Number of property check for chemdb  dataset took 0.5046963691711426s
Understandability | Number of label check for chemdb  dataset took 5.102691173553467s
Understandability | URI regex check for chemdb  dataset took 1.9419829845428467s
Understandability | Vocabs check for chemdb  dataset took 0.8414194583892822s
Verifiability | Authors check for chemdb  dataset took 1.1498494148254395s
Verifiability | Publishers check for chemdb  dataset took 0.8101053237915039s
Performance | Throughput check for chemdb  dataset took 13.493979454040527s
Amount of data | Check the number of entities for chemdb  dataset took 6.914138793945312e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.81465744972229s
Interlinking | sameAs chians check for chemdb  dataset took 1.118117094039917s
Interlinking | skos check for chemdb  dataset took 2.0091583728790283s
Interlinking | skos check for chemdb  dataset took 0.48964762687683105s
Timeliness | dataset update frequency check for chemdb  dataset took 1.149580955505371s
Currency | Creation date check for chemdb  dataset took 1.310319185256958s
Currency | Modification date check for chemdb  dataset took 1.0002086162567139s
Rep.Conc. | URIs length for chemdb  dataset took 2.928818702697754s
Interoperability | New vocabularies check for chemdb  dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.4952101707458496s
Accuracy | Check Functional Property for chemdb  dataset took 0.8496336936950684s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.7744574546813965s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.189889430999756s
Accuracy | Check White space in annotation for chemdb  dataset took 0.030187368392944336s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.0336306095123291s
Consistency | Disjoint class check for chemdb  dataset took 0.8091611862182617s
Consistency | Check Misplaced properties for chemdb  dataset took 1.1848158836364746s
Consistency | Misplaced classes for chemdb  dataset took 0.5852751731872559s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.426626443862915s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.307314157485962s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 1.9901156425476074s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.03509044647216797s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.49996066093444824s
Security | Sign check for chemdb  dataset took 1.8331456184387207s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2535.371180534363s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.3311338424682617s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.021304607391357422s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.939338684082031e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb  dataset took 1.2874603271484375e-05s
INFO | --- Analysis for chemdb-basicInfo took 4694.539186477661s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5062625408172607s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.00027561187744140625s
Extra | Recovery of all triples for chemdb estimated properties dataset took 19.028066635131836s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.484994649887085s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5232236385345459s
Interoperability | New terms check for chemdb estimated properties dataset took 3.849909543991089s
Versatility | Languages check for chemdb estimated properties dataset took 28.01221489906311s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5088229179382324s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.49883151054382324s
Versatility | Serialization formats check for chemdb estimated properties dataset took 1.481320858001709s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.8204865455627441s
License | MR license check for chemdb estimated properties dataset took 2.9003725051879883s
License | HR license check for chemdb estimated properties dataset took 4.253371715545654s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5055181980133057s
Understandability | Number of label check for chemdb estimated properties dataset took 4.778351306915283s
Understandability | URI regex check for chemdb estimated properties dataset took 1.908482551574707s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.8172123432159424s
Verifiability | Authors check for chemdb estimated properties dataset took 1.174943208694458s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.8041088581085205s
Performance | Throughput check for chemdb estimated properties dataset took 14.337416648864746s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 9.703636169433594e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.694732666015625s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 1.1231181621551514s
Interlinking | skos check for chemdb estimated properties dataset took 1.8747217655181885s
Interlinking | skos check for chemdb estimated properties dataset took 0.5007767677307129s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 1.14853835105896s
Currency | Creation date check for chemdb estimated properties dataset took 1.3085706233978271s
Currency | Modification date check for chemdb estimated properties dataset took 0.9885168075561523s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 3.366272211074829s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.4968996047973633s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.7789082527160645s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.7677640914916992s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 2.9676146507263184s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.03076791763305664s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03385663032531738s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.7977950572967529s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.1964540481567383s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.5793087482452393s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 3.825514554977417s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.261183738708496s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 1.9529602527618408s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03215193748474121s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.5038645267486572s
Security | Sign check for chemdb estimated properties dataset took 1.8518846035003662s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2528.467089653015s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 1.6329782009124756s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.02114081382751465s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 5.412101745605469e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.239776611328125e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 4629.899613380432s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5092794895172119s
Availability | VoID file availability check for chemdb phase transition dataset took 0.00046443939208984375s
Extra | Recovery of all triples for chemdb phase transition dataset took 9.149262428283691s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.4844141006469727s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5252695083618164s
Interoperability | New terms check for chemdb phase transition dataset took 3.892580986022949s
Versatility | Languages check for chemdb phase transition dataset took 28.456565380096436s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.507072925567627s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5022792816162109s
Versatility | Serialization formats check for chemdb phase transition dataset took 1.4820990562438965s
Availability | RDF dump link check for chemdb phase transition dataset took 0.8329653739929199s
License | MR license check for chemdb phase transition dataset took 3.08309268951416s
License | HR license check for chemdb phase transition dataset took 4.137880802154541s
Amount of data | Number of property check for chemdb phase transition dataset took 0.4941895008087158s
Understandability | Number of label check for chemdb phase transition dataset took 5.154943227767944s
Understandability | URI regex check for chemdb phase transition dataset took 1.9755041599273682s
Understandability | Vocabs check for chemdb phase transition dataset took 0.8104021549224854s
Verifiability | Authors check for chemdb phase transition dataset took 1.1777534484863281s
Verifiability | Publishers check for chemdb phase transition dataset took 0.8359496593475342s
Performance | Throughput check for chemdb phase transition dataset took 13.918596744537354s
Amount of data | Check the number of entities for chemdb phase transition dataset took 6.651878356933594e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.6785569190979004s
Interlinking | sameAs chians check for chemdb phase transition dataset took 1.1144156455993652s
Interlinking | skos check for chemdb phase transition dataset took 1.9759418964385986s
Interlinking | skos check for chemdb phase transition dataset took 0.5054998397827148s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 1.1026642322540283s
Currency | Creation date check for chemdb phase transition dataset took 1.338205337524414s
Currency | Modification date check for chemdb phase transition dataset took 0.9871106147766113s
Rep.Conc. | URIs length for chemdb phase transition dataset took 3.388051986694336s
Interoperability | New vocabularies check for chemdb phase transition dataset took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.5015547275543213s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.7682552337646484s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.7853212356567383s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 3.160867214202881s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.030272960662841797s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03363204002380371s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.8187906742095947s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2059402465820312s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.5817129611968994s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 3.868471622467041s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.2440450191497803s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 1.9513356685638428s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.03227591514587402s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.49843287467956543s
Security | Sign check for chemdb phase transition dataset took 2.6332345008850098s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2534.4537346363068s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 1.1008358001708984s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.021799325942993164s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 6.198883056640625e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 5.53131103515625e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.239776611328125e-05s
INFO | --- Analysis for chemdb-phaseTransition took 4612.5628271102905s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.49671268463134766s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0006089210510253906s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 8.976158618927002s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.484926462173462s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5149450302124023s
Interoperability | New terms check for chemdb thermochemistry dataset took 3.8334579467773438s
Versatility | Languages check for chemdb thermochemistry dataset took 30.120822191238403s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.49294376373291016s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5113954544067383s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 1.4875688552856445s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.838292121887207s
License | MR license check for chemdb thermochemistry dataset took 3.4371087551116943s
License | HR license check for chemdb thermochemistry dataset took 4.336420059204102s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.48511362075805664s
Understandability | Number of label check for chemdb thermochemistry dataset took 6.138291597366333s
Understandability | URI regex check for chemdb thermochemistry dataset took 2.086603879928589s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.8647904396057129s
Verifiability | Authors check for chemdb thermochemistry dataset took 1.217010259628296s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.8608989715576172s
Performance | Throughput check for chemdb thermochemistry dataset took 14.29116415977478s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 4.38690185546875e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.8855481147766113s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 1.2830710411071777s
Interlinking | skos check for chemdb thermochemistry dataset took 2.4235198497772217s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5068962574005127s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 1.2638418674468994s
Currency | Creation date check for chemdb thermochemistry dataset took 1.362870454788208s
Currency | Modification date check for chemdb thermochemistry dataset took 0.9817020893096924s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.416923999786377s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.4889183044433594s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.8113658428192139s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.8089475631713867s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 2.8637592792510986s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.030258893966674805s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03302621841430664s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.9102010726928711s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2064313888549805s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.5832149982452393s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 3.8679659366607666s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.249739170074463s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 1.9883761405944824s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.0323028564453125s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.49831652641296387s
Security | Sign check for chemdb thermochemistry dataset took 2.0656137466430664s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2519.9901971817017s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 1.2850043773651123s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.02123856544494629s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.437301635742188e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 1.6450881958007812e-05s
INFO | --- Analysis for chemdb-thermochemistry took 4597.276171684265s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 9.012222290039062e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.7386987209320068s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.022084474563598633s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.075599670410156e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.049041748046875e-05s
INFO | --- Analysis for chempedia-rdf took 10.001388549804688s
Availability | SPARQL endpoint availability check for Chiman Maru took 5.435943603515625e-05s
Availability | VoID file availability check for Chiman Maru took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.2599005699157715s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 2.956390380859375e-05s
Believability | Calculation of trust value for Chiman Maru took 1.2159347534179688e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 2.7378365993499756s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.33249855041504s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.7182300090789795s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.02285480499267578s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 4.506111145019531e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 797.3431105613708s
Availability | SPARQL endpoint availability check for Chronicling America took 6.628036499023438e-05s
Availability | VoID file availability check for Chronicling America took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.260101318359375s
Reputation | Calculation of the PageRank for Chronicling America took 0.021276235580444336s
Interlinking | Calculation of Degree of Connection for Chronicling America took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0017447471618652344s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.0002474784851074219s
Believability | Calculation of trust value for Chronicling America took 1.1682510375976562e-05s
INFO | --- Analysis for chronicling-america took 8.397746086120605s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 1.0780742168426514s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0005719661712646484s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 82.48957180976868s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.4115915298461914s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.5681943893432617s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.2408745288848877s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.4364557266235352s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.5264878273010254s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.26285433769226074s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.2663695812225342s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 8.710816144943237s
License | MR license check for Cultural Heritage Thesaurus took 0.2928774356842041s
License | HR license check for Cultural Heritage Thesaurus took 0.3343026638031006s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.3038637638092041s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.3359849452972412s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5757274627685547s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.28095149993896484s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.289752721786499s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.2693912982940674s
Performance | Throughput check for Cultural Heritage Thesaurus took 10.977935791015625s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 7.05718994140625e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.29324817657470703s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.25420546531677246s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.30132603645324707s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.29262447357177734s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.2859518527984619s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.5539200305938721s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.580777645111084s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 28.116771936416626s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 2.273170232772827s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.2565476894378662s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.27228212356567383s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.2633984088897705s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 5.743583917617798s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.21982526779174805s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.3115682601928711s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 0.9259848594665527s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.30730533599853516s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.207386016845703s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 1.9965908527374268s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00013589859008789062s
Security | Sign check for Cultural Heritage Thesaurus took 0.2504994869232178s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 385.06728196144104s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.8893790245056152s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.9337828159332275s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0009038448333740234s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00011658668518066406s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.6508951187133789s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for cht took 573.0556907653809s
Availability | SPARQL endpoint availability check for ciard-ring took 4.315376281738281e-05s
Availability | VoID file availability check for ciard-ring took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.6756777763366699s
Reputation | Calculation of the PageRank for ciard-ring took 0.020367860794067383s
Interlinking | Calculation of Degree of Connection for ciard-ring took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.839897155761719e-05s
Believability | Calculation of trust value for ciard-ring took 1.1920928955078125e-05s
INFO | --- Analysis for ciard-ring took 12.77161693572998s
Availability | SPARQL endpoint availability check for Cine Figure took 4.839897155761719e-05s
Availability | VoID file availability check for Cine Figure took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.6858024597167969s
Reputation | Calculation of the PageRank for Cine Figure took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.172325134277344e-05s
Believability | Calculation of trust value for Cine Figure took 1.1205673217773438e-05s
INFO | --- Analysis for Cine_Figure took 2.7651052474975586s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 6.660096883773804s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.25426292419433594s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020462989807128906s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.3392181396484375e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.1444091796875e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 22.637106895446777s
Availability | SPARQL endpoint availability check for CIPFA took 4.291534423828125e-05s
Availability | VoID file availability check for CIPFA took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for CIPFA took 0.2515900135040283s
Reputation | Calculation of the PageRank for CIPFA took 0.020583629608154297s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.409385681152344e-05s
Believability | Calculation of trust value for CIPFA took 8.58306884765625e-06s
INFO | --- Analysis for cipfa took 2.637378454208374s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.04152035713196s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.2623410224914551s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.02097010612487793s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00039076805114746094s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.049041748046875e-05s
INFO | --- Analysis for ckan took 262.50976824760437s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.6595525741577148s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.3029301166534424s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.0013580322265625e-05s
INFO | --- Analysis for CLaSSES took 5.921342134475708s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 7.033348083496094e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.25238800048828125s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.02082347869873047s
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.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.361701965332031e-05s
Believability | Calculation of trust value for Temples of the Classical World took 9.5367431640625e-06s
INFO | --- Analysis for classical_temples took 3.582582712173462s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.8415887355804443s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.2642369270324707s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.021712779998779297s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.726119995117188e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 9.298324584960938e-06s
INFO | --- Analysis for clean-energy-data-reegle took 11.45311975479126s
Availability | SPARQL endpoint availability check for CLLD-afbo took 8.869171142578125e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.2544901371002197s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.02073359489440918s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.796287536621094e-05s
Believability | Calculation of trust value for CLLD-afbo took 1.2874603271484375e-05s
INFO | --- Analysis for clld-afbo took 3.966696262359619s
Availability | SPARQL endpoint availability check for CLLD-APICS took 8.869171142578125e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.26772570610046387s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020576000213623047s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.987022399902344e-05s
Believability | Calculation of trust value for CLLD-APICS took 1.239776611328125e-05s
INFO | --- Analysis for clld-apics took 5.156996965408325s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.601478576660156e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.25681543350219727s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020909547805786133s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 4.1961669921875e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 1.0967254638671875e-05s
INFO | --- Analysis for clld-ewave took 4.33318829536438s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 5.269050598144531e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.26009678840637207s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010395050048828125s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.1682510375976562e-05s
INFO | --- Analysis for clld-glottolog took 3.4691662788391113s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.553794860839844e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.2738959789276123s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 7.772445678710938e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 9.775161743164062e-06s
INFO | --- Analysis for clld-phoible took 3.837693691253662s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 8.606910705566406e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.25401997566223145s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.02127838134765625s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.772445678710938e-05s
Believability | Calculation of trust value for CLLD-SAILS took 1.1682510375976562e-05s
INFO | --- Analysis for clld-sails took 3.5480740070343018s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.458427429199219e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.2669944763183594s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.022724628448486328s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.416175842285156e-05s
Believability | Calculation of trust value for CLLD-WALS took 1.2159347534179688e-05s
INFO | --- Analysis for clld-wals took 3.7558865547180176s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.38690185546875e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.26668763160705566s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.0220944881439209s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.724761962890625e-05s
Believability | Calculation of trust value for CLLD-WOLD took 6.4373016357421875e-06s
INFO | --- Analysis for clld-wold took 3.4569239616394043s
Availability | SPARQL endpoint availability check for COD inventory took 4.315376281738281e-05s
Availability | VoID file availability check for COD inventory took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for COD inventory took 0.2768993377685547s
Reputation | Calculation of the PageRank for COD inventory took 0.02074718475341797s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.409385681152344e-05s
Believability | Calculation of trust value for COD inventory took 1.1444091796875e-05s
INFO | --- Analysis for cod-inventory took 2.990210771560669s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.1833019256591797s
Availability | VoID file availability check for Cooperation Databank took 0.00022029876708984375s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.28621506690979004s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.981590270996094e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.049041748046875e-05s
INFO | --- Analysis for CoDa took 2.556699752807617s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.267692565917969e-05s
Availability | VoID file availability check for CODE Endpoint took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.28419971466064453s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.022474288940429688s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.361701965332031e-05s
Believability | Calculation of trust value for CODE Endpoint took 1.1920928955078125e-05s
INFO | --- Analysis for code-endpoint took 2.915755033493042s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 1.3613052368164062s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.2602956295013428s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.020871877670288086s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.4809112548828125e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 9.059906005859375e-06s
INFO | --- Analysis for coins-openuplabs took 3.7404019832611084s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.404170036315918s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.24840784072875977s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.021109819412231445s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0008480548858642578s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 9.274482727050781e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 1.1920928955078125e-05s
INFO | --- Analysis for CoLChina_sp2000 took 7.075061321258545s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.08474373817443848s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.24372577667236328s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.02105236053466797s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.1484832763671875e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.1444091796875e-05s
INFO | --- Analysis for colinda took 2.4626951217651367s
Availability | SPARQL endpoint availability check for CN  2012 took 25.676424026489258s
Availability | VoID file availability check for CN  2012 took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.26590490341186523s
Reputation | Calculation of the PageRank for CN  2012 took 0.022599220275878906s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.220008850097656e-05s
Believability | Calculation of trust value for CN  2012 took 9.5367431640625e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 124.83606719970703s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 8.487701416015625e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.2572364807128906s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.02064657211303711s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.24249267578125e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 1.1205673217773438e-05s
INFO | --- Analysis for comments-on-literature-in-literature took 2.8370399475097656s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 3.886222839355469e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.24628138542175293s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.02277231216430664s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 3.075599670410156e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 1.0013580322265625e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 2.817305564880371s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 8.559226989746094e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.2514355182647705s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.1948089599609375e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 9.775161743164062e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 2.8339927196502686s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.0531158447265625e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.2641274929046631s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.02088022232055664s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 2.9802322387695312e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 1.0013580322265625e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.8026554584503174s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 8.058547973632812e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.25338244438171387s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.0279159545898438e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 1.0013580322265625e-05s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.7858405113220215s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.5060837268829346s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0011768341064453125s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.2567470073699951s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.022096872329711914s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.1444091796875e-05s
INFO | --- Analysis for CompHistSem took 3.8846678733825684s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 2.1624515056610107s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.2515740394592285s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.020524978637695312s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.62396240234375e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 2.2411346435546875e-05s
INFO | --- Analysis for comsode-d3-2 took 7.589672088623047s
Availability | SPARQL endpoint availability check for ConceptNet took 7.128715515136719e-05s
Availability | VoID file availability check for ConceptNet took 0.0011546611785888672s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.23278284072875977s
Reputation | Calculation of the PageRank for ConceptNet took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for ConceptNet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 3.1948089599609375e-05s
Believability | Calculation of trust value for ConceptNet took 1.1444091796875e-05s
INFO | --- Analysis for conceptnet took 2.787599802017212s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.363059997558594e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.24861955642700195s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020558595657348633s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.153915405273438e-05s
Believability | Calculation of trust value for 2011 US Congress People took 8.58306884765625e-06s
INFO | --- Analysis for congresspeople took 2.792775869369507s
Availability | SPARQL endpoint availability check for MIMO took 0.29112911224365234s
Availability | VoID file availability check for MIMO took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for MIMO took 0.2855091094970703s
Reputation | Calculation of the PageRank for MIMO took 0.02202129364013672s
Interlinking | Calculation of Degree of Connection for MIMO took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.1920928955078125e-05s
Believability | Calculation of trust value for MIMO took 1.1920928955078125e-05s
INFO | --- Analysis for CONNECTED took 3.851139783859253s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.2712979316711426s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.022835969924926758s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 3.147125244140625e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.783724069595337s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 8.320808410644531e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.24773287773132324s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.020941495895385742s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 3.218650817871094e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.1920928955078125e-05s
INFO | --- Analysis for copac-library-catalogue took 2.7927632331848145s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.458427429199219e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.24206161499023438s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020613908767700195s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.1948089599609375e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.0728836059570312e-05s
INFO | --- Analysis for Copyright_Free_Music took 3.0771982669830322s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.410743713378906e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.2615838050842285s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 6.532669067382812e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.0728836059570312e-05s
INFO | --- Analysis for copyrighttermbank took 33.84674549102783s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.246579885482788s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0006253719329833984s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.23673605918884277s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020344257354736328s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.838539123535156e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.1920928955078125e-05s
INFO | --- Analysis for core took 6.773833513259888s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 1.1339037418365479s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0005521774291992188s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 95.6165759563446s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.9398937225341797s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 9.359517812728882s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.138128280639648s
Versatility | Languages check for Corine linked dataset @PSNC took 300.2070355415344s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 1.8845102787017822s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.249863862991333s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 8.160173654556274s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.32557129859924316s
License | MR license check for Corine linked dataset @PSNC took 0.7380731105804443s
License | HR license check for Corine linked dataset @PSNC took 300.1919221878052s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.20474481582641602s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.6500637531280518s
Understandability | URI regex check for Corine linked dataset @PSNC took 0.9696774482727051s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.49508213996887207s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.20862627029418945s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.2581784725189209s
Performance | Throughput check for Corine linked dataset @PSNC took 11.449012279510498s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 6.723403930664062e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.20009112358093262s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.1815948486328125s
Interlinking | skos check for Corine linked dataset @PSNC took 0.43161654472351074s
Interlinking | skos check for Corine linked dataset @PSNC took 0.40618395805358887s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 4.756634473800659s
Currency | Creation date check for Corine linked dataset @PSNC took 0.4581634998321533s
Currency | Modification date check for Corine linked dataset @PSNC took 0.240952730178833s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 161.43100786209106s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.21222424507141113s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.3572218418121338s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.4046175479888916s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 37.524444818496704s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.673400402069092s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.639512062072754s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.19344091415405273s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 87.89667415618896s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.46664023399353s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 37.30111861228943s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.3415100574493408s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 89.3400547504425s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.6850574016571045s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.5785741806030273s
Security | Sign check for Corine linked dataset @PSNC took 0.7940413951873779s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 15.559247970581055s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 1.4101710319519043s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.021471023559570312s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.0994415283203125e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 5.0067901611328125e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 7.62939453125e-06s
INFO | --- Analysis for Corine_linked_dataset took 2273.040150165558s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 8.893013000488281e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.2497997283935547s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.02113056182861328s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.0994415283203125e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.0728836059570312e-05s
INFO | --- Analysis for corn took 3.6799685955047607s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 4.3392181396484375e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.2632029056549072s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.022878646850585938s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.1948089599609375e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 1.1205673217773438e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 2.8249502182006836s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 4.172325134277344e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.24461817741394043s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.020540952682495117s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.147125244140625e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.1444091796875e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 2.7819747924804688s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.315376281738281e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.24712157249450684s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020856857299804688s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 6.246566772460938e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.0967254638671875e-05s
INFO | --- Analysis for cornetto took 13.415033340454102s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.12202787399291992s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005888938903808594s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 179.92315793037415s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.5594713687896729s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 104.03376722335815s
Interoperability | New terms check for Corporate Body Named Authority List  took 77.91866660118103s
Versatility | Languages check for Corporate Body Named Authority List  took 300.0904734134674s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 17.603291273117065s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.3376944065093994s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.7231976985931396s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 3.942854642868042s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.328571081161499s
License | MR license check for Corporate Body Named Authority List  took 0.6346032619476318s
License | HR license check for Corporate Body Named Authority List  took 300.1034457683563s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.158949613571167s
Understandability | Number of label check for Corporate Body Named Authority List  took 1.872572898864746s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.3955092430114746s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.12275266647338867s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.18819189071655273s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.2163102626800537s
Performance | Throughput check for Corporate Body Named Authority List  took 10.715734243392944s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 4.863739013671875e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.18619823455810547s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 6.491137742996216s
Interlinking | skos check for Corporate Body Named Authority List  took 0.3167243003845215s
Interlinking | skos check for Corporate Body Named Authority List  took 0.3482387065887451s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.22215723991394043s
Currency | Creation date check for Corporate Body Named Authority List  took 0.36975741386413574s
Currency | Modification date check for Corporate Body Named Authority List  took 0.11250591278076172s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 444.8838002681732s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.16123723983764648s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.1618499755859375s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.19954848289489746s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 96.19820237159729s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.091775417327881s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.6560511589050293s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.20181989669799805s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.4121811389923s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.347174406051636s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 47.66419339179993s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.629124641418457s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.37797474861145s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 2.992706298828125s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.4508492946624756s
Security | Sign check for Corporate Body Named Authority List  took 0.3800349235534668s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 16.870768070220947s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.5890188217163086s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.02064371109008789s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 5.745887756347656e-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.0251998901367188e-05s
INFO | --- Analysis for corporate-body took 14998.834651947021s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.7103450298309326s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.2460339069366455s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for CorpusFibonacci took 5.317768096923828s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 8.726119995117188e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.26770472526550293s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020837783813476562s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 2.956390380859375e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 1.0728836059570312e-05s
INFO | --- Analysis for corscheck took 2.8576819896698s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.10043597221374512s
Availability | VoID file availability check for Country Name Authority List took 0.0007953643798828125s
Extra | Recovery of all triples for Country Name Authority List took 165.81683945655823s
Performance | Total latancy measurement for Country Name Authority List took 0.6036808490753174s
Amount of data | Number of triples check for Country Name Authority List took 68.52547192573547s
Interoperability | New terms check for Country Name Authority List took 75.5761148929596s
Versatility | Languages check for Country Name Authority List took 300.0848939418793s
Interpretability | Number of blank nodes check for Country Name Authority List took 18.677876234054565s
Security | Check HTTPS for Country Name Authority List took 0.4157853126525879s
Interpretability | RDF structures check for Country Name Authority List took 0.2598142623901367s
Versatility | Serialization formats check for Country Name Authority List took 3.281188726425171s
Availability | RDF dump link check for Country Name Authority List took 0.26340675354003906s
License | MR license check for Country Name Authority List took 0.33127617835998535s
License | HR license check for Country Name Authority List took 300.2963788509369s
Amount of data | Number of property check for Country Name Authority List took 0.17859745025634766s
Understandability | Number of label check for Country Name Authority List took 2.3373072147369385s
Understandability | URI regex check for Country Name Authority List took 0.432614803314209s
Understandability | Vocabs check for Country Name Authority List took 0.11140155792236328s
Verifiability | Authors check for Country Name Authority List took 0.12662243843078613s
Verifiability | Publishers check for Country Name Authority List took 0.1272587776184082s
Performance | Throughput check for Country Name Authority List took 11.44167947769165s
Amount of data | Check the number of entities for Country Name Authority List took 0.00012373924255371094s
Verifiability | Contribs. check for Country Name Authority List took 0.13946890830993652s
Interlinking | sameAs chians check for Country Name Authority List took 7.8636696338653564s
Interlinking | skos check for Country Name Authority List took 0.3635380268096924s
Interlinking | skos check for Country Name Authority List took 0.2995738983154297s
Timeliness | dataset update frequency check for Country Name Authority List took 0.33756518363952637s
Currency | Creation date check for Country Name Authority List took 0.25129199028015137s
Currency | Modification date check for Country Name Authority List took 0.12713170051574707s
Rep.Conc. | URIs length for Country Name Authority List took 418.39690589904785s
Interoperability | New vocabularies check for Country Name Authority List took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.16596007347106934s
Accuracy | Check Functional Property for Country Name Authority List took 0.15615105628967285s
Accuracy | Check Empty annotation labels for Country Name Authority List took 39.50007081031799s
Accuracy | Check White space in annotation for Country Name Authority List took 3.191932439804077s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.575554847717285s
Consistency | Disjoint class check for Country Name Authority List took 0.11684942245483398s
Consistency | Check Misplaced properties for Country Name Authority List took 300.4770419597626s
Consistency | Misplaced classes for Country Name Authority List took 8.43588924407959s
Consistency | Check Ontology hijacking for Country Name Authority List took 107.12966418266296s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.7105226516723633s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.51089119911194s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.0030107498168945s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.4185788631439209s
Security | Sign check for Country Name Authority List took 0.5265111923217773s
Availability | Check URIs Dereferenciability for Country Name Authority List took 17.897042512893677s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.36827707290649414s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.02351832389831543s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 6.341934204101562e-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.1920928955078125e-05s
INFO | --- Analysis for country-authority-list took 15483.193912506104s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.0838768482208252s
Availability | VoID file availability check for Courts thesaurus took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.25186634063720703s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0016472339630126953s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 0.0001342296600341797s
Believability | Calculation of trust value for Courts thesaurus took 1.0013580322265625e-05s
INFO | --- Analysis for courts-thesaurus took 2.510350465774536s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 20.4642915725708s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.2778780460357666s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020650625228881836s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 7.82012939453125e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.049041748046875e-05s
INFO | --- Analysis for Covid-on-the-Web took 55.70975303649902s
Availability | SPARQL endpoint availability check for CPA 2008 took 26.73256230354309s
Availability | VoID file availability check for CPA 2008 took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.2583329677581787s
Reputation | Calculation of the PageRank for CPA 2008 took 0.02155780792236328s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.24249267578125e-05s
Believability | Calculation of trust value for CPA 2008 took 4.76837158203125e-06s
INFO | --- Analysis for cpa-2008 took 125.67354035377502s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.38863658905029297s
Availability | VoID file availability check for Cooperative Patent Classification took 0.00033926963806152344s
Extra | Recovery of all triples for Cooperative Patent Classification took 27.3330717086792s
Performance | Total latancy measurement for Cooperative Patent Classification took 1.240865707397461s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.17753720283508s
Versatility | Languages check for Cooperative Patent Classification took 100.19530725479126s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 100.35116791725159s
Interpretability | RDF structures check for Cooperative Patent Classification took 29.528804302215576s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.1537179946899414s
Availability | RDF dump link check for Cooperative Patent Classification took 0.19913268089294434s
License | MR license check for Cooperative Patent Classification took 0.23652362823486328s
License | HR license check for Cooperative Patent Classification took 90.21202659606934s
Amount of data | Number of property check for Cooperative Patent Classification took 0.23111867904663086s
Understandability | Number of label check for Cooperative Patent Classification took 90.23992800712585s
Understandability | URI regex check for Cooperative Patent Classification took 0.4585604667663574s
Understandability | Vocabs check for Cooperative Patent Classification took 0.29190659523010254s
Verifiability | Authors check for Cooperative Patent Classification took 0.24590730667114258s
Verifiability | Publishers check for Cooperative Patent Classification took 0.22312259674072266s
Performance | Throughput check for Cooperative Patent Classification took 11.138957262039185s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.271766662597656e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.15264606475830078s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.16013598442077637s
Interlinking | skos check for Cooperative Patent Classification took 0.1698136329650879s
Interlinking | skos check for Cooperative Patent Classification took 0.1701655387878418s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.16425251960754395s
Currency | Creation date check for Cooperative Patent Classification took 0.2985072135925293s
Currency | Modification date check for Cooperative Patent Classification took 0.3475921154022217s
Rep.Conc. | URIs length for Cooperative Patent Classification took 130.43530988693237s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 20.027349948883057s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 14.941609621047974s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.9426188468933105s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.823245525360107s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.17735505104064941s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 100.50259780883789s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 37.69301176071167s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.5717277526855469s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 101.656414270401s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.786811590194702s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 15.977598667144775s
Security | Sign check for Cooperative Patent Classification took 0.24988842010498047s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.7684175968170166s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 1.3934459686279297s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.0223543643951416s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 5.1975250244140625e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 1.430511474609375e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 8.106231689453125e-06s
INFO | --- Analysis for CPC took 1361.9379642009735s
Availability | SPARQL endpoint availability check for CPC 2008 took 28.394993782043457s
Availability | VoID file availability check for CPC 2008 took 0.0008947849273681641s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.6696052551269531s
Reputation | Calculation of the PageRank for CPC 2008 took 0.02117919921875s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.363059997558594e-05s
Believability | Calculation of trust value for CPC 2008 took 9.298324584960938e-06s
INFO | --- Analysis for cpc-2008 took 127.9944338798523s
Availability | SPARQL endpoint availability check for CPV  2003 took 21.383852005004883s
Availability | VoID file availability check for CPV  2003 took 0.000812530517578125s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.32182788848876953s
Reputation | Calculation of the PageRank for CPV  2003 took 0.021251678466796875s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.029273986816406e-05s
Believability | Calculation of trust value for CPV  2003 took 8.821487426757812e-06s
INFO | --- Analysis for cpv-2003 took 116.46499013900757s
Availability | SPARQL endpoint availability check for CPV 2008 took 26.00011944770813s
Availability | VoID file availability check for CPV 2008 took 0.0008177757263183594s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.6891119480133057s
Reputation | Calculation of the PageRank for CPV 2008 took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.291534423828125e-05s
Believability | Calculation of trust value for CPV 2008 took 8.58306884765625e-06s
INFO | --- Analysis for cpv-2008 took 126.55091190338135s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.7751786708832s
Availability | VoID file availability check for crowdsourcing-fb took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.6861627101898193s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020738601684570312s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 6.246566772460938e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.2636184692382812e-05s
INFO | --- Analysis for crowdsourcing-fb took 535.7684881687164s
Availability | SPARQL endpoint availability check for CRTM took 8.487701416015625e-05s
Availability | VoID file availability check for CRTM took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for CRTM took 0.23996925354003906s
Reputation | Calculation of the PageRank for CRTM took 0.020655155181884766s
Interlinking | Calculation of Degree of Connection for CRTM took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for CRTM took 2.8133392333984375e-05s
Believability | Calculation of trust value for CRTM took 1.1205673217773438e-05s
INFO | --- Analysis for crtm took 4.177282810211182s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 5.340576171875e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.26694583892822266s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.02079486846923828s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 3.6716461181640625e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 1.2159347534179688e-05s
INFO | --- Analysis for crystal-eye took 3.7956395149230957s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.681703567504883s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.3543705940246582s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.021766185760498047s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.744529724121094e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 8.344650268554688e-06s
INFO | --- Analysis for ctic-public-dataset took 44.36464786529541s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 8.153915405273438e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.2701268196105957s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.020389080047607422s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 2.6941299438476562e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 1.0728836059570312e-05s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 2.9370052814483643s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 20.420575618743896s
Availability | VoID file availability check for CulturaLinkedData took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.2757248878479004s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.020848512649536133s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.504753112792969e-05s
Believability | Calculation of trust value for CulturaLinkedData took 1.2636184692382812e-05s
INFO | --- Analysis for culturalinkeddata took 53.51096248626709s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.21465587615966797s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.26523542404174805s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0217282772064209s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.528594970703125e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-ares-or took 3.803615093231201s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11202430725097656s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.006201028823852539s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.2519385814666748s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.021007299423217773s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0008251667022705078s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.172325134277344e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 9.775161743164062e-06s
INFO | --- Analysis for cz-ares-rzp took 2.7973380088806152s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11095476150512695s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.28702306747436523s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.021630048751831055s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 4.124641418457031e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 1.0013580322265625e-05s
INFO | --- Analysis for cz-cenia-irz-chemicals took 3.3262884616851807s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.10636496543884277s
Availability | VoID file availability check for Integrated pollution registry took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.26302194595336914s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.022776126861572266s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 4.076957702636719e-05s
Believability | Calculation of trust value for Integrated pollution registry took 9.5367431640625e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.804506778717041s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.10215568542480469s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.2666306495666504s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.020784378051757812s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.719329833984375e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 8.821487426757812e-06s
INFO | --- Analysis for cz-contracts took 2.7369494438171387s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 8.082389831542969e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.2540097236633301s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 3.0517578125e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 1.1920928955078125e-05s
INFO | --- Analysis for cz-courts took 2.9171302318573s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.11688899993896484s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.2777116298675537s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.02070903778076172s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.719329833984375e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 9.298324584960938e-06s
INFO | --- Analysis for cz-ctia-bans took 6.174412965774536s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.10713768005371094s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.25125789642333984s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.022487163543701172s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.695487976074219e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 9.059906005859375e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.7709896564483643s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.10698080062866211s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.2622079849243164s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.02157425880432129s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.4332275390625e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 8.821487426757812e-06s
INFO | --- Analysis for cz-ctia-focus took 2.7422220706939697s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.11689209938049316s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0007619857788085938s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.2501349449157715s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 3.886222839355469e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 9.059906005859375e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.7241272926330566s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.12148523330688477s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.2617154121398926s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.02225661277770996s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.266334533691406e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 9.5367431640625e-06s
INFO | --- Analysis for cz-ctia-sanctions took 5.994760990142822s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.19677352905273438s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0007622241973876953s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.27549099922180176s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020243406295776367s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.62396240234375e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 8.58306884765625e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 2.934842586517334s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.10550570487976074s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.2744476795196533s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020227909088134766s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.1948089599609375e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 8.344650268554688e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 2.775925874710083s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.5825324058532715s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.2516806125640869s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.528594970703125e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.3301939964294434s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.36193251609802246s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.25652575492858887s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.552436828613281e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.2449376583099365s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.3656899929046631s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0008895397186279297s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.2508823871612549s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.552436828613281e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.5299530029296875e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.187180519104004s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.37282228469848633s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.2745990753173828s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.020414352416992188s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.5762786865234375e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.197153329849243s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.39504194259643555s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.24483585357666016s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.4809112548828125e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.263871431350708s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.37779855728149414s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0009090900421142578s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.26491379737854004s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020796775817871094s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.3855438232421875e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 8.821487426757812e-06s
INFO | --- Analysis for cz-czso-regions took 3.020951986312866s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3337216377258301s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.3406822681427002s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020576000213623047s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.647804260253906e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.3180270195007324s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.33080554008483887s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.2315053939819336s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2526533603668213s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020974159240722656s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.552436828613281e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.3537049293518066s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.3551957607269287s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0003399848937988281s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.23714232444763184s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.021994590759277344s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.719329833984375e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 4.291534423828125e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.1176488399505615s
Availability | SPARQL endpoint availability check for ATC groups took 0.12102341651916504s
Availability | VoID file availability check for ATC groups took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for ATC groups took 0.257702112197876s
Reputation | Calculation of the PageRank for ATC groups took 0.020859956741333008s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ATC groups took 6.604194641113281e-05s
Believability | Calculation of trust value for ATC groups took 1.1920928955078125e-05s
INFO | --- Analysis for cz-eh-1-atc took 2.777778387069702s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.1124887466430664s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.26418471336364746s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.02051568031311035s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.2901763916015625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 8.58306884765625e-06s
INFO | --- Analysis for cz-fulfillments took 2.7348108291625977s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.030101776123046875s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.24681639671325684s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020706892013549805s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.76837158203125e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 8.344650268554688e-06s
INFO | --- Analysis for cz-ic took 3.0972654819488525s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.11079716682434082s
Availability | VoID file availability check for List of Czech data boxes took 0.0002689361572265625s
Extra | Recovery of all triples for List of Czech data boxes took 150.09638500213623s
Performance | Total latancy measurement for List of Czech data boxes took 0.5578923225402832s
Amount of data | Number of triples check for List of Czech data boxes took 9.825539827346802s
Interoperability | New terms check for List of Czech data boxes took 10.78264594078064s
Versatility | Languages check for List of Czech data boxes took 300.1661524772644s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.2851600646972656s
Interpretability | RDF structures check for List of Czech data boxes took 0.1454148292541504s
Versatility | Serialization formats check for List of Czech data boxes took 0.17145633697509766s
Availability | RDF dump link check for List of Czech data boxes took 15.779239654541016s
License | MR license check for List of Czech data boxes took 0.42127037048339844s
License | HR license check for List of Czech data boxes took 57.86523914337158s
Amount of data | Number of property check for List of Czech data boxes took 0.1325681209564209s
Understandability | Number of label check for List of Czech data boxes took 1.5118231773376465s
Understandability | URI regex check for List of Czech data boxes took 0.5073750019073486s
Understandability | Vocabs check for List of Czech data boxes took 0.12984371185302734s
Verifiability | Authors check for List of Czech data boxes took 0.11091780662536621s
Verifiability | Publishers check for List of Czech data boxes took 0.12951898574829102s
Performance | Throughput check for List of Czech data boxes took 11.2091224193573s
Amount of data | Check the number of entities for List of Czech data boxes took 3.007861614227295s
Verifiability | Contribs. check for List of Czech data boxes took 0.137831449508667s
Interlinking | sameAs chians check for List of Czech data boxes took 0.43105459213256836s
Interlinking | skos check for List of Czech data boxes took 0.20168566703796387s
Interlinking | skos check for List of Czech data boxes took 0.10120248794555664s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.23900508880615234s
Currency | Creation date check for List of Czech data boxes took 0.22113418579101562s
Currency | Modification date check for List of Czech data boxes took 0.13863325119018555s
Rep.Conc. | URIs length for List of Czech data boxes took 113.85793209075928s
Interoperability | New vocabularies check for List of Czech data boxes took 10.743240594863892s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.3704249858856201s
Accuracy | Check Functional Property for List of Czech data boxes took 0.25359654426574707s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.24428057670593262s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 32.65884256362915s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.0379350185394287s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.565181016921997s
Consistency | Disjoint class check for List of Czech data boxes took 0.10408520698547363s
Consistency | Check Misplaced properties for List of Czech data boxes took 69.84742593765259s
Consistency | Misplaced classes for List of Czech data boxes took 7.453086853027344s
Consistency | Check Ontology hijacking for List of Czech data boxes took 32.259347438812256s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.3952341079711914s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 64.41267395019531s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.619473457336426s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.345550537109375s
Security | Sign check for List of Czech data boxes took 0.16025066375732422s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 353.0642704963684s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 1.5015625953674316s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.021598100662231445s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 4.863739013671875e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 9.520092725753784s
Believability | Calculation of trust value for List of Czech data boxes took 9.5367431640625e-06s
INFO | --- Analysis for cz-list-of-databoxes took 1615.699730873108s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12153077125549316s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006043910980224609s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 151.32320594787598s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6602790355682373s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.603747129440308s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.666610956192017s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.1745460033417s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3924973011016846s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1284477710723877s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1614384651184082s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 14.729311227798462s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5235099792480469s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 58.11615324020386s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13055968284606934s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.673595905303955s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4702110290527344s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10906600952148438s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13086485862731934s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11644124984741211s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.72777795791626s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0553765296936035s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1436169147491455s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4070725440979004s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1838216781616211s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10372328758239746s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.23904967308044434s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.24609160423278809s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13164949417114258s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 113.56222581863403s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.592298746109009s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.33640360832214355s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.15777969360351562s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.14752697944641113s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 31.06683874130249s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.030344009399414s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6284797191619873s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11302971839904785s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 69.39050602912903s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.544737815856934s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 34.23152542114258s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3856282234191895s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 64.64968991279602s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6454949378967285s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.36969828605651855s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.15723371505737305s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 363.551317691803s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.5480422973632812s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.021744251251220703s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 8.702278137207031e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 12.677277326583862s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 8.58306884765625e-06s
INFO | --- Analysis for cz-nace took 1627.2477941513062s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3063652515411377s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0005629062652587891s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 396.40175461769104s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8726980686187744s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5696725845336914s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.609271287918091s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 300.20313787460327s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.647757053375244s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8646109104156494s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 6.241666793823242s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.389209508895874s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.7545223236083984s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.0368430614471436s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18526291847229004s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5708272457122803s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5222282409667969s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.24397850036621094s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.38373231887817383s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.27854275703430176s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.652214288711548s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.893013000488281e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2324378490447998s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20910358428955078s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4469468593597412s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16668415069580078s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.6156294345855713s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5719959735870361s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4061403274536133s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 86.63489556312561s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1625688076019287s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.30034470558166504s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3010106086730957s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 71.02842473983765s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.3680124282836914s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.6201353073120117s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.200606107711792s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 5.307348012924194s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.964930295944214s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 71.47143983840942s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7609052658081055s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 6.455967426300049s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.139688730239868s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3708200454711914s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2871694564819336s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 930.3097848892212s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4489552974700928s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.021460533142089844s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.695487976074219e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.298324584960938e-06s
INFO | --- Analysis for cz-nkod took 33968.31989145279s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.2931637763977051s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.26381731033325195s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.02144765853881836s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007505416870117188s
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 8.106231689453125e-06s
INFO | --- Analysis for cz-orders took 4.230715990066528s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.20810604095458984s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0005443096160888672s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 144.47610306739807s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.6116068363189697s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 9.598381280899048s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 10.753201484680176s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.1082670688629s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.2682549953460693s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.14216303825378418s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.17712664604187012s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 15.450774431228638s
License | MR license check for Institutions of public power of the Czech Republic took 0.4133267402648926s
License | HR license check for Institutions of public power of the Czech Republic took 57.89090824127197s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.12029480934143066s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.4376378059387207s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.4373798370361328s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.11570119857788086s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.11835551261901855s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.10420489311218262s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.520791292190552s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.0700390338897705s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.1269664764404297s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.4345664978027344s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.19860076904296875s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.1251533031463623s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.24781394004821777s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.2560145854949951s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.12621784210205078s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 113.00132465362549s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 9.794460773468018s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.35114383697509766s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.1857903003692627s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.18362998962402344s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 32.71952939033508s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.071756601333618s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.6170904636383057s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.12533855438232422s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 70.8063576221466s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.487087965011597s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 35.106722354888916s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.3311665058135986s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 63.76386570930481s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.6181373596191406s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.3472132682800293s
Security | Sign check for Institutions of public power of the Czech Republic took 0.14615464210510254s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 349.67070603370667s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 1.403602123260498s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.021595239639282227s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.364418029785156e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 10.902874946594238s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-ovm took 1606.0039329528809s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.10619473457336426s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.27544116973876953s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.021335363388061523s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.647804260253906e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-ovm-agendas took 2.8643085956573486s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1006155014038086s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0006194114685058594s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 58.72727608680725s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.5744462013244629s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 19.073833465576172s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 33.20643210411072s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.08650302886963s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1391763687133789s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.5868973731994629s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13250398635864258s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7866377830505371s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12528634071350098s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12728285789489746s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12629342079162598s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.8865723609924316s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.24895644187927246s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13610148429870605s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.18504905700683594s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11411046981811523s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.504925727844238s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.225440979003906e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12395429611206055s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11282658576965332s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13800740242004395s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11229348182678223s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10405278205871582s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.21532607078552246s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11345100402832031s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 221.58332777023315s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.09918642044067383s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13495111465454102s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13456344604492188s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 12.807516813278198s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.163978338241577s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.5288026332855225s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.20076513290405273s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 168.11995601654053s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.311172485351562s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 18.06663966178894s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.440969705581665s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 169.2739119529724s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 3.1540873050689697s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.25891709327697754s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11603546142578125s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 15.249469518661499s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.6238939762115479s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.021655559539794922s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.749961853027344e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.430511474609375e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.5367431640625e-06s
INFO | --- Analysis for cz-ruian took 1464.368500471115s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7036094665527344s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7264049053192139s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.462501525878906e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 5.242567777633667s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.5213325023651123s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.24777507781982422s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.021943330764770508s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.1682510375976562e-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.172325134277344e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.5612144470214844s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.439394474029541s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.26021242141723633s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020198345184326172s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 2.86102294921875e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 9.059906005859375e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 4.482420206069946s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.11037254333496094s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.26156163215637207s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020554304122924805s
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.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.457069396972656e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.2636184692382812e-05s
INFO | --- Analysis for cz-sidc-drug-ingredients took 3.2389633655548096s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.10875725746154785s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.2897658348083496s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.24249267578125e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.872753381729126s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.10519576072692871s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.2554645538330078s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020310401916503906s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.337860107421875e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.2636184692382812e-05s
INFO | --- Analysis for cz-sidc-drugs took 3.3241965770721436s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.19585418701171875s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0005974769592285156s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 149.27299880981445s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.6104922294616699s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 9.521469354629517s
Interoperability | New terms check for Summary types of Czech institutions of public power took 10.774625062942505s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.1443908214569s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.3392837047576904s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.1219477653503418s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.19025182723999023s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 14.90606951713562s
License | MR license check for Summary types of Czech institutions of public power took 0.11417984962463379s
License | HR license check for Summary types of Czech institutions of public power took 58.19474148750305s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.10921311378479004s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.4301037788391113s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.41793179512023926s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.10482239723205566s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.1121063232421875s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.12434601783752441s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.798167943954468s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.0053672790527344s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.15229058265686035s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.6615660190582275s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.2124636173248291s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.11847472190856934s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.2739076614379883s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.2392127513885498s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.1201639175415039s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 112.30830907821655s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 9.27018666267395s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.3600907325744629s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.19934821128845215s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.1930387020111084s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 31.530789613723755s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.0085370540618896s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.541928768157959s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.12030696868896484s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 69.67207741737366s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.388406038284302s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 31.787304878234863s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.336336374282837s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 63.29161286354065s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.6314055919647217s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.40372276306152344s
Security | Sign check for Summary types of Czech institutions of public power took 0.15106606483459473s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 349.3818361759186s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 1.4337453842163086s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.021399259567260742s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 9.208513259887695s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 9.5367431640625e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 1601.9483349323273s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.10615134239196777s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.2763652801513672s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.504753112792969e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 4.534128665924072s
Availability | SPARQL endpoint availability check for State funding providers took 0.1081397533416748s
Availability | VoID file availability check for State funding providers took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for State funding providers took 0.271162748336792s
Reputation | Calculation of the PageRank for State funding providers took 0.020482540130615234s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.0531158447265625e-05s
Believability | Calculation of trust value for State funding providers took 7.867813110351562e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 3.3626041412353516s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.10301685333251953s
Availability | VoID file availability check for Organizations active in R&D took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.2584824562072754s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.02110743522644043s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.0531158447265625e-05s
Believability | Calculation of trust value for Organizations active in R&D took 8.344650268554688e-06s
INFO | --- Analysis for cz-vavai-organizations took 2.9905025959014893s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.10875725746154785s
Availability | VoID file availability check for R&D Programmes took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.28929710388183594s
Reputation | Calculation of the PageRank for R&D Programmes took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.1484832763671875e-05s
Believability | Calculation of trust value for R&D Programmes took 7.62939453125e-06s
INFO | --- Analysis for cz-vavai-programmes took 2.845590353012085s
Availability | SPARQL endpoint availability check for R&D Projects took 0.11360859870910645s
Availability | VoID file availability check for R&D Projects took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.2536768913269043s
Reputation | Calculation of the PageRank for R&D Projects took 0.0205075740814209s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.172325134277344e-05s
Believability | Calculation of trust value for R&D Projects took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-projects took 2.812835454940796s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.11280298233032227s
Availability | VoID file availability check for Institutional research plans took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.3008289337158203s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020474672317504883s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.2438507080078125e-05s
Believability | Calculation of trust value for Institutional research plans took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.8961143493652344s
Availability | SPARQL endpoint availability check for Results of R&D took 0.11342239379882812s
Availability | VoID file availability check for Results of R&D took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.27645206451416016s
Reputation | Calculation of the PageRank for Results of R&D took 0.021313905715942383s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.1961669921875e-05s
Believability | Calculation of trust value for Results of R&D took 8.106231689453125e-06s
INFO | --- Analysis for cz-vavai-results took 2.8514022827148438s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.10468435287475586s
Availability | VoID file availability check for Tenders in R&D took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.3078787326812744s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.020725727081298828s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.124641418457031e-05s
Believability | Calculation of trust value for Tenders in R&D took 8.344650268554688e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.8710508346557617s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 8.630752563476562e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0066089630126953125s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.2605738639831543s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.0209810733795166s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007126331329345703s
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.0967254638671875e-05s
INFO | --- Analysis for czech_addresses took 4.140869617462158s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.6625998020172119s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.2885758876800537s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 4.4345855712890625e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 1.049041748046875e-05s
INFO | --- Analysis for DanteLatinLoanwords took 4.219527006149292s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.3615410327911377s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0005445480346679688s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 147.3368535041809s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 0.9725713729858398s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 12.973305940628052s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.358348369598389s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.3111424446106s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.19643616676330566s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.11217594146728516s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 1.0099055767059326s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.21827340126037598s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.39701414108276367s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.25579261779785156s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 76.58246684074402s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.20914483070373535s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 2.938253164291382s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.6203980445861816s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.23223137855529785s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.2156815528869629s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.2317662239074707s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 10.875346660614014s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 8.106231689453125e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.19969820976257324s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 1.1065912246704102s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.5174610614776611s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.2033092975616455s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.5418341159820557s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 0.40631556510925293s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 0.4205007553100586s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 91.58562684059143s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.21360063552856445s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.3073732852935791s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.2625412940979004s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 44.178043603897095s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.217780828475952s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.610995054244995s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.21245121955871582s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 20.48441219329834s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.406564950942993s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 46.02756690979004s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.5019524097442627s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 21.319591283798218s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.7788329124450684s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.2253267765045166s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 1.0998222827911377s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 13.070208311080933s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 1.3265652656555176s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.020784616470336914s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014066696166992188s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.430511474609375e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.1682510375976562e-05s
INFO | --- Analysis for data-bnf-fr took 812.0448508262634s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.2828683853149414s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.24732232093811035s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.02114081382751465s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 6.651878356933594e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 1.049041748046875e-05s
INFO | --- Analysis for data-cnr-it took 4.056729316711426s
Availability | SPARQL endpoint availability check for Data.gov took 1.758622407913208s
Availability | VoID file availability check for Data.gov took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Data.gov took 0.689410924911499s
Reputation | Calculation of the PageRank for Data.gov took 0.020893096923828125s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.5762786865234375e-05s
Believability | Calculation of trust value for Data.gov took 9.298324584960938e-06s
INFO | --- Analysis for data-gov took 20.72521209716797s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.15411853790283203s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.2744927406311035s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020237207412719727s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.341934204101562e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 9.298324584960938e-06s
INFO | --- Analysis for data-gov-ie took 3.183750629425049s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.38690185546875e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.2763254642486572s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.02029132843017578s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.081031799316406e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 9.298324584960938e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.540884017944336s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 22.20366883277893s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0007131099700927734s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.27847814559936523s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02165389060974121s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.079673767089844e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 1.0251998901367188e-05s
INFO | --- Analysis for data-hnm-hu took 168.5235276222229s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.32207250595092773s
Availability | VoID file availability check for Climb Dataincubator took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.2635378837585449s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.081031799316406e-05s
Believability | Calculation of trust value for Climb Dataincubator took 9.298324584960938e-06s
INFO | --- Analysis for data-incubator-climb took 3.1958863735198975s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.172325134277344e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.2870140075683594s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.02160048484802246s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.393692016601562e-05s
Believability | Calculation of trust value for Discogs in RDF took 1.0251998901367188e-05s
INFO | --- Analysis for data-incubator-discogs took 9.19063401222229s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.0615847110748291s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.000789642333984375s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.27743101119995117s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.025032758712768555s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0015747547149658203s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 0.0001010894775390625s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 9.5367431640625e-06s
INFO | --- Analysis for data-incubator-metoffice took 6.772557973861694s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.08197927474975586s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0007939338684082031s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.2491316795349121s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.021814584732055664s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.96453857421875e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 1.2159347534179688e-05s
INFO | --- Analysis for data-incubator-moseley took 8.874366044998169s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.06253647804260254s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.25763893127441406s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.893013000488281e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.1682510375976562e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 2.551569700241089s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 4.627652645111084s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0007271766662597656s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.2702960968017578s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.021727800369262695s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0008463859558105469s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 9.632110595703125e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 8.821487426757812e-06s
INFO | --- Analysis for data-incubator-nasa took 13.621012926101685s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.06909489631652832s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2867121696472168s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.021103382110595703s
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.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.843971252441406e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 9.775161743164062e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.540191650390625s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.05808901786804199s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.29220056533813477s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.02087998390197754s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.489059448242188e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.2159347534179688e-05s
INFO | --- Analysis for data-incubator-pokedex took 4.438705205917358s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.06379079818725586s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.26192593574523926s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020730018615722656s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.749961853027344e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.049041748046875e-05s
INFO | --- Analysis for data-incubator-smcjournals took 2.5287694931030273s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.5420539379119873s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0013382434844970703s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 14.528021812438965s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.4295849800109863s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 16.203361988067627s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.6515631675720215s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.304765939712524s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.30564260482788s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.31647300720214844s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.5890133380889893s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.35076308250427246s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.48720216751098633s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.3332951068878174s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.3458411693573s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.5117204189300537s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 17.879263877868652s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.868156909942627s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.3861429691314697s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.7021598815917969s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.6916418075561523s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 11.043687105178833s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 7.486343383789062e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.4121236801147461s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.9962918758392334s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.40282106399536133s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.4033021926879883s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.429811954498291s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.9570095539093018s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.9537491798400879s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 36.70434236526489s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.36876440048217773s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.34945034980773926s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.32411932945251465s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 32.209431648254395s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 2.966858148574829s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.108080863952637s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.6225244998931885s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 1.8557648658752441s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 8.16428542137146s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 28.070347785949707s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.3445558547973633s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 2.0066728591918945s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.8075733184814453s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.6817026138305664s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.42269015312194824s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 5.1550133228302s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.8063170909881592s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.021207571029663086s
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.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 4.5299530029296875e-06s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 7.3909759521484375e-06s
INFO | --- Analysis for data-open-ac-uk took 584.2161314487457s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.9016513824462891s
Availability | VoID file availability check for Persée in RDF took 0.6441469192504883s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.6780812740325928s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 9.989738464355469e-05s
Believability | Calculation of trust value for Persée in RDF took 1.049041748046875e-05s
INFO | --- Analysis for data-persee-fr took 9.053228855133057s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 8.440017700195312e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.7053563594818115s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.1948089599609375e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 1.049041748046875e-05s
INFO | --- Analysis for data-southampton-ac-uk took 3.8130910396575928s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.663618564605713s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.24467968940734863s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.021574974060058594s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00012540817260742188s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.0728836059570312e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 14.645947217941284s
Availability | SPARQL endpoint availability check for Open Data Web took 2.2665650844573975s
Availability | VoID file availability check for Open Data Web took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.24858903884887695s
Reputation | Calculation of the PageRank for Open Data Web took 0.022197723388671875s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.1948089599609375e-05s
Believability | Calculation of trust value for Open Data Web took 1.1682510375976562e-05s
INFO | --- Analysis for data.odw.tw took 6.190818548202515s
Availability | SPARQL endpoint availability check for DataFAQs took 4.00543212890625e-05s
Availability | VoID file availability check for DataFAQs took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.2586054801940918s
Reputation | Calculation of the PageRank for DataFAQs took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.361701965332031e-05s
Believability | Calculation of trust value for DataFAQs took 1.049041748046875e-05s
INFO | --- Analysis for datafaqs took 2.808434009552002s
Availability | SPARQL endpoint availability check for datahub took 6.318092346191406e-05s
Availability | VoID file availability check for datahub took 0.00039768218994140625s
Completeness | Calculation of interlinking completeness for datahub took 0.24529290199279785s
Reputation | Calculation of the PageRank for datahub took 0.02096724510192871s
Interlinking | Calculation of Degree of Connection for datahub took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for datahub took 4.863739013671875e-05s
Believability | Calculation of trust value for datahub took 1.2636184692382812e-05s
INFO | --- Analysis for datahub took 4.196139097213745s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 5.09573221206665s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0006921291351318359s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.276763916015625s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020786523818969727s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.266334533691406e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 1.239776611328125e-05s
INFO | --- Analysis for datahub-kr-datamap took 14.922678470611572s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.2941005229949951s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.2613677978515625s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.02086472511291504s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.43865966796875e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.3113021850585938e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.241701364517212s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.203699827194214s
Availability | VoID file availability check for datos-artium-org took 0.0007686614990234375s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.8349213600158691s
Reputation | Calculation of the PageRank for datos-artium-org took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011157989501953125s
Believability | Calculation of trust value for datos-artium-org took 1.1444091796875e-05s
INFO | --- Analysis for datos-artium-org took 165.80340361595154s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.8686435222625732s
Availability | VoID file availability check for Datos.bcn.cl took 0.0007326602935791016s
Extra | Recovery of all triples for Datos.bcn.cl took 34.11057257652283s
Performance | Total latancy measurement for Datos.bcn.cl took 6.027894496917725s
Amount of data | Number of triples check for Datos.bcn.cl took 8.9005126953125s
Interoperability | New terms check for Datos.bcn.cl took 3.835865020751953s
Versatility | Languages check for Datos.bcn.cl took 300.9734437465668s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.2164905071258545s
Security | Check HTTPS for Datos.bcn.cl took 0.7292828559875488s
Interpretability | RDF structures check for Datos.bcn.cl took 1.2284550666809082s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2201550006866455s
Availability | RDF dump link check for Datos.bcn.cl took 1.2217953205108643s
License | MR license check for Datos.bcn.cl took 1.229107141494751s
License | HR license check for Datos.bcn.cl took 62.212982177734375s
Amount of data | Number of property check for Datos.bcn.cl took 1.2114064693450928s
Understandability | Number of label check for Datos.bcn.cl took 2.0241165161132812s
Understandability | URI regex check for Datos.bcn.cl took 2.3504323959350586s
Understandability | Vocabs check for Datos.bcn.cl took 1.1982300281524658s
Verifiability | Authors check for Datos.bcn.cl took 1.2476277351379395s
Verifiability | Publishers check for Datos.bcn.cl took 1.2359600067138672s
Performance | Throughput check for Datos.bcn.cl took 11.96342921257019s
Amount of data | Check the number of entities for Datos.bcn.cl took 0.00011897087097167969s
Verifiability | Contribs. check for Datos.bcn.cl took 1.2014493942260742s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.2385454177856445s
Interlinking | skos check for Datos.bcn.cl took 1.2088780403137207s
Interlinking | skos check for Datos.bcn.cl took 1.2028629779815674s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.2082812786102295s
Currency | Creation date check for Datos.bcn.cl took 2.4303557872772217s
Currency | Modification date check for Datos.bcn.cl took 1.2244789600372314s
Rep.Conc. | URIs length for Datos.bcn.cl took 36.62686824798584s
Interoperability | New vocabularies check for Datos.bcn.cl took 6.67572021484375e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.225806474685669s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.2037310600280762s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.2036268711090088s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 10.421690940856934s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.23511886596679688s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.26103949546813965s
Consistency | Disjoint class check for Datos.bcn.cl took 1.1942672729492188s
Consistency | Check Misplaced properties for Datos.bcn.cl took 12.316251993179321s
Consistency | Misplaced classes for Datos.bcn.cl took 1.997408390045166s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 11.728541851043701s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.3037779331207275s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 7.474464416503906s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.2904524803161621s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.457613468170166s
Security | Sign check for Datos.bcn.cl took 2.1725404262542725s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 7890.0185832977295s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.7470638751983643s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.021260976791381836s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 8.440017700195312e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.430511474609375e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 9.298324584960938e-06s
INFO | --- Analysis for datos-bcn-cl took 8748.694462060928s
Availability | SPARQL endpoint availability check for datos.bne.es took 30.150818347930908s
Availability | VoID file availability check for datos.bne.es took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.7303450107574463s
Reputation | Calculation of the PageRank for datos.bne.es took 0.021332263946533203s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0009250640869140625s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.0001239776611328125s
Believability | Calculation of trust value for datos.bne.es took 7.867813110351562e-06s
INFO | --- Analysis for datos-bne-es took 116.07188677787781s
Availability | SPARQL endpoint availability check for dbacademic took 0.15247535705566406s
Availability | VoID file availability check for dbacademic took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for dbacademic took 0.26424169540405273s
Reputation | Calculation of the PageRank for dbacademic took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.00084686279296875s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.2901763916015625e-05s
Believability | Calculation of trust value for dbacademic took 4.76837158203125e-06s
INFO | --- Analysis for dbacademic took 2.9074981212615967s
Availability | SPARQL endpoint availability check for DBkWik took 15.562648296356201s
Availability | VoID file availability check for DBkWik took 0.0006377696990966797s
Extra | Recovery of all triples for DBkWik took 8.455727577209473s
Performance | Total latancy measurement for DBkWik took 31.980031490325928s
Amount of data | Number of triples check for DBkWik took 5.546668529510498s
Interoperability | New terms check for DBkWik took 62.646721839904785s
Versatility | Languages check for DBkWik took 68.44845843315125s
Interpretability | Number of blank nodes check for DBkWik took 32.44865870475769s
Interpretability | RDF structures check for DBkWik took 0.560835599899292s
Versatility | Serialization formats check for DBkWik took 0.42424845695495605s
Availability | RDF dump link check for DBkWik took 2.818549156188965s
License | MR license check for DBkWik took 9.082411050796509s
License | HR license check for DBkWik took 61.702070474624634s
Amount of data | Number of property check for DBkWik took 0.10087203979492188s
Understandability | Number of label check for DBkWik took 3.524362087249756s
Understandability | URI regex check for DBkWik took 2.8108713626861572s
Understandability | Vocabs check for DBkWik took 0.07884645462036133s
Verifiability | Authors check for DBkWik took 0.08310794830322266s
Verifiability | Publishers check for DBkWik took 0.08899402618408203s
Performance | Throughput check for DBkWik took 10.713990211486816s
Amount of data | Check the number of entities for DBkWik took 6.818771362304688e-05s
Verifiability | Contribs. check for DBkWik took 0.23450994491577148s
Interlinking | sameAs chians check for DBkWik took 0.2945871353149414s
Interlinking | skos check for DBkWik took 0.3304891586303711s
Interlinking | skos check for DBkWik took 0.08445620536804199s
Timeliness | dataset update frequency check for DBkWik took 0.34824633598327637s
Currency | Creation date check for DBkWik took 0.6364376544952393s
Currency | Modification date check for DBkWik took 0.17847180366516113s
Rep.Conc. | URIs length for DBkWik took 11.207210063934326s
Interoperability | New vocabularies check for DBkWik took 2.60227370262146s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.0836172103881836s
Accuracy | Check Functional Property for DBkWik took 0.4092214107513428s
Accuracy | Check Inverse Functional Property for DBkWik took 0.23771452903747559s
Accuracy | Check Empty annotation labels for DBkWik took 0.7073218822479248s
Accuracy | Check White space in annotation for DBkWik took 0.023193836212158203s
Accuracy | Check Datatype consistency for DBkWik took 0.03794455528259277s
Consistency | Disjoint class check for DBkWik took 0.2886993885040283s
Consistency | Check Misplaced properties for DBkWik took 12.830540657043457s
Consistency | Misplaced classes for DBkWik took 8.144112586975098s
Consistency | Check Ontology hijacking for DBkWik took 11.296354293823242s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.295342206954956s
Consistency | Check Invalid usage of undefined properties for DBkWik took 15.810643196105957s
Conciseness | Check Extensional conciseness for DBkWik took 0.03394508361816406s
Conciseness | Check Intensional conciseness for DBkWik took 48.35595965385437s
Security | Sign check for DBkWik took 22.168264865875244s
Availability | Check URIs Dereferenciability for DBkWik took 16.049185752868652s
Completeness | Calculation of interlinking completeness for DBkWik took 1.3254823684692383s
Reputation | Calculation of the PageRank for DBkWik took 0.02177119255065918s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0008213520050048828s
Interlinking | Calculation of Clustering coefficient for DBkWik took 0.00012254714965820312s
Interoperability | Check the re-using of existing vocabs for DBkWik took 2.828535795211792s
Believability | Calculation of trust value for DBkWik took 1.2874603271484375e-05s
INFO | --- Analysis for dbkwik took 4436.168221950531s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 5.173683166503906e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.2546114921569824s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.021387100219726562s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00010967254638671875s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.0251998901367188e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 8.228814125061035s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.3336963653564453s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0007808208465576172s
Extra | Recovery of all triples for dblp Knowledge Graph took 7.163892507553101s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.7221033573150635s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.13709378242492676s
Interoperability | New terms check for dblp Knowledge Graph took 1.7766234874725342s
Versatility | Languages check for dblp Knowledge Graph took 0.15102386474609375s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 2.065889596939087s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.1741480827331543s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.16220688819885254s
Availability | RDF dump link check for dblp Knowledge Graph took 0.13796091079711914s
License | MR license check for dblp Knowledge Graph took 0.14939165115356445s
License | HR license check for dblp Knowledge Graph took 30.16041088104248s
Amount of data | Number of property check for dblp Knowledge Graph took 0.1402297019958496s
Understandability | Number of label check for dblp Knowledge Graph took 0.4445991516113281s
Understandability | URI regex check for dblp Knowledge Graph took 0.3013014793395996s
Understandability | Vocabs check for dblp Knowledge Graph took 0.14458942413330078s
Verifiability | Authors check for dblp Knowledge Graph took 0.15195918083190918s
Verifiability | Publishers check for dblp Knowledge Graph took 0.14645099639892578s
Performance | Throughput check for dblp Knowledge Graph took 10.719588279724121s
Amount of data | Check the number of entities for dblp Knowledge Graph took 7.009506225585938e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.14560961723327637s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.1581556797027588s
Interlinking | skos check for dblp Knowledge Graph took 0.16569280624389648s
Interlinking | skos check for dblp Knowledge Graph took 0.12220501899719238s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.14957213401794434s
Currency | Creation date check for dblp Knowledge Graph took 0.2763350009918213s
Currency | Modification date check for dblp Knowledge Graph took 0.31810569763183594s
Rep.Conc. | URIs length for dblp Knowledge Graph took 16.95177984237671s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.16168975830078125s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.1381547451019287s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.11894655227661133s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 6.8625876903533936s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.0866613388061523s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.138972759246826s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.1624772548675537s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.3119161128997803s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 5.526081562042236s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 17409.47729086876s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 5.162707090377808s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.6836371421813965s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.18318533897399902s
Security | Sign check for dblp Knowledge Graph took 0.15134811401367188s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 22.360551118850708s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.9212687015533447s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.0210418701171875s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.9788742065429688e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 1.9073486328125e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 1.2636184692382812e-05s
INFO | --- Analysis for dblp-kg took 17664.95842218399s
Availability | SPARQL endpoint availability check for dbnary took 0.26201748847961426s
Availability | VoID file availability check for dbnary took 0.0005502700805664062s
Extra | Recovery of all triples for dbnary took 1.0384235382080078s
Performance | Total latancy measurement for dbnary took 0.35966014862060547s
Amount of data | Number of triples check for dbnary took 1.4471423625946045s
Interoperability | New terms check for dbnary took 3.636418104171753s
Versatility | Languages check for dbnary took 61.28043723106384s
Interpretability | Number of blank nodes check for dbnary took 4.039352178573608s
Security | Check HTTPS for dbnary took 0.2225635051727295s
Interpretability | RDF structures check for dbnary took 0.15955758094787598s
Versatility | Serialization formats check for dbnary took 0.12743282318115234s
Availability | RDF dump link check for dbnary took 0.08466339111328125s
License | MR license check for dbnary took 0.24801254272460938s
License | HR license check for dbnary took 61.293967485427856s
Amount of data | Number of property check for dbnary took 0.0782155990600586s
Understandability | Number of label check for dbnary took 0.711555004119873s
Understandability | URI regex check for dbnary took 0.13305377960205078s
Understandability | Vocabs check for dbnary took 0.14728426933288574s
Verifiability | Authors check for dbnary took 0.26906251907348633s
Verifiability | Publishers check for dbnary took 0.14463257789611816s
Performance | Throughput check for dbnary took 10.431828737258911s
Amount of data | Check the number of entities for dbnary took 0.00010442733764648438s
Verifiability | Contribs. check for dbnary took 0.1724390983581543s
Interlinking | sameAs chians check for dbnary took 0.07030320167541504s
Interlinking | skos check for dbnary took 0.14643597602844238s
Interlinking | skos check for dbnary took 0.07022809982299805s
Timeliness | dataset update frequency check for dbnary took 0.12180566787719727s
Currency | Creation date check for dbnary took 0.2389533519744873s
Currency | Modification date check for dbnary took 0.17908692359924316s
Rep.Conc. | URIs length for dbnary took 11.22444462776184s
Interoperability | New vocabularies check for dbnary took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.07330656051635742s
Accuracy | Check Functional Property for dbnary took 0.1319732666015625s
Accuracy | Check Inverse Functional Property for dbnary took 0.1905536651611328s
Accuracy | Check Empty annotation labels for dbnary took 0.524773359298706s
Accuracy | Check White space in annotation for dbnary took 0.030745267868041992s
Accuracy | Check Datatype consistency for dbnary took 0.027524232864379883s
Consistency | Disjoint class check for dbnary took 0.16963648796081543s
Consistency | Check Misplaced properties for dbnary took 8.744152069091797s
Consistency | Misplaced classes for dbnary took 0.1997368335723877s
Consistency | Check Ontology hijacking for dbnary took 1.7442519664764404s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.3874938488006592s
Consistency | Check Invalid usage of undefined properties for dbnary took 10.02168345451355s
Conciseness | Check Extensional conciseness for dbnary took 0.03226518630981445s
Conciseness | Check Intensional conciseness for dbnary took 0.14392662048339844s
Security | Sign check for dbnary took 0.11262273788452148s
Availability | Check URIs Dereferenciability for dbnary took 15.558158874511719s
Completeness | Calculation of interlinking completeness for dbnary took 0.3691678047180176s
Reputation | Calculation of the PageRank for dbnary took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for dbnary took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for dbnary took 5.698204040527344e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.1920928955078125e-06s
Believability | Calculation of trust value for dbnary took 1.0251998901367188e-05s
INFO | --- Analysis for dbnary took 301.6484661102295s
Availability | SPARQL endpoint availability check for DBpedia took 0.893679141998291s
Availability | VoID file availability check for DBpedia took 0.0006148815155029297s
Extra | Recovery of all triples for DBpedia took 2.942467212677002s
Performance | Total latancy measurement for DBpedia took 2.7703487873077393s
Amount of data | Number of triples check for DBpedia took 1.0855214595794678s
Interoperability | New terms check for DBpedia took 4.893518447875977s
Versatility | Languages check for DBpedia took 31.549134254455566s
Interpretability | Number of blank nodes check for DBpedia took 0.5449464321136475s
Security | Check HTTPS for DBpedia took 0.7430787086486816s
Interpretability | RDF structures check for DBpedia took 1.2446320056915283s
Versatility | Serialization formats check for DBpedia took 0.6354460716247559s
Availability | RDF dump link check for DBpedia took 0.7594988346099854s
License | MR license check for DBpedia took 2.127955436706543s
License | HR license check for DBpedia took 32.60622572898865s
Amount of data | Number of property check for DBpedia took 0.5859508514404297s
Understandability | Number of label check for DBpedia took 2.8674023151397705s
Understandability | URI regex check for DBpedia took 2.35858416557312s
Understandability | Vocabs check for DBpedia took 0.9056105613708496s
Verifiability | Authors check for DBpedia took 1.8799996376037598s
Verifiability | Publishers check for DBpedia took 0.6443076133728027s
Performance | Throughput check for DBpedia took 11.268005847930908s
Amount of data | Check the number of entities for DBpedia took 9.393692016601562e-05s
Verifiability | Contribs. check for DBpedia took 0.5437495708465576s
Interlinking | sameAs chians check for DBpedia took 3.6167538166046143s
Interlinking | skos check for DBpedia took 1.043868064880371s
Interlinking | skos check for DBpedia took 0.5750253200531006s
Timeliness | dataset update frequency check for DBpedia took 0.6015546321868896s
Currency | Creation date check for DBpedia took 2.494130849838257s
Currency | Modification date check for DBpedia took 1.214554786682129s
Rep.Conc. | URIs length for DBpedia took 36.958786725997925s
Interoperability | New vocabularies check for DBpedia took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.5910956859588623s
Accuracy | Check Functional Property for DBpedia took 0.6069443225860596s
Accuracy | Check Inverse Functional Property for DBpedia took 0.6048779487609863s
Accuracy | Check Empty annotation labels for DBpedia took 4.321552515029907s
Accuracy | Check White space in annotation for DBpedia took 0.02908039093017578s
Accuracy | Check Datatype consistency for DBpedia took 0.028028488159179688s
Consistency | Disjoint class check for DBpedia took 0.5887773036956787s
Consistency | Check Misplaced properties for DBpedia took 33.898632287979126s
Consistency | Misplaced classes for DBpedia took 1.7283196449279785s
Consistency | Check Ontology hijacking for DBpedia took 3.7742815017700195s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.2851078510284424s
Consistency | Check Invalid usage of undefined properties for DBpedia took 2.3307769298553467s
Conciseness | Check Extensional conciseness for DBpedia took 0.031241655349731445s
Conciseness | Check Intensional conciseness for DBpedia took 1.9000356197357178s
Security | Sign check for DBpedia took 1.039320468902588s
Availability | Check URIs Dereferenciability for DBpedia took 2029.3079030513763s
Completeness | Calculation of interlinking completeness for DBpedia took 1.211582899093628s
Reputation | Calculation of the PageRank for DBpedia took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for DBpedia took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008780956268310547s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia took 2514.037422657013s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.4345855712890625e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.6918783187866211s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.628036499023438e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-abstract-corpus took 9.080825328826904s
Availability | SPARQL endpoint availability check for DBpedia Commons took 4.6372971534729s
Availability | VoID file availability check for DBpedia Commons took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.6994016170501709s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 8.034706115722656e-05s
Believability | Calculation of trust value for DBpedia Commons took 1.1682510375976562e-05s
INFO | --- Analysis for dbpedia-commons took 14.328534364700317s
Availability | SPARQL endpoint availability check for DBpedia in German took 7.653236389160156e-05s
Availability | VoID file availability check for DBpedia in German took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.28725767135620117s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.604194641113281e-05s
Believability | Calculation of trust value for DBpedia in German took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia-de took 3.757023572921753s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 0.8829588890075684s
Availability | VoID file availability check for DBpedia in Greek took 0.0003159046173095703s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.25621891021728516s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.0210263729095459s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.0001900196075439453s
Believability | Calculation of trust value for DBpedia in Greek took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-el took 6.922884702682495s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.41407299041748047s
Availability | VoID file availability check for DBpedia in Spanish took 0.0004968643188476562s
Extra | Recovery of all triples for DBpedia in Spanish took 2.811495304107666s
Performance | Total latancy measurement for DBpedia in Spanish took 1.2406342029571533s
Amount of data | Number of triples check for DBpedia in Spanish took 0.9333696365356445s
Interoperability | New terms check for DBpedia in Spanish took 2.8121278285980225s
Versatility | Languages check for DBpedia in Spanish took 61.406506299972534s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.4159395694732666s
Security | Check HTTPS for DBpedia in Spanish took 0.13863325119018555s
Interpretability | RDF structures check for DBpedia in Spanish took 0.9995255470275879s
Versatility | Serialization formats check for DBpedia in Spanish took 0.748744010925293s
Availability | RDF dump link check for DBpedia in Spanish took 0.3665170669555664s
License | MR license check for DBpedia in Spanish took 0.878685712814331s
License | HR license check for DBpedia in Spanish took 61.48526930809021s
Amount of data | Number of property check for DBpedia in Spanish took 0.316486120223999s
Understandability | Number of label check for DBpedia in Spanish took 1.6864697933197021s
Understandability | URI regex check for DBpedia in Spanish took 0.7445168495178223s
Understandability | Vocabs check for DBpedia in Spanish took 0.37132978439331055s
Verifiability | Authors check for DBpedia in Spanish took 0.29659175872802734s
Verifiability | Publishers check for DBpedia in Spanish took 0.27903318405151367s
Performance | Throughput check for DBpedia in Spanish took 12.822413444519043s
Amount of data | Check the number of entities for DBpedia in Spanish took 7.510185241699219e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.2891364097595215s
Interlinking | sameAs chians check for DBpedia in Spanish took 3.587858200073242s
Interlinking | skos check for DBpedia in Spanish took 0.7400758266448975s
Interlinking | skos check for DBpedia in Spanish took 0.2386777400970459s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.4712247848510742s
Currency | Creation date check for DBpedia in Spanish took 0.5766117572784424s
Currency | Modification date check for DBpedia in Spanish took 0.5781981945037842s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.710752248764038s
Interoperability | New vocabularies check for DBpedia in Spanish took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.2794203758239746s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.5135886669158936s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.4523754119873047s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.820960521697998s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.031029462814331055s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.028224468231201172s
Consistency | Disjoint class check for DBpedia in Spanish took 0.2718675136566162s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.027997970581055s
Consistency | Misplaced classes for DBpedia in Spanish took 1.1082804203033447s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.438474655151367s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.2625272274017334s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 6.87808895111084s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03359079360961914s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 4.366103649139404s
Security | Sign check for DBpedia in Spanish took 0.34326171875s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 15.803623914718628s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.3103501796722412s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.021078109741210938s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00011348724365234375s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-es took 1250.9008808135986s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.1176323890686035s
Availability | VoID file availability check for DBpedia in Basque took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.2562835216522217s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.504753112792969e-05s
Believability | Calculation of trust value for DBpedia in Basque took 8.58306884765625e-06s
INFO | --- Analysis for dbpedia-eu took 6.598188161849976s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.128798246383667s
Availability | VoID file availability check for DBpedia in French took 0.04695391654968262s
Extra | Recovery of all triples for DBpedia in French took 100.00224351882935s
Performance | Total latancy measurement for DBpedia in French took 0.3820068836212158s
Amount of data | Number of triples check for DBpedia in French took 2.3445920944213867s
Interoperability | New terms check for DBpedia in French took 2.439906358718872s
Versatility | Languages check for DBpedia in French took 300.036328792572s
Interpretability | Number of blank nodes check for DBpedia in French took 0.1900651454925537s
Security | Check HTTPS for DBpedia in French took 0.19703435897827148s
Interpretability | RDF structures check for DBpedia in French took 0.2642838954925537s
Versatility | Serialization formats check for DBpedia in French took 0.21747422218322754s
Availability | RDF dump link check for DBpedia in French took 6.676436185836792s
License | MR license check for DBpedia in French took 0.7519097328186035s
License | HR license check for DBpedia in French took 84.890793800354s
Amount of data | Number of property check for DBpedia in French took 0.09249162673950195s
Understandability | Number of label check for DBpedia in French took 1.2424850463867188s
Understandability | URI regex check for DBpedia in French took 0.20044302940368652s
Understandability | Vocabs check for DBpedia in French took 0.10174131393432617s
Verifiability | Authors check for DBpedia in French took 0.20805144309997559s
Verifiability | Publishers check for DBpedia in French took 0.09779787063598633s
Performance | Throughput check for DBpedia in French took 10.437114715576172s
Amount of data | Check the number of entities for DBpedia in French took 2.0143043994903564s
Verifiability | Contribs. check for DBpedia in French took 0.12770938873291016s
Interlinking | sameAs chians check for DBpedia in French took 0.2829265594482422s
Interlinking | skos check for DBpedia in French took 0.2729811668395996s
Interlinking | skos check for DBpedia in French took 0.06836295127868652s
Timeliness | dataset update frequency check for DBpedia in French took 0.4290173053741455s
Currency | Creation date check for DBpedia in French took 0.19324922561645508s
Currency | Modification date check for DBpedia in French took 0.16241145133972168s
Rep.Conc. | URIs length for DBpedia in French took 38.15357232093811s
Interoperability | New vocabularies check for DBpedia in French took 7.390607833862305s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.09776186943054199s
Accuracy | Check Functional Property for DBpedia in French took 0.09496140480041504s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.0924677848815918s
Accuracy | Check Empty annotation labels for DBpedia in French took 28.607974767684937s
Accuracy | Check White space in annotation for DBpedia in French took 3.111248254776001s
Accuracy | Check Datatype consistency for DBpedia in French took 2.6680800914764404s
Consistency | Disjoint class check for DBpedia in French took 0.108642578125s
Consistency | Check Misplaced properties for DBpedia in French took 7.697281837463379s
Consistency | Misplaced classes for DBpedia in French took 9.206138610839844s
Consistency | Check Ontology hijacking for DBpedia in French took 20.617623805999756s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.3116939067840576s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 9.75157618522644s
Conciseness | Check Extensional conciseness for DBpedia in French took 2.927711009979248s
Conciseness | Check Intensional conciseness for DBpedia in French took 1.0859627723693848s
Security | Sign check for DBpedia in French took 0.12908244132995605s
Availability | Check URIs Dereferenciability for DBpedia in French took 1057.6070392131805s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.35118603706359863s
Reputation | Calculation of the PageRank for DBpedia in French took 0.021872520446777344s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 6.151199340820312e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00016832351684570312s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 6.29170560836792s
Believability | Calculation of trust value for DBpedia in French took 1.0013580322265625e-05s
INFO | --- Analysis for dbpedia-fr took 1929.577675819397s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.901594877243042s
Availability | VoID file availability check for DBpedia in Japanese took 4.142434358596802s
Extra | Recovery of all triples for DBpedia in Japanese took 5.51902437210083s
Performance | Total latancy measurement for DBpedia in Japanese took 6.62345290184021s
Amount of data | Number of triples check for DBpedia in Japanese took 92.73063945770264s
Interoperability | New terms check for DBpedia in Japanese took 18.59307050704956s
Versatility | Languages check for DBpedia in Japanese took 1.3259687423706055s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3302631378173828s
Security | Check HTTPS for DBpedia in Japanese took 0.7985031604766846s
Interpretability | RDF structures check for DBpedia in Japanese took 1.392984390258789s
Versatility | Serialization formats check for DBpedia in Japanese took 1.3471124172210693s
Availability | RDF dump link check for DBpedia in Japanese took 1.329615592956543s
License | MR license check for DBpedia in Japanese took 1.3581509590148926s
License | HR license check for DBpedia in Japanese took 92.78951716423035s
Amount of data | Number of property check for DBpedia in Japanese took 1.3258180618286133s
Understandability | Number of label check for DBpedia in Japanese took 12.74997854232788s
Understandability | URI regex check for DBpedia in Japanese took 2.658541202545166s
Understandability | Vocabs check for DBpedia in Japanese took 1.3294739723205566s
Verifiability | Authors check for DBpedia in Japanese took 1.3439960479736328s
Verifiability | Publishers check for DBpedia in Japanese took 1.3310649394989014s
Performance | Throughput check for DBpedia in Japanese took 13.248317003250122s
Amount of data | Check the number of entities for DBpedia in Japanese took 7.104873657226562e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.347425937652588s
Interlinking | sameAs chians check for DBpedia in Japanese took 3.1209022998809814s
Interlinking | skos check for DBpedia in Japanese took 1.3632595539093018s
Interlinking | skos check for DBpedia in Japanese took 1.3252522945404053s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.3510751724243164s
Currency | Creation date check for DBpedia in Japanese took 2.678856134414673s
Currency | Modification date check for DBpedia in Japanese took 2.6696531772613525s
Rep.Conc. | URIs length for DBpedia in Japanese took 80.27440333366394s
Interoperability | New vocabularies check for DBpedia in Japanese took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.320021629333496s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.031839609146118164s
Consistency | Disjoint class check for DBpedia in Japanese took 1.3295016288757324s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.237461090087891s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.3368186950683594s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 94.3130271434784s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.03310990333557129s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 3.4879202842712402s
Security | Sign check for DBpedia in Japanese took 1.349731683731079s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 13.083136081695557s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.9569118022918701s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.020847082138061523s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010418891906738281s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-ja took 989.4534544944763s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.458427429199219e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006868839263916016s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.24224567413330078s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020776033401489258s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.822845458984375e-05s
Believability | Calculation of trust value for dbpedia lite took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-lite took 22.346424341201782s
Availability | SPARQL endpoint availability check for DBpedia-Live took 4.124641418457031e-05s
Availability | VoID file availability check for DBpedia-Live took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.27039027214050293s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.02077198028564453s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.123283386230469e-05s
Believability | Calculation of trust value for DBpedia-Live took 9.775161743164062e-06s
INFO | --- Analysis for dbpedia-live took 2.7871503829956055s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.24040746688842773s
Availability | VoID file availability check for DBpedia in Dutch took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.26156115531921387s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.02200007438659668s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00018548965454101562s
Believability | Calculation of trust value for DBpedia in Dutch took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-nl took 3.2135250568389893s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 30.037861585617065s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.31010937690734863s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020544767379760742s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.368492126464844e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-pt took 52.02291440963745s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 3.981590270996094e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.2630493640899658s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.022861957550048828s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.075599670410156e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 1.2159347534179688e-05s
INFO | --- Analysis for dbpedia-spotlight took 2.8530802726745605s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.291534423828125e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.2533423900604248s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.021785259246826172s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0006840229034423828s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.723403930664062e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.1682510375976562e-05s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 13.548826694488525s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.124641418457031e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.2618865966796875s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.020319223403930664s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 2.9325485229492188e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 1.1920928955078125e-05s
INFO | --- Analysis for dbpedia-wikidata took 2.8953869342803955s
Availability | SPARQL endpoint availability check for DBpedia took 4.076957702636719e-05s
Availability | VoID file availability check for DBpedia took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for DBpedia took 0.2418994903564453s
Reputation | Calculation of the PageRank for DBpedia took 0.02032923698425293s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for DBpedia took 2.8848648071289062e-05s
Believability | Calculation of trust value for DBpedia took 1.1920928955078125e-05s
INFO | --- Analysis for dbpedia_ took 2.8301217555999756s
Availability | SPARQL endpoint availability check for DBTropes took 4.839897155761719e-05s
Availability | VoID file availability check for DBTropes took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for DBTropes took 0.2534487247467041s
Reputation | Calculation of the PageRank for DBTropes took 0.02034783363342285s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for DBTropes took 8.96453857421875e-05s
Believability | Calculation of trust value for DBTropes took 1.1920928955078125e-05s
INFO | --- Analysis for dbtropes took 2.9056997299194336s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.076957702636719e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.23566055297851562s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.020383358001708984s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.5762786865234375e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 1.0967254638671875e-05s
INFO | --- Analysis for dbtune took 2.907090187072754s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 9.72747802734375e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.2798960208892822s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.3882598876953125e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 1.0967254638671875e-05s
INFO | --- Analysis for dbtune-artists-last-fm took 4.3213489055633545s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 8.368492126464844e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.24737787246704102s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.02067875862121582s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.504753112792969e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.2159347534179688e-05s
INFO | --- Analysis for dbtune-audioscrobbler took 3.1922788619995117s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.482905864715576s
Availability | VoID file availability check for DBTune.org/classical took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.27587461471557617s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.02084517478942871s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.62939453125e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.1444091796875e-05s
INFO | --- Analysis for dbtune-classical took 8.638585329055786s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.506129503250122s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.253145694732666s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.02053070068359375s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.556510925292969e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 6.4373016357421875e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 11.061043500900269s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 5.482670783996582s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.25100255012512207s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.020182371139526367s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.365776062011719e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.0967254638671875e-05s
INFO | --- Analysis for dbtune-magnatune took 9.4887375831604s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 180.40548944473267s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0007827281951904297s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.41100621223449707s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.020814180374145508s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00011897087097167969s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.1682510375976562e-05s
INFO | --- Analysis for dbtune-musicbrainz took 433.5266737937927s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.3158144950866699s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.24911952018737793s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020804166793823242s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.245208740234375e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.2159347534179688e-05s
INFO | --- Analysis for dbtune-myspace took 3.046426773071289s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.076957702636719e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.28995180130004883s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.020576953887939453s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 2.956390380859375e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 1.2159347534179688e-05s
INFO | --- Analysis for dclg-openuplabs took 2.9617726802825928s
Availability | SPARQL endpoint availability check for data.dcs took 6.771087646484375e-05s
Availability | VoID file availability check for data.dcs took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for data.dcs took 0.26175546646118164s
Reputation | Calculation of the PageRank for data.dcs took 0.02080845832824707s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.628036499023438e-05s
Believability | Calculation of trust value for data.dcs took 1.2874603271484375e-05s
INFO | --- Analysis for dcs-sheffield took 2.554197311401367s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.076957702636719e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.25286197662353516s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020807266235351562s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0010454654693603516s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 3.695487976074219e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 1.33514404296875e-05s
INFO | --- Analysis for de-budget took 2.8429031372070312s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.5299530029296875e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2473280429840088s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.0226590633392334s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.647804260253906e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 1.239776611328125e-05s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.717554569244385s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 0.00010085105895996094s
Availability | VoID file availability check for Debian Package Tracking System took 0.0010476112365722656s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.2821211814880371s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020551681518554688s
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.0021331310272216797s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.982948303222656e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 7.867813110351562e-06s
INFO | --- Analysis for debian-package-tracking-system took 4.457774639129639s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 4.220008850097656e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.24293303489685059s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.170967102050781e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.33514404296875e-05s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.8505911827087402s
Availability | SPARQL endpoint availability check for Demografie took 4.4345855712890625e-05s
Availability | VoID file availability check for Demografie took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Demografie took 0.26047539710998535s
Reputation | Calculation of the PageRank for Demografie took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for Demografie took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Demografie took 3.361701965332031e-05s
Believability | Calculation of trust value for Demografie took 1.239776611328125e-05s
INFO | --- Analysis for demografie took 2.848202705383301s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.2438507080078125e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.25449180603027344s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.02066183090209961s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.647804260253906e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.2636184692382812e-05s
INFO | --- Analysis for desaparecidos took 2.703397035598755s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.220008850097656e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.00036144256591796875s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.2517049312591553s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.846687316894531e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 7.867813110351562e-06s
INFO | --- Analysis for deustoentrepreneurship took 4.759207010269165s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.267692565917969e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.24502348899841309s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.02051377296447754s
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.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.000102996826171875s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 7.62939453125e-06s
INFO | --- Analysis for deustotech took 9.896363258361816s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.476808786392212s
Availability | VoID file availability check for Deutsche Biographie took 0.0004162788391113281s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.2866373062133789s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.020760536193847656s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.9577484130859375e-05s
Believability | Calculation of trust value for Deutsche Biographie took 7.62939453125e-06s
INFO | --- Analysis for deutsche-biographie took 4.365836143493652s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 4.482269287109375e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2445974349975586s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.02166008949279785s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.650520324707031e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.1920928955078125e-05s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 7.667581558227539s
Availability | SPARQL endpoint availability check for dev8d took 0.0001232624053955078s
Availability | VoID file availability check for dev8d took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for dev8d took 0.30662083625793457s
Reputation | Calculation of the PageRank for dev8d took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for dev8d took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for dev8d took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.723403930664062e-05s
Believability | Calculation of trust value for dev8d took 8.344650268554688e-06s
INFO | --- Analysis for dev8d took 3.591634750366211s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.126494884490967s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.27833008766174316s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.02089214324951172s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.841255187988281e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.7404556274414062e-05s
INFO | --- Analysis for dewey_decimal_classification took 92.72479701042175s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 5.030632019042969e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0004076957702636719s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.27280378341674805s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.020334482192993164s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 2.8848648071289062e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 7.62939453125e-06s
INFO | --- Analysis for DHSVM took 32.49977374076843s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.363059997558594e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.24607062339782715s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 2.9325485229492188e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 8.106231689453125e-06s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 2.779284954071045s
Availability | SPARQL endpoint availability check for Diavgeia took 4.673004150390625e-05s
Availability | VoID file availability check for Diavgeia took 0.0003898143768310547s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.2444469928741455s
Reputation | Calculation of the PageRank for Diavgeia took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.225440979003906e-05s
Believability | Calculation of trust value for Diavgeia took 5.0067901611328125e-06s
INFO | --- Analysis for diavgeia took 5.335971832275391s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 5.5789947509765625e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00034356117248535156s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.26642584800720215s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011396408081054688s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for didactalia took 9.127540111541748s
Availability | SPARQL endpoint availability check for diigo.feed took 8.130073547363281e-05s
Availability | VoID file availability check for diigo.feed took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.247514009475708s
Reputation | Calculation of the PageRank for diigo.feed took 0.02084207534790039s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 2.956390380859375e-05s
Believability | Calculation of trust value for diigo.feed took 7.152557373046875e-06s
INFO | --- Analysis for diigo-feed took 2.9463603496551514s
Availability | SPARQL endpoint availability check for DisGeNET took 1.9391131401062012s
Availability | VoID file availability check for DisGeNET took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.26277732849121094s
Reputation | Calculation of the PageRank for DisGeNET took 0.021068334579467773s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015783309936523438s
Believability | Calculation of trust value for DisGeNET took 1.33514404296875e-05s
INFO | --- Analysis for disgenet took 7.821300745010376s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.1961669921875e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.27765750885009766s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.020871877670288086s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 3.528594970703125e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 1.0251998901367188e-05s
INFO | --- Analysis for disk took 2.8823604583740234s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 8.344650268554688e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.32180261611938477s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.020493507385253906s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 3.147125244140625e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 9.5367431640625e-06s
INFO | --- Analysis for distritos-zaragoza took 2.877030849456787s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 8.487701416015625e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2732698917388916s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.022619247436523438s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.0040740966796875e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.239776611328125e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 7.5977678298950195s
Availability | SPARQL endpoint availability check for DM2E took 8.630752563476562e-05s
Availability | VoID file availability check for DM2E took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for DM2E took 0.25751185417175293s
Reputation | Calculation of the PageRank for DM2E took 0.020696401596069336s
Interlinking | Calculation of Degree of Connection for DM2E took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.0001087188720703125s
Believability | Calculation of trust value for DM2E took 9.298324584960938e-06s
INFO | --- Analysis for dm2e took 2.9742040634155273s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.100799560546875e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.2879481315612793s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.075599670410156e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 9.775161743164062e-06s
INFO | --- Analysis for dmoz_rdf_dump took 2.914137840270996s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 7.62939453125e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.31392788887023926s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020966053009033203s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00015616416931152344s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 1.1682510375976562e-05s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 7.693633317947388s
Availability | SPARQL endpoint availability check for DOAP Store took 4.1961669921875e-05s
Availability | VoID file availability check for DOAP Store took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.26757001876831055s
Reputation | Calculation of the PageRank for DOAP Store took 0.021923542022705078s
Interlinking | Calculation of Degree of Connection for DOAP Store took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 3.504753112792969e-05s
Believability | Calculation of trust value for DOAP Store took 1.049041748046875e-05s
INFO | --- Analysis for doap_store took 2.931666374206543s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 8.535385131835938e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.25461554527282715s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.29425048828125e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 5.245208740234375e-06s
INFO | --- Analysis for doi took 7.20441198348999s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.1484832763671875e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.2591378688812256s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.02111077308654785s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.0994415283203125e-05s
Believability | Calculation of trust value for Driggu Florentino took 1.0728836059570312e-05s
INFO | --- Analysis for Driggu took 4.487416982650757s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 6.230642557144165s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.2393934726715088s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.838539123535156e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.2159347534179688e-05s
INFO | --- Analysis for drug-data-hifm took 36.1389479637146s
Availability | SPARQL endpoint availability check for dspace took 8.416175842285156e-05s
Availability | VoID file availability check for dspace took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for dspace took 0.2420942783355713s
Reputation | Calculation of the PageRank for dspace took 0.02280116081237793s
Interlinking | Calculation of Degree of Connection for dspace took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for dspace took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for dspace took 3.361701965332031e-05s
Believability | Calculation of trust value for dspace took 1.2874603271484375e-05s
INFO | --- Analysis for dspace took 2.785399913787842s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 4.220008850097656e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.23679661750793457s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.02194046974182129s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.314018249511719e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 1.3589859008789062e-05s
INFO | --- Analysis for duraark-linked-building-data took 2.8744449615478516s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.81263422966003s
Availability | VoID file availability check for MetaLex Document Server took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.25412583351135254s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.020631074905395508s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.886222839355469e-05s
Believability | Calculation of trust value for MetaLex Document Server took 1.52587890625e-05s
INFO | --- Analysis for dutch-national-regulations-metalex took 555.1584899425507s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.3126516342163086s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.2755770683288574s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.021586894989013672s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.647804260253906e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 1.0251998901367188e-05s
INFO | --- Analysis for dutch-ships-and-sailors took 13.98574948310852s
Availability | SPARQL endpoint availability check for DWS-Group took 4.267692565917969e-05s
Availability | VoID file availability check for DWS-Group took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.24603676795959473s
Reputation | Calculation of the PageRank for DWS-Group took 0.02214193344116211s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010085105895996094s
Believability | Calculation of trust value for DWS-Group took 1.0967254638671875e-05s
INFO | --- Analysis for dws-group took 2.503262758255005s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.172325134277344e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.26055121421813965s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.020777225494384766s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.0994415283203125e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 9.5367431640625e-06s
INFO | --- Analysis for E1 took 4.131403207778931s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.07599115371704102s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.2460477352142334s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020943880081176758s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.0001201629638671875s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i-alaska took 2.513270616531372s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.04282402992248535s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.2897355556488037s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.5789947509765625e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-cau took 2.505035400390625s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.052634477615356445s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.2575085163116455s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.02102375030517578s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.437301635742188e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 9.5367431640625e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.3961384296417236s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.04137444496154785s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.26717233657836914s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.918212890625e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 9.298324584960938e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.4868996143341064s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.05422043800354004s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.00042510032653808594s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.2550477981567383s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.020609617233276367s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00013494491577148438s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.0013580322265625e-05s
INFO | --- Analysis for eagle-i-dartmouth took 2.468278169631958s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.04586672782897949s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004241466522216797s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.262648344039917s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.487701416015625e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-famu took 2.4547362327575684s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.04846382141113281s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.25630640983581543s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.022053956985473633s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00013184547424316406s
Believability | Calculation of trust value for eagle-i @ Harvard University took 2.6702880859375e-05s
INFO | --- Analysis for eagle-i-harvard took 2.4423606395721436s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.051399946212768555s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.23588919639587402s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.021240234375s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00013256072998046875s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i-hawaii took 2.4654905796051025s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.043089866638183594s
Availability | VoID file availability check for eagle-i @ Howard University took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.2978496551513672s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.022710084915161133s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.771087646484375e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-howard took 2.499671459197998s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.04168224334716797s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.2358543872833252s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.818771362304688e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.4626829624176025s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.03499913215637207s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.2652311325073242s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020483016967773438s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011420249938964844s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.0013580322265625e-05s
INFO | --- Analysis for eagle-i-jsu took 2.465456962585449s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.04302072525024414s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.23664212226867676s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.02219223976135254s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.838539123535156e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-meharry took 2.764846086502075s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.033966779708862305s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.40991687774658203s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.775161743164062e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i-montana took 2.8270537853240967s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.04147791862487793s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.2891812324523926s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.584426879882812e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-msm took 2.5602846145629883s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.03959846496582031s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0007526874542236328s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2736480236053467s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.0001266002655029297s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i-ohsu took 2.5456535816192627s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.048052310943603516s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.24953341484069824s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.67572021484375e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-psm took 2.4436018466949463s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.0471348762512207s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.00042629241943359375s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.2658054828643799s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020589828491210938s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.747245788574219e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-tsu took 2.4292736053466797s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.039040327072143555s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2630784511566162s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020926713943481445s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.532669067382812e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i-tuskegee took 2.3907740116119385s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.047360897064208984s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.2629880905151367s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.02201366424560547s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 9.965896606445312e-05s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-uccaribe took 2.4439308643341064s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.04018139839172363s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.2765390872955322s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.020979881286621094s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0001239776611328125s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-upr took 2.493544816970825s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.06517601013183594s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.26315951347351074s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.198883056640625e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 9.5367431640625e-06s
INFO | --- Analysis for eagle-i-utep took 2.4823174476623535s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.044677734375s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.24371838569641113s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020902633666992188s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 6.914138793945312e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.430511474609375e-05s
INFO | --- Analysis for eagle-i-utsa took 2.5017049312591553s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.17717385292053223s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.23660039901733398s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.020594120025634766s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.250640869140625e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 9.775161743164062e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.577688217163086s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.03938627243041992s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.29183459281921387s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020778894424438477s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.557868957519531e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 1.0251998901367188e-05s
INFO | --- Analysis for eagle-i-xula took 2.4608967304229736s
Availability | SPARQL endpoint availability check for Emergency situation took 0.6109621524810791s
Availability | VoID file availability check for Emergency situation took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.26781749725341797s
Reputation | Calculation of the PageRank for Emergency situation took 0.02036881446838379s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.9114227294921875e-05s
Believability | Calculation of trust value for Emergency situation took 1.0967254638671875e-05s
INFO | --- Analysis for Earthquake took 3.6913039684295654s
Availability | SPARQL endpoint availability check for ESO took 0.4845426082611084s
Availability | VoID file availability check for ESO took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for ESO took 0.32173848152160645s
Reputation | Calculation of the PageRank for ESO took 0.021515607833862305s
Interlinking | Calculation of Degree of Connection for ESO took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for ESO took 7.939338684082031e-05s
Believability | Calculation of trust value for ESO took 1.0251998901367188e-05s
INFO | --- Analysis for Earthquake_case took 4.1043736934661865s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.0736684799194336s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.26942896842956543s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020534753799438477s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 9.870529174804688e-05s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for ecb-linked-data took 2.4603846073150635s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 5.6451146602630615s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.26013755798339844s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.021823644638061523s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 4.00543212890625e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 8.821487426757812e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 13.17796778678894s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 5.347274303436279s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.32343053817749023s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.02090287208557129s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.914138793945312e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for ecco-tcp-linked-data took 13.055010318756104s
Availability | SPARQL endpoint availability check for ECLAP took 20.62863826751709s
Availability | VoID file availability check for ECLAP took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for ECLAP took 0.28055381774902344s
Reputation | Calculation of the PageRank for ECLAP took 0.02071356773376465s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0009102821350097656s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.5299530029296875e-05s
Believability | Calculation of trust value for ECLAP took 1.2159347534179688e-05s
INFO | --- Analysis for eclap took 53.04680585861206s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 5.030632019042969e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.27364635467529297s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.02151012420654297s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.1920928955078125e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.3828277587890625e-05s
INFO | --- Analysis for ECNU-GISer took 3.9189229011535645s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 5.698204040527344e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2839839458465576s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020452022552490234s
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.0006833076477050781s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.459785461425781e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.2159347534179688e-05s
INFO | --- Analysis for ecs took 2.5468616485595703s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 8.487701416015625e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.24646878242492676s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.147125244140625e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 1.239776611328125e-05s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.945666551589966s
Availability | SPARQL endpoint availability check for Edublogs took 0.00010156631469726562s
Availability | VoID file availability check for Edublogs took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Edublogs took 0.27680516242980957s
Reputation | Calculation of the PageRank for Edublogs took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.655952453613281e-05s
Believability | Calculation of trust value for Edublogs took 1.1682510375976562e-05s
INFO | --- Analysis for edublogs took 3.283916711807251s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.6068418025970459s
Availability | VoID file availability check for education.data.gov.uk took 0.0006730556488037109s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.2602674961090088s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.021967649459838867s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 3.910064697265625e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.988380432128906e-05s
Believability | Calculation of trust value for education.data.gov.uk took 8.58306884765625e-06s
INFO | --- Analysis for education-data-gov-uk took 4.774296045303345s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 6.842613220214844e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.24978113174438477s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.075599670410156e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 1.430511474609375e-05s
INFO | --- Analysis for education-openuplabs took 2.935224771499634s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.37873911857605s
Availability | VoID file availability check for Educational programs - SISVU took 0.0011968612670898438s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.40293002128601074s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.021059274673461914s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 6.175041198730469e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 9.5367431640625e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1320.6457750797272s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 1.0745494365692139s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.2655019760131836s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.027743816375732422s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.029273986816406e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 8.821487426757812e-06s
INFO | --- Analysis for eea took 10.463090419769287s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.468231201171875s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.6912992000579834s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020417213439941406s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.173683166503906e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 7.867813110351562e-06s
INFO | --- Analysis for eea-rod took 6.486830472946167s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.181013822555542s
Availability | VoID file availability check for EEA Vocabularies took 0.0013580322265625s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.2786707878112793s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.021833419799804688s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.106231689453125e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.239776611328125e-05s
INFO | --- Analysis for eea-vocabularies took 5.52931022644043s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 8.368492126464844e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.2489488124847412s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.021138429641723633s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.337860107421875e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 1.2636184692382812e-05s
INFO | --- Analysis for ege-university-linked-open-data took 2.893435001373291s
Availability | SPARQL endpoint availability check for E-Government Ontology took 1.6735172271728516s
Availability | VoID file availability check for E-Government Ontology took 0.0003192424774169922s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.33832693099975586s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.021062612533569336s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for EGovOntology took 5.347100734710693s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4571237564086914s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0005362033843994141s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 3.1694273948669434s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.322098731994629s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6901028156280518s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9294230937957764s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.347535848617554s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 5.777925729751587s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6452984809875488s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8008878231048584s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.25672221183776855s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.48870062828063965s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 7.0389745235443115s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.27895665168762207s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3633718490600586s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5953073501586914s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3171505928039551s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3460044860839844s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.25623440742492676s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 10.857184886932373s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 0.00010895729064941406s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3601961135864258s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2643616199493408s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.42884230613708496s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23800206184387207s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2951939105987549s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8852229118347168s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24974918365478516s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 6.382654666900635s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.27499985694885254s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2910497188568115s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.29859352111816406s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.05391526222229s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.029803752899169922s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0283811092376709s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.26514267921447754s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.487413644790649s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4410107135772705s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.5036168098449707s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2908740043640137s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.350181341171265s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03308725357055664s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.450528621673584s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4134078025817871s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3129.853623151779s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5245013236999512s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.021266937255859375s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.6689300537109375e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 8.344650268554688e-06s
INFO | --- Analysis for ei2a took 3401.8344025611877s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 5.2928924560546875e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0003666877746582031s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.2356877326965332s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010347366333007812s
Believability | Calculation of trust value for EIONET RDF Data took 5.245208740234375e-06s
INFO | --- Analysis for eionet-rdf took 2.9099841117858887s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 5.4836273193359375e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.25913047790527344s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.0205843448638916s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.0279159545898438e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 6.67572021484375e-06s
INFO | --- Analysis for ElgooG_ took 2.3324451446533203s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 4.1961669921875e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.2599062919616699s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.02105402946472168s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 2.86102294921875e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 6.9141387939453125e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 2.8527650833129883s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.19158935546875s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.2637324333190918s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 8.273124694824219e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.1205673217773438e-05s
INFO | --- Analysis for elviajero took 19.22069239616394s
Availability | SPARQL endpoint availability check for EMN took 8.845329284667969e-05s
Availability | VoID file availability check for EMN took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for EMN took 0.26970410346984863s
Reputation | Calculation of the PageRank for EMN took 0.02315998077392578s
Interlinking | Calculation of Degree of Connection for EMN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EMN took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for EMN took 4.267692565917969e-05s
Believability | Calculation of trust value for EMN took 1.049041748046875e-05s
INFO | --- Analysis for emn took 2.7488484382629395s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.2502021789550781s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020277976989746094s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 4.982948303222656e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 8.106231689453125e-06s
INFO | --- Analysis for enakting-co2emission took 2.3974132537841797s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 0.00010395050048828125s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.27131223678588867s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.020274877548217773s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 3.814697265625e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 9.059906005859375e-06s
INFO | --- Analysis for enakting-crime took 2.667344570159912s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 8.654594421386719e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.2748594284057617s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.02240777015686035s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.0531158447265625e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 8.344650268554688e-06s
INFO | --- Analysis for enakting-energy took 2.4655649662017822s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.263934850692749s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.655952453613281e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 8.344650268554688e-06s
INFO | --- Analysis for enakting-mortality took 2.374603509902954s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.2701148986816406s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.719329833984375e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 4.5299530029296875e-06s
INFO | --- Analysis for enakting-nhs took 2.3897457122802734s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.2636229991912842s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020586252212524414s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.173683166503906e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 4.76837158203125e-06s
INFO | --- Analysis for enakting-population took 2.4119832515716553s
Availability | SPARQL endpoint availability check for Enel Shops took 4.696846008300781e-05s
Availability | VoID file availability check for Enel Shops took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.2565946578979492s
Reputation | Calculation of the PageRank for Enel Shops took 0.020529747009277344s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.075599670410156e-05s
Believability | Calculation of trust value for Enel Shops took 1.239776611328125e-05s
INFO | --- Analysis for enel-shops took 2.8769590854644775s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.00543212890625e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.2708604335784912s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 2.86102294921875e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 6.4373016357421875e-06s
INFO | --- Analysis for energy-efficiency took 2.8850183486938477s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 3.9577484130859375e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.2756361961364746s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.02073979377746582s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.218650817871094e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 1.0013580322265625e-05s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 2.8885738849639893s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 3.981590270996094e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.2602856159210205s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.020277976989746094s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 2.86102294921875e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 1.049041748046875e-05s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 2.8641812801361084s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.2539958953857422s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.021221637725830078s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 3.147125244140625e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 1.0967254638671875e-05s
INFO | --- Analysis for english-heritage-components-thesaurus took 2.904266357421875s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 8.487701416015625e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.24664926528930664s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.020493507385253906s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 7.414817810058594e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 2.9087066650390625e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 1.1205673217773438e-05s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.8410487174987793s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 4.076957702636719e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.24718141555786133s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.020482778549194336s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 3.4332275390625e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 1.0728836059570312e-05s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 2.834554433822632s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 8.487701416015625e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.24699902534484863s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.021663188934326172s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 3.123283386230469e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 1.1682510375976562e-05s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.8333687782287598s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 4.029273986816406e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.3129875659942627s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.02288818359375s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 3.814697265625e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 2.9802322387695312e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 1.0967254638671875e-05s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 2.950324535369873s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.531381368637085s
Availability | VoID file availability check for English Heritage Periods List took 0.000804901123046875s
Extra | Recovery of all triples for English Heritage Periods List took 0.3878653049468994s
Performance | Total latancy measurement for English Heritage Periods List took 1.6247100830078125s
Amount of data | Number of triples check for English Heritage Periods List took 0.5149998664855957s
Versatility | Languages check for English Heritage Periods List took 0.2649705410003662s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.5004298686981201s
Security | Check HTTPS for English Heritage Periods List took 0.2654702663421631s
Interpretability | RDF structures check for English Heritage Periods List took 0.29027795791625977s
Versatility | Serialization formats check for English Heritage Periods List took 0.4931924343109131s
Availability | RDF dump link check for English Heritage Periods List took 0.30236172676086426s
License | MR license check for English Heritage Periods List took 0.41805005073547363s
License | HR license check for English Heritage Periods List took 0.3609778881072998s
Amount of data | Number of property check for English Heritage Periods List took 0.36395931243896484s
Understandability | Number of label check for English Heritage Periods List took 0.44698119163513184s
Understandability | URI regex check for English Heritage Periods List took 0.634361743927002s
Understandability | Vocabs check for English Heritage Periods List took 0.41486263275146484s
Verifiability | Authors check for English Heritage Periods List took 0.41384196281433105s
Verifiability | Publishers check for English Heritage Periods List took 0.3687291145324707s
Performance | Throughput check for English Heritage Periods List took 12.782792568206787s
Amount of data | Check the number of entities for English Heritage Periods List took 7.033348083496094e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.38774943351745605s
Interlinking | sameAs chians check for English Heritage Periods List took 0.4061136245727539s
Interlinking | skos check for English Heritage Periods List took 0.48114728927612305s
Interlinking | skos check for English Heritage Periods List took 0.34288740158081055s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.4623098373413086s
Currency | Creation date check for English Heritage Periods List took 0.6693501472473145s
Currency | Modification date check for English Heritage Periods List took 0.7206261157989502s
Rep.Conc. | URIs length for English Heritage Periods List took 0.6340939998626709s
Interoperability | New vocabularies check for English Heritage Periods List took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.33194708824157715s
Accuracy | Check Functional Property for English Heritage Periods List took 0.3171272277832031s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.31596875190734863s
Consistency | Disjoint class check for English Heritage Periods List took 0.43473052978515625s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.31604719161987305s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.6591269969940186s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0001442432403564453s
Security | Sign check for English Heritage Periods List took 0.4354989528656006s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.25869154930114746s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 4.00543212890625e-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.1920928955078125e-05s
INFO | --- Analysis for english-heritage-periods-list took 65.88781404495239s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.3811988830566406s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0006952285766601562s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 0.8262901306152344s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 1.0255870819091797s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.29357314109802246s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.5205731391906738s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.4535961151123047s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 30.161562204360962s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.12052297592163086s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.25311708450317383s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.12616515159606934s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 48.96214771270752s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.23479151725769043s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.21572995185852s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.23462390899658203s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.2671778202056885s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.2667572498321533s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.21513605117797852s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.13909173011779785s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.4367043972015381s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 11.735631465911865s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 7.43865966796875e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.13939428329467773s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.5234458446502686s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.28287816047668457s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.13866925239562988s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.21431994438171387s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.36931443214416504s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.24823546409606934s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 1.3571453094482422s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.15415048599243164s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.14900684356689453s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.1473395824432373s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.23461413383483887s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 0.5317320823669434s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 1.4635639190673828s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.563323974609375s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.000141143798828125s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.3435540199279785s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.14878368377685547s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.2804546356201172s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 4.506111145019531e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.430511474609375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 8.58306884765625e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 269.1426610946655s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.142991304397583s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0006461143493652344s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 0.7649059295654297s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.805140495300293s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.13942503929138184s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.5075819492340088s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.4178180694580078s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 30.173261404037476s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.1681971549987793s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.21989035606384277s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.20434856414794922s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 46.72433257102966s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.21006155014038086s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.171754121780396s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.1496415138244629s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.20516443252563477s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.3618454933166504s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.14581847190856934s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.1504056453704834s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.39181089401245117s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 11.178542137145996s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 6.961822509765625e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.22038745880126953s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.18813180923461914s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.13318634033203125s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.12715840339660645s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.3257870674133301s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.3507120609283447s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.2122499942779541s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.1542043685913086s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.15051698684692383s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.15259122848510742s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.13896465301513672s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.14286279678344727s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.5019073486328125s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 1.061311960220337s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.514000415802002s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.00016355514526367188s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.22509098052978516s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.14432311058044434s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.3553578853607178s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.021435976028442383s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 4.220008850097656e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Score 2010 took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 1.0967254638671875e-05s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 262.0597403049469s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.172325134277344e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.2669250965118408s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.023447751998901367s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 3.123283386230469e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 1.1682510375976562e-05s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 2.922314405441284s
Availability | SPARQL endpoint availability check for English WordNet took 8.749961853027344e-05s
Availability | VoID file availability check for English WordNet took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for English WordNet took 0.2577853202819824s
Reputation | Calculation of the PageRank for English WordNet took 0.022759675979614258s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.5762786865234375e-05s
Believability | Calculation of trust value for English WordNet took 1.1205673217773438e-05s
INFO | --- Analysis for english-wordnet took 3.045428514480591s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.100799560546875e-05s
Availability | VoID file availability check for English Heritage Places took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.2527792453765869s
Reputation | Calculation of the PageRank for English Heritage Places took 0.020362377166748047s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 3.170967102050781e-05s
Believability | Calculation of trust value for English Heritage Places took 1.2159347534179688e-05s
INFO | --- Analysis for englishheritage_places took 2.906825304031372s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.18731069564819336s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.2772257328033447s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.02119159698486328s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 8.940696716308594e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.1444091796875e-05s
INFO | --- Analysis for enipedia took 2.6550095081329346s
Availability | SPARQL endpoint availability check for Enslaved.org took 8.392333984375e-05s
Availability | VoID file availability check for Enslaved.org took 0.001322031021118164s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.26466894149780273s
Reputation | Calculation of the PageRank for Enslaved.org took 0.021482467651367188s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.24249267578125e-05s
Believability | Calculation of trust value for Enslaved.org took 1.1444091796875e-05s
INFO | --- Analysis for enslaved.org took 4.628404378890991s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.5153524875640869s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.2594425678253174s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020602703094482422s
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.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.3882598876953125e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 1.1920928955078125e-05s
INFO | --- Analysis for entice-graph took 3.2279481887817383s
Availability | SPARQL endpoint availability check for Entrez Gene took 8.606910705566406e-05s
Availability | VoID file availability check for Entrez Gene took 0.0008578300476074219s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.25443172454833984s
Reputation | Calculation of the PageRank for Entrez Gene took 0.020644664764404297s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.910064697265625e-05s
Believability | Calculation of trust value for Entrez Gene took 1.1444091796875e-05s
INFO | --- Analysis for entrez_gene took 27.511099576950073s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 8.368492126464844e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.26825523376464844s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0008833408355712891s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 4.57763671875e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 1.239776611328125e-05s
INFO | --- Analysis for entrez_gene_extract took 2.912600517272949s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 0.9798521995544434s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.2537078857421875s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.1021575927734375e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 7.62939453125e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 11.482029438018799s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.2982211112976074s
Availability | VoID file availability check for environment.data.gov.uk took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.3019747734069824s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020855188369750977s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.887580871582031e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 8.106231689453125e-06s
INFO | --- Analysis for environment-data-gov-uk took 9.731145143508911s
Availability | SPARQL endpoint availability check for EARTh took 270.83993649482727s
Availability | VoID file availability check for EARTh took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for EARTh took 0.25002169609069824s
Reputation | Calculation of the PageRank for EARTh took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for EARTh took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for EARTh took 9.72747802734375e-05s
Believability | Calculation of trust value for EARTh took 1.0728836059570312e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 560.311133146286s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.33905458450317383s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0004799365997314453s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 143.36823225021362s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 1.0381667613983154s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 11.193701982498169s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 14.051333904266357s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.1937475204468s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.108004093170166s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.3064136505126953s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 12.811427354812622s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.27588629722595215s
License | MR license check for Micka (EO metadata) @PSNC took 0.7395079135894775s
License | HR license check for Micka (EO metadata) @PSNC took 300.23436641693115s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.2093064785003662s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 1.6358273029327393s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 0.7539410591125488s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.3403489589691162s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.22448062896728516s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.2535820007324219s
Performance | Throughput check for Micka (EO metadata) @PSNC took 11.47217845916748s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 0.00010800361633300781s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.19854331016540527s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.20043253898620605s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4890286922454834s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.43700695037841797s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 5.138153791427612s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.4930241107940674s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.23591399192810059s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 172.7825174331665s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.21541285514831543s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.45072078704833984s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.27788758277893066s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 40.83111906051636s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.6682558059692383s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.595874071121216s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.19977307319641113s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 88.34095811843872s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.218260765075684s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 40.632363080978394s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.3271405696868896s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 87.77466344833374s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.674088478088379s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.5067996978759766s
Security | Sign check for Micka (EO metadata) @PSNC took 1.114522933959961s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 14.253237247467041s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.3114809989929199s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.021635770797729492s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 4.3392181396484375e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 1.0013580322265625e-05s
INFO | --- Analysis for EO_metadata took 2351.1511602401733s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 6.723403930664062e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.2601497173309326s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.020827531814575195s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.552436828613281e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 7.152557373046875e-06s
INFO | --- Analysis for EOKP-Datasets took 3.336704730987549s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.100799560546875e-05s
Availability | VoID file availability check for EPA-CDR took 0.0003662109375s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.2662346363067627s
Reputation | Calculation of the PageRank for EPA-CDR took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.552436828613281e-05s
Believability | Calculation of trust value for EPA-CDR took 5.0067901611328125e-06s
INFO | --- Analysis for epa-cdr took 7.37016224861145s
Availability | SPARQL endpoint availability check for EPA-FRS took 0.00010395050048828125s
Availability | VoID file availability check for EPA-FRS took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.2631046772003174s
Reputation | Calculation of the PageRank for EPA-FRS took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.486343383789062e-05s
Believability | Calculation of trust value for EPA-FRS took 5.245208740234375e-06s
INFO | --- Analysis for epa-frs took 7.0779242515563965s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.100799560546875e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0003879070281982422s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.2674388885498047s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020614147186279297s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 4.0531158447265625e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.0067901611328125e-06s
INFO | --- Analysis for epa-rcra took 5.712522983551025s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.1961669921875e-05s
Availability | VoID file availability check for EPA-SRS took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.2399272918701172s
Reputation | Calculation of the PageRank for EPA-SRS took 0.02070474624633789s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.963180541992188e-05s
Believability | Calculation of trust value for EPA-SRS took 8.821487426757812e-06s
INFO | --- Analysis for epa-srs took 8.692989587783813s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.291534423828125e-05s
Availability | VoID file availability check for EPA-TRI took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.24553227424621582s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.719329833984375e-05s
Believability | Calculation of trust value for EPA-TRI took 5.7220458984375e-06s
INFO | --- Analysis for epa-tri took 5.80996298789978s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 4.00543212890625e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.24880456924438477s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.02191638946533203s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.891654968261719e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 1.2159347534179688e-05s
INFO | --- Analysis for epo took 2.8511760234832764s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.03570246696472168s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.25481462478637695s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.02074718475341797s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00013518333435058594s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.4026095867156982s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.4802236557006836s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.2547597885131836s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.021140098571777344s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.296966552734375e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 1.1205673217773438e-05s
INFO | --- Analysis for eprtr took 3.6904380321502686s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.632211446762085s
Availability | VoID file availability check for Railway Infrastructure KG took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.2757894992828369s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.020671606063842773s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 3.123283386230469e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 1.1444091796875e-05s
INFO | --- Analysis for ERAKG took 3.0483362674713135s
Availability | SPARQL endpoint availability check for reg took 7.557868957519531e-05s
Availability | VoID file availability check for reg took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for reg took 0.23762273788452148s
Reputation | Calculation of the PageRank for reg took 0.02071857452392578s
Interlinking | Calculation of Degree of Connection for reg took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for reg took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for reg took 1.2636184692382812e-05s
Believability | Calculation of trust value for reg took 1.2636184692382812e-05s
INFO | --- Analysis for erg took 2.2110421657562256s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.21234607696533203s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.27387237548828125s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.02057790756225586s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.361701965332031e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 1.0251998901367188e-05s
INFO | --- Analysis for es-msssi-drug-prices took 2.8379924297332764s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 0.00010633468627929688s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0008351802825927734s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.2677483558654785s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.020779848098754883s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 9.441375732421875e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 9.298324584960938e-06s
INFO | --- Analysis for esd-standards took 3.959886074066162s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.5299530029296875e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.26371002197265625s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.02090764045715332s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.2479248046875e-05s
Believability | Calculation of trust value for ESD-Toolkit took 9.5367431640625e-06s
INFO | --- Analysis for esd-toolkit took 3.180997133255005s
Availability | SPARQL endpoint availability check for Dataset Esis took 6.699562072753906e-05s
Availability | VoID file availability check for Dataset Esis took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.251070499420166s
Reputation | Calculation of the PageRank for Dataset Esis took 0.020906448364257812s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.3855438232421875e-05s
Believability | Calculation of trust value for Dataset Esis took 1.239776611328125e-05s
INFO | --- Analysis for esislearning took 2.76143741607666s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 4.3392181396484375e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.2678701877593994s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020892858505249023s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.2901763916015625e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 1.1920928955078125e-05s
INFO | --- Analysis for ESV took 4.65692925453186s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.5116627216339111s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.2567558288574219s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.02078723907470703s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.933906555175781e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.1205673217773438e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.008167028427124s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 5.756803512573242s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.2712442874908447s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020794153213500977s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.295608520507812e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 1.2159347534179688e-05s
INFO | --- Analysis for eu-agencies-bodies took 16.46003556251526s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 7.200241088867188e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.27642393112182617s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.020655393600463867s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.075599670410156e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.239776611328125e-05s
INFO | --- Analysis for eu-dgt-tm took 2.8947956562042236s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 8.845329284667969e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.29004716873168945s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.02165055274963379s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.1920928955078125e-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.367134094238281e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 8.821487426757812e-06s
INFO | --- Analysis for eu-institutions took 7.730420112609863s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.0844109058380127s
Availability | VoID file availability check for EU Parliament Media Library took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.25075674057006836s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.6716461181640625e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 9.775161743164062e-06s
INFO | --- Analysis for eu-parliament-media took 8.242274284362793s
Availability | SPARQL endpoint availability check for EU Who Is Who took 0.9921419620513916s
Availability | VoID file availability check for EU Who Is Who took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.23977065086364746s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020527124404907227s
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.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.361701965332031e-05s
Believability | Calculation of trust value for EU Who Is Who took 8.821487426757812e-06s
INFO | --- Analysis for eu-who-is-who took 12.051879644393921s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.9702911376953125s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.252164363861084s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.02261066436767578s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.00543212890625e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for eumida-linked-data took 9.864017009735107s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.2763667106628418s
Availability | VoID file availability check for European Nature Information System took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.2587881088256836s
Reputation | Calculation of the PageRank for European Nature Information System took 0.022062301635742188s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010704994201660156s
Believability | Calculation of trust value for European Nature Information System took 1.1205673217773438e-05s
INFO | --- Analysis for eunis took 4.118955850601196s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 5.805229187011719s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.2617604732513428s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020482778549194336s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 6.842613220214844e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for eur-lex-rdf took 16.156759023666382s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 1.025768756866455s
Availability | VoID file availability check for Standard Eurobarometer took 0.00036334991455078125s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.2322995662689209s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020334243774414062s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 3.9577484130859375e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 4.76837158203125e-06s
INFO | --- Analysis for eurobarometer-standard took 9.644228219985962s
Availability | SPARQL endpoint availability check for European Election Results took 0.9665703773498535s
Availability | VoID file availability check for European Election Results took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for European Election Results took 0.2768080234527588s
Reputation | Calculation of the PageRank for European Election Results took 0.020221471786499023s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.218650817871094e-05s
Believability | Calculation of trust value for European Election Results took 4.76837158203125e-06s
INFO | --- Analysis for european-election-results took 10.084070920944214s
Availability | SPARQL endpoint availability check for EPO patents took 0.38979506492614746s
Availability | VoID file availability check for EPO patents took 0.0003197193145751953s
Extra | Recovery of all triples for EPO patents took 31.860900163650513s
Performance | Total latancy measurement for EPO patents took 0.9494054317474365s
Amount of data | Number of triples check for EPO patents took 90.26966404914856s
Versatility | Languages check for EPO patents took 100.2244164943695s
Interpretability | Number of blank nodes check for EPO patents took 90.33721256256104s
Interpretability | RDF structures check for EPO patents took 0.21812009811401367s
Versatility | Serialization formats check for EPO patents took 0.20646381378173828s
Availability | RDF dump link check for EPO patents took 0.161055326461792s
License | MR license check for EPO patents took 0.21384835243225098s
License | HR license check for EPO patents took 90.16288900375366s
Amount of data | Number of property check for EPO patents took 0.19809484481811523s
Understandability | Number of label check for EPO patents took 90.2251832485199s
Understandability | URI regex check for EPO patents took 0.5135540962219238s
Understandability | Vocabs check for EPO patents took 0.16427183151245117s
Verifiability | Authors check for EPO patents took 0.20451664924621582s
Verifiability | Publishers check for EPO patents took 0.19122052192687988s
Performance | Throughput check for EPO patents took 11.070903301239014s
Amount of data | Check the number of entities for EPO patents took 0.0001468658447265625s
Verifiability | Contribs. check for EPO patents took 0.1546323299407959s
Interlinking | sameAs chians check for EPO patents took 0.14972925186157227s
Interlinking | skos check for EPO patents took 0.18161749839782715s
Interlinking | skos check for EPO patents took 0.16422390937805176s
Timeliness | dataset update frequency check for EPO patents took 0.19151091575622559s
Currency | Creation date check for EPO patents took 0.44631052017211914s
Currency | Modification date check for EPO patents took 0.3755307197570801s
Rep.Conc. | URIs length for EPO patents took 139.6195547580719s
Interoperability | New vocabularies check for EPO patents took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.23113107681274414s
Accuracy | Check Empty annotation labels for EPO patents took 28.91696333885193s
Accuracy | Check White space in annotation for EPO patents took 2.9876294136047363s
Accuracy | Check Datatype consistency for EPO patents took 4.840177774429321s
Consistency | Disjoint class check for EPO patents took 0.143965482711792s
Consistency | Check Misplaced properties for EPO patents took 100.4070897102356s
Consistency | Check Ontology hijacking for EPO patents took 28.49416470527649s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.551180124282837s
Consistency | Check Invalid usage of undefined properties for EPO patents took 101.60096144676208s
Conciseness | Check Extensional conciseness for EPO patents took 2.7690510749816895s
Conciseness | Check Intensional conciseness for EPO patents took 0.3758862018585205s
Security | Sign check for EPO patents took 0.2892780303955078s
Availability | Check URIs Dereferenciability for EPO patents took 1.5723912715911865s
Completeness | Calculation of interlinking completeness for EPO patents took 0.43584322929382324s
Reputation | Calculation of the PageRank for EPO patents took 0.02148270606994629s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0010623931884765625s
Interlinking | Calculation of Clustering coefficient for EPO patents took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 1.6689300537109375e-06s
Believability | Calculation of trust value for EPO patents took 7.3909759521484375e-06s
INFO | --- Analysis for European_Patent_Information took 1217.8490574359894s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 4.267692565917969e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.24238157272338867s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.020753145217895508s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.147125244140625e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for europeana-lod took 2.8397128582000732s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 6.818771362304688e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.2944068908691406s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.107589721679688e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 7.3909759521484375e-06s
INFO | --- Analysis for europeana-lod-v1 took 7.716881513595581s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.08171272277832031s
Availability | VoID file availability check for Europeana SPARQL took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.28116941452026367s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.021424055099487305s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0009298324584960938s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 6.341934204101562e-05s
Believability | Calculation of trust value for Europeana SPARQL took 1.2636184692382812e-05s
INFO | --- Analysis for europeana-sparql took 2.6736114025115967s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.08197832107543945s
Availability | VoID file availability check for EuroSentiment took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.2785205841064453s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02260565757751465s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 4.124641418457031e-05s
Believability | Calculation of trust value for EuroSentiment took 1.3113021850585938e-05s
INFO | --- Analysis for eurosentiment took 3.225062131881714s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 9.322166442871094e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.2618436813354492s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.020824432373046875s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 3.3855438232421875e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0016987323760986328s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 0.00016307830810546875s
Believability | Calculation of trust value for Eurostat RDF datasets took 1.0013580322265625e-05s
INFO | --- Analysis for eurostat-rdf took 11.113666296005249s
Availability | SPARQL endpoint availability check for EuroVoc took 0.18326258659362793s
Availability | VoID file availability check for EuroVoc took 0.0006480216979980469s
Extra | Recovery of all triples for EuroVoc took 405.05958366394043s
Performance | Total latancy measurement for EuroVoc took 0.6181087493896484s
Amount of data | Number of triples check for EuroVoc took 54.88255596160889s
Interoperability | New terms check for EuroVoc took 77.14401030540466s
Versatility | Languages check for EuroVoc took 300.10623240470886s
Interpretability | Number of blank nodes check for EuroVoc took 17.675597190856934s
Security | Check HTTPS for EuroVoc took 0.34816789627075195s
Interpretability | RDF structures check for EuroVoc took 0.2609903812408447s
Versatility | Serialization formats check for EuroVoc took 4.81814980506897s
Availability | RDF dump link check for EuroVoc took 0.28711676597595215s
License | MR license check for EuroVoc took 0.4140310287475586s
License | HR license check for EuroVoc took 300.1041724681854s
Amount of data | Number of property check for EuroVoc took 0.141707181930542s
Understandability | Number of label check for EuroVoc took 1.9001476764678955s
Understandability | URI regex check for EuroVoc took 0.34215688705444336s
Understandability | Vocabs check for EuroVoc took 0.11087203025817871s
Verifiability | Authors check for EuroVoc took 0.2509317398071289s
Verifiability | Publishers check for EuroVoc took 0.17928409576416016s
Performance | Throughput check for EuroVoc took 10.51182746887207s
Amount of data | Check the number of entities for EuroVoc took 7.152557373046875e-05s
Verifiability | Contribs. check for EuroVoc took 0.1218101978302002s
Interlinking | sameAs chians check for EuroVoc took 6.455105781555176s
Interlinking | skos check for EuroVoc took 0.3389096260070801s
Interlinking | skos check for EuroVoc took 0.16021037101745605s
Timeliness | dataset update frequency check for EuroVoc took 0.22756528854370117s
Currency | Creation date check for EuroVoc took 0.371321439743042s
Currency | Modification date check for EuroVoc took 0.1381371021270752s
Rep.Conc. | URIs length for EuroVoc took 421.0778875350952s
Interoperability | New vocabularies check for EuroVoc took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.125413179397583s
Accuracy | Check Functional Property for EuroVoc took 0.18081116676330566s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.16815876960754395s
Accuracy | Check Empty annotation labels for EuroVoc took 42.62594938278198s
Accuracy | Check White space in annotation for EuroVoc took 3.076573610305786s
Accuracy | Check Datatype consistency for EuroVoc took 2.5757272243499756s
Consistency | Disjoint class check for EuroVoc took 0.17309331893920898s
Consistency | Check Misplaced properties for EuroVoc took 300.4147596359253s
Consistency | Misplaced classes for EuroVoc took 8.325496196746826s
Consistency | Check Ontology hijacking for EuroVoc took 110.22942185401917s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.7606685161590576s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.5861132144928s
Conciseness | Check Extensional conciseness for EuroVoc took 3.0307140350341797s
Conciseness | Check Intensional conciseness for EuroVoc took 0.4637336730957031s
Security | Sign check for EuroVoc took 0.2724604606628418s
Availability | Check URIs Dereferenciability for EuroVoc took 18.3583824634552s
Completeness | Calculation of interlinking completeness for EuroVoc took 1.5750198364257812s
Reputation | Calculation of the PageRank for EuroVoc took 0.021454334259033203s
Interlinking | Calculation of Degree of Connection for EuroVoc took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 8.0108642578125e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.1920928955078125e-06s
Believability | Calculation of trust value for EuroVoc took 1.049041748046875e-05s
INFO | --- Analysis for eurovoc took 15824.020246744156s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 4.029273986816406e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.23768234252929688s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.021677732467651367s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 4.0531158447265625e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 6.67572021484375e-06s
INFO | --- Analysis for eurovoc-in-skos took 5.355913400650024s
Availability | SPARQL endpoint availability check for European Television Heritage took 4.076957702636719e-05s
Availability | VoID file availability check for European Television Heritage took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.7160649299621582s
Reputation | Calculation of the PageRank for European Television Heritage took 0.020704984664916992s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 2.956390380859375e-05s
Believability | Calculation of trust value for European Television Heritage took 6.67572021484375e-06s
INFO | --- Analysis for euscreen took 4.176856517791748s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.38690185546875e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.00034737586975097656s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.2395613193511963s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.02086043357849121s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 5.316734313964844e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 4.76837158203125e-06s
INFO | --- Analysis for euskadi-farmacias took 7.246463775634766s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.6914844512939453s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.2765767574310303s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.02028203010559082s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.266334533691406e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 6.9141387939453125e-06s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.144285678863525s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.306377649307251s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.26093602180480957s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.02060389518737793s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.367134094238281e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 1.1444091796875e-05s
INFO | --- Analysis for eutc-productions took 7.7700254917144775s
Availability | SPARQL endpoint availability check for EventMedia took 0.37274909019470215s
Availability | VoID file availability check for EventMedia took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for EventMedia took 0.2525792121887207s
Reputation | Calculation of the PageRank for EventMedia took 0.020863771438598633s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00011038780212402344s
Believability | Calculation of trust value for EventMedia took 1.1682510375976562e-05s
INFO | --- Analysis for event-media took 8.2258620262146s
Availability | SPARQL endpoint availability check for EventKG took 4.220008850097656e-05s
Availability | VoID file availability check for EventKG took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for EventKG took 0.2627723217010498s
Reputation | Calculation of the PageRank for EventKG took 0.02068328857421875s
Interlinking | Calculation of Degree of Connection for EventKG took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.344650268554688e-05s
Believability | Calculation of trust value for EventKG took 7.152557373046875e-06s
INFO | --- Analysis for eventkg took 5.811689138412476s
Availability | SPARQL endpoint availability check for Eventseer took 9.643896579742432s
Availability | VoID file availability check for Eventseer took 0.00034308433532714844s
Completeness | Calculation of interlinking completeness for Eventseer took 0.23424768447875977s
Reputation | Calculation of the PageRank for Eventseer took 0.020781278610229492s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.76837158203125e-05s
Believability | Calculation of trust value for Eventseer took 1.1205673217773438e-05s
INFO | --- Analysis for eventseer took 12.058611869812012s
Availability | SPARQL endpoint availability check for Face Link took 4.172325134277344e-05s
Availability | VoID file availability check for Face Link took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Face Link took 0.2573091983795166s
Reputation | Calculation of the PageRank for Face Link took 0.02090930938720703s
Interlinking | Calculation of Degree of Connection for Face Link took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.218650817871094e-05s
Believability | Calculation of trust value for Face Link took 8.821487426757812e-06s
INFO | --- Analysis for Face_Link took 2.260056257247925s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 4.1484832763671875e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.24610066413879395s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.020325183868408203s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 3.0994415283203125e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 2.765655517578125e-05s
INFO | --- Analysis for facebook-lids took 2.839362382888794s
Availability | SPARQL endpoint availability check for Fact Forge took 4.124641418457031e-05s
Availability | VoID file availability check for Fact Forge took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.2558863162994385s
Reputation | Calculation of the PageRank for Fact Forge took 0.021427154541015625s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 3.0279159545898438e-05s
Believability | Calculation of trust value for Fact Forge took 1.239776611328125e-05s
INFO | --- Analysis for fact-forge took 2.879190683364868s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5678300857543945s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0005195140838623047s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 125.02012991905212s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0090787410736084s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.42170524597168s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 14.385574340820312s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.22716784477234s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.1918272972106934s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3220529556274414s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 12.722344875335693s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.35495781898498535s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.761183500289917s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.2074191570282s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19365715980529785s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.0126545429229736s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.8049907684326172s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5404798984527588s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.210188627243042s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.25496578216552734s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.170703649520874s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.677078247070312e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19959425926208496s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18796443939208984s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.42589306831359863s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.40866589546203613s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.615067958831787s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4644899368286133s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.23978137969970703s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 154.6321084499359s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2147352695465088s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.34258413314819336s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.37932491302490234s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 39.511627435684204s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6569080352783203s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.573911190032959s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18625617027282715s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 86.29836535453796s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.331506252288818s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 33.3909387588501s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.4405913352966309s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 89.04304790496826s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.742526054382324s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5526037216186523s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0750610828399658s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 16.485872745513916s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9820706844329834s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.021042346954345703s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.9114227294921875e-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.239776611328125e-05s
INFO | --- Analysis for FADN_(2019) took 2306.4526257514954s
Availability | SPARQL endpoint availability check for FAMEData took 4.267692565917969e-05s
Availability | VoID file availability check for FAMEData took 0.00036454200744628906s
Completeness | Calculation of interlinking completeness for FAMEData took 0.7668380737304688s
Reputation | Calculation of the PageRank for FAMEData took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.4332275390625e-05s
Believability | Calculation of trust value for FAMEData took 1.1682510375976562e-05s
INFO | --- Analysis for famedata took 7.868514537811279s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 8.821487426757812e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.2510402202606201s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.020472288131713867s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.441375732421875e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 9.059906005859375e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 13.118411302566528s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.12023043632507324s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.6762027740478516s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020362377166748047s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010371208190917969s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for fao-linked-data took 4.2578444480896s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 7.700920104980469e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.251248836517334s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.020320653915405273s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.0279159545898438e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.0967254638671875e-05s
INFO | --- Analysis for FAO_species took 2.3075551986694336s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.512067794799805s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.2751157283782959s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.021523714065551758s
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.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.4345855712890625e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.2636184692382812e-05s
INFO | --- Analysis for farmbio-chembl took 68.08653450012207s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 4.506111145019531e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.24884843826293945s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.020822525024414062s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 3.075599670410156e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 7.152557373046875e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 3.668527603149414s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 4.029273986816406e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.26804304122924805s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020406246185302734s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 1.1444091796875e-05s
INFO | --- Analysis for farolapp-dataset took 2.837028741836548s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 8.893013000488281e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.24884247779846191s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.022495269775390625s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0008132457733154297s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 3.0994415283203125e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 1.1920928955078125e-05s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 2.914400815963745s
Availability | SPARQL endpoint availability check for I4.0-Onto took 8.630752563476562e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.24952006340026855s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.021997928619384766s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.6716461181640625e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.0967254638671875e-05s
INFO | --- Analysis for fatimazahra took 2.235687255859375s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 5.340576171875e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.2844531536102295s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.02151632308959961s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 2.9087066650390625e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 1.1444091796875e-05s
INFO | --- Analysis for federal-economic-rdf took 2.876636266708374s
Availability | SPARQL endpoint availability check for Feed Wrapper took 3.981590270996094e-05s
Availability | VoID file availability check for Feed Wrapper took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.25222277641296387s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.022582292556762695s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 3.218650817871094e-05s
Believability | Calculation of trust value for Feed Wrapper took 1.049041748046875e-05s
INFO | --- Analysis for feedwrapper-lids took 2.863434076309204s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.076957702636719e-05s
Availability | VoID file availability check for FHIR STU3 took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.27823972702026367s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020839691162109375s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 3.075599670410156e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.0013580322265625e-05s
INFO | --- Analysis for FHIR_STU3 took 2.6539385318756104s
Availability | SPARQL endpoint availability check for FiESTA took 6.079673767089844e-05s
Availability | VoID file availability check for FiESTA took 0.0007653236389160156s
Completeness | Calculation of interlinking completeness for FiESTA took 0.2748374938964844s
Reputation | Calculation of the PageRank for FiESTA took 0.020676612854003906s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for FiESTA took 4.1961669921875e-05s
Believability | Calculation of trust value for FiESTA took 1.2159347534179688e-05s
INFO | --- Analysis for fiesta took 12.49338150024414s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 9.1552734375e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.2700784206390381s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02109241485595703s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.24249267578125e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.1682510375976562e-05s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.3646767139434814s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 4.7206878662109375e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.2799227237701416s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.02059173583984375s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0008556842803955078s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.390975952148438e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 8.821487426757812e-06s
INFO | --- Analysis for finnish-municipalities took 3.9700570106506348s
Availability | SPARQL endpoint availability check for firmao took 4.0531158447265625e-05s
Availability | VoID file availability check for firmao took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for firmao took 0.2614114284515381s
Reputation | Calculation of the PageRank for firmao took 0.021239519119262695s
Interlinking | Calculation of Degree of Connection for firmao took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for firmao took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for firmao took 3.4809112548828125e-05s
Believability | Calculation of trust value for firmao took 1.2874603271484375e-05s
INFO | --- Analysis for firmao took 2.898561477661133s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 6.604194641113281e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.2418653964996338s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.0232698917388916s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 3.647804260253906e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.869854211807251s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.19824719429016113s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0005457401275634766s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 124.27946543693542s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 1.0108766555786133s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 9.325599431991577s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 14.196777820587158s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.22533321380615s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 2.1027212142944336s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.32218337059020996s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 12.150746583938599s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.301302433013916s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.6538066864013672s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.17732787132263s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.22245025634765625s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 1.5785877704620361s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 0.6039888858795166s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.5318663120269775s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.2077345848083496s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.24699807167053223s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 10.801156520843506s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 7.2479248046875e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.20429706573486328s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.18624424934387207s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.40776991844177246s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.40485429763793945s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 4.33453631401062s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.49670886993408203s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.25475287437438965s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 158.27091884613037s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.2030644416809082s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.3638617992401123s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.3900721073150635s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 37.128052711486816s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.6752126216888428s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.5967843532562256s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.20861506462097168s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 88.18245124816895s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.361735820770264s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 44.6234495639801s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.4287190437316895s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 88.49556303024292s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.7066473960876465s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.513434648513794s
Security | Sign check for Norway fishery stocks dataset @PSNC took 1.0255110263824463s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 17.355222940444946s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 1.0642178058624268s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.02124500274658203s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 3.0994415283203125e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 2307.689329624176s
Availability | SPARQL endpoint availability check for Fishes of Texas took 5.14984130859375e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.6966502666473389s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.02103734016418457s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.630752563476562e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.0013580322265625e-05s
INFO | --- Analysis for fishes-of-texas took 5.00846791267395s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.220008850097656e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.26122570037841797s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 0.00010085105895996094s
Believability | Calculation of trust value for flickr? wrappr took 1.2159347534179688e-05s
INFO | --- Analysis for flickr-wrappr took 3.9544906616210938s
Availability | SPARQL endpoint availability check for flickr.person took 4.267692565917969e-05s
Availability | VoID file availability check for flickr.person took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for flickr.person took 0.26276326179504395s
Reputation | Calculation of the PageRank for flickr.person took 0.021563291549682617s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for flickr.person took 3.266334533691406e-05s
Believability | Calculation of trust value for flickr.person took 1.239776611328125e-05s
INFO | --- Analysis for flickr_person took 3.7319631576538086s
Availability | SPARQL endpoint availability check for flickr.videoobject took 3.981590270996094e-05s
Availability | VoID file availability check for flickr.videoobject took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.2672579288482666s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.02071833610534668s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 3.218650817871094e-05s
Believability | Calculation of trust value for flickr.videoobject took 1.0728836059570312e-05s
INFO | --- Analysis for flickr_videoobject took 3.357654333114624s
Availability | SPARQL endpoint availability check for Future land use simulation model took 8.606910705566406e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.2787168025970459s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.02100229263305664s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.170967102050781e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.2874603271484375e-05s
INFO | --- Analysis for FLUS took 8.257267713546753s
Availability | SPARQL endpoint availability check for Fly-TED took 4.9591064453125e-05s
Availability | VoID file availability check for Fly-TED took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.24860882759094238s
Reputation | Calculation of the PageRank for Fly-TED took 0.023171663284301758s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 3.409385681152344e-05s
Believability | Calculation of trust value for Fly-TED took 1.2636184692382812e-05s
INFO | --- Analysis for fly-ted took 2.8601691722869873s
Availability | SPARQL endpoint availability check for FlyAtlas took 8.344650268554688e-05s
Availability | VoID file availability check for FlyAtlas took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.2657027244567871s
Reputation | Calculation of the PageRank for FlyAtlas took 0.02138042449951172s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.266334533691406e-05s
Believability | Calculation of trust value for FlyAtlas took 1.33514404296875e-05s
INFO | --- Analysis for flyatlas took 2.847482919692993s
Availability | SPARQL endpoint availability check for Flybase took 4.412927865982056s
Availability | VoID file availability check for Flybase took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for Flybase took 0.23356223106384277s
Reputation | Calculation of the PageRank for Flybase took 0.02038288116455078s
Interlinking | Calculation of Degree of Connection for Flybase took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.695487976074219e-05s
Believability | Calculation of trust value for Flybase took 1.0728836059570312e-05s
INFO | --- Analysis for flybase took 34.35488152503967s
Availability | SPARQL endpoint availability check for Flyted took 9.426390647888184s
Availability | VoID file availability check for Flyted took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Flyted took 0.29091763496398926s
Reputation | Calculation of the PageRank for Flyted took 0.021576642990112305s
Interlinking | Calculation of Degree of Connection for Flyted took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.0517578125e-05s
Believability | Calculation of trust value for Flyted took 1.1682510375976562e-05s
INFO | --- Analysis for flyted took 20.000468730926514s
Availability | SPARQL endpoint availability check for Foodista took 3.992135524749756s
Availability | VoID file availability check for Foodista took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for Foodista took 0.26401782035827637s
Reputation | Calculation of the PageRank for Foodista took 0.020435333251953125s
Interlinking | Calculation of Degree of Connection for Foodista took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.0279159545898438e-05s
Believability | Calculation of trust value for Foodista took 1.0967254638671875e-05s
INFO | --- Analysis for foodista took 14.521762132644653s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2051074504852295s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.259382963180542s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.020921945571899414s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.081031799316406e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1444091796875e-05s
INFO | --- Analysis for foodpedia took 2.603012800216675s
Availability | SPARQL endpoint availability check for FORGE Course information took 7.939338684082031e-05s
Availability | VoID file availability check for FORGE Course information took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.2656419277191162s
Reputation | Calculation of the PageRank for FORGE Course information took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 5.030632019042969e-05s
Believability | Calculation of trust value for FORGE Course information took 1.0728836059570312e-05s
INFO | --- Analysis for forge-course-information took 2.848186731338501s
Availability | SPARQL endpoint availability check for FrameBase schema took 5.054473876953125e-05s
Availability | VoID file availability check for FrameBase schema took 0.0008099079132080078s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.2730112075805664s
Reputation | Calculation of the PageRank for FrameBase schema took 0.02092146873474121s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.649162292480469e-05s
Believability | Calculation of trust value for FrameBase schema took 1.2159347534179688e-05s
INFO | --- Analysis for framebase-schema took 2.9515929222106934s
Availability | SPARQL endpoint availability check for FrameNet took 4.172325134277344e-05s
Availability | VoID file availability check for FrameNet took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for FrameNet took 0.2720475196838379s
Reputation | Calculation of the PageRank for FrameNet took 0.020601987838745117s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for FrameNet took 3.123283386230469e-05s
Believability | Calculation of trust value for FrameNet took 1.2159347534179688e-05s
INFO | --- Analysis for framenet took 2.8516323566436768s
Availability | SPARQL endpoint availability check for Framester took 4.172325134277344e-05s
Availability | VoID file availability check for Framester took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for Framester took 0.257676362991333s
Reputation | Calculation of the PageRank for Framester took 0.021022558212280273s
Interlinking | Calculation of Degree of Connection for Framester took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Framester took 7.724761962890625e-05s
Believability | Calculation of trust value for Framester took 1.1920928955078125e-05s
INFO | --- Analysis for framester took 3.8010971546173096s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.07601690292358398s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2631351947784424s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.020894765853881836s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.58306884765625e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 1.2159347534179688e-05s
INFO | --- Analysis for frb-linked-data took 2.49645733833313s
Availability | SPARQL endpoint availability check for Freebase took 4.410743713378906e-05s
Availability | VoID file availability check for Freebase took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Freebase took 0.25907349586486816s
Reputation | Calculation of the PageRank for Freebase took 0.021090030670166016s
Interlinking | Calculation of Degree of Connection for Freebase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.0002636909484863281s
Believability | Calculation of trust value for Freebase took 1.0251998901367188e-05s
INFO | --- Analysis for freebase took 3.733353853225708s
Availability | SPARQL endpoint availability check for Freeyork took 4.291534423828125e-05s
Availability | VoID file availability check for Freeyork took 0.0007886886596679688s
Completeness | Calculation of interlinking completeness for Freeyork took 0.26031494140625s
Reputation | Calculation of the PageRank for Freeyork took 0.022074460983276367s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010704994201660156s
Believability | Calculation of trust value for Freeyork took 1.0251998901367188e-05s
INFO | --- Analysis for freeyork-org took 3.53987979888916s
Availability | SPARQL endpoint availability check for French School Program took 4.220008850097656e-05s
Availability | VoID file availability check for French School Program took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for French School Program took 0.2361907958984375s
Reputation | Calculation of the PageRank for French School Program took 0.021027565002441406s
Interlinking | Calculation of Degree of Connection for French School Program took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for French School Program took 3.123283386230469e-05s
Believability | Calculation of trust value for French School Program took 1.2159347534179688e-05s
INFO | --- Analysis for french-school-program took 2.781676769256592s
Availability | SPARQL endpoint availability check for French School System took 5.364418029785156e-05s
Availability | VoID file availability check for French School System took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for French School System took 0.28739261627197266s
Reputation | Calculation of the PageRank for French School System took 0.02118659019470215s
Interlinking | Calculation of Degree of Connection for French School System took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for French School System took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for French School System took 3.1948089599609375e-05s
Believability | Calculation of trust value for French School System took 1.1682510375976562e-05s
INFO | --- Analysis for french-school-system took 2.8580760955810547s
Availability | SPARQL endpoint availability check for French TimeBank took 4.220008850097656e-05s
Availability | VoID file availability check for French TimeBank took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.2852346897125244s
Reputation | Calculation of the PageRank for French TimeBank took 0.020874738693237305s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.266334533691406e-05s
Believability | Calculation of trust value for French TimeBank took 1.1682510375976562e-05s
INFO | --- Analysis for french-timebank took 2.8816754817962646s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.6963696479797363s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.2833983898162842s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.02084636688232422s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.605552673339844e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 9.059906005859375e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.505511045455933s
Availability | SPARQL endpoint availability check for DailyMed took 0.7021565437316895s
Availability | VoID file availability check for DailyMed took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for DailyMed took 0.27773571014404297s
Reputation | Calculation of the PageRank for DailyMed took 0.020924806594848633s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.822845458984375e-05s
Believability | Calculation of trust value for DailyMed took 1.33514404296875e-05s
INFO | --- Analysis for fu-berlin-dailymed took 5.525606632232666s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.6559340953826904s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.27298474311828613s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.023297786712646484s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0008151531219482422s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 9.512901306152344e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.2159347534179688e-05s
INFO | --- Analysis for fu-berlin-dblp took 4.251115560531616s
Availability | SPARQL endpoint availability check for Diseasome took 0.6542873382568359s
Availability | VoID file availability check for Diseasome took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Diseasome took 0.24682307243347168s
Reputation | Calculation of the PageRank for Diseasome took 0.020733356475830078s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00010657310485839844s
Believability | Calculation of trust value for Diseasome took 1.1682510375976562e-05s
INFO | --- Analysis for fu-berlin-diseasome took 5.455716848373413s
Availability | SPARQL endpoint availability check for DrugBank took 0.6710841655731201s
Availability | VoID file availability check for DrugBank took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for DrugBank took 0.24939966201782227s
Reputation | Calculation of the PageRank for DrugBank took 0.020798444747924805s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011444091796875s
Believability | Calculation of trust value for DrugBank took 1.2874603271484375e-05s
INFO | --- Analysis for fu-berlin-drugbank took 5.453700542449951s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.646237850189209s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.24661946296691895s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020736217498779297s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.075599670410156e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.3113021850585938e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 4.200657844543457s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.6712183952331543s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.24533414840698242s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.021227598190307617s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.390975952148438e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 9.5367431640625e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.278587102890015s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.6776411533355713s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.2763385772705078s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.021007776260375977s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.653236389160156e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 1.0013580322265625e-05s
INFO | --- Analysis for fu-berlin-eures took 4.339614629745483s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.6694531440734863s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2740955352783203s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020868778228759766s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 0.0001049041748046875s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 1.1682510375976562e-05s
INFO | --- Analysis for fu-berlin-eurostat took 4.974481821060181s
Availability | SPARQL endpoint availability check for MediCare took 0.639556884765625s
Availability | VoID file availability check for MediCare took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for MediCare took 0.2462761402130127s
Reputation | Calculation of the PageRank for MediCare took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for MediCare took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.363059997558594e-05s
Believability | Calculation of trust value for MediCare took 1.2636184692382812e-05s
INFO | --- Analysis for fu-berlin-medicare took 4.998260498046875s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.696038007736206s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.2600533962249756s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.200241088867188e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 9.059906005859375e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.359369516372681s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.6764402389526367s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.24997663497924805s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.021192073822021484s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.298324584960938e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.1682510375976562e-05s
INFO | --- Analysis for fu-berlin-sider took 4.96091890335083s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.6866886615753174s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.2488551139831543s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020782470703125s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.605552673339844e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.0967254638671875e-05s
INFO | --- Analysis for fu-berlin-stitch took 4.278069734573364s
Availability | SPARQL endpoint availability check for fvdb took 5.0067901611328125e-05s
Availability | VoID file availability check for fvdb took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for fvdb took 0.234022855758667s
Reputation | Calculation of the PageRank for fvdb took 0.020709753036499023s
Interlinking | Calculation of Degree of Connection for fvdb took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.147125244140625e-05s
Believability | Calculation of trust value for fvdb took 1.1920928955078125e-05s
INFO | --- Analysis for fv took 12.360239267349243s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 4.76837158203125e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0007290840148925781s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.25783276557922363s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.02104949951171875s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.266334533691406e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 1.1920928955078125e-05s
INFO | --- Analysis for GACS took 3.050851821899414s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 6.341934204101562e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.25357985496520996s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.02102518081665039s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 3.4332275390625e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 1.3589859008789062e-05s
INFO | --- Analysis for galen_from_co-odeorg took 2.847683906555176s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 8.821487426757812e-05s
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.28867268562316895s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.02090764045715332s
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.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.267692565917969e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.172271013259888s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 9.34600830078125e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.2649955749511719s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.020831584930419922s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00010418891906738281s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.3828277587890625e-05s
INFO | --- Analysis for garnicaplywood took 3.9417176246643066s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 5.53131103515625e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.24421310424804688s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.021114826202392578s
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.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.00011277198791503906s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.0728836059570312e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.447632789611816s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.2827885150909424s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.27585673332214355s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 0.00011444091796875s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.1682510375976562e-05s
INFO | --- Analysis for gemet took 4.916488170623779s
Availability | SPARQL endpoint availability check for gemet-annotated took 5.888938903808594e-05s
Availability | VoID file availability check for gemet-annotated took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.2527484893798828s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020860910415649414s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.790855407714844e-05s
Believability | Calculation of trust value for gemet-annotated took 1.2636184692382812e-05s
INFO | --- Analysis for gemet-annotated took 2.876185894012451s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.7672350406646729s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.28887128829956055s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020391464233398438s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.9577484130859375e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.2636184692382812e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.072709083557129s
Availability | SPARQL endpoint availability check for Super Ontology took 3.0761189460754395s
Availability | VoID file availability check for Super Ontology took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.24744653701782227s
Reputation | Calculation of the PageRank for Super Ontology took 0.020889759063720703s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for Super Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 6.41195011138916s
Availability | SPARQL endpoint availability check for geo.place took 5.4836273193359375e-05s
Availability | VoID file availability check for geo.place took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for geo.place took 0.2521703243255615s
Reputation | Calculation of the PageRank for geo.place took 0.022482872009277344s
Interlinking | Calculation of Degree of Connection for geo.place took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for geo.place took 3.266334533691406e-05s
Believability | Calculation of trust value for geo.place took 1.239776611328125e-05s
INFO | --- Analysis for geo_place took 2.851731538772583s
Availability | SPARQL endpoint availability check for Geographic detector model took 4.38690185546875e-05s
Availability | VoID file availability check for Geographic detector model took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.2827944755554199s
Reputation | Calculation of the PageRank for Geographic detector model took 0.020345211029052734s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.0279159545898438e-05s
Believability | Calculation of trust value for Geographic detector model took 1.4781951904296875e-05s
INFO | --- Analysis for GeoDetector took 21.219655990600586s
Availability | SPARQL endpoint availability check for geodomainwn took 8.58306884765625e-05s
Availability | VoID file availability check for geodomainwn took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.24823927879333496s
Reputation | Calculation of the PageRank for geodomainwn took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.553794860839844e-05s
Believability | Calculation of trust value for geodomainwn took 9.059906005859375e-06s
INFO | --- Analysis for geodomainwn took 6.663701057434082s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.410743713378906e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.2504417896270752s
Reputation | Calculation of the PageRank for GeoEcuador took 0.021044254302978516s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 7.462501525878906e-05s
Believability | Calculation of trust value for GeoEcuador took 1.1682510375976562e-05s
INFO | --- Analysis for geoecuador took 12.706939935684204s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.2377877235412598s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.2634258270263672s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.021932125091552734s
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.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.747245788574219e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.2874603271484375e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 49.33898377418518s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 9.942054748535156e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.25220799446105957s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020789623260498047s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.1948089599609375e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 1.1444091796875e-05s
INFO | --- Analysis for geographic-openuplabs took 2.7630069255828857s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.4405965805053711s
Availability | VoID file availability check for GeoLinkedData took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.23685550689697266s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.02060556411743164s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.797645568847656e-05s
Believability | Calculation of trust value for GeoLinkedData took 8.821487426757812e-06s
INFO | --- Analysis for geolinkeddata took 3.9133756160736084s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.23645234107971191s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0005571842193603516s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 8.894853830337524s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.3338184356689453s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.11097240447998047s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.446359634399414s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.15928196907043457s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.11695384979248047s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.20695209503173828s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.06869268417358398s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.06878829002380371s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.05948591232299805s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.06808090209960938s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.762669324874878s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.06934475898742676s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.07429099082946777s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.1273787021636963s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.06039929389953613s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.0682368278503418s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.06803369522094727s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.42113447189331s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 6.961822509765625e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.07578158378601074s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.06718754768371582s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.06873846054077148s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.06878900527954102s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.07505106925964355s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.14972877502441406s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.12836146354675293s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.2265887260437012s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 1.3067529201507568s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.06908726692199707s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06688976287841797s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.0672454833984375s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.3110387325286865s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007307767868041992s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.22738385200500488s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.07534098625183105s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.20555591583251953s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5236971378326416s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.279900550842285s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.5914332866668701s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.7811686992645264s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.18098878860473633s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.07440352439880371s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.0691688060760498s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.25414204597473145s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.0210115909576416s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.797645568847656e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 0.7012038230895996s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 112.45964360237122s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.458427429199219e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.23843169212341309s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.00048041343688964844s
Believability | Calculation of trust value for GeoNames Semantic Web took 8.58306884765625e-06s
INFO | --- Analysis for geonames-semantic-web took 3.116708278656006s
Availability | SPARQL endpoint availability check for Geospatial World  took 8.58306884765625e-05s
Availability | VoID file availability check for Geospatial World  took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.24552273750305176s
Reputation | Calculation of the PageRank for Geospatial World  took 0.02107858657836914s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010752677917480469s
Believability | Calculation of trust value for Geospatial World  took 1.1205673217773438e-05s
INFO | --- Analysis for geospatialworld-net took 2.8298468589782715s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5048980712890625s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0004177093505859375s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.2561349868774414s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020818233489990234s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00014162063598632812s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 6.67572021484375e-06s
INFO | --- Analysis for geospecies took 5.624211549758911s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.291534423828125e-05s
Availability | VoID file availability check for GeoWordNet took 0.0003948211669921875s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.24866127967834473s
Reputation | Calculation of the PageRank for GeoWordNet took 0.020702123641967773s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.793571472167969e-05s
Believability | Calculation of trust value for GeoWordNet took 6.67572021484375e-06s
INFO | --- Analysis for geowordnet took 11.899246215820312s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.09200525283813477s
Availability | VoID file availability check for German labor law thesaurus took 0.00022339820861816406s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.23421311378479004s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 7.867813110351562e-05s
Believability | Calculation of trust value for German labor law thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.4395339488983154s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.2438507080078125e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0003647804260253906s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.2433454990386963s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.02076888084411621s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.100799560546875e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 7.867813110351562e-06s
INFO | --- Analysis for germlex took 2.599616050720215s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.4896845817565918s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.3014407157897949s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2556438446044922s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.5367431640625e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 7.867813110351562e-06s
INFO | --- Analysis for gesis-thesoz took 7.369989633560181s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.878692626953125s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0004076957702636719s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.2623250484466553s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.021309375762939453s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0008718967437744141s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 8.7738037109375e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for getty-aat took 18.335882663726807s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.2769911289215088s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.2375798225402832s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020879030227661133s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.269050598144531e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 7.62939453125e-06s
INFO | --- Analysis for getty-tgn took 13.530517816543579s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 7.285049915313721s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0007486343383789062s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.29103755950927734s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.021061182022094727s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.600120544433594e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 8.344650268554688e-06s
INFO | --- Analysis for gipuzkoademografia took 30.635795831680298s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 9.1552734375e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.2667233943939209s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.022325992584228516s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.1948089599609375e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 6.67572021484375e-06s
INFO | --- Analysis for glastonbury-2011 took 5.339452743530273s
Availability | SPARQL endpoint availability check for Global Change Information System took 6.651878356933594e-05s
Availability | VoID file availability check for Global Change Information System took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.266650915145874s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020969152450561523s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 3.123283386230469e-05s
Believability | Calculation of trust value for Global Change Information System took 1.0967254638671875e-05s
INFO | --- Analysis for global-change-information-system took 2.8802101612091064s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.76837158203125e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.2312014102935791s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.021037578582763672s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.792213439941406e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 1.1205673217773438e-05s
INFO | --- Analysis for global-hunger-index-2011 took 3.645961284637451s
Availability | SPARQL endpoint availability check for Glottolog took 4.172325134277344e-05s
Availability | VoID file availability check for Glottolog took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2526402473449707s
Reputation | Calculation of the PageRank for Glottolog took 0.021480798721313477s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Glottolog took 4.76837158203125e-05s
Believability | Calculation of trust value for Glottolog took 1.1205673217773438e-05s
INFO | --- Analysis for glottolog took 6.268645524978638s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.1484832763671875e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0007908344268798828s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.28368663787841797s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.021683454513549805s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00011134147644042969s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.239776611328125e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 54.68107199668884s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 9.059906005859375e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.26680994033813477s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.021636247634887695s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 3.1948089599609375e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 1.2159347534179688e-05s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.8897628784179688s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.0531158447265625e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.2594282627105713s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.020795822143554688s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0009338855743408203s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.314018249511719e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.2159347534179688e-05s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 2.8186237812042236s
Availability | SPARQL endpoint availability check for 1121 took 8.654594421386719e-05s
Availability | VoID file availability check for 1121 took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for 1121 took 0.2487635612487793s
Reputation | Calculation of the PageRank for 1121 took 0.02055835723876953s
Interlinking | Calculation of Degree of Connection for 1121 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for 1121 took 2.8133392333984375e-05s
Believability | Calculation of trust value for 1121 took 1.1920928955078125e-05s
INFO | --- Analysis for God_ took 3.091381311416626s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 5.125999450683594e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.25804853439331055s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020450353622436523s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.078315734863281e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 6.67572021484375e-06s
INFO | --- Analysis for gold took 4.009859323501587s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.38690185546875e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.2586381435394287s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.389617919921875e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 6.9141387939453125e-06s
INFO | --- Analysis for googleart-wrapper took 2.752293586730957s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.09743118286132812s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.24839425086975098s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020676136016845703s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.600120544433594e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.1682510375976562e-05s
INFO | --- Analysis for govagribus-denmark took 35.35408401489258s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.4222753047943115s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.26584959030151367s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 7.939338684082031e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 23.967271089553833s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.185861349105835s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.2629709243774414s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020480632781982422s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 0.00010132789611816406s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 8.58306884765625e-06s
INFO | --- Analysis for govtrack took 3.9869229793548584s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 8.678436279296875e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.2749965190887451s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 5.841255187988281e-05s
Believability | Calculation of trust value for greek-administrative-geography took 6.67572021484375e-06s
INFO | --- Analysis for greek-administrative-geography took 2.664517879486084s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.26801609992980957s
Availability | VoID file availability check for Greek Wordnet took 0.0004069805145263672s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.25739288330078125s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.02092742919921875s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.315376281738281e-05s
Believability | Calculation of trust value for Greek Wordnet took 7.152557373046875e-06s
INFO | --- Analysis for greek-wordnet took 2.5954949855804443s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.33547353744506836s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0005848407745361328s
Extra | Recovery of all triples for Greek prisons releases Jan 2018 - Dec 2023 took 11.656064510345459s
Performance | Total latancy measurement for Greek prisons releases Jan 2018 - Dec 2023 took 0.6169590950012207s
Amount of data | Number of triples check for Greek prisons releases Jan 2018 - Dec 2023 took 0.6079590320587158s
Interoperability | New terms check for Greek prisons releases Jan 2018 - Dec 2023 took 1.6657824516296387s
Versatility | Languages check for Greek prisons releases Jan 2018 - Dec 2023 took 1.6984469890594482s
Interpretability | Number of blank nodes check for Greek prisons releases Jan 2018 - Dec 2023 took 0.4883852005004883s
Interpretability | RDF structures check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12769031524658203s
Versatility | Serialization formats check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12803387641906738s
Availability | RDF dump link check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11854410171508789s
License | MR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12662935256958008s
License | HR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5937020778656006s
Amount of data | Number of property check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11903214454650879s
Understandability | Number of label check for Greek prisons releases Jan 2018 - Dec 2023 took 0.20381450653076172s
Understandability | URI regex check for Greek prisons releases Jan 2018 - Dec 2023 took 0.24872422218322754s
Understandability | Vocabs check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12672877311706543s
Verifiability | Authors check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12041449546813965s
Verifiability | Publishers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1351628303527832s
Performance | Throughput check for Greek prisons releases Jan 2018 - Dec 2023 took 10.598162412643433s
Amount of data | Check the number of entities for Greek prisons releases Jan 2018 - Dec 2023 took 9.179115295410156e-05s
Verifiability | Contribs. check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13859772682189941s
Interlinking | sameAs chians check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1187887191772461s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12492799758911133s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12619256973266602s
Timeliness | dataset update frequency check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1328270435333252s
Currency | Creation date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.25142502784729004s
Currency | Modification date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.23620128631591797s
Rep.Conc. | URIs length for Greek prisons releases Jan 2018 - Dec 2023 took 7.778860330581665s
Interoperability | New vocabularies check for Greek prisons releases Jan 2018 - Dec 2023 took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13449311256408691s
Accuracy | Check Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.12436461448669434s
Accuracy | Check Inverse Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.11655497550964355s
Accuracy | Check Empty annotation labels for Greek prisons releases Jan 2018 - Dec 2023 took 2.1280386447906494s
Accuracy | Check White space in annotation for Greek prisons releases Jan 2018 - Dec 2023 took 0.2906069755554199s
Accuracy | Check Datatype consistency for Greek prisons releases Jan 2018 - Dec 2023 took 4.606613874435425s
Consistency | Disjoint class check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1283409595489502s
Consistency | Check Misplaced properties for Greek prisons releases Jan 2018 - Dec 2023 took 1.2524263858795166s
Consistency | Check Ontology hijacking for Greek prisons releases Jan 2018 - Dec 2023 took 2.9698495864868164s
Consistency | Check Invalid usage of undefined classes for Greek prisons releases Jan 2018 - Dec 2023 took 1.310652494430542s
Consistency | Check Invalid usage of undefined properties for Greek prisons releases Jan 2018 - Dec 2023 took 2.5210845470428467s
Conciseness | Check Extensional conciseness for Greek prisons releases Jan 2018 - Dec 2023 took 2.8379015922546387s
Security | Sign check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1246645450592041s
Availability | Check URIs Dereferenciability for Greek prisons releases Jan 2018 - Dec 2023 took 4865.962092638016s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.6719529628753662s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.021387338638305664s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.5497207641601562e-05s
Interoperability | Check the re-using of existing vocabs for Greek prisons releases Jan 2018 - Dec 2023 took 4.291534423828125e-06s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 8.106231689453125e-06s
INFO | --- Analysis for greek_prisons_releases took 4943.658198595047s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.897026538848877s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.7378847599029541s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.724761962890625e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 6.67572021484375e-06s
INFO | --- Analysis for greekchildrensartmuseum took 7.041958808898926s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 5.14984130859375e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.00075531005859375s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.24354219436645508s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.0001304149627685547s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for green-competitiveness-gnoss took 11.725676536560059s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.377394437789917s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.008550643920898438s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.2761991024017334s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.696846008300781e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 6.4373016357421875e-06s
INFO | --- Analysis for grrp took 2.8281707763671875s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.2249143123626709s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.2632467746734619s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020858049392700195s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.866455078125e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 8.58306884765625e-06s
INFO | --- Analysis for grrt took 3.075129985809326s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.6036567687988281s
Availability | VoID file availability check for Geological Timescale took 0.0005853176116943359s
Extra | Recovery of all triples for Geological Timescale took 3.436635732650757s
Performance | Total latancy measurement for Geological Timescale took 3.338592052459717s
Amount of data | Number of triples check for Geological Timescale took 1.0379250049591064s
Interoperability | New terms check for Geological Timescale took 1.7430479526519775s
Versatility | Languages check for Geological Timescale took 0.5608096122741699s
Interpretability | Number of blank nodes check for Geological Timescale took 1.0166234970092773s
Security | Check HTTPS for Geological Timescale took 0.36907267570495605s
Interpretability | RDF structures check for Geological Timescale took 0.40831470489501953s
Versatility | Serialization formats check for Geological Timescale took 0.9448509216308594s
Availability | RDF dump link check for Geological Timescale took 1.1570465564727783s
License | MR license check for Geological Timescale took 0.4293227195739746s
License | HR license check for Geological Timescale took 0.4427790641784668s
Amount of data | Number of property check for Geological Timescale took 1.4948220252990723s
Understandability | Number of label check for Geological Timescale took 0.4514119625091553s
Understandability | URI regex check for Geological Timescale took 1.7695090770721436s
Understandability | Vocabs check for Geological Timescale took 0.9823887348175049s
Verifiability | Authors check for Geological Timescale took 0.4057655334472656s
Verifiability | Publishers check for Geological Timescale took 0.44875168800354004s
Performance | Throughput check for Geological Timescale took 12.85162353515625s
Amount of data | Check the number of entities for Geological Timescale took 0.021191120147705078s
Verifiability | Contribs. check for Geological Timescale took 0.3789854049682617s
Interlinking | sameAs chians check for Geological Timescale took 0.9914810657501221s
Interlinking | skos check for Geological Timescale took 0.38936519622802734s
Interlinking | skos check for Geological Timescale took 0.4001328945159912s
Timeliness | dataset update frequency check for Geological Timescale took 0.4087178707122803s
Currency | Creation date check for Geological Timescale took 1.365403652191162s
Currency | Modification date check for Geological Timescale took 0.9610855579376221s
Rep.Conc. | URIs length for Geological Timescale took 1.5824577808380127s
Interoperability | New vocabularies check for Geological Timescale took 2.2109110355377197s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.4461371898651123s
Accuracy | Check Functional Property for Geological Timescale took 0.44181346893310547s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.9707763195037842s
Accuracy | Check Empty annotation labels for Geological Timescale took 0.7861776351928711s
Accuracy | Check White space in annotation for Geological Timescale took 0.0153350830078125s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07155013084411621s
Consistency | Disjoint class check for Geological Timescale took 0.4453566074371338s
Consistency | Check Misplaced properties for Geological Timescale took 1.9119017124176025s
Consistency | Misplaced classes for Geological Timescale took 1.0603060722351074s
Consistency | Check Ontology hijacking for Geological Timescale took 1.796194076538086s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.2920801639556885s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 1.71632981300354s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.04903411865234375s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.46261096000671387s
Security | Sign check for Geological Timescale took 1.0092296600341797s
Availability | Check URIs Dereferenciability for Geological Timescale took 7.651692867279053s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.26407289505004883s
Reputation | Calculation of the PageRank for Geological Timescale took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 1.9870107173919678s
Believability | Calculation of trust value for Geological Timescale took 1.33514404296875e-05s
INFO | --- Analysis for GTS took 109.84569692611694s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.2576565742492676s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.02153778076171875s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.361701965332031e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for GTS-ont took 2.666912078857422s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.315376281738281e-05s
Availability | VoID file availability check for GUTSTOK  took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.26308393478393555s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.020795583724975586s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.0040740966796875e-05s
Believability | Calculation of trust value for GUTSTOK  took 1.1682510375976562e-05s
INFO | --- Analysis for Guillaume_Forget took 3.1794815063476562s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.172325134277344e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0007700920104980469s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.27020978927612305s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.020936012268066406s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 7.510185241699219e-05s
Believability | Calculation of trust value for Project Gutenberg took 1.2159347534179688e-05s
INFO | --- Analysis for gutenberg took 18.205350399017334s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.363059997558594e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.2536923885345459s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.647804260253906e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 9.059906005859375e-06s
INFO | --- Analysis for gwa-ili took 5.757863521575928s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 8.392333984375e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.2508242130279541s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.020662546157836914s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.075599670410156e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 1.049041748046875e-05s
INFO | --- Analysis for GWR took 22.09720468521118s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 8.392333984375e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.24647164344787598s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.020810842514038086s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0008490085601806641s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.5762786865234375e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 6.9141387939453125e-06s
INFO | --- Analysis for HASM took 21.506503105163574s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 6.651878356933594e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.2626657485961914s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.743171691894531e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 1.2159347534179688e-05s
INFO | --- Analysis for hcls-knowledge-base took 2.893425226211548s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 0.5739068984985352s
Availability | VoID file availability check for HealthCare Ontology took 0.00032901763916015625s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.25632691383361816s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.020702838897705078s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0009906291961669922s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 4.172325134277344e-05s
Believability | Calculation of trust value for HealthCare Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for HealthCare_Ontology took 3.5347061157226562s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 8.487701416015625e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.26073193550109863s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.020772933959960938s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.151199340820312e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 9.775161743164062e-06s
INFO | --- Analysis for heartfailure took 2.69240140914917s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.41565179824829s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.3115048408508301s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.022137165069580078s
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.2636184692382812e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 4.482269287109375e-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.0251998901367188e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 119.29907822608948s
Availability | SPARQL endpoint availability check for Hedatuz took 0.25842928886413574s
Availability | VoID file availability check for Hedatuz took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.25280332565307617s
Reputation | Calculation of the PageRank for Hedatuz took 0.021664857864379883s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.933906555175781e-05s
Believability | Calculation of trust value for Hedatuz took 1.1920928955078125e-05s
INFO | --- Analysis for hedatuz took 2.8934473991394043s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.23238468170166016s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2957487106323242s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020993709564208984s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012946128845214844s
Believability | Calculation of trust value for Hellenic Fire Brigade took 1.0251998901367188e-05s
INFO | --- Analysis for hellenic-fire-brigade took 2.7440648078918457s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.02608776092529297s
Availability | VoID file availability check for Hellenic Police took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.2585482597351074s
Reputation | Calculation of the PageRank for Hellenic Police took 0.020448923110961914s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00012993812561035156s
Believability | Calculation of trust value for Hellenic Police took 5.4836273193359375e-06s
INFO | --- Analysis for hellenic-police took 2.3854799270629883s
Availability | SPARQL endpoint availability check for Hermos took 4.076957702636719e-05s
Availability | VoID file availability check for Hermos took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for Hermos took 0.24552655220031738s
Reputation | Calculation of the PageRank for Hermos took 0.021298885345458984s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Hermos took 2.8848648071289062e-05s
Believability | Calculation of trust value for Hermos took 7.152557373046875e-06s
INFO | --- Analysis for Hermos took 2.9028303623199463s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.696846008300781e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.2513539791107178s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.02114415168762207s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 3.123283386230469e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 1.239776611328125e-05s
INFO | --- Analysis for Himanshu_Mahawar took 2.306295394897461s
Availability | SPARQL endpoint availability check for HITO took 0.41217470169067383s
Availability | VoID file availability check for HITO took 0.0003833770751953125s
Extra | Recovery of all triples for HITO took 1.7522687911987305s
Performance | Total latancy measurement for HITO took 0.98016357421875s
Amount of data | Number of triples check for HITO took 0.2042984962463379s
Interoperability | New terms check for HITO took 1.5277676582336426s
Versatility | Languages check for HITO took 0.20744729042053223s
Interpretability | Number of blank nodes check for HITO took 0.19953155517578125s
Interpretability | RDF structures check for HITO took 0.21077919006347656s
Versatility | Serialization formats check for HITO took 0.20856595039367676s
Availability | RDF dump link check for HITO took 0.1969151496887207s
License | MR license check for HITO took 0.2062547206878662s
License | HR license check for HITO took 0.2094268798828125s
Amount of data | Number of property check for HITO took 0.21508169174194336s
Understandability | Number of label check for HITO took 0.2123556137084961s
Understandability | URI regex check for HITO took 0.3735475540161133s
Understandability | Vocabs check for HITO took 0.21050071716308594s
Verifiability | Authors check for HITO took 0.1904129981994629s
Verifiability | Publishers check for HITO took 0.2097184658050537s
Performance | Throughput check for HITO took 11.564510345458984s
Amount of data | Check the number of entities for HITO took 7.128715515136719e-05s
Verifiability | Contribs. check for HITO took 0.19431495666503906s
Interlinking | sameAs chians check for HITO took 0.2105414867401123s
Interlinking | skos check for HITO took 0.2104489803314209s
Interlinking | skos check for HITO took 0.20643305778503418s
Timeliness | dataset update frequency check for HITO took 0.19994068145751953s
Currency | Creation date check for HITO took 0.4214508533477783s
Currency | Modification date check for HITO took 0.4013524055480957s
Rep.Conc. | URIs length for HITO took 1.0777032375335693s
Interoperability | New vocabularies check for HITO took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.19824743270874023s
Accuracy | Check Functional Property for HITO took 0.20850086212158203s
Accuracy | Check Inverse Functional Property for HITO took 0.19614410400390625s
Accuracy | Check Empty annotation labels for HITO took 0.4974064826965332s
Accuracy | Check White space in annotation for HITO took 0.013392448425292969s
Accuracy | Check Datatype consistency for HITO took 0.0747215747833252s
Consistency | Disjoint class check for HITO took 0.20783567428588867s
Consistency | Check Misplaced properties for HITO took 0.4987144470214844s
Consistency | Misplaced classes for HITO took 0.35975050926208496s
Consistency | Check Ontology hijacking for HITO took 1.816995620727539s
Consistency | Check Invalid usage of undefined classes for HITO took 1.3434326648712158s
Consistency | Check Invalid usage of undefined properties for HITO took 1.5924293994903564s
Conciseness | Check Extensional conciseness for HITO took 0.06275415420532227s
Conciseness | Check Intensional conciseness for HITO took 0.188507080078125s
Security | Sign check for HITO took 0.19204211235046387s
Availability | Check URIs Dereferenciability for HITO took 2161.349275827408s
Completeness | Calculation of interlinking completeness for HITO took 1.0721774101257324s
Reputation | Calculation of the PageRank for HITO took 0.021091699600219727s
Interlinking | Calculation of Degree of Connection for HITO took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for HITO took 9.512901306152344e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.1920928955078125e-06s
Believability | Calculation of trust value for HITO took 1.1920928955078125e-05s
INFO | --- Analysis for hito took 2221.598654985428s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 18.002792835235596s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.28151988983154297s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.021183013916015625s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 4.553794860839844e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 1.2159347534179688e-05s
INFO | --- Analysis for Hoa_Thinh_Phat took 51.50109934806824s
Availability | SPARQL endpoint availability check for Homologene took 4.9591064453125e-05s
Availability | VoID file availability check for Homologene took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Homologene took 0.2795681953430176s
Reputation | Calculation of the PageRank for Homologene took 0.0215151309967041s
Interlinking | Calculation of Degree of Connection for Homologene took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Homologene took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Homologene took 3.123283386230469e-05s
Believability | Calculation of trust value for Homologene took 7.152557373046875e-06s
INFO | --- Analysis for homologene took 2.945690870285034s
Availability | SPARQL endpoint availability check for gseg took 9.012222290039062e-05s
Availability | VoID file availability check for gseg took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for gseg took 0.26401185989379883s
Reputation | Calculation of the PageRank for gseg took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for gseg took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for gseg took 3.218650817871094e-05s
Believability | Calculation of trust value for gseg took 1.1920928955078125e-05s
INFO | --- Analysis for hongse took 3.171565294265747s
Availability | SPARQL endpoint availability check for Noticias Universia took 4.220008850097656e-05s
Availability | VoID file availability check for Noticias Universia took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.2618706226348877s
Reputation | Calculation of the PageRank for Noticias Universia took 0.022655725479125977s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 3.337860107421875e-05s
Believability | Calculation of trust value for Noticias Universia took 1.2874603271484375e-05s
INFO | --- Analysis for http-data-noticias-universia-net took 3.0416951179504395s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 7.033348083496094e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.2636756896972656s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.022303342819213867s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 3.24249267578125e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.1444091796875e-05s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 3.0042741298675537s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 9.771491289138794s
Availability | VoID file availability check for COURAGE Dataset took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.2603721618652344s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.02117753028869629s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.5762786865234375e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.1444091796875e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 13.980497121810913s
Availability | SPARQL endpoint availability check for RoadTrb took 8.845329284667969e-05s
Availability | VoID file availability check for RoadTrb took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.2665588855743408s
Reputation | Calculation of the PageRank for RoadTrb took 0.021851062774658203s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.170967102050781e-05s
Believability | Calculation of trust value for RoadTrb took 1.239776611328125e-05s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 3.281280755996704s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0007276535034179688s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.26415061950683594s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.021573305130004883s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.647804260253906e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.239776611328125e-05s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 25.948025226593018s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 4.410743713378906e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.2621591091156006s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.02219104766845703s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.123283386230469e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.2159347534179688e-05s
INFO | --- Analysis for http:pakistan.com took 2.4549264907836914s
Availability | SPARQL endpoint availability check for CEDICT took 4.2438507080078125e-05s
Availability | VoID file availability check for CEDICT took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for CEDICT took 0.26242566108703613s
Reputation | Calculation of the PageRank for CEDICT took 0.02065753936767578s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for CEDICT took 4.935264587402344e-05s
Believability | Calculation of trust value for CEDICT took 1.0728836059570312e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 3.9545583724975586s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 2.7892096042633057s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2704446315765381s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020897865295410156s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.200241088867188e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.33514404296875e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 6.054634094238281s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.124641418457031e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.2693827152252197s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.02252984046936035s
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.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.314018249511719e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 1.2159347534179688e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 3.032142400741577s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 5.054473876953125e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.26336669921875s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.020928144454956055s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 2.9325485229492188e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.0967254638671875e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.4656403064727783s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.26017022132873535s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for Soccer Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for http:www.msm.com took 2.4378347396850586s
Availability | SPARQL endpoint availability check for Game Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Game Ontology took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.2759737968444824s
Reputation | Calculation of the PageRank for Game Ontology took 0.020504236221313477s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.0279159545898438e-05s
Believability | Calculation of trust value for Game Ontology took 7.867813110351562e-06s
INFO | --- Analysis for http:www.RAG.comgameonto# took 2.9910929203033447s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 7.796287536621094e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007851123809814453s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.26747941970825195s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.409385681152344e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.2636184692382812e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 2.999706983566284s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 5.435943603515625e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.27724790573120117s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.170967102050781e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.2159347534179688e-05s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.4727349281311035s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.6253204345703125e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.28383469581604004s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021977663040161133s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.1948089599609375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1920928955078125e-05s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.438232183456421s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.220008850097656e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.28258299827575684s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.266334533691406e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.4373016357421875e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.4983415603637695s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.000102996826171875s
Availability | VoID file availability check for Indian Biodiversity took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2586829662322998s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020807743072509766s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.1948089599609375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2874603271484375e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.436767816543579s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.940696716308594e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.25989389419555664s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.123283386230469e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.152557373046875e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 3.868619203567505s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 6.818771362304688e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2613389492034912s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02225017547607422s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9087066650390625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.0013580322265625e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.4541077613830566s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.7206878662109375e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.27342700958251953s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.022289037704467773s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.0040740966796875e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0967254638671875e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 4.162893056869507s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.1077790260314941s
Availability | VoID file availability check for Bookkeeping took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.2737259864807129s
Reputation | Calculation of the PageRank for Bookkeeping took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bookkeeping took 7.152557373046875e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 4.111992120742798s
Availability | SPARQL endpoint availability check for Legal Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Legal Ontology took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.261791467666626s
Reputation | Calculation of the PageRank for Legal Ontology took 0.020526409149169922s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for Legal Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 2.903562545776367s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 5.364418029785156e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.30609869956970215s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020336389541625977s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.534027099609375e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.1205673217773438e-05s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.6771233081817627s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.458427429199219e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.2571685314178467s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 2.8848648071289062e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 1.0967254638671875e-05s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.602849006652832s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 4.935264587402344e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.27448511123657227s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.020483016967773438s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 2.8371810913085938e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 1.1682510375976562e-05s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 2.9507293701171875s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 4.029273986816406e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2754940986633301s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.020410776138305664s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 1.0967254638671875e-05s
INFO | --- Analysis for hud-library-usagedata took 2.9797682762145996s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.4422895908355713s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.27309751510620117s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.022205829620361328s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.000102996826171875s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 9.775161743164062e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 4.244446039199829s
Availability | SPARQL endpoint availability check for IATE RDF took 8.726119995117188e-05s
Availability | VoID file availability check for IATE RDF took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.2607841491699219s
Reputation | Calculation of the PageRank for IATE RDF took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.4809112548828125e-05s
Believability | Calculation of trust value for IATE RDF took 1.0728836059570312e-05s
INFO | --- Analysis for iate-rdf took 2.7256691455841064s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.239838600158691s
Availability | VoID file availability check for IATI as Linked Data took 0.0006258487701416016s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.2750115394592285s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.02039623260498047s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.249282836914062e-05s
Believability | Calculation of trust value for IATI as Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for iati-as-linked-data took 13.765929937362671s
Availability | SPARQL endpoint availability check for ICANE took 0.3376271724700928s
Availability | VoID file availability check for ICANE took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for ICANE took 0.26837706565856934s
Reputation | Calculation of the PageRank for ICANE took 0.0209810733795166s
Interlinking | Calculation of Degree of Connection for ICANE took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.654594421386719e-05s
Believability | Calculation of trust value for ICANE took 9.5367431640625e-06s
INFO | --- Analysis for icane took 3.6436967849731445s
Availability | SPARQL endpoint availability check for ichoose took 0.14751219749450684s
Availability | VoID file availability check for ichoose took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for ichoose took 0.2621042728424072s
Reputation | Calculation of the PageRank for ichoose took 0.021171092987060547s
Interlinking | Calculation of Degree of Connection for ichoose took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ichoose took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.937980651855469e-05s
Believability | Calculation of trust value for ichoose took 1.0013580322265625e-05s
INFO | --- Analysis for ichoose took 54.69097304344177s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 0.26300811767578125s
Availability | VoID file availability check for The Iconology Dataset took 0.0004940032958984375s
Extra | Recovery of all triples for The Iconology Dataset took 3.139171838760376s
Performance | Total latancy measurement for The Iconology Dataset took 0.4025897979736328s
Amount of data | Number of triples check for The Iconology Dataset took 0.21332192420959473s
Interoperability | New terms check for The Iconology Dataset took 1.4402217864990234s
Versatility | Languages check for The Iconology Dataset took 0.6013190746307373s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.21155452728271484s
Interpretability | RDF structures check for The Iconology Dataset took 0.11439800262451172s
Versatility | Serialization formats check for The Iconology Dataset took 0.09691572189331055s
Availability | RDF dump link check for The Iconology Dataset took 0.08112692832946777s
License | MR license check for The Iconology Dataset took 0.09196686744689941s
License | HR license check for The Iconology Dataset took 0.4011869430541992s
Amount of data | Number of property check for The Iconology Dataset took 0.09596467018127441s
Understandability | Number of label check for The Iconology Dataset took 0.13298368453979492s
Understandability | URI regex check for The Iconology Dataset took 0.16439104080200195s
Understandability | Vocabs check for The Iconology Dataset took 0.08377766609191895s
Verifiability | Authors check for The Iconology Dataset took 0.09317302703857422s
Verifiability | Publishers check for The Iconology Dataset took 0.0838921070098877s
Performance | Throughput check for The Iconology Dataset took 10.356670379638672s
Amount of data | Check the number of entities for The Iconology Dataset took 6.031990051269531e-05s
Verifiability | Contribs. check for The Iconology Dataset took 0.07980179786682129s
Interlinking | sameAs chians check for The Iconology Dataset took 0.09109282493591309s
Interlinking | skos check for The Iconology Dataset took 0.08451223373413086s
Interlinking | skos check for The Iconology Dataset took 0.07453393936157227s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.08641672134399414s
Currency | Creation date check for The Iconology Dataset took 0.16389131546020508s
Currency | Modification date check for The Iconology Dataset took 0.18022441864013672s
Rep.Conc. | URIs length for The Iconology Dataset took 1.2535409927368164s
Interoperability | New vocabularies check for The Iconology Dataset took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08040237426757812s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.2693452835083008s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.01635599136352539s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.42526674270629883s
Consistency | Disjoint class check for The Iconology Dataset took 0.08110761642456055s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.1464698314666748s
Consistency | Misplaced classes for The Iconology Dataset took 0.8455612659454346s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.6685304641723633s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.3045737743377686s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.3844773769378662s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.28916263580322266s
Security | Sign check for The Iconology Dataset took 0.07987260818481445s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2520.2433865070343s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 1.6775617599487305s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.020843982696533203s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 2.1219253540039062e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for The Iconology Dataset took 1.0967254638671875e-05s
INFO | --- Analysis for iconology-dataset took 2577.2233815193176s
Availability | SPARQL endpoint availability check for Identifiers.org took 4.506111145019531e-05s
Availability | VoID file availability check for Identifiers.org took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.277815580368042s
Reputation | Calculation of the PageRank for Identifiers.org took 0.020388364791870117s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 3.7670135498046875e-05s
Believability | Calculation of trust value for Identifiers.org took 1.1920928955078125e-05s
INFO | --- Analysis for identifiers-org took 2.9933884143829346s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.363059997558594e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.2636096477508545s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 0.00010275840759277344s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 1.049041748046875e-05s
INFO | --- Analysis for idreffr took 23.093624114990234s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 1.803934097290039s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.25812625885009766s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020334482192993164s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.7206878662109375e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 1.1205673217773438e-05s
INFO | --- Analysis for ids took 4.6886210441589355s
Availability | SPARQL endpoint availability check for ietflang took 4.172325134277344e-05s
Availability | VoID file availability check for ietflang took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for ietflang took 0.3050098419189453s
Reputation | Calculation of the PageRank for ietflang took 0.020344972610473633s
Interlinking | Calculation of Degree of Connection for ietflang took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ietflang took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.4345855712890625e-05s
Believability | Calculation of trust value for ietflang took 1.1205673217773438e-05s
INFO | --- Analysis for ietflang took 12.633905410766602s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.6355440616607666s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.2632896900177002s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02256178855895996s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.6716461181640625e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.0967254638671875e-05s
INFO | --- Analysis for IGVLL took 4.782547473907471s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 19.47164821624756s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0005936622619628906s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 19.022817611694336s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 49.16740155220032s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 10.80120301246643s
Interoperability | New terms check for 3LGM² IHE Ontology took 10.115652084350586s
Versatility | Languages check for 3LGM² IHE Ontology took 12.498196601867676s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 9.4515061378479s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 11.279082536697388s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 10.408925533294678s
Availability | RDF dump link check for 3LGM² IHE Ontology took 7.856632232666016s
License | MR license check for 3LGM² IHE Ontology took 10.945555448532104s
License | HR license check for 3LGM² IHE Ontology took 5.269936561584473s
Amount of data | Number of property check for 3LGM² IHE Ontology took 9.265347242355347s
Understandability | Number of label check for 3LGM² IHE Ontology took 7.781559944152832s
Understandability | URI regex check for 3LGM² IHE Ontology took 20.11023187637329s
Understandability | Vocabs check for 3LGM² IHE Ontology took 5.898481607437134s
Verifiability | Authors check for 3LGM² IHE Ontology took 12.680792570114136s
Verifiability | Publishers check for 3LGM² IHE Ontology took 5.207905530929565s
Performance | Throughput check for 3LGM² IHE Ontology took 53.806883096694946s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 4.0531158447265625e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.8437840938568115s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.25176024436950684s
Interlinking | skos check for 3LGM² IHE Ontology took 0.19858598709106445s
Interlinking | skos check for 3LGM² IHE Ontology took 0.1957228183746338s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.1973743438720703s
Currency | Creation date check for 3LGM² IHE Ontology took 0.4975318908691406s
Currency | Modification date check for 3LGM² IHE Ontology took 0.5714538097381592s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 1.212601900100708s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.21248626708984375s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.5336909294128418s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.2059950828552246s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.32843804359436035s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.0017430782318115234s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.04958081245422363s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.20850086212158203s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.8521051406860352s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.289165735244751s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.659933090209961s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.3276243209838867s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.7730281352996826s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.030530691146850586s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.1979367733001709s
Security | Sign check for 3LGM² IHE Ontology took 0.19845342636108398s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 747.240823507309s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.5633959770202637s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.021329879760742188s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 4.0531158447265625e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.1920928955078125e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 8.344650268554688e-06s
INFO | --- Analysis for IHE took 1099.117213010788s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 3.4128987789154053s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0005266666412353516s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 7.18841290473938s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 8.163778305053711s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 17.637744665145874s
Interoperability | New terms check for Test Site, LOD Lab 317 took 7.952426433563232s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.68023920059204s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 2.2303576469421387s
Security | Check HTTPS for Test Site, LOD Lab 317 took 1.123701572418213s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 2.8833093643188477s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 2.283414125442505s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.8071718215942383s
License | MR license check for Test Site, LOD Lab 317 took 2.2780721187591553s
License | HR license check for Test Site, LOD Lab 317 took 2.545530319213867s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.762770414352417s
Understandability | Number of label check for Test Site, LOD Lab 317 took 3.1365249156951904s
Understandability | URI regex check for Test Site, LOD Lab 317 took 3.7980830669403076s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.6719706058502197s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.7453320026397705s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 1.6627185344696045s
Performance | Throughput check for Test Site, LOD Lab 317 took 16.56026864051819s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 3.600120544433594e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.7131996154785156s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.7532546520233154s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.9671564102172852s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.6920444965362549s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.985215425491333s
Currency | Creation date check for Test Site, LOD Lab 317 took 3.386970043182373s
Currency | Modification date check for Test Site, LOD Lab 317 took 3.3767473697662354s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 33.939878940582275s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.6698925495147705s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.815782070159912s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.7876076698303223s
Accuracy | Check Empty annotation labels for Test Site, LOD Lab 317 took 3.9557597637176514s
Accuracy | Check White space in annotation for Test Site, LOD Lab 317 took 0.030364036560058594s
Accuracy | Check Datatype consistency for Test Site, LOD Lab 317 took 0.028116226196289062s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.6524081230163574s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 24.406904935836792s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 2.014800548553467s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 5.358582973480225s
Consistency | Check Invalid usage of undefined classes for Test Site, LOD Lab 317 took 1.298699140548706s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 23.45421576499939s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.03174877166748047s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.265007972717285s
Security | Sign check for Test Site, LOD Lab 317 took 2.341212511062622s
Availability | Check URIs Dereferenciability for Test Site, LOD Lab 317 took 14.207072019577026s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.7372050285339355s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.021411895751953125s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.600120544433594e-05s
Interoperability | Check the re-using of existing vocabs for Test Site, LOD Lab 317 took 1.1920928955078125e-06s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 7.152557373046875e-06s
INFO | --- Analysis for iislod-test took 517.6117293834686s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 8.535385131835938e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0004069805145263672s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.2871670722961426s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.020685672760009766s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.170967102050781e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 1.0728836059570312e-05s
INFO | --- Analysis for ILUSOC took 18.31759524345398s
Availability | SPARQL endpoint availability check for im@sparql took 6.548225402832031s
Availability | VoID file availability check for im@sparql took 0.00035309791564941406s
Completeness | Calculation of interlinking completeness for im@sparql took 0.2636585235595703s
Reputation | Calculation of the PageRank for im@sparql took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.4332275390625e-05s
Believability | Calculation of trust value for im@sparql took 7.152557373046875e-06s
INFO | --- Analysis for im@sparql took 13.632428169250488s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.1961669921875e-05s
Availability | VoID file availability check for imagery bailingniao took 0.00034737586975097656s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.24227595329284668s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.0279159545898438e-05s
Believability | Calculation of trust value for imagery bailingniao took 6.9141387939453125e-06s
INFO | --- Analysis for imagery_bailingniao took 3.960991621017456s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.0526211261749268s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0008862018585205078s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 20.43431258201599s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.3501994609832764s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.98678970336914s
Interoperability | New terms check for Imagesnippets Image Descriptions took 2.2250423431396484s
Versatility | Languages check for Imagesnippets Image Descriptions took 20.257700204849243s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.030890941619873s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.6855106353759766s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.6887221336364746s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7023923397064209s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.6680352687835693s
License | MR license check for Imagesnippets Image Descriptions took 0.6594746112823486s
License | HR license check for Imagesnippets Image Descriptions took 30.690465211868286s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.6817080974578857s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.56622052192688s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.3577005863189697s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.6485774517059326s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.6686229705810547s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.6778354644775391s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.54212760925293s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 6.747245788574219e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.6518874168395996s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.698528528213501s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6806950569152832s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6897046566009521s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.6611783504486084s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.33404541015625s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.3745524883270264s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 33.42948389053345s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.6486461162567139s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.6612083911895752s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.6572215557098389s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 11.627119064331055s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.218226432800293s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.306480884552002s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.6899526119232178s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.781657457351685s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 5.082296371459961s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.4795477390289307s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.647269248962402s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 2.830625057220459s
Security | Sign check for Imagesnippets Image Descriptions took 0.6792502403259277s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 10.363050699234009s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.4573390483856201s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.560585021972656e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.430511474609375e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 7.867813110351562e-06s
INFO | --- Analysis for imagesnippets took 371.69534277915955s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.5782582759857178s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.263216495513916s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.020795345306396484s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.726119995117188e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for imf-linked-data took 3.0643293857574463s
Availability | SPARQL endpoint availability check for IMGpedia took 4.100799560546875e-05s
Availability | VoID file availability check for IMGpedia took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.2800567150115967s
Reputation | Calculation of the PageRank for IMGpedia took 0.02098703384399414s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.0994415283203125e-05s
Believability | Calculation of trust value for IMGpedia took 7.3909759521484375e-06s
INFO | --- Analysis for imgpedia took 2.995771646499634s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 4.410743713378906e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.2994043827056885s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.020705699920654297s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 3.147125244140625e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 8.58306884765625e-06s
INFO | --- Analysis for import-status-of-gmo-crops took 2.9810001850128174s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.363059997558594e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.27989840507507324s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.02208709716796875s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.2874603271484375e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 1.1920928955078125e-05s
INFO | --- Analysis for Imtiaz took 2.4971437454223633s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.506111145019531e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.26353907585144043s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.023079872131347656s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 3.170967102050781e-05s
Believability | Calculation of trust value for Royalty Free Music took 1.0728836059570312e-05s
INFO | --- Analysis for inaudio.org took 4.0268330574035645s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 8.320808410644531e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.265331506729126s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.021582603454589844s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 3.1948089599609375e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 1.1920928955078125e-05s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 3.0639257431030273s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 4.410743713378906e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.26605796813964844s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.021051406860351562s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 3.0040740966796875e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 1.2159347534179688e-05s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 3.015763521194458s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.6159675121307373s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.2634615898132324s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.02029561996459961s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 1.0967254638671875e-05s
INFO | --- Analysis for IndexThomisticusTreebank took 4.193809747695923s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.1961669921875e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.2654111385345459s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 2.765655517578125e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.1444091796875e-05s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 2.978048086166382s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.506111145019531e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.30121469497680664s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020296096801757812s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00010657310485839844s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 6.9141387939453125e-06s
INFO | --- Analysis for ineverycrea took 23.165628910064697s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.220008850097656e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.00037217140197753906s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.2704432010650635s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.940696716308594e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.0967254638671875e-05s
INFO | --- Analysis for ineverycrea-argentina took 13.407166481018066s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 270.6914367675781s
Availability | VoID file availability check for Influence Tracker Dataset took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.3030586242675781s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02116084098815918s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.581710815429688e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 7.867813110351562e-06s
INFO | --- Analysis for influence-tracker-dataset took 564.3117957115173s
Availability | SPARQL endpoint availability check for INSEMTIVES took 4.124641418457031e-05s
Availability | VoID file availability check for INSEMTIVES took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.2539989948272705s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020703792572021484s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 3.0040740966796875e-05s
Believability | Calculation of trust value for INSEMTIVES took 1.0728836059570312e-05s
INFO | --- Analysis for insemtives took 2.9597675800323486s
Availability | SPARQL endpoint availability check for instagram.person took 4.172325134277344e-05s
Availability | VoID file availability check for instagram.person took 0.000457763671875s
Completeness | Calculation of interlinking completeness for instagram.person took 0.2518274784088135s
Reputation | Calculation of the PageRank for instagram.person took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for instagram.person took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for instagram.person took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for instagram.person took 2.7418136596679688e-05s
Believability | Calculation of trust value for instagram.person took 1.0728836059570312e-05s
INFO | --- Analysis for instagram_person took 2.9668924808502197s
Availability | SPARQL endpoint availability check for instagram.videoobject took 4.0531158447265625e-05s
Availability | VoID file availability check for instagram.videoobject took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.28647804260253906s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.02034783363342285s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 2.9087066650390625e-05s
Believability | Calculation of trust value for instagram.videoobject took 1.239776611328125e-05s
INFO | --- Analysis for instagram_videoobject took 3.0276334285736084s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.887580871582031e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.2991170883178711s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.020826339721679688s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 3.170967102050781e-05s
Believability | Calculation of trust value for Instance Hub Countries took 1.0013580322265625e-05s
INFO | --- Analysis for instance-hub-countries took 2.9747767448425293s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 8.58306884765625e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.27814531326293945s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.02309703826904297s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 2.9325485229492188e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 5.7220458984375e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.477175712585449s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.00543212890625e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.2889406681060791s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.023385286331176758s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 2.9325485229492188e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 1.049041748046875e-05s
INFO | --- Analysis for instance-hub-organizations took 3.0248019695281982s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.029273986816406e-05s
Availability | VoID file availability check for Instance Hub People took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.26715588569641113s
Reputation | Calculation of the PageRank for Instance Hub People took 0.02114582061767578s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 3.0517578125e-05s
Believability | Calculation of trust value for Instance Hub People took 1.0013580322265625e-05s
INFO | --- Analysis for instance-hub-people took 2.988158941268921s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 4.076957702636719e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.2943429946899414s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.020729780197143555s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 2.9325485229492188e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 1.1205673217773438e-05s
INFO | --- Analysis for instance-hub-us-civil-servants took 3.0135955810546875s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 8.463859558105469e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.276029109954834s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.022202730178833008s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.075599670410156e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 1.0967254638671875e-05s
INFO | --- Analysis for instance-hub-us-congressional-committees took 3.0387065410614014s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 6.580352783203125e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.2585780620574951s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.02205514907836914s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 3.170967102050781e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 1.0728836059570312e-05s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.988048553466797s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 4.0531158447265625e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.26549243927001953s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 1.049041748046875e-05s
INFO | --- Analysis for instance-hub-us-crops took 3.0595107078552246s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 8.0108642578125e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.27758097648620605s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.020947933197021484s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 2.9325485229492188e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 1.0251998901367188e-05s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.9775757789611816s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 4.9114227294921875e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.294757604598999s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.020641326904296875s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 2.973421335220337s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.28395843505859375s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.020909786224365234s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0010480880737304688s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 3.790855407714844e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 7.867813110351562e-06s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 2.9550583362579346s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 7.605552673339844e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.29341673851013184s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 2.9802322387695312e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 6.9141387939453125e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 2.985236644744873s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 5.3882598876953125e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0003352165222167969s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.2741081714630127s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00011372566223144531s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for interactivemaps-gnoss took 10.59117078781128s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 7.2479248046875e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.2692875862121582s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.02191758155822754s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0010688304901123047s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.695487976074219e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 1.1682510375976562e-05s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 2.9744560718536377s
Availability | SPARQL endpoint availability check for intervalue took 0.25157976150512695s
Availability | VoID file availability check for intervalue took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for intervalue took 0.2796182632446289s
Reputation | Calculation of the PageRank for intervalue took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for intervalue took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.508827209472656e-05s
Believability | Calculation of trust value for intervalue took 1.1682510375976562e-05s
INFO | --- Analysis for intervalue took 2.677935838699341s
Availability | SPARQL endpoint availability check for Inztrow took 4.1484832763671875e-05s
Availability | VoID file availability check for Inztrow took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Inztrow took 0.2776341438293457s
Reputation | Calculation of the PageRank for Inztrow took 0.022037982940673828s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Inztrow took 2.9325485229492188e-05s
Believability | Calculation of trust value for Inztrow took 1.1682510375976562e-05s
INFO | --- Analysis for Inztrow took 3.7622978687286377s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 8.106231689453125e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.2641913890838623s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.020452022552490234s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 2.9325485229492188e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 1.1444091796875e-05s
INFO | --- Analysis for ipbes took 3.7285876274108887s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.172325134277344e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.2831087112426758s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.021358489990234375s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0009493827819824219s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.839897155761719e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 1.1920928955078125e-05s
INFO | --- Analysis for iptc-newscodes took 3.552361488342285s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.1484832763671875e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.2775745391845703s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 2.765655517578125e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 1.1205673217773438e-05s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 3.0689516067504883s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.4930310249328613s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.2568531036376953s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.703636169433594e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 1.0251998901367188e-05s
INFO | --- Analysis for iserve took 9.296725273132324s
Availability | SPARQL endpoint availability check for ISIC V4 took 21.08809733390808s
Availability | VoID file availability check for ISIC V4 took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.2894113063812256s
Reputation | Calculation of the PageRank for ISIC V4 took 0.0279085636138916s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 4.3392181396484375e-05s
Believability | Calculation of trust value for ISIC V4 took 8.821487426757812e-06s
INFO | --- Analysis for isic-v4 took 116.17103719711304s
Availability | SPARQL endpoint availability check for Isidore took 5.125999450683594e-05s
Availability | VoID file availability check for Isidore took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Isidore took 0.24832558631896973s
Reputation | Calculation of the PageRank for Isidore took 0.022879362106323242s
Interlinking | Calculation of Degree of Connection for Isidore took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Isidore took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Isidore took 2.8133392333984375e-05s
Believability | Calculation of trust value for Isidore took 1.1920928955078125e-05s
INFO | --- Analysis for isidore took 2.975468397140503s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.291534423828125e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.2680480480194092s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.021692514419555664s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 6.699562072753906e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 5.9604644775390625e-06s
INFO | --- Analysis for isil-dbpedia took 4.306314468383789s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 6.079673767089844e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.2749912738800049s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.020709514617919922s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 2.956390380859375e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 7.62939453125e-06s
INFO | --- Analysis for iso-3166-2-data took 2.97621488571167s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.2438507080078125e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.27966809272766113s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.409385681152344e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 7.152557373046875e-06s
INFO | --- Analysis for iso-639-oasis took 3.1279420852661133s
Availability | SPARQL endpoint availability check for ISOcat took 4.410743713378906e-05s
Availability | VoID file availability check for ISOcat took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for ISOcat took 0.4024844169616699s
Reputation | Calculation of the PageRank for ISOcat took 0.022559404373168945s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.103515625e-05s
Believability | Calculation of trust value for ISOcat took 9.298324584960938e-06s
INFO | --- Analysis for isocat took 33.524961948394775s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 8.893013000488281e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.27797889709472656s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020969390869140625s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.814697265625e-05s
Believability | Calculation of trust value for ISOcat-metadata took 9.5367431640625e-06s
INFO | --- Analysis for isocat-metadata took 4.789880752563477s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 3.886222839355469e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.27007484436035156s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.02125835418701172s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 3.0040740966796875e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 9.775161743164062e-06s
INFO | --- Analysis for ispra-lod-ihi took 2.978513479232788s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10703229904174805s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0005693435668945312s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.299702405929565s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.24495482444763184s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12236785888671875s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.9616899490356445s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 93.10448026657104s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.05421018600463867s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.03137469291687012s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08070874214172363s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07311725616455078s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.05703306198120117s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10960125923156738s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.53556060791016s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.051836252212524414s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2284305095672607s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2058579921722412s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08538222312927246s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0874471664428711s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.04942822456359863s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.28995680809021s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.3392181396484375e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08839273452758789s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14424538612365723s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.33996129035949707s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3373229503631592s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08718729019165039s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09789252281188965s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.04845094680786133s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 13.485896587371826s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.05023336410522461s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.051200151443481445s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.05564689636230469s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.6575443744659424s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.31474828720092773s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2647709846496582s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.04856133460998535s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.465912580490112s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.8752143383026123s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.833428144454956s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3702449798583984s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.712382316589355s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2897982597351074s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.059098005294799805s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07451295852661133s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 12.24624228477478s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.36464571952819824s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.870529174804688e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2159347534179688e-05s
INFO | --- Analysis for ispra-lod-place took 448.43232822418213s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.124641418457031e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.2780461311340332s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.0279159545898438e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.2159347534179688e-05s
INFO | --- Analysis for ispra-lod-rmn took 2.993800640106201s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.04925060272216797s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.00026702880859375s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 5.995694160461426s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.2803208827972412s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.12647294998168945s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.991591453552246s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 90.28718638420105s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.06216788291931152s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.0317387580871582s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.09353232383728027s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.06940126419067383s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.05988717079162598s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.12560009956359863s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 91.73129487037659s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.053344011306762695s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 0.9876649379730225s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.236893892288208s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.09692978858947754s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.0977935791015625s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.050504207611083984s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.571962833404541s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 6.937980651855469e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.09583044052124023s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.17212438583374023s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.40743446350097656s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.413189172744751s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.10219764709472656s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.10596942901611328s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.051445722579956055s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 13.502723455429077s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.05100107192993164s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.053998470306396484s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.05378866195678711s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 2.7849388122558594s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.31322145462036133s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.26371097564697266s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.0501711368560791s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.44574236869812s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.8802852630615234s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 2.919414520263672s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.3436107635498047s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.842366933822632s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.29383158683776855s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.05849742889404297s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.08066344261169434s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 11.513541221618652s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.47116708755493164s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.021210432052612305s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.315376281738281e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.1920928955078125e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 1.2636184692382812e-05s
INFO | --- Analysis for ispra-lod-ron took 443.3368880748749s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 9.202957153320312e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.2479393482208252s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.022936344146728516s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 3.0040740966796875e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 1.1682510375976562e-05s
INFO | --- Analysis for ispra-lod-sc took 3.0416030883789062s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.6162118911743164s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.2773549556732178s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.021811485290527344s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.417533874511719e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 1.3113021850585938e-05s
INFO | --- Analysis for issa-agritrop took 4.530141830444336s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 6.961822509765625e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.27487874031066895s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02109074592590332s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.910064697265625e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 7.62939453125e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.4272968769073486s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 8.940696716308594e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.29137659072875977s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.0205996036529541s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007226467132568359s
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.33514404296875e-05s
INFO | --- Analysis for ISSN:_0080-3626 took 2.725722551345825s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.291534423828125e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.24724364280700684s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.4332275390625e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 1.1920928955078125e-05s
INFO | --- Analysis for ISSN:_0080-3626. took 2.534964084625244s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 0.24610114097595215s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.2759683132171631s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.02224278450012207s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 9.202957153320312e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 1.0728836059570312e-05s
INFO | --- Analysis for istat-immigration took 2.7253196239471436s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 7.081031799316406e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.2544209957122803s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.021884679794311523s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 2.9802322387695312e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 7.152557373046875e-06s
INFO | --- Analysis for istat-immigrazione took 2.975536823272705s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.24720120429992676s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0007886886596679688s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.26935815811157227s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.02213597297668457s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.0279159545898438e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 1.0728836059570312e-05s
INFO | --- Analysis for it-aifa-drug-prices took 2.972921848297119s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 0.2234642505645752s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.25824880599975586s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.021110057830810547s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.414817810058594e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 1.2874603271484375e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 2.6604745388031006s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 5.030632019042969e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.26910901069641113s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.020864248275756836s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 3.62396240234375e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 1.239776611328125e-05s
INFO | --- Analysis for iucr-acta-cryst-e took 2.989530563354492s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.124641418457031e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.27939915657043457s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.020796537399291992s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 2.956390380859375e-05s
Believability | Calculation of trust value for IWMI Research Reports took 1.2874603271484375e-05s
INFO | --- Analysis for iwmi-research-reports took 3.047480821609497s
Availability | SPARQL endpoint availability check for IWN took 9.083747863769531e-05s
Availability | VoID file availability check for IWN took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for IWN took 0.2549862861633301s
Reputation | Calculation of the PageRank for IWN took 0.021798133850097656s
Interlinking | Calculation of Degree of Connection for IWN took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for IWN took 3.814697265625e-05s
Believability | Calculation of trust value for IWN took 9.5367431640625e-06s
INFO | --- Analysis for iwn took 2.9814839363098145s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 4.029273986816406e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.2778468132019043s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.021863460540771484s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 3.123283386230469e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 1.0013580322265625e-05s
INFO | --- Analysis for j-global-knowledge took 3.030055522918701s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 4.100799560546875e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.001107931137084961s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.29106616973876953s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.020757436752319336s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 3.075599670410156e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 1.2159347534179688e-05s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 3.034850835800171s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 5.688910245895386s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.2869548797607422s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.508827209472656e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 1.4066696166992188e-05s
INFO | --- Analysis for jamendo-dbtune took 10.525564908981323s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 8.654594421386719e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.25838398933410645s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.021625995635986328s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.696846008300781e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.692003965377808s
Availability | SPARQL endpoint availability check for JEL Classification took 8.630752563476562e-05s
Availability | VoID file availability check for JEL Classification took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2532625198364258s
Reputation | Calculation of the PageRank for JEL Classification took 0.022138357162475586s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.24249267578125e-05s
Believability | Calculation of trust value for JEL Classification took 9.5367431640625e-06s
INFO | --- Analysis for jel-classification took 4.778231143951416s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.204376459121704s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.27944207191467285s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.02263617515563965s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.933906555175781e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 1.0728836059570312e-05s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 7.892224550247192s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.87468123435974s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.25068187713623047s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.021010637283325195s
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.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.700920104980469e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 7.152557373046875e-06s
INFO | --- Analysis for jita took 540.7201704978943s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 9.775161743164062e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.26981425285339355s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.020830631256103516s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 3.361701965332031e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 1.4543533325195312e-05s
INFO | --- Analysis for jmdict took 3.0544183254241943s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.079456090927124s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.27872347831726074s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.020628690719604492s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 9.369850158691406e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.1205673217773438e-05s
INFO | --- Analysis for john-goodwins-family-tree took 63.10946989059448s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.696846008300781e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.2773127555847168s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.02302694320678711s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007076263427734375s
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.0251998901367188e-05s
INFO | --- Analysis for jp-cos took 4.634287118911743s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 8.177757263183594e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.26754021644592285s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.020807981491088867s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 3.981590270996094e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 1.2159347534179688e-05s
INFO | --- Analysis for jp-textbook took 4.258871793746948s
Availability | SPARQL endpoint availability check for JRC-Names took 8.797645568847656e-05s
Availability | VoID file availability check for JRC-Names took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.2746443748474121s
Reputation | Calculation of the PageRank for JRC-Names took 0.02120041847229004s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.552436828613281e-05s
Believability | Calculation of trust value for JRC-Names took 1.049041748046875e-05s
INFO | --- Analysis for jrc-names-ec took 4.866590738296509s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.2341101169586182s
Availability | VoID file availability check for JRC-Names-MLODE took 0.00042557716369628906s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.2789936065673828s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.020800352096557617s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.723403930664062e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 1.0728836059570312e-05s
INFO | --- Analysis for jrc-names-mlode took 3.8853743076324463s
Availability | SPARQL endpoint availability check for JudaicaLink took 8.392333984375e-05s
Availability | VoID file availability check for JudaicaLink took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.25330352783203125s
Reputation | Calculation of the PageRank for JudaicaLink took 0.022558927536010742s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 9.942054748535156e-05s
Believability | Calculation of trust value for JudaicaLink took 1.0728836059570312e-05s
INFO | --- Analysis for judaicalink took 22.593432426452637s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 4.291534423828125e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.25437164306640625s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.021164655685424805s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 3.409385681152344e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 1.049041748046875e-05s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.94319224357605s
Availability | SPARQL endpoint availability check for KAKEN took 6.413459777832031e-05s
Availability | VoID file availability check for KAKEN took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for KAKEN took 0.26433229446411133s
Reputation | Calculation of the PageRank for KAKEN took 0.02080821990966797s
Interlinking | Calculation of Degree of Connection for KAKEN took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for KAKEN took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for KAKEN took 3.24249267578125e-05s
Believability | Calculation of trust value for KAKEN took 1.0013580322265625e-05s
INFO | --- Analysis for kaken took 2.9149625301361084s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.07888317108154297s
Availability | VoID file availability check for Kallikratis municipalities took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.26880908012390137s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.022773265838623047s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 0.00010204315185546875s
Believability | Calculation of trust value for Kallikratis municipalities took 8.58306884765625e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.532731294631958s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.291534423828125e-05s
Availability | VoID file availability check for Openflights Routes took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.24932503700256348s
Reputation | Calculation of the PageRank for Openflights Routes took 0.02104496955871582s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.361701965332031e-05s
Believability | Calculation of trust value for Openflights Routes took 1.0251998901367188e-05s
INFO | --- Analysis for kasabi-openflights-routes took 2.966897487640381s
Availability | SPARQL endpoint availability check for EU Soccer League took 8.58306884765625e-05s
Availability | VoID file availability check for EU Soccer League took 0.0003459453582763672s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.2665872573852539s
Reputation | Calculation of the PageRank for EU Soccer League took 0.02215433120727539s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.24249267578125e-05s
Believability | Calculation of trust value for EU Soccer League took 1.2159347534179688e-05s
INFO | --- Analysis for KG:Course_Submission took 4.217611074447632s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 4.267692565917969e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.2846102714538574s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.020992517471313477s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.2159347534179688e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 9.298324584960938e-06s
INFO | --- Analysis for KING took 2.640669584274292s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 8.463859558105469e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.2625846862792969s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020817995071411133s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.747245788574219e-05s
Believability | Calculation of trust value for Klappstuhlclub took 7.62939453125e-06s
INFO | --- Analysis for klappstuhlclub took 12.570991516113281s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.917996406555176s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.27001214027404785s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.023050785064697266s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.341934204101562e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 1.1205673217773438e-05s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.38469409942627s
Availability | SPARQL endpoint availability check for Knowledge Forest took 8.749961853027344e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.24686145782470703s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.24249267578125e-05s
Believability | Calculation of trust value for Knowledge Forest took 6.4373016357421875e-06s
INFO | --- Analysis for knowledge-map took 3.0144591331481934s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.267692565917969e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.26946187019348145s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020916223526000977s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.409385681152344e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.0251998901367188e-05s
INFO | --- Analysis for KnowledgeFusion took 2.4364800453186035s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.4345855712890625e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.2615234851837158s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.022203683853149414s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.771087646484375e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 1.2874603271484375e-05s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.362568616867065s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 7.486343383789062e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.26389527320861816s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 3.123283386230469e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 1.1920928955078125e-05s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 3.0162367820739746s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.298324584960938e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.29996705055236816s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.021038532257080078s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.266334533691406e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.298324584960938e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.4750800132751465s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 8.0108642578125e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.2738037109375s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.020600080490112305s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 3.0994415283203125e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 1.239776611328125e-05s
INFO | --- Analysis for ktr took 3.020960807800293s
Availability | SPARQL endpoint availability check for Informatics Studies took 8.249282836914062e-05s
Availability | VoID file availability check for Informatics Studies took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.256023645401001s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 3.314018249511719e-05s
Believability | Calculation of trust value for Informatics Studies took 1.2636184692382812e-05s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 3.156994342803955s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.07540059089660645s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0006730556488037109s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2859835624694824s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.02080845832824707s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007512569427490234s
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.1205673217773438e-05s
INFO | --- Analysis for kupkb took 9.666253328323364s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 6.914138793945312e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.2521171569824219s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.021517515182495117s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 3.337860107421875e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 1.1444091796875e-05s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 3.026604175567627s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 9.634411811828613s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.25980281829833984s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.02045726776123047s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 8.106231689453125e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 1.1920928955078125e-05s
INFO | --- Analysis for l3s-dblp took 43.96095943450928s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 22.42458152770996s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.3576061725616455s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020505905151367188s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0008211135864257812s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 8.20159912109375e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 6.198883056640625e-06s
INFO | --- Analysis for lak-dataset took 65.63466477394104s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.26350998878479004s
Availability | VoID file availability check for  Language Name Authority List  took 0.00031876564025878906s
Extra | Recovery of all triples for  Language Name Authority List  took 162.65011191368103s
Performance | Total latancy measurement for  Language Name Authority List  took 0.5576941967010498s
Amount of data | Number of triples check for  Language Name Authority List  took 62.32541632652283s
Interoperability | New terms check for  Language Name Authority List  took 78.6156497001648s
Versatility | Languages check for  Language Name Authority List  took 300.13546919822693s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 17.560574054718018s
Security | Check HTTPS for  Language Name Authority List  took 0.3307797908782959s
Interpretability | RDF structures check for  Language Name Authority List  took 0.4150874614715576s
Versatility | Serialization formats check for  Language Name Authority List  took 3.2838611602783203s
Availability | RDF dump link check for  Language Name Authority List  took 0.24864459037780762s
License | MR license check for  Language Name Authority List  took 0.4987950325012207s
License | HR license check for  Language Name Authority List  took 300.09227871894836s
Amount of data | Number of property check for  Language Name Authority List  took 0.1783747673034668s
Understandability | Number of label check for  Language Name Authority List  took 3.1078526973724365s
Understandability | URI regex check for  Language Name Authority List  took 0.33595728874206543s
Understandability | Vocabs check for  Language Name Authority List  took 0.10644650459289551s
Verifiability | Authors check for  Language Name Authority List  took 0.22962641716003418s
Verifiability | Publishers check for  Language Name Authority List  took 0.3356962203979492s
Performance | Throughput check for  Language Name Authority List  took 10.517608880996704s
Amount of data | Check the number of entities for  Language Name Authority List  took 6.914138793945312e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.23000741004943848s
Interlinking | sameAs chians check for  Language Name Authority List  took 7.001325607299805s
Interlinking | skos check for  Language Name Authority List  took 0.14574861526489258s
Interlinking | skos check for  Language Name Authority List  took 0.29852747917175293s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.25293421745300293s
Currency | Creation date check for  Language Name Authority List  took 0.3729710578918457s
Currency | Modification date check for  Language Name Authority List  took 0.11834502220153809s
Rep.Conc. | URIs length for  Language Name Authority List  took 449.96706438064575s
Interoperability | New vocabularies check for  Language Name Authority List  took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.15798449516296387s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.18543124198913574s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.17169785499572754s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 39.12974572181702s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.2294247150421143s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.6417429447174072s
Consistency | Disjoint class check for  Language Name Authority List  took 0.12341618537902832s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.3393952846527s
Consistency | Misplaced classes for  Language Name Authority List  took 8.542892932891846s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 34.37735605239868s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.5843188762664795s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.49995040893555s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 2.9708168506622314s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.39681267738342285s
Security | Sign check for  Language Name Authority List  took 0.2753875255584717s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 16.79296064376831s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 1.1534993648529053s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.020985126495361328s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 8.7738037109375e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 2.6226043701171875e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 1.33514404296875e-05s
INFO | --- Analysis for language-authority-list took 14963.058862447739s
Availability | SPARQL endpoint availability check for Lark took 384.90016746520996s
Availability | VoID file availability check for Lark took 0.0009980201721191406s
Completeness | Calculation of interlinking completeness for Lark took 0.5654089450836182s
Reputation | Calculation of the PageRank for Lark took 0.020918846130371094s
Interlinking | Calculation of Degree of Connection for Lark took 2.9802322387695312e-05s
Interlinking | Calculation of Centrality for Lark took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Lark took 7.939338684082031e-05s
Believability | Calculation of trust value for Lark took 7.62939453125e-06s
INFO | --- Analysis for LARK took 1680.7628281116486s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.5568451881408691s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0003783702850341797s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.25173234939575195s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 4.029273986816406e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for LASLA took 4.899237632751465s
Availability | SPARQL endpoint availability check for LATC Linksets took 9.441375732421875e-05s
Availability | VoID file availability check for LATC Linksets took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.26497578620910645s
Reputation | Calculation of the PageRank for LATC Linksets took 0.020523786544799805s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 3.218650817871094e-05s
Believability | Calculation of trust value for LATC Linksets took 1.1920928955078125e-05s
INFO | --- Analysis for latc-linksets took 4.261949300765991s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.45572662353515625s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.2826812267303467s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020411968231201172s
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.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 3.838539123535156e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for Latin_Vallex2.0 took 3.9435253143310547s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.4481348991394043s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.00035643577575683594s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.25911545753479004s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.8623809814453125e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 7.62939453125e-06s
INFO | --- Analysis for LatinAffectus took 3.7884061336517334s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.500096321105957s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.29886460304260254s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.023116588592529297s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007352828979492188s
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 7.3909759521484375e-06s
INFO | --- Analysis for LatinWordnetLiLa took 4.239000558853149s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 0.0001049041748046875s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.263533353805542s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 3.2901763916015625e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 1.2636184692382812e-05s
INFO | --- Analysis for lcc took 2.9783718585968018s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.315376281738281e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0003955364227294922s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.27693772315979004s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02214980125427246s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00012111663818359375s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.3589859008789062e-05s
INFO | --- Analysis for lcsh took 5.3893797397613525s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.649162292480469e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.2704479694366455s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.021052122116088867s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007128715515136719s
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 7.867813110351562e-06s
INFO | --- Analysis for lcsubjects took 2.7424023151397705s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 4.076957702636719e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.2833986282348633s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.020692825317382812s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 3.24249267578125e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 1.33514404296875e-05s
INFO | --- Analysis for ldqm-dbpedia-2016 took 3.0514369010925293s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.787603616714478s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0015377998352050781s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.3005249500274658s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 5.1975250244140625e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.2874603271484375e-05s
INFO | --- Analysis for ldt@library took 36.898622274398804s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 8.368492126464844e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.27466726303100586s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 3.24249267578125e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 1.2636184692382812e-05s
INFO | --- Analysis for learned-genre-ontology-eng took 3.0633535385131836s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 5.745887756347656e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.28110623359680176s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.02067089080810547s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 3.147125244140625e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 1.3113021850585938e-05s
INFO | --- Analysis for learned-genre-ontology-intl took 3.0315792560577393s
Availability | SPARQL endpoint availability check for U ime Legije took 4.363059997558594e-05s
Availability | VoID file availability check for U ime Legije took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.2708601951599121s
Reputation | Calculation of the PageRank for U ime Legije took 0.02057051658630371s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.170967102050781e-05s
Believability | Calculation of trust value for U ime Legije took 1.1682510375976562e-05s
INFO | --- Analysis for LEGIJA_STRANACA took 2.4618852138519287s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 9.989738464355469e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.2760038375854492s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.021158695220947266s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 3.218650817871094e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 1.2874603271484375e-05s
INFO | --- Analysis for legislation-openuplabs took 2.9658238887786865s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.4980630874633789s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.2515387535095215s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.021409988403320312s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 8.320808410644531e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.2874603271484375e-05s
INFO | --- Analysis for LemmaBank took 4.4374165534973145s
Availability | SPARQL endpoint availability check for lemonUby took 4.57763671875e-05s
Availability | VoID file availability check for lemonUby took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for lemonUby took 0.2521038055419922s
Reputation | Calculation of the PageRank for lemonUby took 0.021166086196899414s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.556510925292969e-05s
Believability | Calculation of trust value for lemonUby took 9.298324584960938e-06s
INFO | --- Analysis for lemonuby took 3.4312312602996826s
Availability | SPARQL endpoint availability check for LemonWiktionary took 8.416175842285156e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.26229262351989746s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020893335342407227s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.528594970703125e-05s
Believability | Calculation of trust value for LemonWiktionary took 1.0013580322265625e-05s
INFO | --- Analysis for lemonwiktionary took 4.679640293121338s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.5264461040496826s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.2618904113769531s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.021446943283081055s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.647804260253906e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 9.298324584960938e-06s
INFO | --- Analysis for LewisShort took 3.9471285343170166s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 0.9855413436889648s
Availability | VoID file availability check for LEXIN-RDF took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.2890591621398926s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.02078557014465332s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 2.956390380859375e-05s
Believability | Calculation of trust value for LEXIN-RDF took 9.775161743164062e-06s
INFO | --- Analysis for lexin-rdf took 5.572062730789185s
Availability | SPARQL endpoint availability check for lexinfo took 4.220008850097656e-05s
Availability | VoID file availability check for lexinfo took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for lexinfo took 0.2598879337310791s
Reputation | Calculation of the PageRank for lexinfo took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for lexinfo took 0.00011038780212402344s
Believability | Calculation of trust value for lexinfo took 9.298324584960938e-06s
INFO | --- Analysis for lexinfo took 2.7756168842315674s
Availability | SPARQL endpoint availability check for Lexvo took 4.267692565917969e-05s
Availability | VoID file availability check for Lexvo took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Lexvo took 0.2767934799194336s
Reputation | Calculation of the PageRank for Lexvo took 0.02159404754638672s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017976760864257812s
Believability | Calculation of trust value for Lexvo took 9.059906005859375e-06s
INFO | --- Analysis for lexvo took 2.960649013519287s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.076957702636719e-05s
Availability | VoID file availability check for Lexvo.org took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.2478628158569336s
Reputation | Calculation of the PageRank for Lexvo.org took 0.022850990295410156s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.152557373046875e-05s
Believability | Calculation of trust value for Lexvo.org took 9.298324584960938e-06s
INFO | --- Analysis for lexvo-org took 2.524728298187256s
Availability | SPARQL endpoint availability check for LIBRIS took 0.28470325469970703s
Availability | VoID file availability check for LIBRIS took 0.0005526542663574219s
Extra | Recovery of all triples for LIBRIS took 6.000582933425903s
Performance | Total latancy measurement for LIBRIS took 0.6796185970306396s
Amount of data | Number of triples check for LIBRIS took 24.639739513397217s
Interoperability | New terms check for LIBRIS took 15.10042142868042s
Versatility | Languages check for LIBRIS took 0.15033507347106934s
Interpretability | Number of blank nodes check for LIBRIS took 300.1004967689514s
Security | Check HTTPS for LIBRIS took 0.33421850204467773s
Interpretability | RDF structures check for LIBRIS took 0.3224296569824219s
Versatility | Serialization formats check for LIBRIS took 0.20149016380310059s
Availability | RDF dump link check for LIBRIS took 0.12497234344482422s
License | MR license check for LIBRIS took 0.23433566093444824s
License | HR license check for LIBRIS took 0.2450251579284668s
Amount of data | Number of property check for LIBRIS took 0.14467692375183105s
Understandability | Number of label check for LIBRIS took 0.43171262741088867s
Understandability | URI regex check for LIBRIS took 0.3970983028411865s
Understandability | Vocabs check for LIBRIS took 0.1266038417816162s
Verifiability | Authors check for LIBRIS took 0.1782550811767578s
Verifiability | Publishers check for LIBRIS took 0.15759897232055664s
Performance | Throughput check for LIBRIS took 10.425496101379395s
Amount of data | Check the number of entities for LIBRIS took 7.677078247070312e-05s
Verifiability | Contribs. check for LIBRIS took 0.16717863082885742s
Interlinking | sameAs chians check for LIBRIS took 0.23642897605895996s
Interlinking | skos check for LIBRIS took 0.4104609489440918s
Interlinking | skos check for LIBRIS took 0.12162542343139648s
Timeliness | dataset update frequency check for LIBRIS took 0.1335434913635254s
Currency | Creation date check for LIBRIS took 0.34148597717285156s
Currency | Modification date check for LIBRIS took 0.5635561943054199s
Rep.Conc. | URIs length for LIBRIS took 79.9264645576477s
Interoperability | New vocabularies check for LIBRIS took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.1583268642425537s
Accuracy | Check Functional Property for LIBRIS took 0.19524073600769043s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.13310766220092773s
Accuracy | Check Datatype consistency for LIBRIS took 0.27568936347961426s
Consistency | Disjoint class check for LIBRIS took 0.14199185371398926s
Consistency | Check Misplaced properties for LIBRIS took 61.16144776344299s
Consistency | Misplaced classes for LIBRIS took 1.0895020961761475s
Consistency | Check Ontology hijacking for LIBRIS took 3.305718421936035s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.3711318969726562s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 62.50454020500183s
Conciseness | Check Extensional conciseness for LIBRIS took 0.28732776641845703s
Conciseness | Check Intensional conciseness for LIBRIS took 0.3663644790649414s
Security | Sign check for LIBRIS took 0.29022693634033203s
Availability | Check URIs Dereferenciability for LIBRIS took 13.596577167510986s
Completeness | Calculation of interlinking completeness for LIBRIS took 1.2433662414550781s
Reputation | Calculation of the PageRank for LIBRIS took 0.02048492431640625s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 0.00010061264038085938s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.9073486328125e-06s
Believability | Calculation of trust value for LIBRIS took 1.5735626220703125e-05s
INFO | --- Analysis for libris took 1068.8537800312042s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.07839059829711914s
Availability | VoID file availability check for Public Library of Veroia took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.27939748764038086s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.0233156681060791s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.62939453125e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.3828277587890625e-05s
INFO | --- Analysis for libver took 3.818021774291992s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.10017156600952148s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.2758901119232178s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.021872520446777344s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.225440979003906e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 9.298324584960938e-06s
INFO | --- Analysis for lichfield-spending took 2.62351393699646s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.4345855712890625e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0007162094116210938s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.2980811595916748s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.24249267578125e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.2159347534179688e-05s
INFO | --- Analysis for lime took 6.7679102420806885s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 6.628036499023438e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.4658010005950928s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.27291274070739746s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.020583391189575195s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010561943054199219s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.2159347534179688e-05s
INFO | --- Analysis for lingvoj took 12.296447277069092s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.2438507080078125e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.2612147331237793s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.021610021591186523s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.463859558105469e-05s
Believability | Calculation of trust value for Linked Crunchbase took 1.0251998901367188e-05s
INFO | --- Analysis for linked-crunchbase took 15.027339696884155s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.133093595504761s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.26502060890197754s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.020857572555541992s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.152557373046875e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.0967254638671875e-05s
INFO | --- Analysis for linked-drugs took 20.558923959732056s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.267692565917969e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.26747870445251465s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.02224278450012207s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.322166442871094e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 9.059906005859375e-06s
INFO | --- Analysis for linked-edgar took 4.768808126449585s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 9.822845458984375e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.2868211269378662s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.022191762924194336s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.322166442871094e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 1.1682510375976562e-05s
INFO | --- Analysis for linked-eurostat took 4.650402307510376s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.2438507080078125e-05s
Availability | VoID file availability check for linked hypernyms took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.29854345321655273s
Reputation | Calculation of the PageRank for linked hypernyms took 0.0216214656829834s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.033348083496094e-05s
Believability | Calculation of trust value for linked hypernyms took 1.1444091796875e-05s
INFO | --- Analysis for linked-hypernyms took 3.387955665588379s
Availability | SPARQL endpoint availability check for Linked Life Data took 208.2811312675476s
Availability | VoID file availability check for Linked Life Data took 0.0007023811340332031s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.9561898708343506s
Reputation | Calculation of the PageRank for Linked Life Data took 0.020876169204711914s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 5.793571472167969e-05s
Believability | Calculation of trust value for Linked Life Data took 1.1682510375976562e-05s
INFO | --- Analysis for linked-life-data took 701.0902738571167s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.3433687686920166s
Availability | VoID file availability check for Linked Logainm took 0.00033283233642578125s
Extra | Recovery of all triples for Linked Logainm took 1.572962999343872s
Performance | Total latancy measurement for Linked Logainm took 0.6013717651367188s
Amount of data | Number of triples check for Linked Logainm took 0.15079736709594727s
Interoperability | New terms check for Linked Logainm took 1.4707720279693604s
Versatility | Languages check for Linked Logainm took 1.4431757926940918s
Interpretability | Number of blank nodes check for Linked Logainm took 0.11258697509765625s
Security | Check HTTPS for Linked Logainm took 0.2998692989349365s
Interpretability | RDF structures check for Linked Logainm took 0.2413172721862793s
Versatility | Serialization formats check for Linked Logainm took 0.13190388679504395s
Availability | RDF dump link check for Linked Logainm took 0.12974143028259277s
License | MR license check for Linked Logainm took 0.13977861404418945s
License | HR license check for Linked Logainm took 0.13525128364562988s
Amount of data | Number of property check for Linked Logainm took 0.12627530097961426s
Understandability | Number of label check for Linked Logainm took 0.18990373611450195s
Understandability | URI regex check for Linked Logainm took 0.2416830062866211s
Understandability | Vocabs check for Linked Logainm took 0.12070894241333008s
Verifiability | Authors check for Linked Logainm took 0.12481141090393066s
Verifiability | Publishers check for Linked Logainm took 0.12048625946044922s
Performance | Throughput check for Linked Logainm took 10.617398500442505s
Amount of data | Check the number of entities for Linked Logainm took 6.842613220214844e-05s
Verifiability | Contribs. check for Linked Logainm took 0.11754155158996582s
Interlinking | sameAs chians check for Linked Logainm took 0.12413525581359863s
Interlinking | skos check for Linked Logainm took 0.1337873935699463s
Interlinking | skos check for Linked Logainm took 0.11146974563598633s
Timeliness | dataset update frequency check for Linked Logainm took 0.12102389335632324s
Currency | Creation date check for Linked Logainm took 0.2535228729248047s
Currency | Modification date check for Linked Logainm took 0.24290776252746582s
Rep.Conc. | URIs length for Linked Logainm took 0.8975460529327393s
Interoperability | New vocabularies check for Linked Logainm took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.1198725700378418s
Accuracy | Check Functional Property for Linked Logainm took 0.20486187934875488s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.20012903213500977s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.5650222301483154s
Accuracy | Check White space in annotation for Linked Logainm took 0.02428889274597168s
Accuracy | Check Datatype consistency for Linked Logainm took 0.028174161911010742s
Consistency | Disjoint class check for Linked Logainm took 0.20496296882629395s
Consistency | Check Misplaced properties for Linked Logainm took 0.33136868476867676s
Consistency | Misplaced classes for Linked Logainm took 0.25715136528015137s
Consistency | Check Ontology hijacking for Linked Logainm took 1.937150239944458s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.3573205471038818s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.5917937755584717s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.03226447105407715s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.19821667671203613s
Security | Sign check for Linked Logainm took 0.1403646469116211s
Availability | Check URIs Dereferenciability for Linked Logainm took 936.8622899055481s
Completeness | Calculation of interlinking completeness for Linked Logainm took 1.35992431640625s
Reputation | Calculation of the PageRank for Linked Logainm took 0.02129340171813965s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0008111000061035156s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 8.749961853027344e-05s
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.239776611328125e-05s
INFO | --- Analysis for linked-logainm took 996.6220140457153s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.38690185546875e-05s
Availability | VoID file availability check for Linked NUTS took 0.0002200603485107422s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.25409388542175293s
Reputation | Calculation of the PageRank for Linked NUTS took 0.02045726776123047s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.221366882324219e-05s
Believability | Calculation of trust value for Linked NUTS took 4.76837158203125e-06s
INFO | --- Analysis for linked-nuts took 2.9166014194488525s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.25714683532714844s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.020348072052001953s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 3.0040740966796875e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 6.9141387939453125e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 3.764943838119507s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 0.34079504013061523s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.25536274909973145s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.600120544433594e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 5.245208740234375e-06s
INFO | --- Analysis for linked-open-camera took 2.81014347076416s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.061601400375366s
Availability | VoID file availability check for Linked Open Commerce took 0.0003902912139892578s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.2680785655975342s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.021033525466918945s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0008678436279296875s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.266334533691406e-05s
Believability | Calculation of trust value for Linked Open Commerce took 7.62939453125e-06s
INFO | --- Analysis for linked-open-commerce took 13.721744537353516s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.0915768146514893s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.27149057388305664s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010180473327636719s
Believability | Calculation of trust value for Linked Open Data of Ecology took 7.152557373046875e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 3.5634069442749023s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.982948303222656e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.270841121673584s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.021041154861450195s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.940696716308594e-05s
Believability | Calculation of trust value for Linked Open Numbers took 6.4373016357421875e-06s
INFO | --- Analysis for linked-open-numbers took 2.70009183883667s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 5.054473876953125e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.000335693359375s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.26300787925720215s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.956390380859375e-05s
Believability | Calculation of trust value for Linked Open Piracy took 4.291534423828125e-06s
INFO | --- Analysis for linked-open-piracy took 6.941466569900513s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 4.076957702636719e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.26203227043151855s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.020659446716308594s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 5.7220458984375e-06s
INFO | --- Analysis for linked-open-senate took 2.895106554031372s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 5.0020153522491455s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.00039505958557128906s
Extra | Recovery of all triples for Linked Open Vocabularies (LOV) took 91.97459673881531s
Performance | Total latancy measurement for Linked Open Vocabularies (LOV) took 7.190819263458252s
Amount of data | Number of triples check for Linked Open Vocabularies (LOV) took 2.481567144393921s
Interoperability | New terms check for Linked Open Vocabularies (LOV) took 3.438732862472534s
Versatility | Languages check for Linked Open Vocabularies (LOV) took 12.368759393692017s
Interpretability | Number of blank nodes check for Linked Open Vocabularies (LOV) took 1.6513841152191162s
Interpretability | RDF structures check for Linked Open Vocabularies (LOV) took 0.20397496223449707s
Versatility | Serialization formats check for Linked Open Vocabularies (LOV) took 0.23420286178588867s
Availability | RDF dump link check for Linked Open Vocabularies (LOV) took 3.068324089050293s
License | MR license check for Linked Open Vocabularies (LOV) took 1.4268238544464111s
License | HR license check for Linked Open Vocabularies (LOV) took 49.009052753448486s
Amount of data | Number of property check for Linked Open Vocabularies (LOV) took 0.3821237087249756s
Understandability | Number of label check for Linked Open Vocabularies (LOV) took 0.9430270195007324s
Understandability | URI regex check for Linked Open Vocabularies (LOV) took 2.675673246383667s
Understandability | Vocabs check for Linked Open Vocabularies (LOV) took 1.8612825870513916s
Verifiability | Authors check for Linked Open Vocabularies (LOV) took 2.250793695449829s
Verifiability | Publishers check for Linked Open Vocabularies (LOV) took 1.5445241928100586s
Performance | Throughput check for Linked Open Vocabularies (LOV) took 16.864351511001587s
Amount of data | Check the number of entities for Linked Open Vocabularies (LOV) took 1.0054872035980225s
Verifiability | Contribs. check for Linked Open Vocabularies (LOV) took 1.415966510772705s
Interlinking | sameAs chians check for Linked Open Vocabularies (LOV) took 1.2187516689300537s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 1.1731822490692139s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 1.9903295040130615s
Timeliness | dataset update frequency check for Linked Open Vocabularies (LOV) took 2.1459269523620605s
Currency | Creation date check for Linked Open Vocabularies (LOV) took 6.374993801116943s
Currency | Modification date check for Linked Open Vocabularies (LOV) took 1.2932789325714111s
Rep.Conc. | URIs length for Linked Open Vocabularies (LOV) took 37.06779384613037s
Interoperability | New vocabularies check for Linked Open Vocabularies (LOV) took 66.87174797058105s
Consistency | Deprecated classes/propertiers check for Linked Open Vocabularies (LOV) took 1.6612184047698975s
Accuracy | Check Functional Property for Linked Open Vocabularies (LOV) took 1.67514967918396s
Accuracy | Check Inverse Functional Property for Linked Open Vocabularies (LOV) took 0.9225428104400635s
Accuracy | Check Empty annotation labels for Linked Open Vocabularies (LOV) took 12.869055271148682s
Accuracy | Check White space in annotation for Linked Open Vocabularies (LOV) took 0.6942496299743652s
Accuracy | Check Datatype consistency for Linked Open Vocabularies (LOV) took 4.738593578338623s
Consistency | Disjoint class check for Linked Open Vocabularies (LOV) took 1.126659870147705s
Consistency | Check Misplaced properties for Linked Open Vocabularies (LOV) took 11.896597385406494s
Consistency | Misplaced classes for Linked Open Vocabularies (LOV) took 1.336808204650879s
Consistency | Check Ontology hijacking for Linked Open Vocabularies (LOV) took 9.173826932907104s
Consistency | Check Invalid usage of undefined classes for Linked Open Vocabularies (LOV) took 1.3702964782714844s
Conciseness | Check Extensional conciseness for Linked Open Vocabularies (LOV) took 2.805654764175415s
Conciseness | Check Intensional conciseness for Linked Open Vocabularies (LOV) took 4.72576904296875s
Security | Sign check for Linked Open Vocabularies (LOV) took 0.8796894550323486s
Availability | Check URIs Dereferenciability for Linked Open Vocabularies (LOV) took 5857.002410650253s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 1.8465535640716553s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.021433353424072266s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 7.915496826171875e-05s
Interoperability | Check the re-using of existing vocabs for Linked Open Vocabularies (LOV) took 58.48638129234314s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.1205673217773438e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 7131.411906003952s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 9.012222290039062e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.2763197422027588s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.022867679595947266s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0008373260498046875s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 4.553794860839844e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 9.775161743164062e-06s
INFO | --- Analysis for linked-periodicals took 3.5544955730438232s
Availability | SPARQL endpoint availability check for Linked Index took 0.00012612342834472656s
Availability | VoID file availability check for Linked Index took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Linked Index took 0.271226167678833s
Reputation | Calculation of the PageRank for Linked Index took 0.021149635314941406s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.630752563476562e-05s
Believability | Calculation of trust value for Linked Index took 1.52587890625e-05s
INFO | --- Analysis for linked-stockindex took 3.4162204265594482s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 5.276646614074707s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.27143216133117676s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 4.00543212890625e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.2159347534179688e-05s
INFO | --- Analysis for linked-structured-product-labels took 20.467690467834473s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.8397715091705322s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.26149773597717285s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.020655155181884766s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.552436828613281e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 1.0967254638671875e-05s
INFO | --- Analysis for linked-taiwan-geo-names took 3.7496957778930664s
Availability | SPARQL endpoint availability check for Linked TCGA took 21.844924688339233s
Availability | VoID file availability check for Linked TCGA took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.27376532554626465s
Reputation | Calculation of the PageRank for Linked TCGA took 0.020748138427734375s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 9.250640869140625e-05s
Believability | Calculation of trust value for Linked TCGA took 1.1920928955078125e-05s
INFO | --- Analysis for linked-tcga took 64.7442615032196s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.2695798873901367s
Availability | VoID file availability check for Linked User Feedback took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.25325751304626465s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.022099733352661133s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 4.982948303222656e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.239776611328125e-05s
INFO | --- Analysis for linked-user-feedback took 3.1103787422180176s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.1484832763671875e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0011801719665527344s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.26293492317199707s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 8.96453857421875e-05s
Believability | Calculation of trust value for USPTO Patent data took 1.0728836059570312e-05s
INFO | --- Analysis for linked-uspto-patent-data took 53.45453238487244s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 4.00543212890625e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.2577848434448242s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.020626306533813477s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 3.147125244140625e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 1.1205673217773438e-05s
INFO | --- Analysis for linked-web-apis took 3.288907051086426s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 4.100799560546875e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.246978759765625s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.814697265625e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 1.0013580322265625e-05s
INFO | --- Analysis for linkedarc took 2.804027795791626s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.059842586517333984s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.2588827610015869s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.02263951301574707s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.695487976074219e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.0013580322265625e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 2.743957281112671s
Availability | SPARQL endpoint availability check for LinkedCT took 1.6608572006225586s
Availability | VoID file availability check for LinkedCT took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.25580716133117676s
Reputation | Calculation of the PageRank for LinkedCT took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.703636169433594e-05s
Believability | Calculation of trust value for LinkedCT took 1.0967254638671875e-05s
INFO | --- Analysis for linkedct took 5.079218149185181s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.13599824905395508s
Availability | VoID file availability check for LinkedGeoData took 0.00047516822814941406s
Extra | Recovery of all triples for LinkedGeoData took 8.216737985610962s
Performance | Total latancy measurement for LinkedGeoData took 0.6452720165252686s
Amount of data | Number of triples check for LinkedGeoData took 47.090579986572266s
Interoperability | New terms check for LinkedGeoData took 91.0258424282074s
Versatility | Languages check for LinkedGeoData took 180.92737889289856s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.19732165336608887s
Security | Check HTTPS for LinkedGeoData took 0.33165574073791504s
Interpretability | RDF structures check for LinkedGeoData took 1.0476160049438477s
Versatility | Serialization formats check for LinkedGeoData took 0.4036877155303955s
Availability | RDF dump link check for LinkedGeoData took 0.16581940650939941s
License | MR license check for LinkedGeoData took 0.8466329574584961s
License | HR license check for LinkedGeoData took 114.86921072006226s
Amount of data | Number of property check for LinkedGeoData took 0.25171422958374023s
Understandability | Number of label check for LinkedGeoData took 2.384453773498535s
Understandability | URI regex check for LinkedGeoData took 0.39528656005859375s
Understandability | Vocabs check for LinkedGeoData took 0.13184571266174316s
Verifiability | Authors check for LinkedGeoData took 0.18347692489624023s
Verifiability | Publishers check for LinkedGeoData took 0.14571857452392578s
Performance | Throughput check for LinkedGeoData took 10.592527151107788s
Amount of data | Check the number of entities for LinkedGeoData took 0.06526041030883789s
Verifiability | Contribs. check for LinkedGeoData took 0.13559699058532715s
Interlinking | sameAs chians check for LinkedGeoData took 0.32910633087158203s
Interlinking | skos check for LinkedGeoData took 0.41951918601989746s
Interlinking | skos check for LinkedGeoData took 0.13866448402404785s
Timeliness | dataset update frequency check for LinkedGeoData took 0.42320752143859863s
Currency | Creation date check for LinkedGeoData took 0.4113032817840576s
Currency | Modification date check for LinkedGeoData took 0.28598809242248535s
Rep.Conc. | URIs length for LinkedGeoData took 272.9575266838074s
Interoperability | New vocabularies check for LinkedGeoData took 12.09042739868164s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.14204788208007812s
Accuracy | Check Functional Property for LinkedGeoData took 0.22001433372497559s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.20840144157409668s
Accuracy | Check Empty annotation labels for LinkedGeoData took 1.9741547107696533s
Accuracy | Check White space in annotation for LinkedGeoData took 0.1575310230255127s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.13811159133911133s
Consistency | Disjoint class check for LinkedGeoData took 0.2496645450592041s
Consistency | Check Misplaced properties for LinkedGeoData took 181.0140678882599s
Consistency | Misplaced classes for LinkedGeoData took 0.6433165073394775s
Consistency | Check Ontology hijacking for LinkedGeoData took 3.772231101989746s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.3766295909881592s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 181.75854992866516s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.15421271324157715s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.26499152183532715s
Security | Sign check for LinkedGeoData took 0.8322227001190186s
Availability | Check URIs Dereferenciability for LinkedGeoData took 16.077186107635498s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.6798548698425293s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.021013975143432617s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.0001270771026611328s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 13.665120840072632s
Believability | Calculation of trust value for LinkedGeoData took 1.3113021850585938e-05s
INFO | --- Analysis for linkedgeodata took 2183.985024213791s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 8.511543273925781e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.2675607204437256s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.020722150802612305s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.075599670410156e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 1.049041748046875e-05s
INFO | --- Analysis for linkedgeodata-aerodromes took 3.026043653488159s
Availability | SPARQL endpoint availability check for LinkedLCCN took 1.0438857078552246s
Availability | VoID file availability check for LinkedLCCN took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.24681687355041504s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.020482778549194336s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010085105895996094s
Believability | Calculation of trust value for LinkedLCCN took 5.4836273193359375e-06s
INFO | --- Analysis for linkedlccn took 17.179592847824097s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.1961669921875e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.2342360019683838s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.0208892822265625s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.981590270996094e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.1920928955078125e-05s
INFO | --- Analysis for linkedmarkmail took 2.506040096282959s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.625895500183105s
Availability | VoID file availability check for Linked Movie DataBase took 0.0008099079132080078s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.2592658996582031s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.02105236053466797s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.0001423358917236328s
Believability | Calculation of trust value for Linked Movie DataBase took 1.1920928955078125e-05s
INFO | --- Analysis for linkedmdb took 133.41681480407715s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.4802370071411133s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.2783012390136719s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0210416316986084s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0009725093841552734s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 9.083747863769531e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for linkedspending took 4.547320604324341s
Availability | SPARQL endpoint availability check for LinkedStats took 6.67572021484375e-05s
Availability | VoID file availability check for LinkedStats took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.2633657455444336s
Reputation | Calculation of the PageRank for LinkedStats took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 3.0040740966796875e-05s
Believability | Calculation of trust value for LinkedStats took 1.3113021850585938e-05s
INFO | --- Analysis for linkedstats took 2.863355875015259s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.1484832763671875e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.27234554290771484s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.02080821990966797s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 3.147125244140625e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 1.3113021850585938e-05s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 2.932196855545044s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 0.00010561943054199219s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.27432966232299805s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.020607948303222656s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 3.314018249511719e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 1.3113021850585938e-05s
INFO | --- Analysis for linking-open-drug-data took 2.9786221981048584s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.07102036476135254s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.25708985328674316s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007483959197998047s
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.239776611328125e-05s
INFO | --- Analysis for linklion took 2.5061323642730713s
Availability | SPARQL endpoint availability check for Lion's Den took 4.172325134277344e-05s
Availability | VoID file availability check for Lion's Den took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.27728915214538574s
Reputation | Calculation of the PageRank for Lion's Den took 0.02086329460144043s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 3.0517578125e-05s
Believability | Calculation of trust value for Lion's Den took 1.2874603271484375e-05s
INFO | --- Analysis for lionsden took 2.9032297134399414s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 24.86161518096924s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.2589590549468994s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020490646362304688s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.0067901611328125e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 1.621246337890625e-05s
INFO | --- Analysis for lista-encabezamientos-materia took 30.214690446853638s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 0.00010466575622558594s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.24405455589294434s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.020853519439697266s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 1.33514404296875e-05s
INFO | --- Analysis for livtdm took 2.9525701999664307s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 4.3392181396484375e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.2489776611328125s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.020660877227783203s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 3.0279159545898438e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 1.3113021850585938e-05s
INFO | --- Analysis for livtdm2017 took 2.9027132987976074s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.25402212142944336s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.020994186401367188s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 3.0040740966796875e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 1.239776611328125e-05s
INFO | --- Analysis for lobi took 2.930192470550537s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.2967190742492676s
Availability | VoID file availability check for lobid-organisations took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.27312135696411133s
Reputation | Calculation of the PageRank for lobid-organisations took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.465217590332031e-05s
Believability | Calculation of trust value for lobid-organisations took 1.2636184692382812e-05s
INFO | --- Analysis for lobid-organisations took 5.4871368408203125s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.748450756072998s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0012156963348388672s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.28383350372314453s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00010204315185546875s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 1.239776611328125e-05s
INFO | --- Analysis for lobid-resources took 7.676334857940674s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.24877452850341797s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.02199697494506836s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 6.985664367675781e-05s
Believability | Calculation of trust value for Linked Open Colors took 1.2874603271484375e-05s
INFO | --- Analysis for loc took 6.7730553150177s
Availability | SPARQL endpoint availability check for Location Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Location Ontology took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.26552271842956543s
Reputation | Calculation of the PageRank for Location Ontology took 0.020331859588623047s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for Location Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for Location_Ontology took 4.354679584503174s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 9.799003601074219e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.25969409942626953s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020729780197143555s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 2.956390380859375e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 6.67572021484375e-06s
INFO | --- Analysis for locv took 58.328527212142944s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7570388317108154s
Availability | VoID file availability check for LOD-a-lot took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.27315688133239746s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.1948089599609375e-05s
Believability | Calculation of trust value for LOD-a-lot took 7.867813110351562e-06s
INFO | --- Analysis for lod-a-lot took 13.933764696121216s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.363059997558594e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.275524377822876s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.02059149742126465s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 3.24249267578125e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 9.059906005859375e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 2.830820322036743s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.267692565917969e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.28986501693725586s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 3.5762786865234375e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 7.62939453125e-06s
INFO | --- Analysis for lod-taiwan took 2.8838298320770264s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.410743713378906e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.00037360191345214844s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.2496960163116455s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.020702838897705078s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.678436279296875e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 7.3909759521484375e-06s
INFO | --- Analysis for lod2-project-wiki took 3.5702662467956543s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.8284711837768555s
Availability | VoID file availability check for LODAC BDLS took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.2369225025177002s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020570755004882812s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 8.153915405273438e-05s
Believability | Calculation of trust value for LODAC BDLS took 7.152557373046875e-06s
INFO | --- Analysis for lodac-bdls took 13.776516199111938s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.0531158447265625e-05s
Availability | VoID file availability check for LODRussia Math took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.23944830894470215s
Reputation | Calculation of the PageRank for LODRussia Math took 0.020395994186401367s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 2.9325485229492188e-05s
Believability | Calculation of trust value for LODRussia Math took 7.867813110351562e-06s
INFO | --- Analysis for lodrussia-math took 2.8519585132598877s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.1961669921875e-05s
Availability | VoID file availability check for LODRussia Nano took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.24882936477661133s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.022005558013916016s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 3.218650817871094e-05s
Believability | Calculation of trust value for LODRussia Nano took 1.0967254638671875e-05s
INFO | --- Analysis for lodrussia-nano took 2.819182872772217s
Availability | SPARQL endpoint availability check for LODStats took 3.9577484130859375e-05s
Availability | VoID file availability check for LODStats took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for LODStats took 0.26784324645996094s
Reputation | Calculation of the PageRank for LODStats took 0.020865678787231445s
Interlinking | Calculation of Degree of Connection for LODStats took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LODStats took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for LODStats took 3.24249267578125e-05s
Believability | Calculation of trust value for LODStats took 1.1205673217773438e-05s
INFO | --- Analysis for lodstats took 2.918541431427002s
Availability | SPARQL endpoint availability check for LODUM took 3.981590270996094e-05s
Availability | VoID file availability check for LODUM took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for LODUM took 0.2546265125274658s
Reputation | Calculation of the PageRank for LODUM took 0.020826339721679688s
Interlinking | Calculation of Degree of Connection for LODUM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LODUM took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for LODUM took 3.0040740966796875e-05s
Believability | Calculation of trust value for LODUM took 1.1444091796875e-05s
INFO | --- Analysis for lodum took 2.880336046218872s
Availability | SPARQL endpoint availability check for lofd took 0.1481635570526123s
Availability | VoID file availability check for lofd took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for lofd took 0.29631996154785156s
Reputation | Calculation of the PageRank for lofd took 0.021327495574951172s
Interlinking | Calculation of Degree of Connection for lofd took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for lofd took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for lofd took 3.409385681152344e-05s
Believability | Calculation of trust value for lofd took 1.049041748046875e-05s
INFO | --- Analysis for lofd took 2.634770393371582s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 271.5686342716217s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0010581016540527344s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.2691686153411865s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.020859718322753906s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.4836273193359375e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 9.5367431640625e-06s
INFO | --- Analysis for loius took 585.6606559753418s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.1484832763671875e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.25734591484069824s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 3.4809112548828125e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 1.0728836059570312e-05s
INFO | --- Analysis for loius-linking-italian-university-statistics took 2.920976161956787s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.6724021434783936s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.28105998039245605s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.020252704620361328s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 6.842613220214844e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 8.344650268554688e-06s
INFO | --- Analysis for london-gazette took 4.154246091842651s
Availability | SPARQL endpoint availability check for Weather Stations took 4.863739013671875e-05s
Availability | VoID file availability check for Weather Stations took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.2522449493408203s
Reputation | Calculation of the PageRank for Weather Stations took 0.02265620231628418s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.630752563476562e-05s
Believability | Calculation of trust value for Weather Stations took 1.1205673217773438e-05s
INFO | --- Analysis for los_metar took 13.669150829315186s
Availability | SPARQL endpoint availability check for Lotico took 0.8812892436981201s
Availability | VoID file availability check for Lotico took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for Lotico took 0.24534249305725098s
Reputation | Calculation of the PageRank for Lotico took 0.020437955856323242s
Interlinking | Calculation of Degree of Connection for Lotico took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.082389831542969e-05s
Believability | Calculation of trust value for Lotico took 1.049041748046875e-05s
INFO | --- Analysis for lotico took 6.35395073890686s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.3675389289855957s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0005869865417480469s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 1.0479178428649902s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 0.9023346900939941s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.14099931716918945s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.8980860710144043s
Versatility | Languages check for Lower Layer Super Output Areas took 0.5052826404571533s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 30.19054126739502s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.1712329387664795s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.1973106861114502s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.13451528549194336s
Availability | RDF dump link check for Lower Layer Super Output Areas took 48.77780628204346s
License | MR license check for Lower Layer Super Output Areas took 0.1433887481689453s
License | HR license check for Lower Layer Super Output Areas took 30.229458808898926s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.1656174659729004s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.22698187828063965s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.33800339698791504s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.13260483741760254s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.19475603103637695s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.16271638870239258s
Performance | Throughput check for Lower Layer Super Output Areas took 11.44160771369934s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 7.724761962890625e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.1565556526184082s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.21376347541809082s
Interlinking | skos check for Lower Layer Super Output Areas took 0.18917465209960938s
Interlinking | skos check for Lower Layer Super Output Areas took 0.20665693283081055s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.133040189743042s
Currency | Creation date check for Lower Layer Super Output Areas took 0.4295330047607422s
Currency | Modification date check for Lower Layer Super Output Areas took 0.15853571891784668s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 1.8421611785888672s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.14878153800964355s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.18939733505249023s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.20579171180725098s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.14866352081298828s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 0.6619904041290283s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 1.3251793384552002s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.614637851715088s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.00014138221740722656s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.41213345527648926s
Security | Sign check for Lower Layer Super Output Areas took 0.1423182487487793s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.4348733425140381s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020750761032104492s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 1.1920928955078125e-06s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.049041748046875e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 267.62917256355286s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3582029342651367s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.00046539306640625s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 135.554949760437s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9320695400238037s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.676305770874023s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.691498279571533s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2411267757416s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.452421188354492s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3212308883666992s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.419478416442871s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3261375427246094s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6340725421905518s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.1740825176239s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3426647186279297s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.2210044860839844s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.8199763298034668s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.49140310287475586s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20334386825561523s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2624471187591553s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.464986085891724s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.00010228157043457031s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19539475440979004s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21291637420654297s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.510901689529419s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.47026753425598145s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 6.209007978439331s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5266246795654297s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.25542473793029785s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 164.7451934814453s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20032262802124023s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3581357002258301s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4191451072692871s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 47.4194061756134s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.7080183029174805s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.5832059383392334s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20636343955993652s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 88.44024348258972s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.201467275619507s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 35.6976273059845s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3807518482208252s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 88.26325488090515s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.7456741333007812s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.604010820388794s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1191089153289795s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 13.149399280548096s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.45285511016845703s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.020953655242919922s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for LPIS_(Poland) took 2330.2164874076843s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21761226654052734s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0005168914794921875s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 140.02211833000183s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.9580559730529785s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.379812240600586s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 14.467102527618408s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.1976478099823s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.132091522216797s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3220188617706299s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 10.344235897064209s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3653535842895508s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.79695725440979s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.2414286136627s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2297210693359375s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.2530770301818848s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.9798104763031006s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5461320877075195s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20706653594970703s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.24005794525146484s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.148327827453613s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.2479248046875e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21390771865844727s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18918800354003906s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.46148204803466797s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4359931945800781s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.252902507781982s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.47545361518859863s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.25879383087158203s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 169.14507603645325s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20543479919433594s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4025750160217285s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3655383586883545s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 51.743746280670166s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.6599602699279785s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.718686103820801s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19865822792053223s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 88.71138882637024s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.413652896881104s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 44.378140449523926s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.3694531917572021s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 89.76106548309326s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7891271114349365s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5937638282775879s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.3145074844360352s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 13.862199783325195s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.6228809356689453s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.021333932876586914s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.5762786865234375e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.814697265625e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 6.4373016357421875e-06s
INFO | --- Analysis for LPIS_Czech_Republic took 2346.399265766144s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 8.821487426757812e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.26572608947753906s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.022835493087768555s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.910064697265625e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 1.239776611328125e-05s
INFO | --- Analysis for lremap-auth took 3.081725597381592s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.1961669921875e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.2838599681854248s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.020885229110717773s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.2901763916015625e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.1920928955078125e-05s
INFO | --- Analysis for lremap-conf took 2.6779181957244873s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 8.511543273925781e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.25548696517944336s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.02205681800842285s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.4332275390625e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.2159347534179688e-05s
INFO | --- Analysis for lremap-ri took 3.0646109580993652s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.482269287109375e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.2601468563079834s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.020976543426513672s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.552436828613281e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.1444091796875e-05s
INFO | --- Analysis for lremap-sub took 2.6514039039611816s
Availability | SPARQL endpoint availability check for LSQ took 9.083747863769531e-05s
Availability | VoID file availability check for LSQ took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for LSQ took 0.26508378982543945s
Reputation | Calculation of the PageRank for LSQ took 0.020689010620117188s
Interlinking | Calculation of Degree of Connection for LSQ took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.409385681152344e-05s
Believability | Calculation of trust value for LSQ took 1.2159347534179688e-05s
INFO | --- Analysis for lsq took 3.9357073307037354s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.655059814453125s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.25600719451904297s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.02238011360168457s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.981590270996094e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 1.0967254638671875e-05s
INFO | --- Analysis for LucaniPharsalia took 4.215776443481445s
Availability | SPARQL endpoint availability check for Linked rules took 4.172325134277344e-05s
Availability | VoID file availability check for Linked rules took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Linked rules took 0.2921638488769531s
Reputation | Calculation of the PageRank for Linked rules took 0.020694255828857422s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.1948089599609375e-05s
Believability | Calculation of trust value for Linked rules took 1.1205673217773438e-05s
INFO | --- Analysis for Luminaires_senlis took 2.389063835144043s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.100799560546875e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.3042714595794678s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 3.886222839355469e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 1.2159347534179688e-05s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 2.934663772583008s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.141506910324097s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.27486681938171387s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020858287811279297s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 3.3855438232421875e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 1.0728836059570312e-05s
INFO | --- Analysis for makg took 64.96194744110107s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.172325134277344e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.23614001274108887s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.020270586013793945s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.552436828613281e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 6.67572021484375e-06s
INFO | --- Analysis for manchester-university-reading-lists took 3.340907096862793s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.172325134277344e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.2872166633605957s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020418167114257812s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 2.86102294921875e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.1682510375976562e-05s
INFO | --- Analysis for manish took 2.454127311706543s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 4.1484832763671875e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.0008609294891357422s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.2806992530822754s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.021296262741088867s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 2.9802322387695312e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 1.0967254638671875e-05s
INFO | --- Analysis for mapa-referencia-bogota took 2.8753576278686523s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 4.1484832763671875e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.00032520294189453125s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.28388404846191406s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 3.0994415283203125e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 6.9141387939453125e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 4.31676173210144s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.1961669921875e-05s
Availability | VoID file availability check for MARC Codes List took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.27872347831726074s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00012254714965820312s
Believability | Calculation of trust value for MARC Codes List took 1.049041748046875e-05s
INFO | --- Analysis for marc-codes took 12.146180152893066s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.1961669921875e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.2449626922607422s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.020798683166503906s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.9577484130859375e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.0967254638671875e-05s
INFO | --- Analysis for masc took 5.817585468292236s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.124641418457031e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.24239635467529297s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.0203244686126709s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.7670135498046875e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 1.0728836059570312e-05s
INFO | --- Analysis for masc-bn-nif took 2.3637471199035645s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.2198359966278076s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.25154900550842285s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.02032017707824707s
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.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 2.9325485229492188e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 6.4373016357421875e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 3.7533488273620605s
Availability | SPARQL endpoint availability check for medline took 0.00010085105895996094s
Availability | VoID file availability check for medline took 0.00034809112548828125s
Completeness | Calculation of interlinking completeness for medline took 0.26060938835144043s
Reputation | Calculation of the PageRank for medline took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for medline took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for medline took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for medline took 3.361701965332031e-05s
Believability | Calculation of trust value for medline took 9.775161743164062e-06s
INFO | --- Analysis for medline took 6.830133676528931s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.8535149097442627s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.27723002433776855s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.0202789306640625s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.890296936035156e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 1.1205673217773438e-05s
INFO | --- Analysis for meducator took 12.624380350112915s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 0.00010156631469726562s
Availability | VoID file availability check for Finnish translation of mesh took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.2615623474121094s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.020350217819213867s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 3.0517578125e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 1.1682510375976562e-05s
INFO | --- Analysis for mesh-finnish took 2.927677631378174s
Availability | SPARQL endpoint availability check for MeSH headings took 8.392333984375e-05s
Availability | VoID file availability check for MeSH headings took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.2544741630554199s
Reputation | Calculation of the PageRank for MeSH headings took 0.02042412757873535s
Interlinking | Calculation of Degree of Connection for MeSH headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 2.956390380859375e-05s
Believability | Calculation of trust value for MeSH headings took 1.1920928955078125e-05s
INFO | --- Analysis for mesh_headings took 2.8063347339630127s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 0.0001385211944580078s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.27150607109069824s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 2.956390380859375e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 1.1920928955078125e-05s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.985940456390381s
Availability | SPARQL endpoint availability check for MeSH pairs took 8.20159912109375e-05s
Availability | VoID file availability check for MeSH pairs took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.267474889755249s
Reputation | Calculation of the PageRank for MeSH pairs took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MeSH pairs took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 3.0517578125e-05s
Believability | Calculation of trust value for MeSH pairs took 1.1682510375976562e-05s
INFO | --- Analysis for mesh_pairs took 2.834805727005005s
Availability | SPARQL endpoint availability check for MeSH titles took 4.124641418457031e-05s
Availability | VoID file availability check for MeSH titles took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.2535853385925293s
Reputation | Calculation of the PageRank for MeSH titles took 0.022028684616088867s
Interlinking | Calculation of Degree of Connection for MeSH titles took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MeSH titles took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 3.0279159545898438e-05s
Believability | Calculation of trust value for MeSH titles took 1.1920928955078125e-05s
INFO | --- Analysis for mesh_titles took 2.9387664794921875s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 4.1484832763671875e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.2601315975189209s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.022673606872558594s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 2.956390380859375e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 1.2636184692382812e-05s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.925215721130371s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 4.2438507080078125e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.2615673542022705s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.022138595581054688s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0008094310760498047s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 3.981590270996094e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.1682510375976562e-05s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.8650591373443604s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.2438507080078125e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.2736485004425049s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.022387027740478516s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 6.961822509765625e-05s
Believability | Calculation of trust value for MetaShare metadata model took 1.1920928955078125e-05s
INFO | --- Analysis for metashare took 2.583073616027832s
Availability | SPARQL endpoint availability check for MExiCo took 8.797645568847656e-05s
Availability | VoID file availability check for MExiCo took 0.0006883144378662109s
Completeness | Calculation of interlinking completeness for MExiCo took 0.2672553062438965s
Reputation | Calculation of the PageRank for MExiCo took 0.020382404327392578s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for MExiCo took 5.269050598144531e-05s
Believability | Calculation of trust value for MExiCo took 1.2874603271484375e-05s
INFO | --- Analysis for mexico took 22.525514841079712s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.0065240859985352s
Availability | VoID file availability check for Coronavirus dataset took 0.0005059242248535156s
Extra | Recovery of all triples for Coronavirus dataset took 10.606359481811523s
Performance | Total latancy measurement for Coronavirus dataset took 2.4505791664123535s
Amount of data | Number of triples check for Coronavirus dataset took 1.1794922351837158s
Interoperability | New terms check for Coronavirus dataset took 2.6050686836242676s
Versatility | Languages check for Coronavirus dataset took 60.47853708267212s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.128788709640503s
Interpretability | RDF structures check for Coronavirus dataset took 0.506260871887207s
Versatility | Serialization formats check for Coronavirus dataset took 0.5250921249389648s
Availability | RDF dump link check for Coronavirus dataset took 0.4912374019622803s
License | MR license check for Coronavirus dataset took 0.5392467975616455s
License | HR license check for Coronavirus dataset took 41.50140714645386s
Amount of data | Number of property check for Coronavirus dataset took 0.493549108505249s
Understandability | Number of label check for Coronavirus dataset took 0.7572813034057617s
Understandability | URI regex check for Coronavirus dataset took 1.0207855701446533s
Understandability | Vocabs check for Coronavirus dataset took 0.5088236331939697s
Verifiability | Authors check for Coronavirus dataset took 0.49622559547424316s
Verifiability | Publishers check for Coronavirus dataset took 0.5072546005249023s
Performance | Throughput check for Coronavirus dataset took 14.29814887046814s
Amount of data | Check the number of entities for Coronavirus dataset took 7.081031799316406e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.48932623863220215s
Interlinking | sameAs chians check for Coronavirus dataset took 0.4984767436981201s
Interlinking | skos check for Coronavirus dataset took 0.532827615737915s
Interlinking | skos check for Coronavirus dataset took 0.49350619316101074s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.4981381893157959s
Currency | Creation date check for Coronavirus dataset took 0.9974448680877686s
Currency | Modification date check for Coronavirus dataset took 0.9948928356170654s
Rep.Conc. | URIs length for Coronavirus dataset took 9.100303888320923s
Interoperability | New vocabularies check for Coronavirus dataset took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.4874413013458252s
Accuracy | Check Functional Property for Coronavirus dataset took 0.719264030456543s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.7254812717437744s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.36983585357666s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.02242279052734375s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.02789592742919922s
Consistency | Disjoint class check for Coronavirus dataset took 1.05570650100708s
Consistency | Check Misplaced properties for Coronavirus dataset took 8.113657474517822s
Consistency | Misplaced classes for Coronavirus dataset took 0.5848236083984375s
Consistency | Check Ontology hijacking for Coronavirus dataset took 4.066567659378052s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.358180046081543s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 7.206153154373169s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.03235936164855957s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5397138595581055s
Security | Sign check for Coronavirus dataset took 0.5158908367156982s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3042.3635840415955s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.8815953731536865s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021999835968017578s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0008919239044189453s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 0.0001232624053955078s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Coronavirus dataset took 1.239776611328125e-05s
INFO | --- Analysis for micro-coronavirus took 3283.148279428482s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 4.38690185546875e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00033926963806152344s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.260927677154541s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.02076888084411621s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00011014938354492188s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.2874603271484375e-05s
INFO | --- Analysis for miguiadeviajes-gnoss took 8.209799766540527s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 8.988380432128906e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.25253868103027344s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.02315998077392578s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00010919570922851562s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.3113021850585938e-05s
INFO | --- Analysis for mismuseos-gnoss took 9.42203688621521s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.13190269470214844s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.264451265335083s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.02323627471923828s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.5299530029296875e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.2874603271484375e-05s
INFO | --- Analysis for mlsa took 3.033196449279785s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 5.984306335449219e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.2679576873779297s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020804882049560547s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.337860107421875e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 1.2159347534179688e-05s
INFO | --- Analysis for model took 35.53144335746765s
Availability | SPARQL endpoint availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 4.38690185546875e-05s
Availability | VoID file availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007622241973876953s
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.24614405632019043s
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.020838260650634766s
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.2636184692382812e-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.0007331371307373047s
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.2901763916015625e-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.3113021850585938e-05s
INFO | --- Analysis for model1 took 21.228933334350586s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 8.416175842285156e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.25388073921203613s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.020941734313964844s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 3.409385681152344e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 1.2636184692382812e-05s
INFO | --- Analysis for mond took 2.90730619430542s
Availability | SPARQL endpoint availability check for MONDIS took 9.34600830078125e-05s
Availability | VoID file availability check for MONDIS took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for MONDIS took 0.24107623100280762s
Reputation | Calculation of the PageRank for MONDIS took 0.022482633590698242s
Interlinking | Calculation of Degree of Connection for MONDIS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MONDIS took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for MONDIS took 3.218650817871094e-05s
Believability | Calculation of trust value for MONDIS took 1.71661376953125e-05s
INFO | --- Analysis for mondis took 2.886904239654541s
Availability | SPARQL endpoint availability check for Monumentos took 4.172325134277344e-05s
Availability | VoID file availability check for Monumentos took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Monumentos took 0.8174300193786621s
Reputation | Calculation of the PageRank for Monumentos took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for Monumentos took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Monumentos took 3.123283386230469e-05s
Believability | Calculation of trust value for Monumentos took 1.33514404296875e-05s
INFO | --- Analysis for monumentos-zaragoza took 4.710069894790649s
Availability | SPARQL endpoint availability check for MORElab took 0.9277510643005371s
Availability | VoID file availability check for MORElab took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for MORElab took 0.2622826099395752s
Reputation | Calculation of the PageRank for MORElab took 0.0210573673248291s
Interlinking | Calculation of Degree of Connection for MORElab took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.869171142578125e-05s
Believability | Calculation of trust value for MORElab took 1.2636184692382812e-05s
INFO | --- Analysis for morelab took 4.266753435134888s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 1.7960422039031982s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.28594303131103516s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.021047115325927734s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.7738037109375e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 1.33514404296875e-05s
INFO | --- Analysis for msc took 16.30315065383911s
Availability | SPARQL endpoint availability check for Multext-East took 9.250640869140625e-05s
Availability | VoID file availability check for Multext-East took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Multext-East took 0.25855255126953125s
Reputation | Calculation of the PageRank for Multext-East took 0.020851850509643555s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.7670135498046875e-05s
Believability | Calculation of trust value for Multext-East took 8.58306884765625e-06s
INFO | --- Analysis for multext-east took 2.3721439838409424s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.1484832763671875e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.00022220611572265625s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.2473900318145752s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.020607471466064453s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 3.123283386230469e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 5.9604644775390625e-06s
INFO | --- Analysis for multilingualeulaw took 2.8409512042999268s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.4345855712890625e-05s
Availability | VoID file availability check for Multimedia Lab took 0.00022530555725097656s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.24615955352783203s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.552436828613281e-05s
Believability | Calculation of trust value for Multimedia Lab took 6.4373016357421875e-06s
INFO | --- Analysis for multimedia-lab took 2.3784868717193604s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.363059997558594e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.27012038230895996s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 3.2901763916015625e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 5.245208740234375e-06s
INFO | --- Analysis for munich-offener-haushalt took 2.821305274963379s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.613584041595459s
Availability | VoID file availability check for Muninn World War I took 0.000354766845703125s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.24665284156799316s
Reputation | Calculation of the PageRank for Muninn World War I took 0.02091693878173828s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.535385131835938e-05s
Believability | Calculation of trust value for Muninn World War I took 8.344650268554688e-06s
INFO | --- Analysis for muninn-world-war-i took 10.521310329437256s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.410743713378906e-05s
Availability | VoID file availability check for Musei Italiani took 0.0003027915954589844s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.26302576065063477s
Reputation | Calculation of the PageRank for Musei Italiani took 0.02222895622253418s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 3.504753112792969e-05s
Believability | Calculation of trust value for Musei Italiani took 6.9141387939453125e-06s
INFO | --- Analysis for musei-italiani took 2.858219623565674s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00014400482177734375s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.2526681423187256s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.02080512046813965s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00010466575622558594s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.2874603271484375e-05s
INFO | --- Analysis for museosespania-gnoss took 36.92541980743408s
Availability | SPARQL endpoint availability check for Italian Museums took 0.6844146251678467s
Availability | VoID file availability check for Italian Museums took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.28026413917541504s
Reputation | Calculation of the PageRank for Italian Museums took 0.0207672119140625s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.082389831542969e-05s
Believability | Calculation of trust value for Italian Museums took 1.0967254638671875e-05s
INFO | --- Analysis for museums-in-italy took 3.1699416637420654s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.1484832763671875e-05s
Availability | VoID file availability check for MusicBrainz took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.27866530418395996s
Reputation | Calculation of the PageRank for MusicBrainz took 0.020960330963134766s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 3.6716461181640625e-05s
Believability | Calculation of trust value for MusicBrainz took 1.2159347534179688e-05s
INFO | --- Analysis for musicbrainz_ took 2.96162486076355s
Availability | SPARQL endpoint availability check for MusicNet Codex took 8.177757263183594e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.2601609230041504s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.022703170776367188s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 3.218650817871094e-05s
Believability | Calculation of trust value for MusicNet Codex took 1.33514404296875e-05s
INFO | --- Analysis for musicnet_codex took 2.85977840423584s
Availability | SPARQL endpoint availability check for Muziekweb took 0.7089676856994629s
Availability | VoID file availability check for Muziekweb took 0.0005648136138916016s
Extra | Recovery of all triples for Muziekweb took 2.0193817615509033s
Performance | Total latancy measurement for Muziekweb took 1.5109806060791016s
Amount of data | Number of triples check for Muziekweb took 0.3890085220336914s
Interoperability | New terms check for Muziekweb took 1.7966010570526123s
Versatility | Languages check for Muziekweb took 50.3317334651947s
Interpretability | Number of blank nodes check for Muziekweb took 0.31525087356567383s
Interpretability | RDF structures check for Muziekweb took 0.3258340358734131s
Versatility | Serialization formats check for Muziekweb took 0.3907449245452881s
Availability | RDF dump link check for Muziekweb took 0.3019883632659912s
License | MR license check for Muziekweb took 0.3081803321838379s
License | HR license check for Muziekweb took 12.451965808868408s
Amount of data | Number of property check for Muziekweb took 0.31136655807495117s
Understandability | Number of label check for Muziekweb took 0.3755357265472412s
Understandability | URI regex check for Muziekweb took 0.6902108192443848s
Understandability | Vocabs check for Muziekweb took 0.3294038772583008s
Verifiability | Authors check for Muziekweb took 0.4005279541015625s
Verifiability | Publishers check for Muziekweb took 0.3044004440307617s
Performance | Throughput check for Muziekweb took 12.497847318649292s
Amount of data | Check the number of entities for Muziekweb took 8.606910705566406e-05s
Verifiability | Contribs. check for Muziekweb took 0.3290221691131592s
Interlinking | sameAs chians check for Muziekweb took 0.3358922004699707s
Interlinking | skos check for Muziekweb took 0.328357458114624s
Interlinking | skos check for Muziekweb took 0.33001041412353516s
Timeliness | dataset update frequency check for Muziekweb took 0.36789965629577637s
Currency | Creation date check for Muziekweb took 0.9611546993255615s
Currency | Modification date check for Muziekweb took 0.9126369953155518s
Rep.Conc. | URIs length for Muziekweb took 1.9656574726104736s
Interoperability | New vocabularies check for Muziekweb took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.3109769821166992s
Accuracy | Check Functional Property for Muziekweb took 0.6143474578857422s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.5849246978759766s
Accuracy | Check Empty annotation labels for Muziekweb took 1.0187761783599854s
Accuracy | Check White space in annotation for Muziekweb took 0.028485536575317383s
Accuracy | Check Datatype consistency for Muziekweb took 0.02947211265563965s
Consistency | Disjoint class check for Muziekweb took 0.45182156562805176s
Consistency | Check Misplaced properties for Muziekweb took 1.2035706043243408s
Consistency | Check Ontology hijacking for Muziekweb took 2.277402639389038s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.312727689743042s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.654191017150879s
Conciseness | Check Extensional conciseness for Muziekweb took 0.032906293869018555s
Conciseness | Check Intensional conciseness for Muziekweb took 0.3172321319580078s
Security | Sign check for Muziekweb took 0.31141209602355957s
Availability | Check URIs Dereferenciability for Muziekweb took 2009.230422258377s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.5405869483947754s
Reputation | Calculation of the PageRank for Muziekweb took 0.021496295928955078s
Interlinking | Calculation of Degree of Connection for Muziekweb took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 5.626678466796875e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.430511474609375e-06s
Believability | Calculation of trust value for Muziekweb took 1.2159347534179688e-05s
INFO | --- Analysis for muziekweb took 2135.9376912117004s
Availability | SPARQL endpoint availability check for myExperiment took 0.4154479503631592s
Availability | VoID file availability check for myExperiment took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for myExperiment took 0.28101277351379395s
Reputation | Calculation of the PageRank for myExperiment took 0.022214651107788086s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for myExperiment took 9.489059448242188e-05s
Believability | Calculation of trust value for myExperiment took 1.049041748046875e-05s
INFO | --- Analysis for my-experiment took 3.969620943069458s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.06466269493103027s
Availability | VoID file availability check for My Family Lineage took 0.0003452301025390625s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.2562835216522217s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020722627639770508s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.749961853027344e-05s
Believability | Calculation of trust value for My Family Lineage took 1.1682510375976562e-05s
INFO | --- Analysis for my-family-lineage took 13.582775354385376s
Availability | SPARQL endpoint availability check for My ontology test took 0.7826218605041504s
Availability | VoID file availability check for My ontology test took 0.00035381317138671875s
Completeness | Calculation of interlinking completeness for My ontology test took 0.2692561149597168s
Reputation | Calculation of the PageRank for My ontology test took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for My ontology test took 2.8371810913085938e-05s
Believability | Calculation of trust value for My ontology test took 7.62939453125e-06s
INFO | --- Analysis for myontologytest took 3.318345546722412s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 9.131431579589844e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.6612045764923096s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.00010538101196289062s
Believability | Calculation of trust value for myopenlink dataspaces took 1.1444091796875e-05s
INFO | --- Analysis for myopenlink-dataspaces took 4.061791658401489s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 6.575202941894531s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.25383782386779785s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.020900964736938477s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 7.104873657226562e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for n-lex-as-linked-data took 15.958424091339111s
Availability | SPARQL endpoint availability check for NAICS 2007 took 26.855228662490845s
Availability | VoID file availability check for NAICS 2007 took 0.0007491111755371094s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.2656071186065674s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.02082037925720215s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.363059997558594e-05s
Believability | Calculation of trust value for NAICS 2007 took 1.0013580322265625e-05s
INFO | --- Analysis for naics-2007 took 126.0075044631958s
Availability | SPARQL endpoint availability check for NAICS 2012 took 25.66313123703003s
Availability | VoID file availability check for NAICS 2012 took 0.0008032321929931641s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.2712821960449219s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.02070784568786621s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.364418029785156e-05s
Believability | Calculation of trust value for NAICS 2012 took 1.049041748046875e-05s
INFO | --- Analysis for naics-2012 took 124.36582565307617s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.24538445472717285s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.020907878875732422s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 5.1021575927734375e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for nalt took 2.861002206802368s
Availability | SPARQL endpoint availability check for Usernames  took 4.2438507080078125e-05s
Availability | VoID file availability check for Usernames  took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Usernames  took 0.2741580009460449s
Reputation | Calculation of the PageRank for Usernames  took 0.020305633544921875s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Usernames  took 2.8848648071289062e-05s
Believability | Calculation of trust value for Usernames  took 1.1682510375976562e-05s
INFO | --- Analysis for Names took 2.358227252960205s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 0.5832164287567139s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0005242824554443359s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.4734537601470947s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 3.8092398643493652s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.188955545425415s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 15.496875524520874s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.8572766780853271s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.630338907241821s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.7993741035461426s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.8400981426239014s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.7977993488311768s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.37096190452575684s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.8820338249206543s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.81311917304993s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.8388442993164062s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 5.487020254135132s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 1.854217529296875s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.8648226261138916s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.6909503936767578s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.43798208236694336s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 13.9536771774292s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 8.606910705566406e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.33983612060546875s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.46155810356140137s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.880408763885498s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.5741665363311768s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.437009334564209s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 2.0231611728668213s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 1.3246519565582275s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.2936840057373047s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.4166686534881592s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.39780378341674805s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.42095422744750977s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.4109516143798828s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007476806640625s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0010056495666503906s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.8717231750488281s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.8557007312774658s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.888512372970581s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.7498188018798828s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.320735216140747s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.7114014625549316s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0007042884826660156s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.8231513500213623s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 6.85526704788208s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.2764158248901367s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.020779132843017578s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.4849853515625e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.1920928955078125e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 9.775161743164062e-06s
INFO | --- Analysis for national-diet-library-authorities took 247.4983730316162s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.8891956806182861s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0006651878356933594s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.0905821323394775s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 2.4003617763519287s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.996177673339844s
Interoperability | New terms check for National Diet Library of Japan subject headings took 15.457271099090576s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.428494930267334s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 14.091149091720581s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.37583136558532715s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.3927450180053711s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.3944716453552246s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.4461984634399414s
License | MR license check for National Diet Library of Japan subject headings took 0.8283801078796387s
License | HR license check for National Diet Library of Japan subject headings took 91.39136910438538s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.9373016357421875s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.372541427612305s
Understandability | URI regex check for National Diet Library of Japan subject headings took 1.457566261291504s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.6601405143737793s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.36586594581604004s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.4435086250305176s
Performance | Throughput check for National Diet Library of Japan subject headings took 14.445492029190063s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 4.00543212890625e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.4147319793701172s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.45113539695739746s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.2547223567962646s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.7224147319793701s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.38223838806152344s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.6372628211975098s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.8076338768005371s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.7612764835357666s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.35071730613708496s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.3913130760192871s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.41953229904174805s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.44460201263427734s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0003294944763183594s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0004630088806152344s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.41193675994873047s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.8060035705566406s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.3757798671722412s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.735316276550293s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.3365626335144043s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.9053523540496826s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0006513595581054688s
Security | Sign check for National Diet Library of Japan subject headings took 0.365572452545166s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 5.2428200244903564s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.4185049533843994s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02092599868774414s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 6.0558319091796875e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 7.3909759521484375e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 241.25598764419556s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.2072703838348389s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.2601299285888672s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.020949363708496094s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.52587890625e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0009922981262207031s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 5.435943603515625e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 1.049041748046875e-05s
INFO | --- Analysis for national-library-of-greece-authority-records took 5.355629920959473s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.3392181396484375e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.25096607208251953s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.021251678466796875s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0009164810180664062s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.677078247070312e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.106231689453125e-06s
INFO | --- Analysis for Naturopathy took 2.9103100299835205s
Availability | SPARQL endpoint availability check for Naturopathy took 7.033348083496094e-05s
Availability | VoID file availability check for Naturopathy took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.23938655853271484s
Reputation | Calculation of the PageRank for Naturopathy took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for Naturopathy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 3.337860107421875e-05s
Believability | Calculation of trust value for Naturopathy took 7.867813110351562e-06s
INFO | --- Analysis for naturopathy2 took 2.8087117671966553s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.254563570022583s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.170967102050781e-05s
Believability | Calculation of trust value for NCI Thesaurus took 1.3589859008789062e-05s
INFO | --- Analysis for nci-thesaurus took 2.9030134677886963s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.3615593910217285s
Availability | VoID file availability check for COVID-19 Data took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.256915807723999s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.020687103271484375s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.3855438232421875e-05s
Believability | Calculation of trust value for COVID-19 Data took 1.2636184692382812e-05s
INFO | --- Analysis for NCMI-COVID-19 took 7.1185784339904785s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.402578115463257s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.2620995044708252s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.2636184692382812e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 1.3113021850585938e-05s
INFO | --- Analysis for NCMICOVID-19 took 6.170367240905762s
Availability | SPARQL endpoint availability check for NDF-RT took 4.410743713378906e-05s
Availability | VoID file availability check for NDF-RT took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.27643752098083496s
Reputation | Calculation of the PageRank for NDF-RT took 0.02077794075012207s
Interlinking | Calculation of Degree of Connection for NDF-RT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 3.218650817871094e-05s
Believability | Calculation of trust value for NDF-RT took 1.1205673217773438e-05s
INFO | --- Analysis for ndf-rt took 2.9369118213653564s
Availability | SPARQL endpoint availability check for Near took 8.702278137207031e-05s
Availability | VoID file availability check for Near took 0.0008859634399414062s
Completeness | Calculation of interlinking completeness for Near took 0.2741420269012451s
Reputation | Calculation of the PageRank for Near took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for Near took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Near took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Near took 8.869171142578125e-05s
Believability | Calculation of trust value for Near took 1.2159347534179688e-05s
INFO | --- Analysis for near took 8.768920421600342s
Availability | SPARQL endpoint availability check for Neel took 8.463859558105469e-05s
Availability | VoID file availability check for Neel took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Neel took 0.2619283199310303s
Reputation | Calculation of the PageRank for Neel took 0.020539045333862305s
Interlinking | Calculation of Degree of Connection for Neel took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Neel took 0.0010046958923339844s
Interlinking | Calculation of Clustering coefficient for Neel took 3.6716461181640625e-05s
Believability | Calculation of trust value for Neel took 1.2636184692382812e-05s
INFO | --- Analysis for neel took 2.8773207664489746s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 3.981590270996094e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.26245808601379395s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 2.956390380859375e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 1.2636184692382812e-05s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.940417766571045s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.4345855712890625e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.2354722023010254s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020522594451904297s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 2.9802322387695312e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.2159347534179688e-05s
INFO | --- Analysis for neurolex-wiki took 2.3876821994781494s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 8.559226989746094e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.000732421875s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.2632560729980469s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.021118640899658203s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.315376281738281e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 1.1682510375976562e-05s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 12.55147099494934s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.315376281738281e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.2605116367340088s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.628036499023438e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 1.4066696166992188e-05s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.074901819229126s
Availability | SPARQL endpoint availability check for Newsweek took 4.2438507080078125e-05s
Availability | VoID file availability check for Newsweek took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Newsweek took 0.2833571434020996s
Reputation | Calculation of the PageRank for Newsweek took 0.02026653289794922s
Interlinking | Calculation of Degree of Connection for Newsweek took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Newsweek took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Newsweek took 3.0040740966796875e-05s
Believability | Calculation of trust value for Newsweek took 1.2636184692382812e-05s
INFO | --- Analysis for newsweek took 2.8359405994415283s
Availability | SPARQL endpoint availability check for neXtProt took 1.6412913799285889s
Availability | VoID file availability check for neXtProt took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for neXtProt took 0.25455641746520996s
Reputation | Calculation of the PageRank for neXtProt took 0.02202439308166504s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.552436828613281e-05s
Believability | Calculation of trust value for neXtProt took 1.239776611328125e-05s
INFO | --- Analysis for nextprot took 4.773233890533447s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 5.602836608886719e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0008320808410644531s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.2537698745727539s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.02059149742126465s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010132789611816406s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.2159347534179688e-05s
INFO | --- Analysis for nextweb-gnoss took 14.348294973373413s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.363059997558594e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.256213903427124s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.02158045768737793s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.0108642578125e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 9.059906005859375e-06s
INFO | --- Analysis for nhs-jargon took 3.155853271484375s
Availability | SPARQL endpoint availability check for NIT Patna took 8.678436279296875e-05s
Availability | VoID file availability check for NIT Patna took 0.0012125968933105469s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.24280548095703125s
Reputation | Calculation of the PageRank for NIT Patna took 0.020333290100097656s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.604194641113281e-05s
Believability | Calculation of trust value for NIT Patna took 1.1920928955078125e-05s
INFO | --- Analysis for NITP took 3.0988800525665283s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 4.0531158447265625e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.26863861083984375s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.4809112548828125e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 1.1920928955078125e-05s
INFO | --- Analysis for nlm_2007_mesh took 2.8298118114471436s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 9.059906005859375e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.2667832374572754s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.020270347595214844s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.0040740966796875e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for nlr-dataset-mod took 3.7655997276306152s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.7294487953186035s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.2646629810333252s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.020853757858276367s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.5762786865234375e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for NLW took 4.150674343109131s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.1927154064178467s
Availability | VoID file availability check for Nobel Prizes took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.2649087905883789s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02254009246826172s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.441375732421875e-05s
Believability | Calculation of trust value for Nobel Prizes took 1.1682510375976562e-05s
INFO | --- Analysis for nobelprizes took 8.78618860244751s
Availability | SPARQL endpoint availability check for NoiPA took 0.2978401184082031s
Availability | VoID file availability check for NoiPA took 0.0005178451538085938s
Extra | Recovery of all triples for NoiPA took 1.4468820095062256s
Performance | Total latancy measurement for NoiPA took 0.6682620048522949s
Amount of data | Number of triples check for NoiPA took 1.4818167686462402s
Interoperability | New terms check for NoiPA took 2.9746646881103516s
Versatility | Languages check for NoiPA took 60.12706398963928s
Interpretability | Number of blank nodes check for NoiPA took 0.3279259204864502s
Interpretability | RDF structures check for NoiPA took 0.468353271484375s
Versatility | Serialization formats check for NoiPA took 0.2549903392791748s
Availability | RDF dump link check for NoiPA took 0.2199711799621582s
License | MR license check for NoiPA took 0.2184128761291504s
License | HR license check for NoiPA took 60.234357833862305s
Amount of data | Number of property check for NoiPA took 0.23482871055603027s
Understandability | Number of label check for NoiPA took 0.5157668590545654s
Understandability | URI regex check for NoiPA took 0.348832368850708s
Understandability | Vocabs check for NoiPA took 0.30100345611572266s
Verifiability | Authors check for NoiPA took 0.18787550926208496s
Verifiability | Publishers check for NoiPA took 0.23595714569091797s
Performance | Throughput check for NoiPA took 10.917841672897339s
Amount of data | Check the number of entities for NoiPA took 6.651878356933594e-05s
Verifiability | Contribs. check for NoiPA took 0.1557445526123047s
Interlinking | sameAs chians check for NoiPA took 0.14396977424621582s
Interlinking | skos check for NoiPA took 0.5927994251251221s
Interlinking | skos check for NoiPA took 0.20151734352111816s
Timeliness | dataset update frequency check for NoiPA took 0.12931346893310547s
Currency | Creation date check for NoiPA took 0.48192787170410156s
Currency | Modification date check for NoiPA took 0.15292596817016602s
Rep.Conc. | URIs length for NoiPA took 19.66766357421875s
Interoperability | New vocabularies check for NoiPA took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.29406261444091797s
Accuracy | Check Functional Property for NoiPA took 0.18980002403259277s
Accuracy | Check Inverse Functional Property for NoiPA took 0.23200345039367676s
Accuracy | Check Empty annotation labels for NoiPA took 0.6824314594268799s
Accuracy | Check White space in annotation for NoiPA took 0.0300137996673584s
Accuracy | Check Datatype consistency for NoiPA took 0.03092169761657715s
Consistency | Disjoint class check for NoiPA took 0.14908576011657715s
Consistency | Check Misplaced properties for NoiPA took 17.941978216171265s
Consistency | Misplaced classes for NoiPA took 0.2837495803833008s
Consistency | Check Ontology hijacking for NoiPA took 1.7815296649932861s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.3034658432006836s
Consistency | Check Invalid usage of undefined properties for NoiPA took 19.273152828216553s
Conciseness | Check Extensional conciseness for NoiPA took 0.035094261169433594s
Conciseness | Check Intensional conciseness for NoiPA took 0.17767620086669922s
Security | Sign check for NoiPA took 0.23337078094482422s
Availability | Check URIs Dereferenciability for NoiPA took 16.84638738632202s
Completeness | Calculation of interlinking completeness for NoiPA took 0.419649600982666s
Reputation | Calculation of the PageRank for NoiPA took 0.02106642723083496s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for NoiPA took 4.172325134277344e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.6689300537109375e-06s
Believability | Calculation of trust value for NoiPA took 1.1205673217773438e-05s
INFO | --- Analysis for NoiPA took 404.32500886917114s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 1.0102465152740479s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.24967336654663086s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02084946632385254s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 0.00010013580322265625s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 7.3909759521484375e-06s
INFO | --- Analysis for nom took 9.633726119995117s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 25.82327151298523s
Availability | VoID file availability check for Nomenclator Asturias took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.2437150478363037s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.021063804626464844s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.296966552734375e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 5.7220458984375e-06s
INFO | --- Analysis for nomenclator-asturias took 136.76369714736938s
Availability | SPARQL endpoint availability check for nomisma took 4.029273986816406e-05s
Availability | VoID file availability check for nomisma took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for nomisma took 0.6635727882385254s
Reputation | Calculation of the PageRank for nomisma took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for nomisma took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for nomisma took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for nomisma took 3.170967102050781e-05s
Believability | Calculation of trust value for nomisma took 1.1920928955078125e-05s
INFO | --- Analysis for nomisma took 3.2845096588134766s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.4900972843170166s
Availability | VoID file availability check for Nomisma.org  took 0.0003726482391357422s
Extra | Recovery of all triples for Nomisma.org  took 300.0404851436615s
Performance | Total latancy measurement for Nomisma.org  took 1.9616599082946777s
Amount of data | Number of triples check for Nomisma.org  took 52.99238681793213s
Interoperability | New terms check for Nomisma.org  took 7.373528957366943s
Versatility | Languages check for Nomisma.org  took 134.87205719947815s
Interpretability | Number of blank nodes check for Nomisma.org  took 38.72340393066406s
Security | Check HTTPS for Nomisma.org  took 0.9488065242767334s
Interpretability | RDF structures check for Nomisma.org  took 0.3863847255706787s
Versatility | Serialization formats check for Nomisma.org  took 0.3947172164916992s
Availability | RDF dump link check for Nomisma.org  took 965.1878988742828s
License | MR license check for Nomisma.org  took 0.4134979248046875s
License | HR license check for Nomisma.org  took 59.673133850097656s
Amount of data | Number of property check for Nomisma.org  took 0.4359126091003418s
Understandability | Number of label check for Nomisma.org  took 8.773929834365845s
Understandability | URI regex check for Nomisma.org  took 0.9548196792602539s
Understandability | Vocabs check for Nomisma.org  took 0.510150671005249s
Verifiability | Authors check for Nomisma.org  took 0.3903815746307373s
Verifiability | Publishers check for Nomisma.org  took 0.4129183292388916s
Performance | Throughput check for Nomisma.org  took 11.723520278930664s
Amount of data | Check the number of entities for Nomisma.org  took 0.0005686283111572266s
Verifiability | Contribs. check for Nomisma.org  took 0.3836665153503418s
Interlinking | sameAs chians check for Nomisma.org  took 0.5738234519958496s
Interlinking | skos check for Nomisma.org  took 1.1315863132476807s
Interlinking | skos check for Nomisma.org  took 0.5697517395019531s
Timeliness | dataset update frequency check for Nomisma.org  took 0.37801647186279297s
Currency | Creation date check for Nomisma.org  took 0.8055975437164307s
Currency | Modification date check for Nomisma.org  took 0.3917043209075928s
Rep.Conc. | URIs length for Nomisma.org  took 591.0284452438354s
Interoperability | New vocabularies check for Nomisma.org  took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.47740960121154785s
Accuracy | Check Functional Property for Nomisma.org  took 0.510674238204956s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.72157883644104s
Consistency | Disjoint class check for Nomisma.org  took 0.37956690788269043s
Consistency | Check Misplaced properties for Nomisma.org  took 28.78743076324463s
Consistency | Check Ontology hijacking for Nomisma.org  took 566.4252939224243s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 30.73511791229248s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.0001628398895263672s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.6026532649993896s
Security | Sign check for Nomisma.org  took 0.38454270362854004s
Availability | Check URIs Dereferenciability for Nomisma.org  took 1838.7408583164215s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 0.6588258743286133s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.021328449249267578s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.6689300537109375e-06s
Believability | Calculation of trust value for Nomisma.org  took 1.049041748046875e-05s
INFO | --- Analysis for nomisma_org took 9093.85192322731s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.43241310119628906s
Availability | VoID file availability check for Curriculum Vitae took 0.0004856586456298828s
Extra | Recovery of all triples for Curriculum Vitae took 1.2883880138397217s
Performance | Total latancy measurement for Curriculum Vitae took 1.2801687717437744s
Amount of data | Number of triples check for Curriculum Vitae took 0.15267229080200195s
Interoperability | New terms check for Curriculum Vitae took 1.6481454372406006s
Versatility | Languages check for Curriculum Vitae took 0.12048101425170898s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.2831602096557617s
Interpretability | RDF structures check for Curriculum Vitae took 0.24799776077270508s
Versatility | Serialization formats check for Curriculum Vitae took 0.31270742416381836s
Availability | RDF dump link check for Curriculum Vitae took 0.25630736351013184s
License | MR license check for Curriculum Vitae took 0.2371807098388672s
License | HR license check for Curriculum Vitae took 0.12745976448059082s
Amount of data | Number of property check for Curriculum Vitae took 0.28053855895996094s
Understandability | Number of label check for Curriculum Vitae took 0.1283421516418457s
Understandability | URI regex check for Curriculum Vitae took 0.24958014488220215s
Understandability | Vocabs check for Curriculum Vitae took 0.24941110610961914s
Verifiability | Authors check for Curriculum Vitae took 0.1511974334716797s
Verifiability | Publishers check for Curriculum Vitae took 0.1339559555053711s
Amount of data | Check the number of entities for Curriculum Vitae took 0.00010943412780761719s
Verifiability | Contribs. check for Curriculum Vitae took 0.23208117485046387s
Interlinking | sameAs chians check for Curriculum Vitae took 0.24676895141601562s
Interlinking | skos check for Curriculum Vitae took 0.12638020515441895s
Interlinking | skos check for Curriculum Vitae took 0.12206387519836426s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.12555289268493652s
Currency | Creation date check for Curriculum Vitae took 0.3486602306365967s
Currency | Modification date check for Curriculum Vitae took 0.5306775569915771s
Rep.Conc. | URIs length for Curriculum Vitae took 0.31200551986694336s
Interoperability | New vocabularies check for Curriculum Vitae took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.2523186206817627s
Accuracy | Check Functional Property for Curriculum Vitae took 0.26760339736938477s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.2678663730621338s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.2516474723815918s
Accuracy | Check White space in annotation for Curriculum Vitae took 0.00010156631469726562s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.0032999515533447266s
Consistency | Disjoint class check for Curriculum Vitae took 0.13911771774291992s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.3347036838531494s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.5565605163574219s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.3169987201690674s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.5696043968200684s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0013391971588134766s
Security | Sign check for Curriculum Vitae took 0.2446146011352539s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 20.634154319763184s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.2899165153503418s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.02239680290222168s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 3.552436828613281e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.6689300537109375e-06s
Believability | Calculation of trust value for Curriculum Vitae took 1.2159347534179688e-05s
INFO | --- Analysis for Nordine_Bittich took 58.77393865585327s
Availability | SPARQL endpoint availability check for NorPark took 0.5006160736083984s
Availability | VoID file availability check for NorPark took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for NorPark took 0.26456117630004883s
Reputation | Calculation of the PageRank for NorPark took 0.021528959274291992s
Interlinking | Calculation of Degree of Connection for NorPark took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.553794860839844e-05s
Believability | Calculation of trust value for NorPark took 1.049041748046875e-05s
INFO | --- Analysis for norpark took 3.534496545791626s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.029520511627197266s
Availability | VoID file availability check for Parking Dataset took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.2922060489654541s
Reputation | Calculation of the PageRank for Parking Dataset took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.506111145019531e-05s
Believability | Calculation of trust value for Parking Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for norpark2 took 2.876481533050537s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.33455872535705566s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0004811286926269531s
Extra | Recovery of all triples for Norway fishery stocks dataset took 137.2896614074707s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.9882302284240723s
Amount of data | Number of triples check for Norway fishery stocks dataset took 9.947277069091797s
Interoperability | New terms check for Norway fishery stocks dataset took 14.507688045501709s
Versatility | Languages check for Norway fishery stocks dataset took 300.2485525608063s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 2.1473777294158936s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.2859790325164795s
Versatility | Serialization formats check for Norway fishery stocks dataset took 10.57481861114502s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.351421594619751s
License | MR license check for Norway fishery stocks dataset took 1.0704336166381836s
License | HR license check for Norway fishery stocks dataset took 300.23609685897827s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.21016216278076172s
Understandability | Number of label check for Norway fishery stocks dataset took 2.3764853477478027s
Understandability | URI regex check for Norway fishery stocks dataset took 1.012970209121704s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.5303072929382324s
Verifiability | Authors check for Norway fishery stocks dataset took 0.19933819770812988s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.2711057662963867s
Performance | Throughput check for Norway fishery stocks dataset took 11.45487666130066s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 3.24249267578125e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.20862793922424316s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.17833518981933594s
Interlinking | skos check for Norway fishery stocks dataset took 0.49140453338623047s
Interlinking | skos check for Norway fishery stocks dataset took 0.4268524646759033s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 8.050389289855957s
Currency | Creation date check for Norway fishery stocks dataset took 0.49402642250061035s
Currency | Modification date check for Norway fishery stocks dataset took 0.24867582321166992s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 167.2099118232727s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.19768142700195312s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.4439964294433594s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.44064807891845703s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 45.49748635292053s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.663252353668213s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.5444893836975098s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.18277430534362793s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 88.79278779029846s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.14304518699646s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 42.34780812263489s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.448683738708496s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 88.86249661445618s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.7476696968078613s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.5364775657653809s
Security | Sign check for Norway fishery stocks dataset took 1.224172830581665s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 15.695054531097412s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.46022939682006836s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.021203994750976562s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 4.291534423828125e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 1.3589859008789062e-05s
INFO | --- Analysis for Norway_Fishery_ took 2342.086930990219s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.26154184341430664s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0011522769927978516s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.2564537525177002s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020882844924926758s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.673004150390625e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.2874603271484375e-05s
INFO | --- Analysis for norwegian-geo-divisions took 6.74122428894043s
Availability | SPARQL endpoint availability check for NorwegianSoE took 8.7738037109375e-05s
Availability | VoID file availability check for NorwegianSoE took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.2550325393676758s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.022311925888061523s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 3.147125244140625e-05s
Believability | Calculation of trust value for NorwegianSoE took 1.3113021850585938e-05s
INFO | --- Analysis for norwegiansoe took 2.9128127098083496s
Availability | SPARQL endpoint availability check for NITP took 8.988380432128906e-05s
Availability | VoID file availability check for NITP took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for NITP took 0.2546684741973877s
Reputation | Calculation of the PageRank for NITP took 0.02172088623046875s
Interlinking | Calculation of Degree of Connection for NITP took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for NITP took 6.604194641113281e-05s
Believability | Calculation of trust value for NITP took 1.2159347534179688e-05s
INFO | --- Analysis for notIdentifier took 2.8710615634918213s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.291534423828125e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.24570465087890625s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.504753112792969e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 1.2636184692382812e-05s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.684161424636841s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 8.559226989746094e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.2587406635284424s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 2.9087066650390625e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 1.2159347534179688e-05s
INFO | --- Analysis for npg took 2.997398614883423s
Availability | SPARQL endpoint availability check for NPM took 4.267692565917969e-05s
Availability | VoID file availability check for NPM took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for NPM took 0.26184940338134766s
Reputation | Calculation of the PageRank for NPM took 0.021543025970458984s
Interlinking | Calculation of Degree of Connection for NPM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NPM took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for NPM took 3.3855438232421875e-05s
Believability | Calculation of trust value for NPM took 1.2159347534179688e-05s
INFO | --- Analysis for npm took 3.2607297897338867s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.060903310775756836s
Availability | VoID file availability check for NTNU special collections took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.2508528232574463s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020398616790771484s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.4836273193359375e-05s
Believability | Calculation of trust value for NTNU special collections took 1.3113021850585938e-05s
INFO | --- Analysis for ntnusc took 5.173793792724609s
Availability | SPARQL endpoint availability check for links took 8.511543273925781e-05s
Availability | VoID file availability check for links took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for links took 0.2671513557434082s
Reputation | Calculation of the PageRank for links took 0.0208437442779541s
Interlinking | Calculation of Degree of Connection for links took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for links took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for links took 1.239776611328125e-05s
Believability | Calculation of trust value for links took 1.0251998901367188e-05s
INFO | --- Analysis for nugmyanmar took 2.5361902713775635s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 8.893013000488281e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.28861331939697266s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.021856069564819336s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0008246898651123047s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 0.00010776519775390625s
Believability | Calculation of trust value for NUTS (GeoVocab) took 9.775161743164062e-06s
INFO | --- Analysis for nuts-geovocab took 2.4565505981445312s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.39611005783081055s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.2512226104736328s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.0229642391204834s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 7.176399230957031e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 1.2159347534179688e-05s
INFO | --- Analysis for nvd took 4.016920328140259s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.5926918983459473s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.26062703132629395s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.249282836914062e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.239776611328125e-05s
INFO | --- Analysis for nvs took 8.07579517364502s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.482269287109375e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.26261138916015625s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.020795583724975586s
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.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.0001842975616455078s
Believability | Calculation of trust value for New York Times - Linked Open Data took 1.2636184692382812e-05s
INFO | --- Analysis for nytimes-linked-open-data took 2.4521472454071045s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 8.296966552734375e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.2612781524658203s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.02123093605041504s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 3.170967102050781e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 1.2159347534179688e-05s
INFO | --- Analysis for o-anc took 2.9559085369110107s
Availability | SPARQL endpoint availability check for OANetzwerk took 5.1021575927734375e-05s
Availability | VoID file availability check for OANetzwerk took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.26731443405151367s
Reputation | Calculation of the PageRank for OANetzwerk took 0.022489547729492188s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 3.218650817871094e-05s
Believability | Calculation of trust value for OANetzwerk took 1.2159347534179688e-05s
INFO | --- Analysis for oanetzwerk took 2.8425536155700684s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 6.67572021484375e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.25629353523254395s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.02069711685180664s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 3.0040740966796875e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 1.2874603271484375e-05s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.9641292095184326s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.557579517364502s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0007295608520507812s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 2.4022223949432373s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 2.140801191329956s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 2.325488805770874s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.825921058654785s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.35346555709839s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.2046167850494385s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.28621602058410645s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.37476587295532227s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.5021138191223145s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.37578511238098145s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.3538680076599121s
License | HR license check for Italian Chamber of Deputies - official dataset took 60.41162061691284s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.3887672424316406s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.8896565437316895s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.8031275272369385s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.6946899890899658s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.5987448692321777s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.3207576274871826s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 11.435177326202393s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 7.462501525878906e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.37607359886169434s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.39951324462890625s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.35393428802490234s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.34821510314941406s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.43170976638793945s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.7520661354064941s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.3644254207611084s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 17.83986735343933s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.3365302085876465s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.44380640983581543s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.3705861568450928s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 1.155540943145752s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.030512332916259766s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.02764725685119629s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.40825772285461426s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 12.97636866569519s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.42502832412719727s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.0423262119293213s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.3680915832519531s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 13.81994104385376s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03408002853393555s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.4317288398742676s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.3561069965362549s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 15.093017816543579s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.31234264373779297s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.021187782287597656s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00011157989501953125s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 1.0967254638671875e-05s
INFO | --- Analysis for ocd took 399.62311720848083s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 5.030632019042969e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.23576807975769043s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.022098541259765625s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.933906555175781e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.6450881958007812e-05s
INFO | --- Analysis for oceandrilling-borehole took 6.121264696121216s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 15.482284784317017s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.28165769577026367s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020495891571044922s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.082389831542969e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.1682510375976562e-05s
INFO | --- Analysis for oceandrilling-codices took 40.26649761199951s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 78.59865427017212s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.29843640327453613s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 4.124641418457031e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.0251998901367188e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 101.89653444290161s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 10.983721733093262s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.25717687606811523s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.02082657814025879s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.743171691894531e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 8.106231689453125e-06s
INFO | --- Analysis for oceandrilling-forams took 19.179449796676636s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 68.70763516426086s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0007851123809814453s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.2783668041229248s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.02109837532043457s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.719329833984375e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.1920928955078125e-05s
INFO | --- Analysis for oceandrilling-janus took 79.91755890846252s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 15.532160520553589s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0007576942443847656s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.25627684593200684s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.021593093872070312s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.1948089599609375e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.1920928955078125e-05s
INFO | --- Analysis for oceandrilling-janusamp took 28.750444412231445s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 5.454362630844116s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0004100799560546875s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.2556300163269043s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.022103548049926758s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.956390380859375e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 6.9141387939453125e-06s
INFO | --- Analysis for oceandrilling-ldeo took 33.926321268081665s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 6.937980651855469e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.2376420497894287s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.626678466796875e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.1444091796875e-05s
INFO | --- Analysis for oclc-fast took 7.701477527618408s
Availability | SPARQL endpoint availability check for Open Data Communities took 8.392333984375e-05s
Availability | VoID file availability check for Open Data Communities took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.24162936210632324s
Reputation | Calculation of the PageRank for Open Data Communities took 0.02062368392944336s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0008099079132080078s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 3.24249267578125e-05s
Believability | Calculation of trust value for Open Data Communities took 7.62939453125e-06s
INFO | --- Analysis for odc took 2.965571403503418s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.6253204345703125e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.2638437747955322s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.022368669509887695s
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.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.314018249511719e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.1205673217773438e-05s
INFO | --- Analysis for odc-imd-environment-score took 6.015043020248413s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 8.296966552734375e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.25809717178344727s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 3.0279159545898438e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 1.2159347534179688e-05s
INFO | --- Analysis for odc-imd-rank-2007 took 2.960658311843872s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.14128708839416504s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0003540515899658203s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 0.8176183700561523s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 0.9552242755889893s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.18543004989624023s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.5369873046875s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.37491607666015625s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 28.249139070510864s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.10039329528808594s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.21195363998413086s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.14365649223327637s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 48.013527154922485s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.16346526145935059s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 30.177761554718018s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.17063522338867188s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.13500142097473145s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.515862226486206s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.1422581672668457s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.1999204158782959s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.13501596450805664s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 11.023935794830322s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 6.961822509765625e-05s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.20350408554077148s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.13819336891174316s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.20348834991455078s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.14541387557983398s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.18995189666748047s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.6871261596679688s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.15588617324829102s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 1.1369383335113525s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.1947922706604004s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.13458752632141113s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.13618898391723633s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.17491483688354492s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.40804433822631836s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 1.2772221565246582s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.602107048034668s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.0001742839813232422s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.6276326179504395s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.15521931648254395s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 34.845407485961914s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.02067399024963379s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.5762786865234375e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 1.6689300537109375e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 5.245208740234375e-06s
INFO | --- Analysis for odc-lsoa took 294.34464859962463s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 9.584426879882812e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.25417590141296387s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.020885229110717773s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 3.0279159545898438e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 1.0967254638671875e-05s
INFO | --- Analysis for odc-population-2005 took 2.895097255706787s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.38690185546875e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.2628192901611328s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.02119278907775879s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0010647773742675781s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 3.933906555175781e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 1.4543533325195312e-05s
INFO | --- Analysis for ods took 2.817842960357666s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.20627522468566895s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.24622035026550293s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.417533874511719e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for oecd-linked-data took 2.5778310298919678s
Availability | SPARQL endpoint availability check for Offener Haushalt took 4.172325134277344e-05s
Availability | VoID file availability check for Offener Haushalt took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.24877309799194336s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.020871639251708984s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 3.0279159545898438e-05s
Believability | Calculation of trust value for Offener Haushalt took 1.3113021850585938e-05s
INFO | --- Analysis for offener-haushalt took 2.81187105178833s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.364793300628662s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.25266432762145996s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.02086043357849121s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 3.933906555175781e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 1.0013580322265625e-05s
INFO | --- Analysis for ogolod took 102.89027452468872s
Availability | SPARQL endpoint availability check for OLAC Metadata took 8.535385131835938e-05s
Availability | VoID file availability check for OLAC Metadata took 0.001407623291015625s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.27535533905029297s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 3.886222839355469e-05s
Believability | Calculation of trust value for OLAC Metadata took 1.239776611328125e-05s
INFO | --- Analysis for olac took 22.540196657180786s
Availability | SPARQL endpoint availability check for OLiA took 4.220008850097656e-05s
Availability | VoID file availability check for OLiA took 0.0008156299591064453s
Completeness | Calculation of interlinking completeness for OLiA took 0.252516508102417s
Reputation | Calculation of the PageRank for OLiA took 0.021647214889526367s
Interlinking | Calculation of Degree of Connection for OLiA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00012111663818359375s
Believability | Calculation of trust value for OLiA took 1.049041748046875e-05s
INFO | --- Analysis for olia took 12.246403455734253s
Availability | SPARQL endpoint availability check for OLiA Discourse took 7.033348083496094e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.2712666988372803s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.02173137664794922s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 3.886222839355469e-05s
Believability | Calculation of trust value for OLiA Discourse took 1.1920928955078125e-05s
INFO | --- Analysis for olia-discourse took 7.076565504074097s
Availability | SPARQL endpoint availability check for Open Land Use took 0.20486736297607422s
Availability | VoID file availability check for Open Land Use took 0.0005273818969726562s
Extra | Recovery of all triples for Open Land Use took 142.07158994674683s
Performance | Total latancy measurement for Open Land Use took 0.9719095230102539s
Amount of data | Number of triples check for Open Land Use took 9.192623853683472s
Interoperability | New terms check for Open Land Use took 14.937822341918945s
Versatility | Languages check for Open Land Use took 300.22858905792236s
Interpretability | Number of blank nodes check for Open Land Use took 2.2311408519744873s
Interpretability | RDF structures check for Open Land Use took 0.30152320861816406s
Versatility | Serialization formats check for Open Land Use took 13.909457683563232s
Availability | RDF dump link check for Open Land Use took 0.34720635414123535s
License | MR license check for Open Land Use took 0.7675797939300537s
License | HR license check for Open Land Use took 300.250563621521s
Amount of data | Number of property check for Open Land Use took 0.3347301483154297s
Understandability | Number of label check for Open Land Use took 2.4849560260772705s
Understandability | URI regex check for Open Land Use took 0.9607665538787842s
Understandability | Vocabs check for Open Land Use took 0.6016895771026611s
Verifiability | Authors check for Open Land Use took 0.20003581047058105s
Verifiability | Publishers check for Open Land Use took 0.24799442291259766s
Performance | Throughput check for Open Land Use took 11.14757490158081s
Amount of data | Check the number of entities for Open Land Use took 6.29425048828125e-05s
Verifiability | Contribs. check for Open Land Use took 0.1810474395751953s
Interlinking | sameAs chians check for Open Land Use took 0.1842949390411377s
Interlinking | skos check for Open Land Use took 0.4403872489929199s
Interlinking | skos check for Open Land Use took 0.4086921215057373s
Timeliness | dataset update frequency check for Open Land Use took 7.011748552322388s
Currency | Creation date check for Open Land Use took 0.4324312210083008s
Currency | Modification date check for Open Land Use took 0.24531102180480957s
Rep.Conc. | URIs length for Open Land Use took 169.17032480239868s
Interoperability | New vocabularies check for Open Land Use took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.19995355606079102s
Accuracy | Check Functional Property for Open Land Use took 0.45424866676330566s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.4311220645904541s
Accuracy | Check Empty annotation labels for Open Land Use took 49.55689287185669s
Accuracy | Check White space in annotation for Open Land Use took 2.653409481048584s
Accuracy | Check Datatype consistency for Open Land Use took 2.6141557693481445s
Consistency | Disjoint class check for Open Land Use took 0.21151161193847656s
Consistency | Check Misplaced properties for Open Land Use took 87.48149991035461s
Consistency | Misplaced classes for Open Land Use took 8.375224590301514s
Consistency | Check Ontology hijacking for Open Land Use took 40.25968623161316s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.4429008960723877s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 89.65437316894531s
Conciseness | Check Extensional conciseness for Open Land Use took 2.7442562580108643s
Conciseness | Check Intensional conciseness for Open Land Use took 0.6240944862365723s
Security | Sign check for Open Land Use took 0.824568510055542s
Availability | Check URIs Dereferenciability for Open Land Use took 14.546075820922852s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.42031192779541016s
Reputation | Calculation of the PageRank for Open Land Use took 0.0224609375s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 3.838539123535156e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Land Use took 1.2159347534179688e-05s
INFO | --- Analysis for OLU took 2342.5997767448425s
Availability | SPARQL endpoint availability check for OmegaWiki took 7.033348083496094e-05s
Availability | VoID file availability check for OmegaWiki took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.2742955684661865s
Reputation | Calculation of the PageRank for OmegaWiki took 0.020772695541381836s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 2.8133392333984375e-05s
Believability | Calculation of trust value for OmegaWiki took 7.152557373046875e-06s
INFO | --- Analysis for omegawiki took 2.891016960144043s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.6778788566589355s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.2410273551940918s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 3.552436828613281e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-als took 3.8897743225097656s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.3017902374267578s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.2555580139160156s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 1.6689300537109375e-05s
INFO | --- Analysis for omwn-arb took 3.134645938873291s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.2541463375091553s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.2567160129547119s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-bul took 2.9630839824676514s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.3019568920135498s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.25377750396728516s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.021802902221679688s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-cow took 3.0484578609466553s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.25841236114501953s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2560153007507324s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020945310592651367s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 2.956390380859375e-05s
INFO | --- Analysis for omwn-cwn took 3.525059223175049s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.25604987144470215s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.2507200241088867s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-dan took 3.0444939136505127s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.25581932067871094s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.2690918445587158s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0008251667022705078s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 5.4836273193359375e-06s
INFO | --- Analysis for omwn-ell took 2.9394798278808594s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.26813578605651855s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2604963779449463s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.022170543670654297s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-eng took 2.9771926403045654s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.224931001663208s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.25948643684387207s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.02217864990234375s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-fas took 2.9574766159057617s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.25294923782348633s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.00040602684020996094s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2608678340911865s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.02239704132080078s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-fin took 2.9770009517669678s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.26453733444213867s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.2527918815612793s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.020667076110839844s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-fra took 2.9872121810913086s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.23131418228149414s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.2695484161376953s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.020829200744628906s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-heb took 2.952395439147949s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.23412704467773438s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.24679160118103027s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.022709131240844727s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 5.9604644775390625e-06s
INFO | --- Analysis for omwn-hrv took 2.9560420513153076s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.27309584617614746s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2345116138458252s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0217587947845459s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 4.100799560546875e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
INFO | --- Analysis for omwn-isl took 3.1058552265167236s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.25850629806518555s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.2585263252258301s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-ita took 3.006531000137329s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.24027085304260254s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.26564908027648926s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.021447181701660156s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0010035037994384766s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 4.649162292480469e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-iwn took 2.9498634338378906s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.252657413482666s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.00048828125s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.25846004486083984s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.020989179611206055s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-jpn took 3.02351450920105s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.266162633895874s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.260451078414917s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.023060083389282227s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-mcr took 2.8930017948150635s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.27654504776000977s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.24198007583618164s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.020633220672607422s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-msa took 2.981621742248535s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.27563953399658203s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.23893308639526367s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.021586179733276367s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-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.074129104614258s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.2850527763366699s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.26303887367248535s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.021136999130249023s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-nor took 3.0017120838165283s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.26773619651794434s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.25786590576171875s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.022897958755493164s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007123947143554688s
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.1444091796875e-05s
INFO | --- Analysis for omwn-pol took 3.0332047939300537s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2590363025665283s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2526571750640869s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.02321314811706543s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 4.1484832763671875e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-por took 2.9892749786376953s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.25313425064086914s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.257326602935791s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0206143856048584s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-ron took 2.945300579071045s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.24577856063842773s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2658665180206299s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.020462751388549805s
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.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-slk took 2.995609760284424s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.24441933631896973s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.00043201446533203125s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.26307249069213867s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020368337631225586s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
INFO | --- Analysis for omwn-slv took 3.043626070022583s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.25702977180480957s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2601478099822998s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0205996036529541s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-swe took 3.0300073623657227s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.2308504581451416s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.23706793785095215s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.020309925079345703s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
INFO | --- Analysis for omwn-tha took 2.9652819633483887s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 4.531682252883911s
Availability | VoID file availability check for OntoBeef Domain took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.2508819103240967s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020418882369995117s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.8160552978515625e-05s
Believability | Calculation of trust value for OntoBeef Domain took 9.775161743164062e-06s
INFO | --- Analysis for ontobeef-domain took 28.30794095993042s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.482269287109375e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.2811245918273926s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.02030801773071289s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.72747802734375e-05s
Believability | Calculation of trust value for Ontos News Portal took 7.62939453125e-06s
INFO | --- Analysis for ontos-news-portal took 3.6023926734924316s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 5.602836608886719e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.00034046173095703125s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.2705867290496826s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020873546600341797s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.147125244140625e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 1.1682510375976562e-05s
INFO | --- Analysis for ookaboo-rdf-dump took 2.5312747955322266s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.6253204345703125e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0003044605255126953s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.24297690391540527s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.695487976074219e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 5.9604644775390625e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 11.136446237564087s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.076957702636719e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.25277161598205566s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.022951602935791016s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 2.9802322387695312e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 1.1205673217773438e-05s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 2.8331360816955566s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 5.7220458984375e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.2482624053955078s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.022388219833374023s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.649162292480469e-05s
Believability | Calculation of trust value for Open Data Euskadi took 8.344650268554688e-06s
INFO | --- Analysis for open-data-euskadi took 8.19831132888794s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 8.535385131835938e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.24226164817810059s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010061264038085938s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 9.775161743164062e-06s
INFO | --- Analysis for open-data-risp took 12.204619884490967s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.22831416130065918s
Availability | VoID file availability check for Open Data Thesaurus took 0.0005221366882324219s
Extra | Recovery of all triples for Open Data Thesaurus took 1.3051319122314453s
Performance | Total latancy measurement for Open Data Thesaurus took 0.4538726806640625s
Amount of data | Number of triples check for Open Data Thesaurus took 0.07957172393798828s
Interoperability | New terms check for Open Data Thesaurus took 1.4293785095214844s
Versatility | Languages check for Open Data Thesaurus took 0.08841180801391602s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.09473133087158203s
Security | Check HTTPS for Open Data Thesaurus took 0.31244587898254395s
Interpretability | RDF structures check for Open Data Thesaurus took 0.08705592155456543s
Versatility | Serialization formats check for Open Data Thesaurus took 0.08468818664550781s
Availability | RDF dump link check for Open Data Thesaurus took 1.0388178825378418s
License | MR license check for Open Data Thesaurus took 0.09578299522399902s
License | HR license check for Open Data Thesaurus took 0.09641790390014648s
Amount of data | Number of property check for Open Data Thesaurus took 0.09869933128356934s
Understandability | Number of label check for Open Data Thesaurus took 0.08016371726989746s
Understandability | URI regex check for Open Data Thesaurus took 0.16494464874267578s
Understandability | Vocabs check for Open Data Thesaurus took 0.08732938766479492s
Verifiability | Authors check for Open Data Thesaurus took 0.08725666999816895s
Verifiability | Publishers check for Open Data Thesaurus took 0.09515666961669922s
Performance | Throughput check for Open Data Thesaurus took 10.44850778579712s
Amount of data | Check the number of entities for Open Data Thesaurus took 7.605552673339844e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.0938260555267334s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.11034989356994629s
Interlinking | skos check for Open Data Thesaurus took 0.09557652473449707s
Interlinking | skos check for Open Data Thesaurus took 0.08780217170715332s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.08057212829589844s
Currency | Creation date check for Open Data Thesaurus took 0.1841433048248291s
Currency | Modification date check for Open Data Thesaurus took 0.1752927303314209s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.387988805770874s
Interoperability | New vocabularies check for Open Data Thesaurus took 0.9557993412017822s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.1109163761138916s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.09424233436584473s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.08342957496643066s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.13535714149475098s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011534690856933594s
Consistency | Disjoint class check for Open Data Thesaurus took 0.09677958488464355s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.18023371696472168s
Consistency | Misplaced classes for Open Data Thesaurus took 0.07876181602478027s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.4738173484802246s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.4337036609649658s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00014495849609375s
Security | Sign check for Open Data Thesaurus took 0.09765958786010742s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.2620198726654053s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.021822452545166016s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.153915405273438e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 0.7015161514282227s
Believability | Calculation of trust value for Open Data Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for open-data-thesaurus took 72.18812394142151s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.124641418457031e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.2675776481628418s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 2.9325485229492188e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0020978450775146484s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 6.246566772460938e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 1.239776611328125e-05s
INFO | --- Analysis for open-data-tor-vergata took 2.9623610973358154s
Availability | SPARQL endpoint availability check for Open Election Data Project took 7.605552673339844e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.24863505363464355s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.699562072753906e-05s
Believability | Calculation of trust value for Open Election Data Project took 9.298324584960938e-06s
INFO | --- Analysis for open-election-data-project took 42.356950759887695s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 4.407686471939087s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.2507312297821045s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02151942253112793s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.368492126464844e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 9.298324584960938e-06s
INFO | --- Analysis for open-energy-info-wiki took 11.122300386428833s
Availability | SPARQL endpoint availability check for Open Library took 4.696846008300781e-05s
Availability | VoID file availability check for Open Library took 0.0007779598236083984s
Completeness | Calculation of interlinking completeness for Open Library took 0.3253209590911865s
Reputation | Calculation of the PageRank for Open Library took 0.022493839263916016s
Interlinking | Calculation of Degree of Connection for Open Library took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.914138793945312e-05s
Believability | Calculation of trust value for Open Library took 1.4066696166992188e-05s
INFO | --- Analysis for open-library took 10.60657262802124s
Availability | SPARQL endpoint availability check for Open Directory took 4.124641418457031e-05s
Availability | VoID file availability check for Open Directory took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Open Directory took 0.29863476753234863s
Reputation | Calculation of the PageRank for Open Directory took 0.021843433380126953s
Interlinking | Calculation of Degree of Connection for Open Directory took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Directory took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Open Directory took 3.0279159545898438e-05s
Believability | Calculation of trust value for Open Directory took 1.430511474609375e-05s
INFO | --- Analysis for open_directory took 2.8456971645355225s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.3464195728302002s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0005471706390380859s
Extra | Recovery of all triples for Open Land Use @PSNC took 135.75136947631836s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.9983236789703369s
Amount of data | Number of triples check for Open Land Use @PSNC took 9.169561624526978s
Interoperability | New terms check for Open Land Use @PSNC took 14.31122612953186s
Versatility | Languages check for Open Land Use @PSNC took 300.17686700820923s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 2.127808094024658s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.28537631034851074s
Versatility | Serialization formats check for Open Land Use @PSNC took 9.408516883850098s
Availability | RDF dump link check for Open Land Use @PSNC took 0.3043038845062256s
License | MR license check for Open Land Use @PSNC took 0.6914184093475342s
License | HR license check for Open Land Use @PSNC took 300.21849489212036s
Amount of data | Number of property check for Open Land Use @PSNC took 0.2197871208190918s
Understandability | Number of label check for Open Land Use @PSNC took 2.3930435180664062s
Understandability | URI regex check for Open Land Use @PSNC took 0.8860070705413818s
Understandability | Vocabs check for Open Land Use @PSNC took 0.5374572277069092s
Verifiability | Authors check for Open Land Use @PSNC took 0.21576929092407227s
Verifiability | Publishers check for Open Land Use @PSNC took 0.2604823112487793s
Performance | Throughput check for Open Land Use @PSNC took 11.491336822509766s
Amount of data | Check the number of entities for Open Land Use @PSNC took 6.961822509765625e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.19581127166748047s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.19737982749938965s
Interlinking | skos check for Open Land Use @PSNC took 0.4730250835418701s
Interlinking | skos check for Open Land Use @PSNC took 0.4738762378692627s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 5.760100841522217s
Currency | Creation date check for Open Land Use @PSNC took 0.4696784019470215s
Currency | Modification date check for Open Land Use @PSNC took 0.24728083610534668s
Rep.Conc. | URIs length for Open Land Use @PSNC took 175.76878380775452s
Interoperability | New vocabularies check for Open Land Use @PSNC took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.21132230758666992s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.3907661437988281s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.3644289970397949s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 47.603514432907104s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.6606838703155518s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.616915702819824s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.19838929176330566s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 89.96405410766602s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.379364013671875s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 39.54421949386597s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.3676352500915527s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 89.9494423866272s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.723289728164673s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.5840587615966797s
Security | Sign check for Open Land Use @PSNC took 0.9415783882141113s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 13.109431505203247s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.6514604091644287s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.02158045768737793s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 4.1961669921875e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.3113021850585938e-05s
INFO | --- Analysis for Open_Land_Use took 2345.849553823471s
Availability | SPARQL endpoint availability check for flyatlas took 1.2330024242401123s
Availability | VoID file availability check for flyatlas took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for flyatlas took 0.26241159439086914s
Reputation | Calculation of the PageRank for flyatlas took 0.020763158798217773s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.0517578125e-05s
Believability | Calculation of trust value for flyatlas took 1.239776611328125e-05s
INFO | --- Analysis for openbiomed-flyatlas took 5.363188982009888s
Availability | SPARQL endpoint availability check for OpenCalais took 4.363059997558594e-05s
Availability | VoID file availability check for OpenCalais took 0.0003151893615722656s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.25693535804748535s
Reputation | Calculation of the PageRank for OpenCalais took 0.020975828170776367s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.0001430511474609375s
Believability | Calculation of trust value for OpenCalais took 6.67572021484375e-06s
INFO | --- Analysis for opencalais took 11.538804292678833s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 4.2438507080078125e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.23866748809814453s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020872116088867188s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.295608520507812e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 9.059906005859375e-06s
INFO | --- Analysis for opencorporates took 2.5849344730377197s
Availability | SPARQL endpoint availability check for OpenCyc took 4.267692565917969e-05s
Availability | VoID file availability check for OpenCyc took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.296466588973999s
Reputation | Calculation of the PageRank for OpenCyc took 0.020743846893310547s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010347366333007812s
Believability | Calculation of trust value for OpenCyc took 1.1444091796875e-05s
INFO | --- Analysis for opencyc took 2.39339542388916s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 5.602836608886719e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.27727556228637695s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020471572875976562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.24249267578125e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 3.267526865005493s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 6.151199340820312e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.2705528736114502s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 3.2626945972442627s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 8.535385131835938e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.2576749324798584s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.02266716957092285s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 2.8622043132781982s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.744529724121094e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.29203343391418457s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.020990371704101562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.3289601802825928s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 8.559226989746094e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0007183551788330078s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.2882730960845947s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.021205425262451172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.012437105178833s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 8.7738037109375e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.24989032745361328s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020963191986083984s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.8061811923980713s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 8.487701416015625e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.24863076210021973s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.02160358428955078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 2.813244104385376s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 5.984306335449219e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.2893657684326172s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020888090133666992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.3032116889953613s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.887580871582031e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0003628730773925781s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.25599145889282227s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.021122455596923828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.00084686279296875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.935264587402344e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 2.6876487731933594s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0003554821014404297s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.24555683135986328s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020817279815673828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0008292198181152344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.0013580322265625e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 2.949476480484009s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.24235844612121582s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 4.025890111923218s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 0.00013971328735351562s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.24730610847473145s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.0208284854888916s
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.000705718994140625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 3.168004274368286s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.2623593807220459s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.02084207534790039s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 2.933034896850586s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.2554585933685303s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.022045612335205078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.3104352951049805s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.2451629638671875s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.900683641433716s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 7.43865966796875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.2552986145019531s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 5.245208740234375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.99678897857666s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.23988580703735352s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.021310091018676758s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.085840940475464s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 6.937980651855469e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.23842239379882812s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.021105527877807617s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0008511543273925781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.935264587402344e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 4.022964239120483s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 7.963180541992188e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.011373281478881836s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.24406909942626953s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.02105236053466797s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.3387486934661865s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.2402629852294922s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.02082037925720215s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 2.9338018894195557s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 9.369850158691406e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.3095412254333496s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.020981788635253906s
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.000713348388671875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 3.1470038890838623s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0003249645233154297s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.2719559669494629s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020452499389648438s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 2.711498975753784s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 6.842613220214844e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.26051783561706543s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.7256267070770264s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.9591064453125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0008025169372558594s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.2637293338775635s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020337581634521484s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.4066696166992188e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 2.7238545417785645s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.24666476249694824s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0202939510345459s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 2.6943440437316895s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.24332022666931152s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0206754207611084s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 2.6151325702667236s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 8.797645568847656e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.257033109664917s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.02243494987487793s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 3.782172441482544s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.267533540725708s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.021187305450439453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 2.693143606185913s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0003154277801513672s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.2603905200958252s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.021049022674560547s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 2.6928160190582275s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0001804828643798828s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.2654895782470703s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020949125289916992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.57763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 2.688692092895508s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 5.841255187988281e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0004067420959472656s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.25523972511291504s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.02107691764831543s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 2.6780905723571777s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2768697738647461s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020665407180786133s
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.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 2.738062858581543s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 6.723403930664062e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.27646732330322266s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.021619796752929688s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 5.14984130859375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 2.7350213527679443s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.893013000488281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.23488402366638184s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.02125239372253418s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.030632019042969e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.2677204608917236s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 8.749961853027344e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.27079105377197266s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.021169185638427734s
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.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.76837158203125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.3236007690429688s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 8.726119995117188e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.2624688148498535s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.021183252334594727s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 2.6067538261413574s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 5.745887756347656e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.2780640125274658s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.020978212356567383s
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.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.673004150390625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 3.822817802429199s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0003993511199951172s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.2517549991607666s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.021875619888305664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0009112358093261719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 5.054473876953125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 2.736450433731079s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.26064538955688477s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.020859956741333008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0010347366333007812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 5.221366882324219e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 3.0697972774505615s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 8.511543273925781e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.25461554527282715s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020998477935791016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.76837158203125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 2.605173110961914s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.9114227294921875e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.2976398468017578s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020827770233154297s
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.000762939453125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 2.940638542175293s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.2513139247894287s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.021142005920410156s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 2.6920130252838135s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 6.628036499023438e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.24320077896118164s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 3.6805975437164307s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 5.540008068084717s
Availability | VoID file availability check for Open Data of Ecuador took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.26177430152893066s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.023099184036254883s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.726119995117188e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.2636184692382812e-05s
INFO | --- Analysis for opendataec took 10.972803354263306s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.38690185546875e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.3007540702819824s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020905256271362305s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.0728836059570312e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 5.430530548095703s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.1961669921875e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.2506530284881592s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020586729049682617s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0010657310485839844s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 7.033348083496094e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 1.1205673217773438e-05s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 2.7345194816589355s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.1961669921875e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.257979154586792s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.021384477615356445s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 1.2159347534179688e-05s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.5380427837371826s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 0.00011205673217773438s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.2540271282196045s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020781278610229492s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 1.1444091796875e-05s
INFO | --- Analysis for opendatascotland-simd-education-rank took 3.838724374771118s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 9.441375732421875e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.2763388156890869s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.021654367446899414s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.1920928955078125e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 3.543224811553955s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 8.273124694824219e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.2632136344909668s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.022179126739501953s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 1.1920928955078125e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 3.528498649597168s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.220008850097656e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.2528567314147949s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02142477035522461s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 1.6689300537109375e-05s
INFO | --- Analysis for opendatascotland-simd-health-rank took 3.4075589179992676s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.220008850097656e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.2633993625640869s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.02301645278930664s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 1.1920928955078125e-05s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 3.4943325519561768s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.410743713378906e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.267437219619751s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020528554916381836s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 1.2636184692382812e-05s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.363743782043457s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 31.176527976989746s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.28479814529418945s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.022384166717529297s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.528594970703125e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.2159347534179688e-05s
INFO | --- Analysis for openlink-lod-cache took 63.654892921447754s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 8.988380432128906e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.24608325958251953s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.02058577537536621s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.512901306152344e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 1.0728836059570312e-05s
INFO | --- Analysis for openlinksw-dataspaces took 2.9171628952026367s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.7206878662109375e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.25641417503356934s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.298324584960938e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 8.821487426757812e-06s
INFO | --- Analysis for openlylocal took 14.174745082855225s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 2.707134246826172s
Availability | VoID file availability check for OpenMobileNetwork took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.306410551071167s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.021034955978393555s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.000997304916381836s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 8.893013000488281e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 1.3113021850585938e-05s
INFO | --- Analysis for openmobilenetwork took 6.96410059928894s
Availability | SPARQL endpoint availability check for OpenTox took 4.363059997558594e-05s
Availability | VoID file availability check for OpenTox took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for OpenTox took 0.2847938537597656s
Reputation | Calculation of the PageRank for OpenTox took 0.02165818214416504s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for OpenTox took 3.075599670410156e-05s
Believability | Calculation of trust value for OpenTox took 1.33514404296875e-05s
INFO | --- Analysis for opentox took 2.8473808765411377s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 6.604194641113281e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.25298500061035156s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.020952939987182617s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 2.9087066650390625e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 7.867813110351562e-06s
INFO | --- Analysis for openuplabs took 2.881317138671875s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 8.916854858398438e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.0003018379211425781s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.24039292335510254s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.020859718322753906s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 5.173683166503906e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 8.58306884765625e-06s
INFO | --- Analysis for opus took 2.849423408508301s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 3.9577484130859375e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.25185561180114746s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.02074742317199707s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.528594970703125e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 7.152557373046875e-06s
INFO | --- Analysis for orcid took 2.8812806606292725s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 1.0069186687469482s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.2971072196960449s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.02103877067565918s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.441375732421875e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for ordnance-survey-linked-data took 6.1576855182647705s
Availability | SPARQL endpoint availability check for oreilly took 4.4345855712890625e-05s
Availability | VoID file availability check for oreilly took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for oreilly took 0.2948617935180664s
Reputation | Calculation of the PageRank for oreilly took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for oreilly took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.8160552978515625e-05s
Believability | Calculation of trust value for oreilly took 1.1920928955078125e-05s
INFO | --- Analysis for oreilly took 4.718612909317017s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.4296793937683105s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.24988412857055664s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.020765304565429688s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 4.458427429199219e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 1.2636184692382812e-05s
INFO | --- Analysis for Organchem-Data took 7.204291343688965s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.15157198905944824s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.24451708793640137s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020612716674804688s
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.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 6.866455078125e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.5020370483398438e-05s
INFO | --- Analysis for organic-edunet took 9.187199115753174s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.4411303997039795s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0005733966827392578s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 12.216495037078857s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.7394578456878662s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.18332886695861816s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.7114951610565186s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 5.9705705642700195s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.1643071174621582s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.23827528953552246s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.1598515510559082s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.1392514705657959s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.1341264247894287s
License | HR license check for Open Research Knowledge Graph (ORKG) took 3.9818408489227295s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.168654203414917s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.1685810089111328s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.3497965335845947s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.13187217712402344s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.14136600494384766s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.16602611541748047s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.783670663833618s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 7.700920104980469e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.16200757026672363s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.16411828994750977s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.1927340030670166s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.18526864051818848s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.19226813316345215s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.3465428352355957s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.36059093475341797s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 7.354414224624634s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.1383800506591797s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.13854694366455078s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.15952610969543457s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 5.72535252571106s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.30843639373779297s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.26930904388427734s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.18545174598693848s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.3647162914276123s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.9621422290802002s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 4.912895441055298s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.3967869281768799s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.3133456707000732s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.2848339080810547s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.16244077682495117s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.16188478469848633s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 1890.7000856399536s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.6864213943481445s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.022832155227661133s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 7.152557373046875e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0009293556213378906s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 6.604194641113281e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 7.748603820800781e-05s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.3589859008789062e-05s
INFO | --- Analysis for orkg took 2153.573339700699s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 3.7905685901641846s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0007083415985107422s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.2639186382293701s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.021158933639526367s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.916854858398438e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 1.1444091796875e-05s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 30.287760257720947s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.462066888809204s
Availability | VoID file availability check for OSM Semantic Network took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.23731446266174316s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.021016836166381836s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.9577484130859375e-05s
Believability | Calculation of trust value for OSM Semantic Network took 1.3589859008789062e-05s
INFO | --- Analysis for osm-semantic-network took 7.987757682800293s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.3553910255432129s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.00029015541076660156s
Extra | Recovery of all triples for Open Transport Map @PSNC took 138.08405184745789s
Performance | Total latancy measurement for Open Transport Map @PSNC took 0.9467582702636719s
Amount of data | Number of triples check for Open Transport Map @PSNC took 9.238349914550781s
Interoperability | New terms check for Open Transport Map @PSNC took 14.261645317077637s
Versatility | Languages check for Open Transport Map @PSNC took 300.24981355667114s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 2.2298107147216797s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.22394633293151855s
Versatility | Serialization formats check for Open Transport Map @PSNC took 11.135045766830444s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.37706995010375977s
License | MR license check for Open Transport Map @PSNC took 0.981879711151123s
License | HR license check for Open Transport Map @PSNC took 300.24780201911926s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.2010350227355957s
Understandability | Number of label check for Open Transport Map @PSNC took 2.5022077560424805s
Understandability | URI regex check for Open Transport Map @PSNC took 0.9565703868865967s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.19020295143127441s
Verifiability | Authors check for Open Transport Map @PSNC took 0.18612384796142578s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.2322549819946289s
Performance | Throughput check for Open Transport Map @PSNC took 11.375962972640991s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 6.699562072753906e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.1982583999633789s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.20123624801635742s
Interlinking | skos check for Open Transport Map @PSNC took 0.44570493698120117s
Interlinking | skos check for Open Transport Map @PSNC took 0.4428246021270752s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 5.299997091293335s
Currency | Creation date check for Open Transport Map @PSNC took 0.5143296718597412s
Currency | Modification date check for Open Transport Map @PSNC took 0.25592684745788574s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 160.26374101638794s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.21161365509033203s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.4568767547607422s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.3834102153778076s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 49.764426469802856s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.6505942344665527s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.5709714889526367s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.21290063858032227s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 87.7756872177124s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.42577075958252s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 33.52271389961243s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.4463016986846924s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 90.41194987297058s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.7698659896850586s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.614739179611206s
Security | Sign check for Open Transport Map @PSNC took 0.7985320091247559s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 16.792495012283325s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.731626033782959s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.02140641212463379s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for OTM took 2326.377426147461s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.839897155761719e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.24712610244750977s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.02097153663635254s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 2.8848648071289062e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 1.1920928955078125e-05s
INFO | --- Analysis for ounl-dspace-in-rdf took 2.8422513008117676s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 8.487701416015625e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.25567150115966797s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 1.2636184692382812e-05s
INFO | --- Analysis for ox-ac-uk-catalogue took 2.8407320976257324s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.1484832763671875e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.27514171600341797s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.02027106285095215s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.7418136596679688e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 1.1682510375976562e-05s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 2.876319169998169s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 4.315376281738281e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.26640772819519043s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 3.0040740966796875e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 1.2159347534179688e-05s
INFO | --- Analysis for ox-ac-uk-openmeters took 3.357516288757324s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 4.0531158447265625e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.261796236038208s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 2.86102294921875e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 1.2636184692382812e-05s
INFO | --- Analysis for ox-ac-uk-timeseries took 2.9334876537323s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 8.726119995117188e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.2548668384552002s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.02143716812133789s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 1.2159347534179688e-05s
INFO | --- Analysis for ox-ac-uk-vacancies took 2.8947594165802s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 0.00020647048950195312s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.2798278331756592s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 2.86102294921875e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 1.1920928955078125e-05s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 3.0497922897338867s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 0.00010538101196289062s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.2604100704193115s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 2.574920654296875e-05s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 2.9325485229492188e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 1.1444091796875e-05s
INFO | --- Analysis for oxpoints took 2.8278110027313232s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 4.308517932891846s
Availability | VoID file availability check for Pali English Lexicon took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.26143813133239746s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.021574020385742188s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 2.9087066650390625e-05s
Believability | Calculation of trust value for Pali English Lexicon took 1.1682510375976562e-05s
INFO | --- Analysis for pali-english-lexicon took 17.560733795166016s
Availability | SPARQL endpoint availability check for PanLex took 1.7420415878295898s
Availability | VoID file availability check for PanLex took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for PanLex took 0.27332329750061035s
Reputation | Calculation of the PageRank for PanLex took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for PanLex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.128715515136719e-05s
Believability | Calculation of trust value for PanLex took 1.239776611328125e-05s
INFO | --- Analysis for panlex took 4.1582887172698975s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.291534423828125e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.2581186294555664s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.02157425880432129s
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.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.719329833984375e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.239776611328125e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 4.667590141296387s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.07045626640319824s
Availability | VoID file availability check for patents.data.gov.uk took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.27176380157470703s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.839897155761719e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 9.298324584960938e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.5461843013763428s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 9.107589721679688e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.2858574390411377s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.022596359252929688s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.647804260253906e-05s
Believability | Calculation of trust value for PDEV-Lemon took 1.2874603271484375e-05s
INFO | --- Analysis for pdev-lemon took 3.532196044921875s
Availability | SPARQL endpoint availability check for pdevlemon took 0.00010776519775390625s
Availability | VoID file availability check for pdevlemon took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.25289463996887207s
Reputation | Calculation of the PageRank for pdevlemon took 0.020745277404785156s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 2.956390380859375e-05s
Believability | Calculation of trust value for pdevlemon took 1.1920928955078125e-05s
INFO | --- Analysis for pdevlemon took 3.094458818435669s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 0.00011134147644042969s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.2500801086425781s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.02077507972717285s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.726119995117188e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 1.1920928955078125e-05s
INFO | --- Analysis for periodo took 19.760825872421265s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.315376281738281e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.2543923854827881s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020754098892211914s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00038123130798339844s
Believability | Calculation of trust value for Personal_Homepages took 1.2636184692382812e-05s
INFO | --- Analysis for personal-homepages took 2.297682762145996s
Availability | SPARQL endpoint availability check for Ontology of University People took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology of University People took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.2570173740386963s
Reputation | Calculation of the PageRank for Ontology of University People took 0.02108287811279297s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 3.170967102050781e-05s
Believability | Calculation of trust value for Ontology of University People took 1.049041748046875e-05s
INFO | --- Analysis for PersonOnto took 2.5331594944000244s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 5.229051351547241s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2441565990447998s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02106189727783203s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.4066696166992188e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1205673217773438e-05s
INFO | --- Analysis for PFKHS took 9.270445585250854s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 3.3607499599456787s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2546987533569336s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020794153213500977s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.6927719116210938e-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.2636184692382812e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.2636184692382812e-05s
INFO | --- Analysis for PFRPPH took 7.49808144569397s
Availability | SPARQL endpoint availability check for PGxLOD took 0.4095282554626465s
Availability | VoID file availability check for PGxLOD took 0.0006375312805175781s
Extra | Recovery of all triples for PGxLOD took 1.864912986755371s
Performance | Total latancy measurement for PGxLOD took 0.7903871536254883s
Amount of data | Number of triples check for PGxLOD took 1.3286104202270508s
Interoperability | New terms check for PGxLOD took 1.9702117443084717s
Versatility | Languages check for PGxLOD took 60.24312210083008s
Interpretability | Number of blank nodes check for PGxLOD took 2.5316343307495117s
Interpretability | RDF structures check for PGxLOD took 0.5533657073974609s
Versatility | Serialization formats check for PGxLOD took 0.3211197853088379s
Availability | RDF dump link check for PGxLOD took 17.063394784927368s
License | MR license check for PGxLOD took 0.3879392147064209s
License | HR license check for PGxLOD took 60.24630689620972s
Amount of data | Number of property check for PGxLOD took 0.18648815155029297s
Understandability | Number of label check for PGxLOD took 2.384965181350708s
Understandability | URI regex check for PGxLOD took 0.42570018768310547s
Understandability | Vocabs check for PGxLOD took 0.35835886001586914s
Verifiability | Authors check for PGxLOD took 0.15735721588134766s
Verifiability | Publishers check for PGxLOD took 0.32248377799987793s
Performance | Throughput check for PGxLOD took 10.999493598937988s
Amount of data | Check the number of entities for PGxLOD took 0.12021255493164062s
Verifiability | Contribs. check for PGxLOD took 0.18020200729370117s
Interlinking | sameAs chians check for PGxLOD took 0.3341515064239502s
Interlinking | skos check for PGxLOD took 0.7704424858093262s
Interlinking | skos check for PGxLOD took 0.1975855827331543s
Timeliness | dataset update frequency check for PGxLOD took 0.39432239532470703s
Currency | Creation date check for PGxLOD took 0.5685734748840332s
Currency | Modification date check for PGxLOD took 0.33339881896972656s
Rep.Conc. | URIs length for PGxLOD took 6.717567443847656s
Interoperability | New vocabularies check for PGxLOD took 23.401618719100952s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.16971659660339355s
Accuracy | Check Functional Property for PGxLOD took 0.18425965309143066s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.1830301284790039s
Accuracy | Check Empty annotation labels for PGxLOD took 0.7396435737609863s
Accuracy | Check White space in annotation for PGxLOD took 0.03642868995666504s
Accuracy | Check Datatype consistency for PGxLOD took 0.02763986587524414s
Consistency | Disjoint class check for PGxLOD took 0.3045995235443115s
Consistency | Check Misplaced properties for PGxLOD took 6.698307037353516s
Consistency | Misplaced classes for PGxLOD took 0.31232523918151855s
Consistency | Check Ontology hijacking for PGxLOD took 1.9386982917785645s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.284221887588501s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 7.1778404712677s
Conciseness | Check Extensional conciseness for PGxLOD took 0.03209090232849121s
Conciseness | Check Intensional conciseness for PGxLOD took 0.25655269622802734s
Security | Sign check for PGxLOD took 0.21880269050598145s
Availability | Check URIs Dereferenciability for PGxLOD took 2203.9420149326324s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.35413622856140137s
Reputation | Calculation of the PageRank for PGxLOD took 0.021460294723510742s
Interlinking | Calculation of Degree of Connection for PGxLOD took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 5.364418029785156e-05s
Interoperability | Check the re-using of existing vocabs for PGxLOD took 6.747673273086548s
Believability | Calculation of trust value for PGxLOD took 1.4543533325195312e-05s
INFO | --- Analysis for PGxLOD took 3514.0281450748444s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.3355762958526611s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.2333359718322754s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.020813465118408203s
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.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 4.00543212890625e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1205673217773438e-05s
INFO | --- Analysis for phoible took 4.860452175140381s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 4.2438507080078125e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.2648184299468994s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.021459341049194336s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.0994415283203125e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 1.1444091796875e-05s
INFO | --- Analysis for PISM took 15.192250490188599s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.220008850097656e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.2687702178955078s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020405054092407227s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.821487426757812e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 7.152557373046875e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.452833414077759s
Availability | SPARQL endpoint availability check for digitized plant specimen took 2.115018606185913s
Availability | VoID file availability check for digitized plant specimen took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.24393057823181152s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 6.961822509765625e-05s
Believability | Calculation of trust value for digitized plant specimen took 7.152557373046875e-06s
INFO | --- Analysis for plant-specimen took 4.396469831466675s
Availability | SPARQL endpoint availability check for Pleiades took 0.00015735626220703125s
Availability | VoID file availability check for Pleiades took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for Pleiades took 0.256148099899292s
Reputation | Calculation of the PageRank for Pleiades took 0.0213773250579834s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0008113384246826172s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.893013000488281e-05s
Believability | Calculation of trust value for Pleiades took 1.1920928955078125e-05s
INFO | --- Analysis for pleiades took 14.505198240280151s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 5.602836608886719e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0007126331329345703s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.24389314651489258s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020400047302246094s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 2.956390380859375e-05s
Believability | Calculation of trust value for podorozhnyk.com took 1.1682510375976562e-05s
INFO | --- Analysis for podorozhnyk took 3.4545834064483643s
Availability | SPARQL endpoint availability check for Poképédia took 8.916854858398438e-05s
Availability | VoID file availability check for Poképédia took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Poképédia took 0.30010056495666504s
Reputation | Calculation of the PageRank for Poképédia took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.104873657226562e-05s
Believability | Calculation of trust value for Poképédia took 1.1205673217773438e-05s
INFO | --- Analysis for pokepedia-fr took 2.731426239013672s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.4345855712890625e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.26049160957336426s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.020480632781982422s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.557868957519531e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.2159347534179688e-05s
INFO | --- Analysis for polymath-virtual-library took 5.922094106674194s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.3524954319000244s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0006380081176757812s
Extra | Recovery of all triples for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 13.769281148910522s
Performance | Total latancy measurement for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.6347901821136475s
Amount of data | Number of triples check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.47584056854248047s
Interoperability | New terms check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.7335796356201172s
Versatility | Languages check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.7644450664520264s
Interpretability | Number of blank nodes check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.426241397857666s
Interpretability | RDF structures check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.14501738548278809s
Versatility | Serialization formats check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13209056854248047s
Availability | RDF dump link check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11788606643676758s
License | MR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13875222206115723s
License | HR license check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.603966474533081s
Amount of data | Number of property check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12979340553283691s
Understandability | Number of label check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.18450069427490234s
Understandability | URI regex check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.25661802291870117s
Understandability | Vocabs check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12384748458862305s
Verifiability | Authors check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12215876579284668s
Verifiability | Publishers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.11989831924438477s
Performance | Throughput check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 10.661773681640625s
Amount of data | Check the number of entities for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 8.249282836914062e-05s
Verifiability | Contribs. check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12781667709350586s
Interlinking | sameAs chians check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12059998512268066s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1264476776123047s
Interlinking | skos check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12798666954040527s
Timeliness | dataset update frequency check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13447833061218262s
Currency | Creation date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2723104953765869s
Currency | Modification date check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.25736236572265625s
Rep.Conc. | URIs length for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.733843803405762s
Interoperability | New vocabularies check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1376185417175293s
Accuracy | Check Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.12919068336486816s
Accuracy | Check Inverse Functional Property for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1224210262298584s
Accuracy | Check Empty annotation labels for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.1305055618286133s
Accuracy | Check White space in annotation for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.19458699226379395s
Accuracy | Check Datatype consistency for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.7685914039611816s
Consistency | Disjoint class check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.13173747062683105s
Consistency | Check Misplaced properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.9005272388458252s
Consistency | Check Ontology hijacking for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 3.326342821121216s
Consistency | Check Invalid usage of undefined classes for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.3341248035430908s
Consistency | Check Invalid usage of undefined properties for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.2406411170959473s
Conciseness | Check Extensional conciseness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.4376373291015625s
Security | Sign check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.1215677261352539s
Availability | Check URIs Dereferenciability for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 4840.2186868190765s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.7477118968963623s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.021740198135375977s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.8133392333984375e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6927719116210938e-05s
Interoperability | Check the re-using of existing vocabs for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.9073486328125e-06s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 7.867813110351562e-06s
INFO | --- Analysis for portuguese_prisons_releases took 4916.306716680527s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.172325134277344e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.2744450569152832s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 3.0517578125e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.843259572982788s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.076957702636719e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.2578883171081543s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.020230531692504883s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 2.8848648071289062e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 2.8219645023345947s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 5.173683166503906e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.254321813583374s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 2.86102294921875e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 6.198883056640625e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.9116249084472656s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 4.1484832763671875e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.2408909797668457s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 2.9087066650390625e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.776083469390869s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 5.841255187988281e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.2596006393432617s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 2.8371810913085938e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 6.67572021484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 2.791511297225952s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 4.124641418457031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.26485586166381836s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.023138046264648438s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0010974407196044922s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 4.3392181396484375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 1.239776611328125e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.8739559650421143s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 8.726119995117188e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.2483973503112793s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.020858287811279297s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.832148313522339s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.863739013671875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.25988030433654785s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 3.123283386230469e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 1.0967254638671875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.8037145137786865s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.124641418457031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.2572903633117676s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.020443439483642578s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 2.9087066650390625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 2.918283224105835s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.2403879165649414s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 2.8133392333984375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.809523344039917s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.2693166732788086s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 2.8848648071289062e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 6.67572021484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.8155734539031982s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 5.841255187988281e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.24841737747192383s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.772953748703003s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 8.678436279296875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.25762033462524414s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.020340442657470703s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 1.1444091796875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.827864170074463s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.254138708114624s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.02050304412841797s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 3.0040740966796875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 1.2874603271484375e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.806755542755127s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 8.702278137207031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.28923630714416504s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.02106475830078125s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 2.9087066650390625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 1.1920928955078125e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.852461338043213s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 8.797645568847656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2615644931793213s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 1.1205673217773438e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.8502283096313477s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 5.1975250244140625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.28871941566467285s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 3.0517578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 1.239776611328125e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.879046678543091s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.2361915111541748s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 3.0040740966796875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 1.1920928955078125e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.8058910369873047s
Availability | SPARQL endpoint availability check for prefix.cc took 0.0001552104949951172s
Availability | VoID file availability check for prefix.cc took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.2668437957763672s
Reputation | Calculation of the PageRank for prefix.cc took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.695487976074219e-05s
Believability | Calculation of trust value for prefix.cc took 1.0728836059570312e-05s
INFO | --- Analysis for prefix-cc took 3.1881463527679443s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 1.5775976181030273s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0007426738739013672s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.2441709041595459s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.020798444747924805s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.887580871582031e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.0967254638671875e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 7.434243202209473s
Availability | SPARQL endpoint availability check for PreLex took 5.956921815872192s
Availability | VoID file availability check for PreLex took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for PreLex took 0.2631974220275879s
Reputation | Calculation of the PageRank for PreLex took 0.020937442779541016s
Interlinking | Calculation of Degree of Connection for PreLex took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for PreLex took 6.961822509765625e-05s
Believability | Calculation of trust value for PreLex took 1.0967254638671875e-05s
INFO | --- Analysis for prelex took 19.667755842208862s
Availability | SPARQL endpoint availability check for Prelinger Archives took 64.88913154602051s
Availability | VoID file availability check for Prelinger Archives took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.25403451919555664s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.021799802780151367s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.838539123535156e-05s
Believability | Calculation of trust value for Prelinger Archives took 1.1444091796875e-05s
INFO | --- Analysis for prelinger_archives took 176.51584935188293s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 11.055888414382935s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0007641315460205078s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.2641761302947998s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.021756887435913086s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 7.700920104980469e-05s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 1.430511474609375e-05s
INFO | --- Analysis for premon took 25.91567850112915s
Availability | SPARQL endpoint availability check for Previsible took 4.458427429199219e-05s
Availability | VoID file availability check for Previsible took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Previsible took 0.25382280349731445s
Reputation | Calculation of the PageRank for Previsible took 0.02111220359802246s
Interlinking | Calculation of Degree of Connection for Previsible took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.1444091796875e-05s
Believability | Calculation of trust value for Previsible took 1.239776611328125e-05s
INFO | --- Analysis for Previsible took 2.266669273376465s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 5.53131103515625e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.3752603530883789s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020857810974121094s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.698204040527344e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 1.3113021850585938e-05s
INFO | --- Analysis for princeton-library-findingaids took 4.098456382751465s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.7671868801116943s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0007441043853759766s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.2505300045013428s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.022004365921020508s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.719329833984375e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for PrinParLat took 4.43340277671814s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.5411920547485352s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.258589506149292s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.939338684082031e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.1444091796875e-05s
INFO | --- Analysis for printed-book-auction-catalogues took 3.2382380962371826s
Availability | SPARQL endpoint availability check for Prior Panel took 4.1484832763671875e-05s
Availability | VoID file availability check for Prior Panel took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.25162577629089355s
Reputation | Calculation of the PageRank for Prior Panel took 0.020690202713012695s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.266334533691406e-05s
Believability | Calculation of trust value for Prior Panel took 1.1682510375976562e-05s
INFO | --- Analysis for Prior_Panel took 2.3034069538116455s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 6.580352783203125e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.26184701919555664s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.020992279052734375s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 3.147125244140625e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 1.3113021850585938e-05s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 2.8349289894104004s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 0.00019860267639160156s
Availability | VoID file availability check for Procomún SPARQL took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.24564409255981445s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.02103257179260254s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.170967102050781e-05s
Believability | Calculation of trust value for Procomún SPARQL took 7.3909759521484375e-06s
INFO | --- Analysis for procomun-sparql took 2.8877012729644775s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.172325134277344e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.264298677444458s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.02077627182006836s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 3.147125244140625e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 1.1682510375976562e-05s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.849180221557617s
Availability | SPARQL endpoint availability check for ProductDB took 0.6754727363586426s
Availability | VoID file availability check for ProductDB took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for ProductDB took 0.2548859119415283s
Reputation | Calculation of the PageRank for ProductDB took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.367134094238281e-05s
Believability | Calculation of trust value for ProductDB took 7.152557373046875e-06s
INFO | --- Analysis for productdb took 3.5710091590881348s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Product Types Ontology took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.25167298316955566s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.02086925506591797s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.557868957519531e-05s
Believability | Calculation of trust value for Product Types Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for productontology took 3.3370673656463623s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.410743713378906e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0008187294006347656s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.25628089904785156s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.02072739601135254s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 9.942054748535156e-05s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 11.00611925125122s
Availability | SPARQL endpoint availability check for provenanceweb took 0.06470990180969238s
Availability | VoID file availability check for provenanceweb took 0.0003216266632080078s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.2587623596191406s
Reputation | Calculation of the PageRank for provenanceweb took 0.021461963653564453s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 8.082389831542969e-05s
Believability | Calculation of trust value for provenanceweb took 7.3909759521484375e-06s
INFO | --- Analysis for provenanceweb took 58.39611625671387s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.220008850097656e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0004169940948486328s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.25510215759277344s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 9.822845458984375e-05s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.1444091796875e-05s
INFO | --- Analysis for proyectoapadrina took 8.99690294265747s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 26.99071478843689s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008282661437988281s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.2572972774505615s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.020903348922729492s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0008630752563476562s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 4.3392181396484375e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 9.059906005859375e-06s
INFO | --- Analysis for pscs-catalogue took 126.64062142372131s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.315376281738281e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.00041937828063964844s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.2610173225402832s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.021410226821899414s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.343292236328125e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 9.059906005859375e-06s
INFO | --- Analysis for psh-subject-headings took 2.878967761993408s
Availability | SPARQL endpoint availability check for Depression took 0.6387944221496582s
Availability | VoID file availability check for Depression took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Depression took 0.24814510345458984s
Reputation | Calculation of the PageRank for Depression took 0.02219843864440918s
Interlinking | Calculation of Degree of Connection for Depression took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Depression took 3.552436828613281e-05s
Believability | Calculation of trust value for Depression took 7.62939453125e-06s
INFO | --- Analysis for Psychology took 2.926703691482544s
Availability | SPARQL endpoint availability check for PubChem RDF took 8.630752563476562e-05s
Availability | VoID file availability check for PubChem RDF took 0.0011937618255615234s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.2606668472290039s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020831584930419922s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0008313655853271484s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.649162292480469e-05s
Believability | Calculation of trust value for PubChem RDF took 1.1444091796875e-05s
INFO | --- Analysis for PubChem_RDF took 5.254980802536011s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 4.2438507080078125e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.2573072910308838s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.02070140838623047s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 3.409385681152344e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 1.1920928955078125e-05s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 2.8477773666381836s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 0.7215845584869385s
Availability | VoID file availability check for Public Spending in Greece took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.27007126808166504s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.021149635314941406s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007097721099853516s
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 7.3909759521484375e-06s
INFO | --- Analysis for public-spending-in-greece took 8.442317485809326s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 4.076957702636719e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.26776671409606934s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.020495891571044922s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 3.075599670410156e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 7.152557373046875e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 2.843050479888916s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 1.0991840362548828s
Availability | VoID file availability check for Publications Office Authority tables took 0.00064849853515625s
Extra | Recovery of all triples for Publications Office Authority tables took 193.52987504005432s
Performance | Total latancy measurement for Publications Office Authority tables took 0.5922145843505859s
Amount of data | Number of triples check for Publications Office Authority tables took 64.37957048416138s
Interoperability | New terms check for Publications Office Authority tables took 75.87161803245544s
Versatility | Languages check for Publications Office Authority tables took 300.115788936615s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 16.350979804992676s
Security | Check HTTPS for Publications Office Authority tables took 0.317537784576416s
Interpretability | RDF structures check for Publications Office Authority tables took 0.33265137672424316s
Versatility | Serialization formats check for Publications Office Authority tables took 2.9880216121673584s
Availability | RDF dump link check for Publications Office Authority tables took 0.35891270637512207s
License | MR license check for Publications Office Authority tables took 0.3733670711517334s
License | HR license check for Publications Office Authority tables took 300.0954599380493s
Amount of data | Number of property check for Publications Office Authority tables took 0.17826557159423828s
Understandability | Number of label check for Publications Office Authority tables took 1.9948899745941162s
Understandability | URI regex check for Publications Office Authority tables took 0.3918170928955078s
Understandability | Vocabs check for Publications Office Authority tables took 0.14031076431274414s
Verifiability | Authors check for Publications Office Authority tables took 0.20019316673278809s
Verifiability | Publishers check for Publications Office Authority tables took 0.18837761878967285s
Performance | Throughput check for Publications Office Authority tables took 10.703582286834717s
Amount of data | Check the number of entities for Publications Office Authority tables took 0.00011539459228515625s
Verifiability | Contribs. check for Publications Office Authority tables took 0.17067909240722656s
Interlinking | sameAs chians check for Publications Office Authority tables took 7.788448810577393s
Interlinking | skos check for Publications Office Authority tables took 0.16265654563903809s
Interlinking | skos check for Publications Office Authority tables took 0.1625819206237793s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.2824387550354004s
Currency | Creation date check for Publications Office Authority tables took 0.2829716205596924s
Currency | Modification date check for Publications Office Authority tables took 0.13463044166564941s
Rep.Conc. | URIs length for Publications Office Authority tables took 433.1229636669159s
Interoperability | New vocabularies check for Publications Office Authority tables took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.14318633079528809s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.1954197883605957s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.1788170337677002s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 39.74812602996826s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.2049713134765625s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.6425416469573975s
Consistency | Disjoint class check for Publications Office Authority tables took 0.18874192237854004s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.3437223434448s
Consistency | Misplaced classes for Publications Office Authority tables took 8.406718492507935s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 91.44731259346008s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.76957368850708s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.5981683731079s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 3.0311856269836426s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.4381368160247803s
Security | Sign check for Publications Office Authority tables took 0.11435818672180176s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 16.401344776153564s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 1.5555980205535889s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.021718263626098633s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.2438507080078125e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.9073486328125e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 8.106231689453125e-06s
INFO | --- Analysis for publications_office_authority_tables took 14850.216262340546s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 4.363059997558594e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.6784915924072266s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.02098250389099121s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.457069396972656e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 1.3113021850585938e-05s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 4.509575843811035s
Availability | SPARQL endpoint availability check for QBOAirbase took 4.291534423828125e-05s
Availability | VoID file availability check for QBOAirbase took 0.0008714199066162109s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.2529902458190918s
Reputation | Calculation of the PageRank for QBOAirbase took 0.02083134651184082s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 8.678436279296875e-05s
Believability | Calculation of trust value for QBOAirbase took 1.3113021850585938e-05s
INFO | --- Analysis for qboairbase took 137.13206720352173s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 4.172325134277344e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.24695873260498047s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 3.170967102050781e-05s
Believability | Calculation of trust value for qualitywebdata.org took 1.2874603271484375e-05s
INFO | --- Analysis for qualitywebdata-org took 4.113046169281006s
Availability | SPARQL endpoint availability check for Qualité de l'air took 8.654594421386719e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.2532474994659424s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.02199268341064453s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 3.1948089599609375e-05s
Believability | Calculation of trust value for Qualité de l'air took 1.2636184692382812e-05s
INFO | --- Analysis for Qualité_de_l'air took 2.7761313915252686s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 8.58306884765625e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0032091140747070312s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.2682943344116211s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.02098989486694336s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.6716461181640625e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 1.2874603271484375e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 49.83256125450134s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.6627063751220703s
Availability | VoID file availability check for Querolus in LiLa took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.26993346214294434s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.933906555175781e-05s
Believability | Calculation of trust value for Querolus in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for Querolus took 4.064525604248047s
Availability | SPARQL endpoint availability check for Quotations Book took 4.1484832763671875e-05s
Availability | VoID file availability check for Quotations Book took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.2533433437347412s
Reputation | Calculation of the PageRank for Quotations Book took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 3.218650817871094e-05s
Believability | Calculation of trust value for Quotations Book took 1.1682510375976562e-05s
INFO | --- Analysis for quotations_book took 3.242920160293579s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.23926448822021484s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.314018249511719e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.239776611328125e-05s
INFO | --- Analysis for r4r took 2.822585105895996s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.4798400402069092s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0004475116729736328s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 28.64162564277649s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.6574952602386475s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.5167899131774902s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.0469439029693604s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.919770956039429s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.74965238571167s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14919161796569824s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14294004440307617s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14132308959960938s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14210271835327148s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1539168357849121s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12967586517333984s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1495506763458252s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2810211181640625s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12977242469787598s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14161086082458496s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15250325202941895s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.784624814987183s
Amount of data | Check the number of entities for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 8.797645568847656e-05s
Verifiability | Contribs. check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1420130729675293s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14140105247497559s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.142988920211792s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1494157314300537s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14213275909423828s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.284374475479126s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.27194976806640625s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 20.552380084991455s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15095853805541992s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12915277481079102s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15137290954589844s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1538987159729004s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.790855407714844e-05s
Accuracy | Check Datatype consistency for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.112231969833374s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14188122749328613s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.765073776245117s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.043053388595581s
Consistency | Check Invalid usage of undefined classes for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.4425897598266602s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.886557340621948s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.818406581878662s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14007115364074707s
Availability | Check URIs Dereferenciability for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 14.669369459152222s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.34842514991760254s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.02108931541442871s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.1457672119140625e-06s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.1920928955078125e-05s
INFO | --- Analysis for racai-legalnero took 161.72471594810486s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 5.030632019042969e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.24234795570373535s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.02065873146057129s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 3.147125244140625e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 1.049041748046875e-05s
INFO | --- Analysis for racai-llod-corola-we took 3.068046808242798s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.14305853843688965s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0004265308380126953s
Extra | Recovery of all triples for PARSEME-Ro corpus took 30.990209579467773s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.6698970794677734s
Amount of data | Number of triples check for PARSEME-Ro corpus took 7.091423749923706s
Interoperability | New terms check for PARSEME-Ro corpus took 2.2179675102233887s
Versatility | Languages check for PARSEME-Ro corpus took 18.71809196472168s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.657720327377319s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.1433415412902832s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.14142918586730957s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.14059042930603027s
License | MR license check for PARSEME-Ro corpus took 0.15263819694519043s
License | HR license check for PARSEME-Ro corpus took 10.152122974395752s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.1414196491241455s
Understandability | Number of label check for PARSEME-Ro corpus took 0.1886444091796875s
Understandability | URI regex check for PARSEME-Ro corpus took 0.2922961711883545s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.14056897163391113s
Verifiability | Authors check for PARSEME-Ro corpus took 0.14150500297546387s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.14217448234558105s
Performance | Throughput check for PARSEME-Ro corpus took 10.919634580612183s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 7.367134094238281e-05s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.15215539932250977s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 0.14107370376586914s
Interlinking | skos check for PARSEME-Ro corpus took 0.1540670394897461s
Interlinking | skos check for PARSEME-Ro corpus took 0.15332269668579102s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 0.15334606170654297s
Currency | Creation date check for PARSEME-Ro corpus took 0.2830996513366699s
Currency | Modification date check for PARSEME-Ro corpus took 0.29404735565185547s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 79.35225200653076s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.13161754608154297s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.1519794464111328s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.15190458297729492s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 1.9825763702392578s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.23215389251708984s
Accuracy | Check Datatype consistency for PARSEME-Ro corpus took 3.958665370941162s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.1558065414428711s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 11.127542734146118s
Consistency | Check Ontology hijacking for PARSEME-Ro corpus took 28.311665296554565s
Consistency | Check Invalid usage of undefined classes for PARSEME-Ro corpus took 1.6640734672546387s
Consistency | Check Invalid usage of undefined properties for PARSEME-Ro corpus took 13.318027257919312s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 2.8232767581939697s
Security | Sign check for PARSEME-Ro corpus took 0.13882660865783691s
Availability | Check URIs Dereferenciability for PARSEME-Ro corpus took 7.2882068157196045s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.3762955665588379s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020157575607299805s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0006785392761230469s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.695487976074219e-05s
Interoperability | Check the re-using of existing vocabs for PARSEME-Ro corpus took 1.6689300537109375e-06s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.3113021850585938e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 279.3934829235077s
Availability | SPARQL endpoint availability check for RoLEX took 0.1277306079864502s
Availability | VoID file availability check for RoLEX took 0.0004696846008300781s
Extra | Recovery of all triples for RoLEX took 33.99708390235901s
Performance | Total latancy measurement for RoLEX took 0.7080905437469482s
Amount of data | Number of triples check for RoLEX took 1.6501312255859375s
Interoperability | New terms check for RoLEX took 1.7704553604125977s
Versatility | Languages check for RoLEX took 4.429086923599243s
Interpretability | Number of blank nodes check for RoLEX took 1.074970006942749s
Interpretability | RDF structures check for RoLEX took 0.15294647216796875s
Versatility | Serialization formats check for RoLEX took 0.14209794998168945s
Availability | RDF dump link check for RoLEX took 0.1416459083557129s
License | MR license check for RoLEX took 0.14351463317871094s
License | HR license check for RoLEX took 0.1429591178894043s
Amount of data | Number of property check for RoLEX took 0.1298835277557373s
Understandability | Number of label check for RoLEX took 0.13208889961242676s
Understandability | URI regex check for RoLEX took 0.29321885108947754s
Understandability | Vocabs check for RoLEX took 0.14233946800231934s
Verifiability | Authors check for RoLEX took 0.1304934024810791s
Verifiability | Publishers check for RoLEX took 0.14165830612182617s
Performance | Throughput check for RoLEX took 11.212558031082153s
Amount of data | Check the number of entities for RoLEX took 0.00010848045349121094s
Verifiability | Contribs. check for RoLEX took 0.1409909725189209s
Interlinking | sameAs chians check for RoLEX took 0.14045071601867676s
Interlinking | skos check for RoLEX took 0.15089678764343262s
Interlinking | skos check for RoLEX took 0.15199828147888184s
Timeliness | dataset update frequency check for RoLEX took 0.14128851890563965s
Currency | Creation date check for RoLEX took 0.29300618171691895s
Currency | Modification date check for RoLEX took 0.29239726066589355s
Rep.Conc. | URIs length for RoLEX took 53.422529458999634s
Interoperability | New vocabularies check for RoLEX took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for RoLEX took 0.15158295631408691s
Accuracy | Check Functional Property for RoLEX took 0.138136625289917s
Accuracy | Check Inverse Functional Property for RoLEX took 0.12921524047851562s
Accuracy | Check Datatype consistency for RoLEX took 4.180025339126587s
Consistency | Disjoint class check for RoLEX took 0.13245749473571777s
Consistency | Check Misplaced properties for RoLEX took 2.563624382019043s
Consistency | Check Ontology hijacking for RoLEX took 8.565129041671753s
Consistency | Check Invalid usage of undefined classes for RoLEX took 1.9663493633270264s
Consistency | Check Invalid usage of undefined properties for RoLEX took 5.003512620925903s
Conciseness | Check Extensional conciseness for RoLEX took 3.0909650325775146s
Security | Sign check for RoLEX took 0.12746596336364746s
Availability | Check URIs Dereferenciability for RoLEX took 7.207029581069946s
Completeness | Calculation of interlinking completeness for RoLEX took 0.7383968830108643s
Reputation | Calculation of the PageRank for RoLEX took 0.021537065505981445s
Interlinking | Calculation of Degree of Connection for RoLEX took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.814697265625e-05s
Interoperability | Check the re-using of existing vocabs for RoLEX took 1.6689300537109375e-06s
Believability | Calculation of trust value for RoLEX took 1.239776611328125e-05s
INFO | --- Analysis for racai-llod-rolex took 174.47575449943542s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 8.606910705566406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0006740093231201172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.24945473670959473s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.02162909507751465s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.147125244140625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.3113021850585938e-05s
INFO | --- Analysis for racai-llod-romanian-treebank took 3.518517017364502s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 0.0001227855682373047s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.6831114292144775s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.022046804428100586s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 3.147125244140625e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 1.1920928955078125e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 3.833559513092041s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.363059997558594e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0006461143493652344s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.25447654724121094s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.021435022354125977s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.123283386230469e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 1.1682510375976562e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.519923210144043s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 4.4345855712890625e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.24911785125732422s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.0207674503326416s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 3.170967102050781e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.1682510375976562e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.595496654510498s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.14232373237609863s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0006859302520751953s
Extra | Recovery of all triples for ROBIN Technical Acquisition Speech Corpus took 9.601398944854736s
Performance | Total latancy measurement for ROBIN Technical Acquisition Speech Corpus took 0.7175583839416504s
Amount of data | Number of triples check for ROBIN Technical Acquisition Speech Corpus took 0.33262014389038086s
Interoperability | New terms check for ROBIN Technical Acquisition Speech Corpus took 1.511075735092163s
Versatility | Languages check for ROBIN Technical Acquisition Speech Corpus took 0.602806806564331s
Interpretability | Number of blank nodes check for ROBIN Technical Acquisition Speech Corpus took 0.2763388156890869s
Interpretability | RDF structures check for ROBIN Technical Acquisition Speech Corpus took 0.14284157752990723s
Versatility | Serialization formats check for ROBIN Technical Acquisition Speech Corpus took 0.15337729454040527s
Availability | RDF dump link check for ROBIN Technical Acquisition Speech Corpus took 0.14047741889953613s
License | MR license check for ROBIN Technical Acquisition Speech Corpus took 0.14160394668579102s
License | HR license check for ROBIN Technical Acquisition Speech Corpus took 0.13731908798217773s
Amount of data | Number of property check for ROBIN Technical Acquisition Speech Corpus took 0.14048027992248535s
Understandability | Number of label check for ROBIN Technical Acquisition Speech Corpus took 0.146712064743042s
Understandability | URI regex check for ROBIN Technical Acquisition Speech Corpus took 0.292743444442749s
Understandability | Vocabs check for ROBIN Technical Acquisition Speech Corpus took 0.15292811393737793s
Verifiability | Authors check for ROBIN Technical Acquisition Speech Corpus took 0.13150334358215332s
Verifiability | Publishers check for ROBIN Technical Acquisition Speech Corpus took 0.1531689167022705s
Performance | Throughput check for ROBIN Technical Acquisition Speech Corpus took 11.09105920791626s
Amount of data | Check the number of entities for ROBIN Technical Acquisition Speech Corpus took 8.249282836914062e-05s
Verifiability | Contribs. check for ROBIN Technical Acquisition Speech Corpus took 0.1412062644958496s
Interlinking | sameAs chians check for ROBIN Technical Acquisition Speech Corpus took 0.13118648529052734s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.13004732131958008s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.13035273551940918s
Timeliness | dataset update frequency check for ROBIN Technical Acquisition Speech Corpus took 0.1416773796081543s
Currency | Creation date check for ROBIN Technical Acquisition Speech Corpus took 0.27286791801452637s
Currency | Modification date check for ROBIN Technical Acquisition Speech Corpus took 0.28403139114379883s
Rep.Conc. | URIs length for ROBIN Technical Acquisition Speech Corpus took 2.6775646209716797s
Interoperability | New vocabularies check for ROBIN Technical Acquisition Speech Corpus took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for ROBIN Technical Acquisition Speech Corpus took 0.15134763717651367s
Accuracy | Check Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.14974188804626465s
Accuracy | Check Inverse Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.13901233673095703s
Accuracy | Check Empty annotation labels for ROBIN Technical Acquisition Speech Corpus took 0.3887605667114258s
Accuracy | Check White space in annotation for ROBIN Technical Acquisition Speech Corpus took 0.009652376174926758s
Accuracy | Check Datatype consistency for ROBIN Technical Acquisition Speech Corpus took 1.2023534774780273s
Consistency | Disjoint class check for ROBIN Technical Acquisition Speech Corpus took 0.1276078224182129s
Consistency | Check Misplaced properties for ROBIN Technical Acquisition Speech Corpus took 0.5954651832580566s
Consistency | Check Ontology hijacking for ROBIN Technical Acquisition Speech Corpus took 2.0547187328338623s
Consistency | Check Invalid usage of undefined classes for ROBIN Technical Acquisition Speech Corpus took 1.322068452835083s
Consistency | Check Invalid usage of undefined properties for ROBIN Technical Acquisition Speech Corpus took 1.6910185813903809s
Conciseness | Check Extensional conciseness for ROBIN Technical Acquisition Speech Corpus took 0.825345516204834s
Security | Sign check for ROBIN Technical Acquisition Speech Corpus took 0.15032744407653809s
Availability | Check URIs Dereferenciability for ROBIN Technical Acquisition Speech Corpus took 3631.0184574127197s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 1.258089303970337s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.022189855575561523s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 3.528594970703125e-05s
Interoperability | Check the re-using of existing vocabs for ROBIN Technical Acquisition Speech Corpus took 1.6689300537109375e-06s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 1.1920928955078125e-05s
INFO | --- Analysis for racai-llod-rtasc took 3692.3671889305115s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.1412644386291504s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0005328655242919922s
Extra | Recovery of all triples for SiMoNERo - the Romanian medical treebank took 34.49341082572937s
Performance | Total latancy measurement for SiMoNERo - the Romanian medical treebank took 0.7141232490539551s
Amount of data | Number of triples check for SiMoNERo - the Romanian medical treebank took 1.1366119384765625s
Interoperability | New terms check for SiMoNERo - the Romanian medical treebank took 1.5579874515533447s
Versatility | Languages check for SiMoNERo - the Romanian medical treebank took 2.49919056892395s
Interpretability | Number of blank nodes check for SiMoNERo - the Romanian medical treebank took 0.8027195930480957s
Interpretability | RDF structures check for SiMoNERo - the Romanian medical treebank took 0.142683744430542s
Versatility | Serialization formats check for SiMoNERo - the Romanian medical treebank took 0.14356088638305664s
Availability | RDF dump link check for SiMoNERo - the Romanian medical treebank took 0.1408979892730713s
License | MR license check for SiMoNERo - the Romanian medical treebank took 0.14205479621887207s
License | HR license check for SiMoNERo - the Romanian medical treebank took 4.624139070510864s
Amount of data | Number of property check for SiMoNERo - the Romanian medical treebank took 0.15277910232543945s
Understandability | Number of label check for SiMoNERo - the Romanian medical treebank took 0.13672137260437012s
Understandability | URI regex check for SiMoNERo - the Romanian medical treebank took 0.2871575355529785s
Understandability | Vocabs check for SiMoNERo - the Romanian medical treebank took 0.14129066467285156s
Verifiability | Authors check for SiMoNERo - the Romanian medical treebank took 0.14315247535705566s
Verifiability | Publishers check for SiMoNERo - the Romanian medical treebank took 0.15309405326843262s
Performance | Throughput check for SiMoNERo - the Romanian medical treebank took 10.89881682395935s
Amount of data | Check the number of entities for SiMoNERo - the Romanian medical treebank took 6.890296936035156e-05s
Verifiability | Contribs. check for SiMoNERo - the Romanian medical treebank took 0.15352845191955566s
Interlinking | sameAs chians check for SiMoNERo - the Romanian medical treebank took 0.14165234565734863s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.14218378067016602s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.15260577201843262s
Timeliness | dataset update frequency check for SiMoNERo - the Romanian medical treebank took 0.1305396556854248s
Currency | Creation date check for SiMoNERo - the Romanian medical treebank took 0.2833518981933594s
Currency | Modification date check for SiMoNERo - the Romanian medical treebank took 0.27240967750549316s
Rep.Conc. | URIs length for SiMoNERo - the Romanian medical treebank took 9.44075632095337s
Interoperability | New vocabularies check for SiMoNERo - the Romanian medical treebank took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for SiMoNERo - the Romanian medical treebank took 0.1501302719116211s
Accuracy | Check Functional Property for SiMoNERo - the Romanian medical treebank took 0.14928507804870605s
Accuracy | Check Inverse Functional Property for SiMoNERo - the Romanian medical treebank took 0.13935565948486328s
Accuracy | Check Empty annotation labels for SiMoNERo - the Romanian medical treebank took 0.6711499691009521s
Accuracy | Check White space in annotation for SiMoNERo - the Romanian medical treebank took 0.019075393676757812s
Accuracy | Check Datatype consistency for SiMoNERo - the Romanian medical treebank took 4.049623727798462s
Consistency | Disjoint class check for SiMoNERo - the Romanian medical treebank took 0.16981005668640137s
Consistency | Check Misplaced properties for SiMoNERo - the Romanian medical treebank took 1.6979353427886963s
Consistency | Check Ontology hijacking for SiMoNERo - the Romanian medical treebank took 4.61467719078064s
Consistency | Check Invalid usage of undefined classes for SiMoNERo - the Romanian medical treebank took 1.3960661888122559s
Consistency | Check Invalid usage of undefined properties for SiMoNERo - the Romanian medical treebank took 2.7284958362579346s
Conciseness | Check Extensional conciseness for SiMoNERo - the Romanian medical treebank took 2.9147539138793945s
Security | Sign check for SiMoNERo - the Romanian medical treebank took 0.14982986450195312s
Availability | Check URIs Dereferenciability for SiMoNERo - the Romanian medical treebank took 1635.7056593894958s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.9552204608917236s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.0220797061920166s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 4.315376281738281e-05s
Interoperability | Check the re-using of existing vocabs for SiMoNERo - the Romanian medical treebank took 1.6689300537109375e-06s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 1.1682510375976562e-05s
INFO | --- Analysis for racai-llod-simonero took 1741.4563400745392s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.22356867790222168s
Availability | VoID file availability check for Rådata nå! took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.2665412425994873s
Reputation | Calculation of the PageRank for Rådata nå! took 0.0210874080657959s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.273124694824219e-05s
Believability | Calculation of trust value for Rådata nå! took 1.0728836059570312e-05s
INFO | --- Analysis for radatana took 5.2629241943359375s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 8.511543273925781e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.25452566146850586s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.022321224212646484s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.9577484130859375e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 1.1682510375976562e-05s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 17.52651834487915s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.076957702636719e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.2406775951385498s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 3.0279159545898438e-05s
Believability | Calculation of trust value for Raphael Research Resource took 1.1205673217773438e-05s
INFO | --- Analysis for raphaelresearchresource took 2.8104910850524902s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 13.49915885925293s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0007178783416748047s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.24961328506469727s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.0279159545898438e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.239776611328125e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 29.647599935531616s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 392.7249367237091s
Availability | VoID file availability check for Polish LGU financial statements took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.3109555244445801s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.021067380905151367s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 3.695487976074219e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 1.0967254638671875e-05s
INFO | --- Analysis for Rb_PL_LGU took 665.6271262168884s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 7.796287536621094e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.2633976936340332s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.020922422409057617s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 3.2901763916015625e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 1.33514404296875e-05s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 4.9747490882873535s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 8.559226989746094e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.2825491428375244s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.02207350730895996s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 3.5762786865234375e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 2.885335683822632s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 8.368492126464844e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.0004050731658935547s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.24384689331054688s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.020779848098754883s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 3.695487976074219e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 2.7811386585235596s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 8.559226989746094e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.27767229080200195s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.02088189125061035s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 3.6716461181640625e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 1.2874603271484375e-05s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 2.878202438354492s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 5.817413330078125e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.26587605476379395s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.020693302154541016s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 3.743171691894531e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 1.3589859008789062e-05s
INFO | --- Analysis for rcahmw-periods-list took 2.8751602172851562s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 8.535385131835938e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2606842517852783s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.021823644638061523s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 0.00011420249938964844s
Believability | Calculation of trust value for RDF Book Mashup took 1.0967254638671875e-05s
INFO | --- Analysis for rdf-book-mashup took 3.427736282348633s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.38690185546875e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.26061534881591797s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.022682905197143555s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00010156631469726562s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 1.1205673217773438e-05s
INFO | --- Analysis for rdfize-lastfm took 2.3696813583374023s
Availability | SPARQL endpoint availability check for RDFLicense took 260.7744970321655s
Availability | VoID file availability check for RDFLicense took 0.0003418922424316406s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.31716203689575195s
Reputation | Calculation of the PageRank for RDFLicense took 0.02115917205810547s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 4.410743713378906e-05s
Believability | Calculation of trust value for RDFLicense took 1.2636184692382812e-05s
INFO | --- Analysis for rdflicense took 535.7051868438721s
Availability | SPARQL endpoint availability check for RDFohloh took 8.797645568847656e-05s
Availability | VoID file availability check for RDFohloh took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.2616605758666992s
Reputation | Calculation of the PageRank for RDFohloh took 0.021354198455810547s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 9.560585021972656e-05s
Believability | Calculation of trust value for RDFohloh took 6.67572021484375e-06s
INFO | --- Analysis for rdfohloh took 7.785975933074951s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.6480579376220703s
Availability | VoID file availability check for Reactome RDF took 0.0004227161407470703s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.2502865791320801s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020701169967651367s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 4.601478576660156e-05s
Believability | Calculation of trust value for Reactome RDF took 1.1682510375976562e-05s
INFO | --- Analysis for reactome-rdf took 4.181389093399048s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.1827075481414795s
Availability | VoID file availability check for Rechtspraak.nl took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.2473282814025879s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.022743701934814453s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0014119148254394531s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 0.00014400482177734375s
Believability | Calculation of trust value for Rechtspraak.nl took 1.0728836059570312e-05s
INFO | --- Analysis for rechtspraak took 2.6225929260253906s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 9.107589721679688e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.354067325592041s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.020694732666015625s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.726119995117188e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 1.1444091796875e-05s
INFO | --- Analysis for red-uno-internacional-santillana took 16.948814868927002s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.05968022346496582s
Availability | VoID file availability check for reference.data.gov.uk took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.25934386253356934s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00015974044799804688s
Believability | Calculation of trust value for reference.data.gov.uk took 9.775161743164062e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.5190346240997314s
Availability | SPARQL endpoint availability check for Regiony took 4.220008850097656e-05s
Availability | VoID file availability check for Regiony took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for Regiony took 0.2465353012084961s
Reputation | Calculation of the PageRank for Regiony took 0.020717382431030273s
Interlinking | Calculation of Degree of Connection for Regiony took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Regiony took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Regiony took 3.218650817871094e-05s
Believability | Calculation of trust value for Regiony took 1.049041748046875e-05s
INFO | --- Analysis for regiony took 2.8319313526153564s
Availability | SPARQL endpoint availability check for RELD took 263.361793756485s
Availability | VoID file availability check for RELD took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for RELD took 0.6814045906066895s
Reputation | Calculation of the PageRank for RELD took 0.021267414093017578s
Interlinking | Calculation of Degree of Connection for RELD took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for RELD took 4.410743713378906e-05s
Believability | Calculation of trust value for RELD took 1.1444091796875e-05s
INFO | --- Analysis for RELD took 539.6749911308289s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.18461036682128906s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0006177425384521484s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.224928617477417s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.32671642303466797s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.2556400299072266s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.661848783493042s
Versatility | Languages check for Repository for Linked Open Archival Data took 16.904696941375732s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 1.8945536613464355s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.22195863723754883s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.1861121654510498s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.23878049850463867s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.15558981895446777s
License | MR license check for Repository for Linked Open Archival Data took 0.3249084949493408s
License | HR license check for Repository for Linked Open Archival Data took 7.416863918304443s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.09188628196716309s
Understandability | Number of label check for Repository for Linked Open Archival Data took 0.8245110511779785s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.45726728439331055s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.13591241836547852s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.15246343612670898s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.15370559692382812s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.33354377746582s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 7.43865966796875e-05s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.06182146072387695s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.11665987968444824s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.1900014877319336s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.08660340309143066s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.21236205101013184s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.17481279373168945s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.20740079879760742s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.2804815769195557s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.06962466239929199s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.08077764511108398s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.08321857452392578s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.40981411933898926s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.02776789665222168s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.028873205184936523s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.1469404697418213s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 1.7137274742126465s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.17732858657836914s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.6677684783935547s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.356027603149414s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 2.9129223823547363s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.03533506393432617s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.0918276309967041s
Security | Sign check for Repository for Linked Open Archival Data took 0.4704005718231201s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 876.165197134018s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.8491711616516113s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.022558212280273438s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 9.465217590332031e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 1.6689300537109375e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 8.344650268554688e-06s
INFO | --- Analysis for reload took 995.188574552536s
Availability | SPARQL endpoint availability check for Land use merced dataset took 4.267692565917969e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.2782435417175293s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.020823001861572266s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for Land use merced dataset took 5.9604644775390625e-05s
INFO | --- Analysis for remote_Sensing took 3.4839882850646973s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 7.29426646232605s
Availability | VoID file availability check for Renewable Energy Generators took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.27448129653930664s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.4345855712890625e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 9.059906005859375e-06s
INFO | --- Analysis for renewable_energy_generators took 23.1193208694458s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.061962127685546875s
Availability | VoID file availability check for research.data.gov.uk took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.24894952774047852s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020903825759887695s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.72747802734375e-05s
Believability | Calculation of trust value for research.data.gov.uk took 9.059906005859375e-06s
INFO | --- Analysis for research-data-gov-uk took 2.475602865219116s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 4.124641418457031e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.2541821002960205s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.021114826202392578s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 3.2901763916015625e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 1.1682510375976562e-05s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 3.204383611679077s
Availability | SPARQL endpoint availability check for Restaurantes took 8.845329284667969e-05s
Availability | VoID file availability check for Restaurantes took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.2592170238494873s
Reputation | Calculation of the PageRank for Restaurantes took 0.021866321563720703s
Interlinking | Calculation of Degree of Connection for Restaurantes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Restaurantes took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 3.314018249511719e-05s
Believability | Calculation of trust value for Restaurantes took 1.239776611328125e-05s
INFO | --- Analysis for restaurantes-zaragoza took 2.858577251434326s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.4345855712890625e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.24477767944335938s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.022174835205078125s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 7.033348083496094e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 1.2159347534179688e-05s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 3.874905586242676s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.09529852867126465s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.2593059539794922s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.020519733428955078s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.170967102050781e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 1.2159347534179688e-05s
INFO | --- Analysis for revistas_turismo took 2.500401020050049s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.3629181385040283s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.24454665184020996s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.021895647048950195s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011849403381347656s
Believability | Calculation of trust value for Revyu.com - Review Anything took 1.1444091796875e-05s
INFO | --- Analysis for revyu took 2.6842100620269775s
Availability | SPARQL endpoint availability check for sdafsadf took 0.42622804641723633s
Availability | VoID file availability check for sdafsadf took 0.031167268753051758s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.26998162269592285s
Reputation | Calculation of the PageRank for sdafsadf took 0.0203249454498291s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.0517578125e-05s
Believability | Calculation of trust value for sdafsadf took 1.1682510375976562e-05s
INFO | --- Analysis for rgsdfg took 3.225196599960327s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.00010442733764648438s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.27384471893310547s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.673004150390625e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 7.62939453125e-06s
INFO | --- Analysis for riese took 22.6490375995636s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 4.100799560546875e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.25462889671325684s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 3.24249267578125e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 1.1205673217773438e-05s
INFO | --- Analysis for rijksmuseum took 2.829946994781494s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 30.9091796875s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.2635796070098877s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.020710468292236328s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 5.125999450683594e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 1.2874603271484375e-05s
INFO | --- Analysis for rism took 83.32922530174255s
Availability | SPARQL endpoint availability check for RISM Authority data took 20.05932354927063s
Availability | VoID file availability check for RISM Authority data took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.27805280685424805s
Reputation | Calculation of the PageRank for RISM Authority data took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.7206878662109375e-05s
Believability | Calculation of trust value for RISM Authority data took 1.1205673217773438e-05s
INFO | --- Analysis for rism-authorities took 73.46329259872437s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.267692565917969e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.23603606224060059s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.0207977294921875s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.049041748046875e-05s
INFO | --- Analysis for rk took 2.3154356479644775s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.07311034202575684s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00042724609375s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.25249743461608887s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.020769357681274414s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00021910667419433594s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-acm took 2.5005741119384766s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.05187726020812988s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0004260540008544922s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.25026512145996094s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.021551847457885742s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00013756752014160156s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-budapest took 2.438459873199463s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.04742693901062012s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.2619915008544922s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.022763967514038086s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00019812583923339844s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-citeseer took 2.5008459091186523s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.04302072525024414s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.2538886070251465s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020305633544921875s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00015616416931152344s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.3323512077331543s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.030992746353149414s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.0002117156982421875s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.23610830307006836s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020406723022460938s
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.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00015163421630859375s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.3134124279022217s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.03570294380187988s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0002117156982421875s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.25432324409484863s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.02048516273498535s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.5762786865234375e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 4.5299530029296875e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.3872194290161133s
Availability | SPARQL endpoint availability check for crm took 4.100799560546875e-05s
Availability | VoID file availability check for crm took 0.001135110855102539s
Completeness | Calculation of interlinking completeness for crm took 0.24073052406311035s
Reputation | Calculation of the PageRank for crm took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for crm took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for crm took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for crm took 2.86102294921875e-05s
Believability | Calculation of trust value for crm took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-crm took 2.77616548538208s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.04320502281188965s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.2767963409423828s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.022658586502075195s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00011396408081054688s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-curriculum took 2.496962785720825s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.049834251403808594s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.25986242294311523s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.02072429656982422s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.078315734863281e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.412742853164673s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.04197335243225098s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.2609279155731201s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.00023365020751953125s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-dblp took 2.426591157913208s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.04132580757141113s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.24877381324768066s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.104873657226562e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.4263453483581543s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.04915738105773926s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.25759410858154297s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.107589721679688e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-deploy took 2.5220508575439453s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.037229299545288086s
Availability | VoID file availability check for digitaleconomy took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.247175931930542s
Reputation | Calculation of the PageRank for digitaleconomy took 0.021559476852416992s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.528594970703125e-05s
Believability | Calculation of trust value for digitaleconomy took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.4113008975982666s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.04310297966003418s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.25316810607910156s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020560503005981445s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.0001456737518310547s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-dotac took 2.4564599990844727s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.046866416931152344s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.24671339988708496s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.410743713378906e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-ecs took 3.26812744140625s
Availability | SPARQL endpoint availability check for enaktingpsi took 8.058547973632812e-05s
Availability | VoID file availability check for enaktingpsi took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.24386858940124512s
Reputation | Calculation of the PageRank for enaktingpsi took 0.023096323013305664s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 2.86102294921875e-05s
Believability | Calculation of trust value for enaktingpsi took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.837984800338745s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.030811309814453125s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00021767616271972656s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.26798224449157715s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020869016647338867s
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.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00017976760864257812s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-eprints took 2.3925671577453613s
Availability | SPARQL endpoint availability check for epsrc took 0.04235577583312988s
Availability | VoID file availability check for epsrc took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for epsrc took 0.2539196014404297s
Reputation | Calculation of the PageRank for epsrc took 0.020544767379760742s
Interlinking | Calculation of Degree of Connection for epsrc took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for epsrc took 6.222724914550781e-05s
Believability | Calculation of trust value for epsrc took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-epsrc took 2.4359796047210693s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.045684814453125s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0004315376281738281s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.26456189155578613s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.00011229515075683594s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-era took 2.466437816619873s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.04354357719421387s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.24999499320983887s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020981788635253906s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010371208190917969s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-eurecom took 2.389813184738159s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 0.000110626220703125s
Availability | VoID file availability check for rkb-explorer-foreign took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.26273107528686523s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.021881818771362305s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 3.0279159545898438e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-foreign took 2.774819850921631s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.04810667037963867s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.2647671699523926s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020390748977661133s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.202957153320312e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-ft took 2.4729573726654053s
Availability | SPARQL endpoint availability check for fun took 0.048862457275390625s
Availability | VoID file availability check for fun took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for fun took 0.2832207679748535s
Reputation | Calculation of the PageRank for fun took 0.021782636642456055s
Interlinking | Calculation of Degree of Connection for fun took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for fun took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for fun took 7.414817810058594e-05s
Believability | Calculation of trust value for fun took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-fun took 2.398135185241699s
Availability | SPARQL endpoint availability check for gdlc took 0.0443577766418457s
Availability | VoID file availability check for gdlc took 0.00043773651123046875s
Completeness | Calculation of interlinking completeness for gdlc took 0.26646852493286133s
Reputation | Calculation of the PageRank for gdlc took 0.021109342575073242s
Interlinking | Calculation of Degree of Connection for gdlc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.699562072753906e-05s
Believability | Calculation of trust value for gdlc took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-gdlc took 2.3872408866882324s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.047930002212524414s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.2504105567932129s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011348724365234375s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-ibm took 2.383565902709961s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.05087780952453613s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.23595309257507324s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.021389245986938477s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001361370086669922s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-ieee took 2.424838066101074s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.04143214225769043s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.2516601085662842s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.021528959274291992s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00013947486877441406s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-irit took 2.4538004398345947s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.04847455024719238s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.2533688545227051s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.022124052047729492s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.318092346191406e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-italy took 2.531365394592285s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.05093812942504883s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.24151992797851562s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.02247333526611328s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.534027099609375e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-jisc took 2.4877920150756836s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.04415726661682129s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.26195335388183594s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.020686864852905273s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.4345855712890625e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-kaunas took 2.4562878608703613s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.03557300567626953s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.2596158981323242s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0001628398895263672s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-kisti took 2.393437623977661s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.04589962959289551s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.00022220611572265625s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.2606813907623291s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.02105402946472168s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.001104116439819336s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.000171661376953125s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-laas took 2.422994613647461s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.04863905906677246s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.2508885860443115s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.022149085998535156s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 7.367134094238281e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 2.438387393951416s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.04679584503173828s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.2612729072570801s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.021131277084350586s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00015497207641601562s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-newcastle took 2.530536651611328s
Availability | SPARQL endpoint availability check for notube took 0.04922771453857422s
Availability | VoID file availability check for notube took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for notube took 0.2554740905761719s
Reputation | Calculation of the PageRank for notube took 0.02275538444519043s
Interlinking | Calculation of Degree of Connection for notube took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for notube took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for notube took 4.744529724121094e-05s
Believability | Calculation of trust value for notube took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-notube took 2.4053475856781006s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.04648995399475098s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.2449345588684082s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.020670413970947266s
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.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.0001304149627685547s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-nsf took 2.427611827850342s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.033693552017211914s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.257265567779541s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020397663116455078s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00015592575073242188s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-oai took 2.367331027984619s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.3392181396484375e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.25930166244506836s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.0207369327545166s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 2.9325485229492188e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-opencyc took 2.8757846355438232s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.042732954025268555s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.2684609889984131s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.020745038986206055s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.05718994140625e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-os took 2.444732904434204s
Availability | SPARQL endpoint availability check for photos took 0.03069782257080078s
Availability | VoID file availability check for photos took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for photos took 0.2556033134460449s
Reputation | Calculation of the PageRank for photos took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for photos took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for photos took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for photos took 7.62939453125e-05s
Believability | Calculation of trust value for photos took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.389907121658325s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.0483856201171875s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.22775650024414062s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.020446062088012695s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011301040649414062s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-pisa took 2.405233860015869s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0429835319519043s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.25115180015563965s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.021442413330078125s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.0001952648162841797s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.421316623687744s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.04618954658508301s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.258770227432251s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.022454500198364258s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0001652240753173828s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-resex took 2.4170567989349365s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.03635573387145996s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.2634263038635254s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.021673917770385742s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 0.00010728836059570312s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-risks took 2.441730499267578s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.048635005950927734s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.24973654747009277s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020290136337280273s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012350082397460938s
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 2.3737668991088867s
Availability | SPARQL endpoint availability check for roni took 0.044283151626586914s
Availability | VoID file availability check for roni took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for roni took 0.2746915817260742s
Reputation | Calculation of the PageRank for roni took 0.022370338439941406s
Interlinking | Calculation of Degree of Connection for roni took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for roni took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for roni took 2.956390380859375e-05s
Believability | Calculation of trust value for roni took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-roni took 2.480490207672119s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.04544806480407715s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.2733898162841797s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.021802902221679688s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00021648406982421875s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-southampton took 2.4951236248016357s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.04318404197692871s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.2617499828338623s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.0001201629638671875s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-ulm took 2.400135040283203s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.041002750396728516s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.25151753425598145s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.942054748535156e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.344602108001709s
Availability | SPARQL endpoint availability check for webconf took 0.04573249816894531s
Availability | VoID file availability check for webconf took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for webconf took 0.25698018074035645s
Reputation | Calculation of the PageRank for webconf took 0.02288222312927246s
Interlinking | Calculation of Degree of Connection for webconf took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007998943328857422s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00011277198791503906s
Believability | Calculation of trust value for webconf took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-webconf took 13.191874742507935s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.04530978202819824s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.2512400150299072s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 6.914138793945312e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-webscience took 2.3558061122894287s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.050470590591430664s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.000888824462890625s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.2484903335571289s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.02199864387512207s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.0002162456512451172s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-wiki took 2.5126497745513916s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.04149460792541504s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.25489330291748047s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.0207369327545166s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.369850158691406e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.438704490661621s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 8.630752563476562e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.009651899337768555s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.2639806270599365s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 2.956390380859375e-05s
Believability | Calculation of trust value for RKB Explorer Data took 1.2874603271484375e-05s
INFO | --- Analysis for rkb_explorer_data took 2.9284605979919434s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.43973398208618164s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.25803589820861816s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 8.559226989746094e-05s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 7.152557373046875e-06s
INFO | --- Analysis for roceeh-road took 3.4771370887756348s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.458427429199219e-05s
Availability | VoID file availability check for The Rosetta Project took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.27037549018859863s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 3.24249267578125e-05s
Believability | Calculation of trust value for The Rosetta Project took 1.2636184692382812e-05s
INFO | --- Analysis for rosetta-project took 2.8647561073303223s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 4.291534423828125e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.00041413307189941406s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.2553582191467285s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.021455049514770508s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 3.0040740966796875e-05s
Believability | Calculation of trust value for ontology terrorist attack took 1.1682510375976562e-05s
INFO | --- Analysis for ROSHANI took 5.094813108444214s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.2438507080078125e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.25910401344299316s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.020315170288085938s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.266334533691406e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 1.2874603271484375e-05s
INFO | --- Analysis for ROSHANI_SAHU took 2.3075695037841797s
Availability | SPARQL endpoint availability check for x took 4.315376281738281e-05s
Availability | VoID file availability check for x took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for x took 0.251436710357666s
Reputation | Calculation of the PageRank for x took 0.02085137367248535s
Interlinking | Calculation of Degree of Connection for x took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for x took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for x took 3.123283386230469e-05s
Believability | Calculation of trust value for x took 1.2636184692382812e-05s
INFO | --- Analysis for Rozprawa,_artykuł took 2.3622336387634277s
Availability | SPARQL endpoint availability check for Rpm Find took 4.0531158447265625e-05s
Availability | VoID file availability check for Rpm Find took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.2434389591217041s
Reputation | Calculation of the PageRank for Rpm Find took 0.020365238189697266s
Interlinking | Calculation of Degree of Connection for Rpm Find took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Rpm Find took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 3.4809112548828125e-05s
Believability | Calculation of trust value for Rpm Find took 1.3113021850585938e-05s
INFO | --- Analysis for rpm_find took 2.814523935317993s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 6.628036499023438e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0007402896881103516s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.2567439079284668s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.021312952041625977s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.890296936035156e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 1.1920928955078125e-05s
INFO | --- Analysis for rss-500-nif-ner-corpus took 3.7849416732788086s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 0.00010061264038085938s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.24923205375671387s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020980358123779297s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.033348083496094e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 1.049041748046875e-05s
INFO | --- Analysis for rubentaelman took 2.7953288555145264s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 5.841255187988281e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.27307677268981934s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.020907878875732422s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.58306884765625e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 1.2159347534179688e-05s
INFO | --- Analysis for rubenverborgh took 4.327569246292114s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 393.60168170928955s
Availability | VoID file availability check for Russian Universities Specialities took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.32181763648986816s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.076957702636719e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 1.239776611328125e-05s
INFO | --- Analysis for russian-universities-specialities took 678.8000628948212s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.0531158447265625e-05s
Availability | VoID file availability check for RuThes Cloud took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.6744844913482666s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.021091222763061523s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 3.838539123535156e-05s
Believability | Calculation of trust value for RuThes Cloud took 1.0728836059570312e-05s
INFO | --- Analysis for ruthes took 5.062530040740967s
Availability | SPARQL endpoint availability check for RxNorm took 6.365776062011719e-05s
Availability | VoID file availability check for RxNorm took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for RxNorm took 0.26580381393432617s
Reputation | Calculation of the PageRank for RxNorm took 0.020984172821044922s
Interlinking | Calculation of Degree of Connection for RxNorm took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RxNorm took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.409385681152344e-05s
Believability | Calculation of trust value for RxNorm took 1.0251998901367188e-05s
INFO | --- Analysis for rxnorm took 2.717526912689209s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 3.2657899856567383s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.2351398468017578s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.022036314010620117s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.790855407714844e-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 7.769319295883179s
Availability | SPARQL endpoint availability check for SALDO took 4.291534423828125e-05s
Availability | VoID file availability check for SALDO took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for SALDO took 0.24887585639953613s
Reputation | Calculation of the PageRank for SALDO took 0.020780086517333984s
Interlinking | Calculation of Degree of Connection for SALDO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SALDO took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for SALDO took 3.147125244140625e-05s
Believability | Calculation of trust value for SALDO took 1.0967254638671875e-05s
INFO | --- Analysis for saldo took 3.365767478942871s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.233112096786499s
Availability | VoID file availability check for SALDO-RDF took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.25075817108154297s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.647804260253906e-05s
Believability | Calculation of trust value for SALDO-RDF took 1.0251998901367188e-05s
INFO | --- Analysis for saldo-rdf took 5.617440938949585s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6300678253173828s
Availability | VoID file availability check for SALDOM-RDF took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.2612929344177246s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.647804260253906e-05s
Believability | Calculation of trust value for SALDOM-RDF took 5.7220458984375e-06s
INFO | --- Analysis for saldom-rdf took 4.654558181762695s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 4.172325134277344e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.24775481224060059s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010228157043457031s
Believability | Calculation of trust value for Salzburgerland DE took 1.0013580322265625e-05s
INFO | --- Analysis for salzburgerland-com-de took 2.95436692237854s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.5299530029296875e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.2463235855102539s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.021279335021972656s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00010752677917480469s
Believability | Calculation of trust value for Salzburgerland EN took 1.2874603271484375e-05s
INFO | --- Analysis for salzburgerland-com-en took 2.796987295150757s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.506111145019531e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.2845640182495117s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.023508787155151367s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0008461475372314453s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00011730194091796875s
Believability | Calculation of trust value for Salzburgerland IT took 1.3113021850585938e-05s
INFO | --- Analysis for salzburgerland-com-it took 2.847364902496338s
Availability | SPARQL endpoint availability check for sameAs.org took 4.291534423828125e-05s
Availability | VoID file availability check for sameAs.org took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.2394709587097168s
Reputation | Calculation of the PageRank for sameAs.org took 0.021027088165283203s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 3.314018249511719e-05s
Believability | Calculation of trust value for sameAs.org took 1.239776611328125e-05s
INFO | --- Analysis for sameas-org took 2.8297066688537598s
Availability | SPARQL endpoint availability check for sandrart.net took 8.606910705566406e-05s
Availability | VoID file availability check for sandrart.net took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.2778594493865967s
Reputation | Calculation of the PageRank for sandrart.net took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.699562072753906e-05s
Believability | Calculation of trust value for sandrart.net took 8.344650268554688e-06s
INFO | --- Analysis for sandrart-net took 3.56624174118042s
Availability | SPARQL endpoint availability check for Taxons  took 0.19974422454833984s
Availability | VoID file availability check for Taxons  took 0.00045371055603027344s
Extra | Recovery of all triples for Taxons  took 20.487976551055908s
Performance | Total latancy measurement for Taxons  took 0.3939661979675293s
Amount of data | Number of triples check for Taxons  took 2.1189138889312744s
Interoperability | New terms check for Taxons  took 1.8402159214019775s
Versatility | Languages check for Taxons  took 39.833067417144775s
Interpretability | Number of blank nodes check for Taxons  took 0.970287561416626s
Security | Check HTTPS for Taxons  took 0.19198274612426758s
Interpretability | RDF structures check for Taxons  took 1.0765368938446045s
Versatility | Serialization formats check for Taxons  took 0.7061219215393066s
Availability | RDF dump link check for Taxons  took 0.08498525619506836s
License | MR license check for Taxons  took 2.021868944168091s
License | HR license check for Taxons  took 1.96150541305542s
Amount of data | Number of property check for Taxons  took 0.09046792984008789s
Understandability | Number of label check for Taxons  took 3.252075672149658s
Understandability | URI regex check for Taxons  took 0.5684747695922852s
Understandability | Vocabs check for Taxons  took 0.23652291297912598s
Verifiability | Authors check for Taxons  took 0.09903478622436523s
Verifiability | Publishers check for Taxons  took 0.08349108695983887s
Performance | Throughput check for Taxons  took 10.3805513381958s
Amount of data | Check the number of entities for Taxons  took 3.9577484130859375e-05s
Verifiability | Contribs. check for Taxons  took 0.08670949935913086s
Interlinking | sameAs chians check for Taxons  took 0.12875151634216309s
Interlinking | skos check for Taxons  took 0.13018250465393066s
Interlinking | skos check for Taxons  took 0.09889698028564453s
Timeliness | dataset update frequency check for Taxons  took 0.5354969501495361s
Currency | Creation date check for Taxons  took 0.16658735275268555s
Currency | Modification date check for Taxons  took 0.18926715850830078s
Rep.Conc. | URIs length for Taxons  took 8.018270492553711s
Interoperability | New vocabularies check for Taxons  took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.09003019332885742s
Accuracy | Check Functional Property for Taxons  took 0.32053470611572266s
Accuracy | Check Inverse Functional Property for Taxons  took 0.3288228511810303s
Accuracy | Check Empty annotation labels for Taxons  took 3.722764730453491s
Accuracy | Check White space in annotation for Taxons  took 0.3049962520599365s
Accuracy | Check Datatype consistency for Taxons  took 0.2641589641571045s
Consistency | Disjoint class check for Taxons  took 0.11468935012817383s
Consistency | Check Misplaced properties for Taxons  took 3.810173511505127s
Consistency | Misplaced classes for Taxons  took 0.944504976272583s
Consistency | Check Ontology hijacking for Taxons  took 4.065178632736206s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.3250541687011719s
Consistency | Check Invalid usage of undefined properties for Taxons  took 5.393426179885864s
Conciseness | Check Extensional conciseness for Taxons  took 0.2800252437591553s
Conciseness | Check Intensional conciseness for Taxons  took 0.15191435813903809s
Security | Sign check for Taxons  took 0.9940574169158936s
Availability | Check URIs Dereferenciability for Taxons  took 1965.455271244049s
Completeness | Calculation of interlinking completeness for Taxons  took 1.1027982234954834s
Reputation | Calculation of the PageRank for Taxons  took 0.02169346809387207s
Interlinking | Calculation of Degree of Connection for Taxons  took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Taxons  took 8.058547973632812e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 2.6226043701171875e-06s
Believability | Calculation of trust value for Taxons  took 1.0967254638671875e-05s
INFO | --- Analysis for sandre took 2149.087297677994s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 4.411104917526245s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.6906819343566895s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.022077322006225586s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.0994415283203125e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 1.1444091796875e-05s
INFO | --- Analysis for sanskrit-english-lexicon took 33.52889084815979s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 264.22408652305603s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0008678436279296875s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.3000216484069824s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.022398948669433594s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 5.650520324707031e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 1.3828277587890625e-05s
INFO | --- Analysis for santillana_guide_dataset took 669.0617628097534s
Availability | SPARQL endpoint availability check for SATAR test  took 0.00010609626770019531s
Availability | VoID file availability check for SATAR test  took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.24225640296936035s
Reputation | Calculation of the PageRank for SATAR test  took 0.020893335342407227s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 2.9087066650390625e-05s
Believability | Calculation of trust value for SATAR test  took 6.67572021484375e-06s
INFO | --- Analysis for SATAR_test took 6.9123945236206055s
Availability | SPARQL endpoint availability check for SCBG Data took 23.567883014678955s
Availability | VoID file availability check for SCBG Data took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.24489426612854004s
Reputation | Calculation of the PageRank for SCBG Data took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0009138584136962891s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.869171142578125e-05s
Believability | Calculation of trust value for SCBG Data took 7.3909759521484375e-06s
INFO | --- Analysis for SCBG-Data took 57.21979641914368s
Availability | SPARQL endpoint availability check for schema.org took 4.100799560546875e-05s
Availability | VoID file availability check for schema.org took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for schema.org took 0.2526888847351074s
Reputation | Calculation of the PageRank for schema.org took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for schema.org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for schema.org took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.552436828613281e-05s
Believability | Calculation of trust value for schema.org took 1.3113021850585938e-05s
INFO | --- Analysis for schema-org took 2.8574838638305664s
Availability | SPARQL endpoint availability check for Schemantra took 0.00010609626770019531s
Availability | VoID file availability check for Schemantra took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Schemantra took 0.26737284660339355s
Reputation | Calculation of the PageRank for Schemantra took 0.020918607711791992s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Schemantra took 3.0994415283203125e-05s
Believability | Calculation of trust value for Schemantra took 1.1444091796875e-05s
INFO | --- Analysis for Schemantra took 3.251783609390259s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 1.6876130104064941s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.26449084281921387s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 4.124641418457031e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 1.1920928955078125e-05s
INFO | --- Analysis for schemapedia took 4.4720282554626465s
Availability | SPARQL endpoint availability check for scholarlydata took 4.00543212890625e-05s
Availability | VoID file availability check for scholarlydata took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.26451921463012695s
Reputation | Calculation of the PageRank for scholarlydata took 0.02277231216430664s
Interlinking | Calculation of Degree of Connection for scholarlydata took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 3.457069396972656e-05s
Believability | Calculation of trust value for scholarlydata took 1.2636184692382812e-05s
INFO | --- Analysis for scholarlydata took 2.866331100463867s
Availability | SPARQL endpoint availability check for Scholarometer took 4.0531158447265625e-05s
Availability | VoID file availability check for Scholarometer took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.2435154914855957s
Reputation | Calculation of the PageRank for Scholarometer took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.487701416015625e-05s
Believability | Calculation of trust value for Scholarometer took 1.1920928955078125e-05s
INFO | --- Analysis for scholarometer took 7.82205057144165s
Availability | SPARQL endpoint availability check for Science Commons took 4.1961669921875e-05s
Availability | VoID file availability check for Science Commons took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Science Commons took 0.2730858325958252s
Reputation | Calculation of the PageRank for Science Commons took 0.020646333694458008s
Interlinking | Calculation of Degree of Connection for Science Commons took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Science Commons took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Science Commons took 3.0517578125e-05s
Believability | Calculation of trust value for Science Commons took 1.2636184692382812e-05s
INFO | --- Analysis for science_commons took 2.8351662158966064s
Availability | SPARQL endpoint availability check for ScienceWise took 4.1961669921875e-05s
Availability | VoID file availability check for ScienceWise took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.2582974433898926s
Reputation | Calculation of the PageRank for ScienceWise took 0.020911455154418945s
Interlinking | Calculation of Degree of Connection for ScienceWise took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ScienceWise took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 3.170967102050781e-05s
Believability | Calculation of trust value for ScienceWise took 1.3589859008789062e-05s
INFO | --- Analysis for sciencewise took 2.851139545440674s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 9.369850158691406e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.24466204643249512s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 3.0994415283203125e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 8.821487426757812e-06s
INFO | --- Analysis for scoreboard took 4.779742479324341s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 8.821487426757812e-05s
Availability | VoID file availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007927417755126953s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.26679134368896484s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.02068161964416504s
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.3113021850585938e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.600120544433594e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 1.1920928955078125e-05s
INFO | --- Analysis for SDDEC took 26.762943983078003s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.172325134277344e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.25246739387512207s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.02221989631652832s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 3.147125244140625e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.2636184692382812e-05s
INFO | --- Analysis for SDG took 4.277597188949585s
Availability | SPARQL endpoint availability check for sears.com took 8.797645568847656e-05s
Availability | VoID file availability check for sears.com took 0.0012671947479248047s
Completeness | Calculation of interlinking completeness for sears.com took 0.24616217613220215s
Reputation | Calculation of the PageRank for sears.com took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for sears.com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.699562072753906e-05s
Believability | Calculation of trust value for sears.com took 1.2159347534179688e-05s
INFO | --- Analysis for sears took 4.751092195510864s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.12308859825134277s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.25700855255126953s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020897388458251953s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.153915405273438e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 5.245208740234375e-06s
INFO | --- Analysis for sec-rdfabout took 2.9218008518218994s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.873273372650146s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.285250186920166s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.02087092399597168s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0008254051208496094s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.678436279296875e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for secold took 168.5128366947174s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.100799560546875e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.0011391639709472656s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.7064523696899414s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.02084970474243164s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 3.218650817871094e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 1.3113021850585938e-05s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 3.374819755554199s
Availability | SPARQL endpoint availability check for semanlink took 5.9604644775390625e-05s
Availability | VoID file availability check for semanlink took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for semanlink took 0.24599123001098633s
Reputation | Calculation of the PageRank for semanlink took 0.020870208740234375s
Interlinking | Calculation of Degree of Connection for semanlink took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00014662742614746094s
Believability | Calculation of trust value for semanlink took 1.2159347534179688e-05s
INFO | --- Analysis for semanlink took 3.547870635986328s
Availability | SPARQL endpoint availability check for Semantic Library took 6.413459777832031e-05s
Availability | VoID file availability check for Semantic Library took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.2643890380859375s
Reputation | Calculation of the PageRank for Semantic Library took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for Semantic Library took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Semantic Library took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 3.2901763916015625e-05s
Believability | Calculation of trust value for Semantic Library took 1.2874603271484375e-05s
INFO | --- Analysis for semantic-library took 3.3084747791290283s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 7.843971252441406e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.24525666236877441s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 3.0517578125e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 1.2636184692382812e-05s
INFO | --- Analysis for semantic-profiling-network took 2.7551021575927734s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.08746337890625s
Availability | VoID file availability check for Semantic Universe Data took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.2870626449584961s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.0994415283203125e-05s
Believability | Calculation of trust value for Semantic Universe Data took 1.1920928955078125e-05s
INFO | --- Analysis for semantic-universe took 2.4405677318573s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.4624183177948s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.2610185146331787s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020435333251953125s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011873245239257812s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.0967254638671875e-05s
INFO | --- Analysis for semantic-web-dog-food took 82.83091974258423s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 4.5299530029296875e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.27401185035705566s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.021877765655517578s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.696846008300781e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 1.3113021850585938e-05s
INFO | --- Analysis for semantic-web-grundlagen took 3.359093427658081s
Availability | SPARQL endpoint availability check for semantic-web-journal took 4.315376281738281e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.2787346839904785s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.02213430404663086s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 3.147125244140625e-05s
Believability | Calculation of trust value for semantic-web-journal took 1.239776611328125e-05s
INFO | --- Analysis for semantic-web-journal took 2.8602561950683594s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.553794860839844e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.25304198265075684s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.02307438850402832s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.416175842285156e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 1.0013580322265625e-05s
INFO | --- Analysis for semantic-xbrl took 3.2989561557769775s
Availability | SPARQL endpoint availability check for Semantic Bible took 7.176399230957031e-05s
Availability | VoID file availability check for Semantic Bible took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.254152774810791s
Reputation | Calculation of the PageRank for Semantic Bible took 0.02262425422668457s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 2.9325485229492188e-05s
Believability | Calculation of trust value for Semantic Bible took 1.1920928955078125e-05s
INFO | --- Analysis for semantic_bible took 2.794191360473633s
Availability | SPARQL endpoint availability check for SemanticQuran took 5.586333990097046s
Availability | VoID file availability check for SemanticQuran took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.26593542098999023s
Reputation | Calculation of the PageRank for SemanticQuran took 0.022136449813842773s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SemanticQuran took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 7.05718994140625e-05s
Believability | Calculation of trust value for SemanticQuran took 5.888938903808594e-05s
INFO | --- Analysis for semanticquran took 14.251386165618896s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.458427429199219e-05s
Availability | VoID file availability check for SemanticTweet took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.26189517974853516s
Reputation | Calculation of the PageRank for SemanticTweet took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.5789947509765625e-05s
Believability | Calculation of trust value for SemanticTweet took 1.5020370483398438e-05s
INFO | --- Analysis for semantictweet took 2.437671184539795s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.172325134277344e-05s
Availability | VoID file availability check for semanticweb.org took 0.0007429122924804688s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.27274584770202637s
Reputation | Calculation of the PageRank for semanticweb.org took 0.02129364013671875s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 8.153915405273438e-05s
Believability | Calculation of trust value for semanticweb.org took 3.0279159545898438e-05s
INFO | --- Analysis for semanticweb-org took 22.642350912094116s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.11674761772155762s
Availability | VoID file availability check for Semantic CrunchBase took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.24840664863586426s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.022854089736938477s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 7.05718994140625e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 1.239776611328125e-05s
INFO | --- Analysis for semsol-crunchbase took 2.4251656532287598s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 4.100799560546875e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.25429296493530273s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 3.266334533691406e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 8.106231689453125e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.852567672729492s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.2613041400909424s
Availability | VoID file availability check for SentimentWortschatz took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.24223971366882324s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.02076411247253418s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.220008850097656e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.2636184692382812e-05s
INFO | --- Analysis for sentiws took 3.421461820602417s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.19710063934326s
Availability | VoID file availability check for seoul-bike-data took 0.0007762908935546875s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.26194024085998535s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.021897315979003906s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 3.075599670410156e-05s
Believability | Calculation of trust value for seoul-bike-data took 1.2874603271484375e-05s
INFO | --- Analysis for seoul-bike-data took 72.73440456390381s
Availability | SPARQL endpoint availability check for Serendipity took 8.061589241027832s
Availability | VoID file availability check for Serendipity took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Serendipity took 0.23577070236206055s
Reputation | Calculation of the PageRank for Serendipity took 0.02098560333251953s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Serendipity took 8.296966552734375e-05s
Believability | Calculation of trust value for Serendipity took 1.0251998901367188e-05s
INFO | --- Analysis for serendipity took 15.493459701538086s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 8.296966552734375e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.24881887435913086s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.020905017852783203s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.8623809814453125e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 1.2159347534179688e-05s
INFO | --- Analysis for Sherry_Wine took 2.5082240104675293s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.38690185546875e-05s
Availability | VoID file availability check for Sherry Wine took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.259812593460083s
Reputation | Calculation of the PageRank for Sherry Wine took 0.021077871322631836s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.314018249511719e-05s
Believability | Calculation of trust value for Sherry Wine took 1.1444091796875e-05s
INFO | --- Analysis for Sherry_Wine_ took 2.288341760635376s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.17270469665527344s
Availability | VoID file availability check for Shoah victims? names took 0.737421989440918s
Extra | Recovery of all triples for Shoah victims? names took 0.9665532112121582s
Performance | Total latancy measurement for Shoah victims? names took 0.4246366024017334s
Amount of data | Number of triples check for Shoah victims? names took 1.1867671012878418s
Interoperability | New terms check for Shoah victims? names took 1.6549086570739746s
Versatility | Languages check for Shoah victims? names took 18.688835382461548s
Interpretability | Number of blank nodes check for Shoah victims? names took 1.8859343528747559s
Security | Check HTTPS for Shoah victims? names took 0.21188664436340332s
Interpretability | RDF structures check for Shoah victims? names took 0.2080535888671875s
Versatility | Serialization formats check for Shoah victims? names took 0.24763250350952148s
Availability | RDF dump link check for Shoah victims? names took 0.16469860076904297s
License | MR license check for Shoah victims? names took 0.3918416500091553s
License | HR license check for Shoah victims? names took 7.832758665084839s
Amount of data | Number of property check for Shoah victims? names took 0.10264825820922852s
Understandability | Number of label check for Shoah victims? names took 1.0934700965881348s
Understandability | URI regex check for Shoah victims? names took 0.45953941345214844s
Understandability | Vocabs check for Shoah victims? names took 0.09737157821655273s
Verifiability | Authors check for Shoah victims? names took 0.1817026138305664s
Verifiability | Publishers check for Shoah victims? names took 0.14523983001708984s
Performance | Throughput check for Shoah victims? names took 10.354907512664795s
Amount of data | Check the number of entities for Shoah victims? names took 6.794929504394531e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.08098387718200684s
Interlinking | sameAs chians check for Shoah victims? names took 0.10384488105773926s
Interlinking | skos check for Shoah victims? names took 0.18036580085754395s
Interlinking | skos check for Shoah victims? names took 0.06520342826843262s
Timeliness | dataset update frequency check for Shoah victims? names took 0.19857573509216309s
Currency | Creation date check for Shoah victims? names took 0.16002774238586426s
Currency | Modification date check for Shoah victims? names took 0.12813806533813477s
Rep.Conc. | URIs length for Shoah victims? names took 2.1929309368133545s
Interoperability | New vocabularies check for Shoah victims? names took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.0917060375213623s
Accuracy | Check Functional Property for Shoah victims? names took 0.10775232315063477s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.07781028747558594s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.54960036277771s
Accuracy | Check White space in annotation for Shoah victims? names took 0.027849912643432617s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.027765989303588867s
Consistency | Disjoint class check for Shoah victims? names took 0.12169146537780762s
Consistency | Check Misplaced properties for Shoah victims? names took 1.6603398323059082s
Consistency | Misplaced classes for Shoah victims? names took 0.1553483009338379s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.623873233795166s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.3005437850952148s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 2.993330240249634s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.0359649658203125s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.10537219047546387s
Security | Sign check for Shoah victims? names took 0.30681824684143066s
Availability | Check URIs Dereferenciability for Shoah victims? names took 833.311441898346s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 1.5052893161773682s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.021284103393554688s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.601478576660156e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.430511474609375e-06s
Believability | Calculation of trust value for Shoah victims? names took 1.7404556274414062e-05s
INFO | --- Analysis for shoah-victims-names took 949.2570850849152s
Availability | SPARQL endpoint availability check for Person took 4.5299530029296875e-05s
Availability | VoID file availability check for Person took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Person took 0.24825716018676758s
Reputation | Calculation of the PageRank for Person took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for Person took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Person took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Person took 2.8848648071289062e-05s
Believability | Calculation of trust value for Person took 1.2874603271484375e-05s
INFO | --- Analysis for Shripriya_Dubey took 3.6917502880096436s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 4.1484832763671875e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.255615234375s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.020333290100097656s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0008027553558349609s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 1.0013580322265625e-05s
INFO | --- Analysis for Shutterstock took 2.2925713062286377s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 5.745887756347656e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.2503488063812256s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 2.9325485229492188e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 1.0967254638671875e-05s
INFO | --- Analysis for simile_data_collection took 2.798112154006958s
Availability | SPARQL endpoint availability check for SIMPLE took 4.124641418457031e-05s
Availability | VoID file availability check for SIMPLE took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.2534971237182617s
Reputation | Calculation of the PageRank for SIMPLE took 0.020973920822143555s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.00543212890625e-05s
Believability | Calculation of trust value for SIMPLE took 1.1920928955078125e-05s
INFO | --- Analysis for simple took 7.808379888534546s
Availability | SPARQL endpoint availability check for SITC-V4 took 26.392529249191284s
Availability | VoID file availability check for SITC-V4 took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.7004766464233398s
Reputation | Calculation of the PageRank for SITC-V4 took 0.020418167114257812s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0008161067962646484s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 3.981590270996094e-05s
Believability | Calculation of trust value for SITC-V4 took 9.775161743164062e-06s
INFO | --- Analysis for sitc-v4 took 126.33863234519958s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0001366138458251953s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.24014902114868164s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 3.9577484130859375e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 7.62939453125e-06s
INFO | --- Analysis for sli_galnet_rdf took 12.952415227890015s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.458427429199219e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.23494815826416016s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020914316177368164s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.409385681152344e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 8.344650268554688e-06s
INFO | --- Analysis for slideshare2rdf took 2.3454623222351074s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 4.792213439941406e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.2333979606628418s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.020980119705200195s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 3.170967102050781e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 7.152557373046875e-06s
INFO | --- Analysis for slidewiki-rdf-sparql took 2.737898826599121s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.46555638313293457s
Availability | VoID file availability check for Linked Stage Graph took 0.0002803802490234375s
Extra | Recovery of all triples for Linked Stage Graph took 2.141327142715454s
Performance | Total latancy measurement for Linked Stage Graph took 0.9494349956512451s
Amount of data | Number of triples check for Linked Stage Graph took 0.21264886856079102s
Interoperability | New terms check for Linked Stage Graph took 1.5879790782928467s
Versatility | Languages check for Linked Stage Graph took 0.6666951179504395s
Interpretability | Number of blank nodes check for Linked Stage Graph took 0.22478413581848145s
Security | Check HTTPS for Linked Stage Graph took 0.11195254325866699s
Interpretability | RDF structures check for Linked Stage Graph took 0.4405362606048584s
Versatility | Serialization formats check for Linked Stage Graph took 0.24908900260925293s
Availability | RDF dump link check for Linked Stage Graph took 0.21037673950195312s
License | MR license check for Linked Stage Graph took 0.42369794845581055s
License | HR license check for Linked Stage Graph took 1.808608055114746s
Amount of data | Number of property check for Linked Stage Graph took 0.21854662895202637s
Understandability | Number of label check for Linked Stage Graph took 0.5714719295501709s
Understandability | URI regex check for Linked Stage Graph took 0.5420582294464111s
Understandability | Vocabs check for Linked Stage Graph took 0.27999210357666016s
Verifiability | Authors check for Linked Stage Graph took 0.19319987297058105s
Verifiability | Publishers check for Linked Stage Graph took 0.20394182205200195s
Performance | Throughput check for Linked Stage Graph took 11.045650720596313s
Amount of data | Check the number of entities for Linked Stage Graph took 3.1948089599609375e-05s
Verifiability | Contribs. check for Linked Stage Graph took 0.18172383308410645s
Interlinking | sameAs chians check for Linked Stage Graph took 0.2759575843811035s
Interlinking | skos check for Linked Stage Graph took 0.2309722900390625s
Interlinking | skos check for Linked Stage Graph took 0.19325041770935059s
Timeliness | dataset update frequency check for Linked Stage Graph took 0.34987711906433105s
Currency | Creation date check for Linked Stage Graph took 0.4166107177734375s
Currency | Modification date check for Linked Stage Graph took 0.4064152240753174s
Rep.Conc. | URIs length for Linked Stage Graph took 1.4968907833099365s
Interoperability | New vocabularies check for Linked Stage Graph took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for Linked Stage Graph took 0.19992709159851074s
Accuracy | Check Functional Property for Linked Stage Graph took 0.4040946960449219s
Accuracy | Check Inverse Functional Property for Linked Stage Graph took 0.18801355361938477s
Accuracy | Check Empty annotation labels for Linked Stage Graph took 0.7503278255462646s
Accuracy | Check White space in annotation for Linked Stage Graph took 0.024424314498901367s
Accuracy | Check Datatype consistency for Linked Stage Graph took 0.02798008918762207s
Consistency | Disjoint class check for Linked Stage Graph took 0.20546483993530273s
Consistency | Check Misplaced properties for Linked Stage Graph took 0.8755683898925781s
Consistency | Misplaced classes for Linked Stage Graph took 0.5499844551086426s
Consistency | Check Ontology hijacking for Linked Stage Graph took 1.9734954833984375s
Consistency | Check Invalid usage of undefined classes for Linked Stage Graph took 1.3025705814361572s
Consistency | Check Invalid usage of undefined properties for Linked Stage Graph took 1.772218942642212s
Conciseness | Check Extensional conciseness for Linked Stage Graph took 0.026322603225708008s
Conciseness | Check Intensional conciseness for Linked Stage Graph took 0.5449659824371338s
Security | Sign check for Linked Stage Graph took 0.525719165802002s
Availability | Check URIs Dereferenciability for Linked Stage Graph took 1240.4279608726501s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 1.571258306503296s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.021078109741210938s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 6.318092346191406e-05s
Interoperability | Check the re-using of existing vocabs for Linked Stage Graph took 1.1920928955078125e-06s
Believability | Calculation of trust value for Linked Stage Graph took 1.5974044799804688e-05s
INFO | --- Analysis for slod took 1312.399742603302s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 4.38690185546875e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.274782657623291s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.021643638610839844s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 3.170967102050781e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.239776611328125e-05s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 4.604815244674683s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.3305654525756836s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.00048089027404785156s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 139.2905032634735s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.9768874645233154s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 9.466653108596802s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 14.224605798721313s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.2525284290314s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 2.141378402709961s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.2921638488769531s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 7.3882737159729s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.36813831329345703s
License | MR license check for Smart Points Of Interest @PSNC took 0.8006007671356201s
License | HR license check for Smart Points Of Interest @PSNC took 300.24644112586975s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.1897141933441162s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 2.8869712352752686s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 0.999990701675415s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.5087583065032959s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.18684768676757812s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.26156067848205566s
Performance | Throughput check for Smart Points Of Interest @PSNC took 11.422658443450928s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 7.390975952148438e-05s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.20051860809326172s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.2014756202697754s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.5083165168762207s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.4481370449066162s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 6.033839464187622s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.4301908016204834s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.2699427604675293s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 152.39370107650757s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.19481992721557617s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.36651039123535156s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.37530946731567383s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 45.58842968940735s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.6743950843811035s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.6653740406036377s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.21124029159545898s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 88.34303522109985s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.338158130645752s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 46.885329484939575s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.4300215244293213s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 89.85335636138916s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.7036402225494385s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.6343090534210205s
Security | Sign check for Smart Points Of Interest @PSNC took 1.1761455535888672s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 13.071370601654053s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.5437030792236328s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.02188420295715332s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00011014938354492188s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for Smart_POI_dataset took 2323.6128158569336s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 5.605158805847168s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0007538795471191406s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.27491044998168945s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.409385681152344e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 7.867813110351562e-06s
INFO | --- Analysis for smartlink took 13.656073808670044s
Availability | SPARQL endpoint availability check for SNIK took 1.9451820850372314s
Availability | VoID file availability check for SNIK took 0.0007915496826171875s
Extra | Recovery of all triples for SNIK took 4.130260467529297s
Performance | Total latancy measurement for SNIK took 0.9683492183685303s
Amount of data | Number of triples check for SNIK took 0.21216440200805664s
Interoperability | New terms check for SNIK took 1.5141808986663818s
Versatility | Languages check for SNIK took 0.2794313430786133s
Interpretability | Number of blank nodes check for SNIK took 0.20429754257202148s
Interpretability | RDF structures check for SNIK took 0.22307753562927246s
Versatility | Serialization formats check for SNIK took 0.3430757522583008s
Availability | RDF dump link check for SNIK took 3.5948219299316406s
License | MR license check for SNIK took 8.852373123168945s
License | HR license check for SNIK took 10.049513101577759s
Amount of data | Number of property check for SNIK took 11.173290729522705s
Understandability | Number of label check for SNIK took 11.127218008041382s
Understandability | URI regex check for SNIK took 21.569273233413696s
Understandability | Vocabs check for SNIK took 8.73496413230896s
Verifiability | Authors check for SNIK took 13.04736852645874s
Verifiability | Publishers check for SNIK took 10.163267850875854s
Performance | Throughput check for SNIK took 87.26984453201294s
Amount of data | Check the number of entities for SNIK took 3.170967102050781e-05s
Verifiability | Contribs. check for SNIK took 9.24223017692566s
Interlinking | sameAs chians check for SNIK took 13.306037187576294s
Interlinking | skos check for SNIK took 11.211823463439941s
Interlinking | skos check for SNIK took 6.539444446563721s
Timeliness | dataset update frequency check for SNIK took 12.728163957595825s
Currency | Creation date check for SNIK took 20.01186180114746s
Currency | Modification date check for SNIK took 15.987759113311768s
Rep.Conc. | URIs length for SNIK took 17.61704182624817s
Interoperability | New vocabularies check for SNIK took 5.9604644775390625e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 5.654320478439331s
Accuracy | Check Functional Property for SNIK took 9.17396855354309s
Accuracy | Check Inverse Functional Property for SNIK took 2.905466079711914s
Accuracy | Check Empty annotation labels for SNIK took 6.689023017883301s
Accuracy | Check White space in annotation for SNIK took 0.0270993709564209s
Accuracy | Check Datatype consistency for SNIK took 0.22022008895874023s
Consistency | Disjoint class check for SNIK took 4.853675603866577s
Consistency | Check Misplaced properties for SNIK took 6.403146505355835s
Consistency | Misplaced classes for SNIK took 10.539919137954712s
Consistency | Check Ontology hijacking for SNIK took 8.339211225509644s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.2974340915679932s
Consistency | Check Invalid usage of undefined properties for SNIK took 11.442560911178589s
Conciseness | Check Extensional conciseness for SNIK took 0.15170979499816895s
Conciseness | Check Intensional conciseness for SNIK took 12.764761924743652s
Security | Sign check for SNIK took 7.2933349609375s
Availability | Check URIs Dereferenciability for SNIK took 1873.9488043785095s
Completeness | Calculation of interlinking completeness for SNIK took 0.3129417896270752s
Reputation | Calculation of the PageRank for SNIK took 0.021923303604125977s
Interlinking | Calculation of Degree of Connection for SNIK took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for SNIK took 9.202957153320312e-05s
Interoperability | Check the re-using of existing vocabs for SNIK took 1.6689300537109375e-06s
Believability | Calculation of trust value for SNIK took 1.2159347534179688e-05s
INFO | --- Analysis for snik took 2346.3918147087097s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.458427429199219e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.2630155086517334s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.020659923553466797s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 2.9802322387695312e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 1.1682510375976562e-05s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 2.8351426124572754s
Availability | SPARQL endpoint availability check for SocialLink took 1.5766515731811523s
Availability | VoID file availability check for SocialLink took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for SocialLink took 0.25421905517578125s
Reputation | Calculation of the PageRank for SocialLink took 0.020709753036499023s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.176399230957031e-05s
Believability | Calculation of trust value for SocialLink took 7.3909759521484375e-06s
INFO | --- Analysis for SocialLink took 5.679355621337891s
Availability | SPARQL endpoint availability check for SocialLink took 5.173683166503906e-05s
Availability | VoID file availability check for SocialLink took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for SocialLink took 0.25261664390563965s
Reputation | Calculation of the PageRank for SocialLink took 0.021901369094848633s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for SocialLink took 2.956390380859375e-05s
Believability | Calculation of trust value for SocialLink took 1.1682510375976562e-05s
INFO | --- Analysis for sociallink took 2.8690268993377686s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 8.845329284667969e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.278104305267334s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.021015644073486328s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.001140594482421875s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 4.172325134277344e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 7.867813110351562e-06s
INFO | --- Analysis for SocialRoles took 20.36072039604187s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.264202356338501s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0007710456848144531s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 16.654539823532104s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.42900753021240234s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.15521955490112305s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.5113201141357422s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.3300516605377197s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.15485882759094238s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.3039672374725342s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.08173036575317383s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.09305763244628906s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.7219507694244385s
License | MR license check for Social Semantic Web Thesaurus took 0.08773064613342285s
License | HR license check for Social Semantic Web Thesaurus took 0.10527825355529785s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.09899377822875977s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.09174251556396484s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.1715404987335205s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.09239768981933594s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.09161090850830078s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.087615966796875s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.530378580093384s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 0.00010776519775390625s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.09454894065856934s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.09472775459289551s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.08773446083068848s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.10062503814697266s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.0964040756225586s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.1728048324584961s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.18408775329589844s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.8068039417266846s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 0.7114758491516113s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.09032917022705078s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.08739566802978516s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.0794987678527832s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.44643068313598633s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012336254119873047s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.08659195899963379s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.29059720039367676s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.08590364456176758s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.0794525146484375s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.5226233005523682s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.0001552104949951172s
Security | Sign check for Social Semantic Web Thesaurus took 0.08715605735778809s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 91.5670382976532s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.24941110610961914s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020738601684570312s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0006799697875976562s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 0.00010228157043457031s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 0.7364330291748047s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 284.7645893096924s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3398778438568115s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.00045418739318847656s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 169.18650770187378s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9738340377807617s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.394856452941895s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 14.48589015007019s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.16927003860474s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.002957344055176s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2716507911682129s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.128351449966431s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.32369208335876465s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20818495750427246s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.2252368927002s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20639276504516602s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.1678831577301025s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.8052191734313965s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4507875442504883s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20117759704589844s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.23702645301818848s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.38846492767334s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 6.246566772460938e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19333124160766602s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21075773239135742s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.40046143531799316s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3947741985321045s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.947600841522217s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4586069583892822s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2572486400604248s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 155.5240478515625s
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.1835029125213623s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4217844009399414s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3985898494720459s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 46.29720115661621s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.674173593521118s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.5752997398376465s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19677066802978516s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 87.39175057411194s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.404742002487183s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 38.3645122051239s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.4325616359710693s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 88.7508590221405s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.7161078453063965s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5517315864562988s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.1830410957336426s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 12.898964166641235s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9427444934844971s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.021599769592285156s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.00543212890625e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Soil_maps took 2461.524950504303s
Availability | SPARQL endpoint availability check for terrorrist ontology took 4.291534423828125e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.681483268737793s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.023004531860351562s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.409385681152344e-05s
Believability | Calculation of trust value for terrorrist ontology took 1.1444091796875e-05s
INFO | --- Analysis for somya_omer took 3.7577385902404785s
Availability | SPARQL endpoint availability check for Sonclubcx took 5.173683166503906e-05s
Availability | VoID file availability check for Sonclubcx took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.25119543075561523s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.1920928955078125e-05s
Believability | Calculation of trust value for Sonclubcx took 1.1205673217773438e-05s
INFO | --- Analysis for sonclubcx took 4.845077753067017s
Availability | SPARQL endpoint availability check for SORS took 8.559226989746094e-05s
Availability | VoID file availability check for SORS took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for SORS took 0.6748151779174805s
Reputation | Calculation of the PageRank for SORS took 0.022674083709716797s
Interlinking | Calculation of Degree of Connection for SORS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for SORS took 5.7697296142578125e-05s
Believability | Calculation of trust value for SORS took 8.106231689453125e-06s
INFO | --- Analysis for sors took 13.405622243881226s
Availability | SPARQL endpoint availability check for Soudy České republiky took 6.29425048828125e-05s
Availability | VoID file availability check for Soudy České republiky took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.24969077110290527s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.021575450897216797s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 3.409385681152344e-05s
Believability | Calculation of trust value for Soudy České republiky took 1.239776611328125e-05s
INFO | --- Analysis for soudy--esk--republiky took 3.7866551876068115s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.363059997558594e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.2589104175567627s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.02270364761352539s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0008177757263183594s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 0.00010561943054199219s
Believability | Calculation of trust value for southampton-ac-uk took 1.3113021850585938e-05s
INFO | --- Analysis for southampton-ac-uk took 3.700517416000366s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 6.095591068267822s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.24617552757263184s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 5.4836273193359375e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 13.048930883407593s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.553794860839844e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.4627950191497803s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.24583959579467773s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020386934280395508s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 8.96453857421875e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 6.4373016357421875e-06s
INFO | --- Analysis for southampton-ecs-eprints took 4.688019752502441s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.49057769775390625s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.00023746490478515625s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 157.9099280834198s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.2076201438903809s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.2338314056396484s
Interoperability | New terms check for Spanish Linguistic Datasets took 2.974318265914917s
Versatility | Languages check for Spanish Linguistic Datasets took 44.948817014694214s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.1503076553344727s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.13995862007141113s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.2516477108001709s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.26857686042785645s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.27048301696777344s
License | MR license check for Spanish Linguistic Datasets took 0.26534056663513184s
License | HR license check for Spanish Linguistic Datasets took 0.35528111457824707s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.25834226608276367s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.3196547031402588s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.5123317241668701s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.2573554515838623s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.2755887508392334s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.247114896774292s
Performance | Throughput check for Spanish Linguistic Datasets took 11.970405101776123s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 7.2479248046875e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.27795863151550293s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.27591896057128906s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2704503536224365s
Interlinking | skos check for Spanish Linguistic Datasets took 0.21288180351257324s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.26843762397766113s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5383541584014893s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5443508625030518s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 58.22875237464905s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.2513270378112793s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.25829100608825684s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.2614750862121582s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.9111623764038086s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.01042795181274414s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.5677313804626465s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.24861407279968262s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.583202123641968s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.272157192230225s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 44.89505195617676s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.5386476516723633s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.641764879226685s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.84713077545166s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.2799222469329834s
Security | Sign check for Spanish Linguistic Datasets took 0.2934086322784424s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 15.8263418674469s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.4155304431915283s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.02071237564086914s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0006954669952392578s
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 1.9073486328125e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 1.1682510375976562e-05s
INFO | --- Analysis for spanish-linguistic-datasets took 415.6301670074463s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.08708381652832031s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.27446722984313965s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020157337188720703s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.6253204345703125e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 1.2159347534179688e-05s
INFO | --- Analysis for sparql-endpoint-status took 2.8517024517059326s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 8.893013000488281e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.27454566955566406s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.020997285842895508s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 3.743171691894531e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 1.3113021850585938e-05s
INFO | --- Analysis for spc-publikovan--s-kl took 2.857179880142212s
Availability | SPARQL endpoint availability check for SPQR took 4.220008850097656e-05s
Availability | VoID file availability check for SPQR took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for SPQR took 0.2569708824157715s
Reputation | Calculation of the PageRank for SPQR took 0.021519899368286133s
Interlinking | Calculation of Degree of Connection for SPQR took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SPQR took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for SPQR took 3.457069396972656e-05s
Believability | Calculation of trust value for SPQR took 7.3909759521484375e-06s
INFO | --- Analysis for spqr took 2.794461250305176s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 8.559226989746094e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.27695631980895996s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.702278137207031e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 1.1682510375976562e-05s
INFO | --- Analysis for springernaturescigraph took 2.909588575363159s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.863739013671875e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.24918270111083984s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.020322084426879883s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.1444091796875e-05s
INFO | --- Analysis for srcmf took 7.7145469188690186s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.28720879554748535s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0006630420684814453s
Extra | Recovery of all triples for Lexicon of Syntactic and Semantic Framework took 1.379993200302124s
Performance | Total latancy measurement for Lexicon of Syntactic and Semantic Framework took 1.7942745685577393s
Amount of data | Number of triples check for Lexicon of Syntactic and Semantic Framework took 0.3541140556335449s
Interoperability | New terms check for Lexicon of Syntactic and Semantic Framework took 1.664923906326294s
Versatility | Languages check for Lexicon of Syntactic and Semantic Framework took 0.3279540538787842s
Interpretability | Number of blank nodes check for Lexicon of Syntactic and Semantic Framework took 0.22725558280944824s
Security | Check HTTPS for Lexicon of Syntactic and Semantic Framework took 0.21813297271728516s
Interpretability | RDF structures check for Lexicon of Syntactic and Semantic Framework took 0.33151769638061523s
Versatility | Serialization formats check for Lexicon of Syntactic and Semantic Framework took 0.2635021209716797s
Availability | RDF dump link check for Lexicon of Syntactic and Semantic Framework took 0.2647275924682617s
License | MR license check for Lexicon of Syntactic and Semantic Framework took 0.2619471549987793s
License | HR license check for Lexicon of Syntactic and Semantic Framework took 0.2737390995025635s
Amount of data | Number of property check for Lexicon of Syntactic and Semantic Framework took 0.44586730003356934s
Understandability | Number of label check for Lexicon of Syntactic and Semantic Framework took 0.443554162979126s
Understandability | URI regex check for Lexicon of Syntactic and Semantic Framework took 0.6318812370300293s
Understandability | Vocabs check for Lexicon of Syntactic and Semantic Framework took 0.14803743362426758s
Verifiability | Authors check for Lexicon of Syntactic and Semantic Framework took 0.1644890308380127s
Verifiability | Publishers check for Lexicon of Syntactic and Semantic Framework took 0.3971085548400879s
Performance | Throughput check for Lexicon of Syntactic and Semantic Framework took 11.783970355987549s
Amount of data | Check the number of entities for Lexicon of Syntactic and Semantic Framework took 7.152557373046875e-05s
Verifiability | Contribs. check for Lexicon of Syntactic and Semantic Framework took 0.36811327934265137s
Interlinking | sameAs chians check for Lexicon of Syntactic and Semantic Framework took 0.15306544303894043s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.43321871757507324s
Interlinking | skos check for Lexicon of Syntactic and Semantic Framework took 0.15279769897460938s
Timeliness | dataset update frequency check for Lexicon of Syntactic and Semantic Framework took 0.29802727699279785s
Currency | Creation date check for Lexicon of Syntactic and Semantic Framework took 0.4417531490325928s
Currency | Modification date check for Lexicon of Syntactic and Semantic Framework took 0.5835464000701904s
Rep.Conc. | URIs length for Lexicon of Syntactic and Semantic Framework took 0.7265768051147461s
Interoperability | New vocabularies check for Lexicon of Syntactic and Semantic Framework took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Lexicon of Syntactic and Semantic Framework took 0.3712761402130127s
Accuracy | Check Functional Property for Lexicon of Syntactic and Semantic Framework took 0.2549271583557129s
Accuracy | Check Inverse Functional Property for Lexicon of Syntactic and Semantic Framework took 0.31256723403930664s
Accuracy | Check Empty annotation labels for Lexicon of Syntactic and Semantic Framework took 0.29112911224365234s
Accuracy | Check White space in annotation for Lexicon of Syntactic and Semantic Framework took 0.0003075599670410156s
Accuracy | Check Datatype consistency for Lexicon of Syntactic and Semantic Framework took 0.035565853118896484s
Consistency | Disjoint class check for Lexicon of Syntactic and Semantic Framework took 0.15759778022766113s
Consistency | Check Misplaced properties for Lexicon of Syntactic and Semantic Framework took 0.555168628692627s
Consistency | Misplaced classes for Lexicon of Syntactic and Semantic Framework took 0.4115738868713379s
Consistency | Check Ontology hijacking for Lexicon of Syntactic and Semantic Framework took 1.5355844497680664s
Consistency | Check Invalid usage of undefined classes for Lexicon of Syntactic and Semantic Framework took 1.3070621490478516s
Consistency | Check Invalid usage of undefined properties for Lexicon of Syntactic and Semantic Framework took 1.5885417461395264s
Conciseness | Check Extensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.019510984420776367s
Conciseness | Check Intensional conciseness for Lexicon of Syntactic and Semantic Framework took 0.2700028419494629s
Security | Sign check for Lexicon of Syntactic and Semantic Framework took 0.16301178932189941s
Availability | Check URIs Dereferenciability for Lexicon of Syntactic and Semantic Framework took 460.5332820415497s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.3478386402130127s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.021845102310180664s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 6.008148193359375e-05s
Interoperability | Check the re-using of existing vocabs for Lexicon of Syntactic and Semantic Framework took 1.1920928955078125e-06s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 1.2636184692382812e-05s
INFO | --- Analysis for ssf took 510.4919285774231s
Availability | SPARQL endpoint availability check for SSF took 4.839897155761719e-05s
Availability | VoID file availability check for SSF took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for SSF took 0.27062535285949707s
Reputation | Calculation of the PageRank for SSF took 0.020340681076049805s
Interlinking | Calculation of Degree of Connection for SSF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SSF took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for SSF took 3.147125244140625e-05s
Believability | Calculation of trust value for SSF took 1.3113021850585938e-05s
INFO | --- Analysis for ssf-lexicon took 3.3402631282806396s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 5.316734313964844e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.2728276252746582s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.020253658294677734s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.001661062240600586s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 6.604194641113281e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 1.1205673217773438e-05s
INFO | --- Analysis for st-andrews-resource-lists took 2.657229423522949s
Availability | SPARQL endpoint availability check for STAC took 4.076957702636719e-05s
Availability | VoID file availability check for STAC took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for STAC took 0.27553606033325195s
Reputation | Calculation of the PageRank for STAC took 0.020331382751464844s
Interlinking | Calculation of Degree of Connection for STAC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for STAC took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for STAC took 3.075599670410156e-05s
Believability | Calculation of trust value for STAC took 1.1444091796875e-05s
INFO | --- Analysis for stac took 2.8438467979431152s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 4.100799560546875e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.0012745857238769531s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.26435256004333496s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.020998716354370117s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 2.9325485229492188e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 1.239776611328125e-05s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 2.942737579345703s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 8.749961853027344e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.2623414993286133s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020518779754638672s
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.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.933906555175781e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 9.298324584960938e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 3.483987331390381s
Availability | SPARQL endpoint availability check for Stammbuch took 8.702278137207031e-05s
Availability | VoID file availability check for Stammbuch took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.2533295154571533s
Reputation | Calculation of the PageRank for Stammbuch took 0.020678043365478516s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 3.266334533691406e-05s
Believability | Calculation of trust value for Stammbuch took 1.2636184692382812e-05s
INFO | --- Analysis for Stammbuch took 2.308579206466675s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.1614735126495361s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.23178720474243164s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.022902488708496094s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010585784912109375s
Believability | Calculation of trust value for statistics.data.gov.uk took 1.0013580322265625e-05s
INFO | --- Analysis for statistics-data-gov-uk took 4.392450332641602s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 4.291534423828125e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.26655030250549316s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.020565032958984375s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 3.170967102050781e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 1.1682510375976562e-05s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.9082486629486084s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.2640819549560547s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.022569656372070312s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00010967254638671875s
Believability | Calculation of trust value for statusnet-1w6-org took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-1w6-org took 3.803184747695923s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.2539694309234619s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.02025890350341797s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.341934204101562e-05s
Believability | Calculation of trust value for statusnet-20100-org took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-20100-org took 2.4247124195098877s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.004446268081665039s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.25829124450683594s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 7.128715515136719e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.717752456665039s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.2543666362762451s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.02080988883972168s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 9.369850158691406e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.432699203491211s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0009815692901611328s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.2848682403564453s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 0.00010132789611816406s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-belfalas-org took 2.5059335231781006s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 6.818771362304688e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.26081156730651855s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.02183246612548828s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0008409023284912109s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00012040138244628906s
Believability | Calculation of trust value for statusnet-bka-li took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-bka-li took 12.515002012252808s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.26393651962280273s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02100205421447754s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 4.696846008300781e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.4305036067962646s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.2707502841949463s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.02216958999633789s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.9591064453125e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-ced117-net took 4.126114845275879s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.25522947311401367s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.0217745304107666s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0009784698486328125s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 6.079673767089844e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.5432045459747314s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.250119686126709s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020914077758789062s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011301040649414062s
Believability | Calculation of trust value for statusnet-chromic-org took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-chromic-org took 2.4748170375823975s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 8.96453857421875e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.2544682025909424s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.021045923233032227s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 8.58306884765625e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-cooleysekula-net took 5.758492708206177s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.2756493091583252s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.02081918716430664s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 6.008148193359375e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-coreyavis-com took 2.3820559978485107s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 0.000110626220703125s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.2608315944671631s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.020616769790649414s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0008141994476318359s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 7.581710815429688e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.0814127922058105s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.9114227294921875e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.2520291805267334s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.020303010940551758s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010085105895996094s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.4663162231445312s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 5.412101745605469e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.2593996524810791s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.020658016204833984s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.175041198730469e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.406494617462158s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.23555874824523926s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.020323753356933594s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.7220458984375e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-doomicile-de took 3.124047040939331s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.2783215045928955s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.0558319091796875e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-dtdns-net took 22.379429817199707s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.2427353858947754s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020833730697631836s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.838539123535156e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-equestriarp-net took 2.32059383392334s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.28563785552978516s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.02200627326965332s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.295608520507812e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 5.888938903808594e-05s
INFO | --- Analysis for statusnet-exdc-net took 2.5097014904022217s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.25635409355163574s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.918212890625e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-fcac-com took 22.2741961479187s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 8.893013000488281e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.02373647689819336s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.2623715400695801s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.02240133285522461s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.507469177246094e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-fcestrada-com took 3.124419689178467s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.24897003173828125s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020483016967773438s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00018405914306640625s
Believability | Calculation of trust value for statusnet-fragdev-com took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-fragdev-com took 3.217977285385132s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 8.726119995117188e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.2350614070892334s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.020850181579589844s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 8.177757263183594e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-freelish-us took 2.392987012863159s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 5.340576171875e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.24763035774230957s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.020962238311767578s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010704994201660156s
Believability | Calculation of trust value for statusnet-gegeweb-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-gegeweb-org took 2.4304726123809814s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 9.369850158691406e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.28925323486328125s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.747245788574219e-05s
Believability | Calculation of trust value for statusnet-glou-org took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-glou-org took 2.5856382846832275s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 6.461143493652344e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.00038909912109375s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.24338173866271973s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020102500915527344s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00012135505676269531s
Believability | Calculation of trust value for statusnet-gomertronic-com took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.325113534927368s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 9.393692016601562e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.243149995803833s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.021231412887573242s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00012826919555664062s
Believability | Calculation of trust value for statusnet-hackerposse-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.827702045440674s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.23206615447998047s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.022330284118652344s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 5.5789947509765625e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-hii-co-il took 3.9579427242279053s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 6.818771362304688e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.24433398246765137s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.020597219467163086s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.72747802734375e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 2.683272361755371s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 8.559226989746094e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.011919498443603516s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.2710080146789551s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.021494626998901367s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.29425048828125e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-imirhil-fr took 2.5232903957366943s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.27467942237854004s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.020810604095458984s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.029273986816406e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-integralblue-com took 2.555140256881714s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.2622251510620117s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.02195572853088379s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.435943603515625e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.366108179092407s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.24684739112854004s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011610984802246094s
Believability | Calculation of trust value for statusnet-jonkman-ca took 5.4836273193359375e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 3.2595720291137695s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.24216222763061523s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020886659622192383s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.226799011230469e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-kaimi-cc took 2.4059505462646484s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0011353492736816406s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.27495360374450684s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.020347118377685547s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 4.696846008300781e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.3379874229431152s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.24926376342773438s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.021561384201049805s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 4.7206878662109375e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-kenzoid-com took 3.329362392425537s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 8.535385131835938e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.26220083236694336s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020960569381713867s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.534027099609375e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-keuser-fr took 2.326986074447632s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.25580263137817383s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.02158331871032715s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.9591064453125e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.4433982372283936s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 9.703636169433594e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.24571871757507324s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.020382404327392578s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.008148193359375e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-lebsanft-org took 2.670358180999756s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 8.535385131835938e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.26425933837890625s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020676136016845703s
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.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.393692016601562e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.6364283561706543s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 9.965896606445312e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.251056432723999s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020163297653198242s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011086463928222656s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.33597993850708s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.2370917797088623s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.0202486515045166s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.364418029785156e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-ludost-net took 3.69326114654541s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.2565159797668457s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.560585021972656e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-lydiastench-com took 2.3441507816314697s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 5.841255187988281e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.2817871570587158s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.020624160766601562s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.364418029785156e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.4820640087127686s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.2708742618560791s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.021105289459228516s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.0001456737518310547s
Believability | Calculation of trust value for statusnet-macno-org took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-macno-org took 2.441511631011963s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 8.440017700195312e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.2329273223876953s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.365776062011719e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.4841792583465576s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.2644612789154053s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020316600799560547s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.821487426757812e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-maymay-net took 41.76984906196594s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 8.845329284667969e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.2614290714263916s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.02112436294555664s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00016498565673828125s
Believability | Calculation of trust value for statusnet-morphtown-de took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-morphtown-de took 2.3692684173583984s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 8.368492126464844e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.25457239151000977s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.020832061767578125s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.989738464355469e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.430976629257202s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 8.463859558105469e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.2444608211517334s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.435943603515625e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.296295642852783s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.25385332107543945s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.173683166503906e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-my-status-tk took 2.3815622329711914s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.2525150775909424s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.020250320434570312s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00010561943054199219s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.4186959266662598s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 5.435943603515625e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.2589738368988037s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.021033048629760742s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 6.175041198730469e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.6547176837921143s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 8.463859558105469e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.27510857582092285s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.02055644989013672s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.151199340820312e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-otbm-fr took 2.528385877609253s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.2635376453399658s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.022319793701171875s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.535385131835938e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.5125277042388916s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 8.630752563476562e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.2615535259246826s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.022233963012695312s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 5.1021575927734375e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-panda-id-au took 3.7201147079467773s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 0.00015735626220703125s
Availability | VoID file availability check for statusnet-piana-eu took 0.0003437995910644531s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.2728450298309326s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.02082514762878418s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.822845458984375e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-piana-eu took 2.4277007579803467s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.274630069732666s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.0206606388092041s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.963180541992188e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-planet-libre-org took 2.521331787109375s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 5.7697296142578125e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.2460014820098877s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.022521018981933594s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0010349750518798828s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00025534629821777344s
Believability | Calculation of trust value for statusnet-postblue-info took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-postblue-info took 2.6700706481933594s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.2618837356567383s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.020307540893554688s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 7.05718994140625e-05s
Believability | Calculation of trust value for statusnet-progval-net took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-progval-net took 2.441659927368164s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 8.630752563476562e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.24323749542236328s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020596981048583984s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.000118255615234375s
Believability | Calculation of trust value for statusnet-qdnx-org took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-qdnx-org took 2.8728301525115967s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.24873805046081543s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020951509475708008s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.103515625e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-qth-fr took 15.346765756607056s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 0.00010561943054199219s
Availability | VoID file availability check for statusnet-quitter-se took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.23569273948669434s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.02027750015258789s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00022459030151367188s
Believability | Calculation of trust value for statusnet-quitter-se took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-quitter-se took 2.5641965866088867s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 8.630752563476562e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.27412939071655273s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020273447036743164s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010037422180175781s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.7494077682495117s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 9.250640869140625e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.24770212173461914s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.602836608886719e-05s
Believability | Calculation of trust value for statusnet-recit-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-recit-org took 4.358762264251709s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 5.9604644775390625e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.2788379192352295s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.022072792053222656s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00014495849609375s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-russwurm-org took 3.1488518714904785s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 9.202957153320312e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.2816479206085205s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.022058486938476562s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0008127689361572266s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.106231689453125e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-samnoble-org took 4.871466875076294s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.2589559555053711s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.344650268554688e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.428842782974243s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.2705366611480713s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.020557641983032227s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 0.00010156631469726562s
Believability | Calculation of trust value for statusnet-scoffoni-net took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.3834028244018555s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.2847609519958496s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.890296936035156e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-sebseb01-net took 2.46366810798645s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 8.559226989746094e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.2772023677825928s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020624876022338867s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0008289813995361328s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 8.058547973632812e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-shnoulle-net took 3.20357608795166s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 9.226799011230469e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0003695487976074219s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.28159022331237793s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.0202176570892334s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00020813941955566406s
Believability | Calculation of trust value for statusnet-skilledtests-com took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 2.8894782066345215s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 8.392333984375e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2513580322265625s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.022729873657226562s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010442733764648438s
Believability | Calculation of trust value for statusnet-somsants-net took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-somsants-net took 2.338884115219116s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.2493293285369873s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.022247314453125s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.0001385211944580078s
Believability | Calculation of trust value for statusnet-soucy-cc took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-soucy-cc took 2.4540603160858154s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.27338647842407227s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.020357608795166016s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 5.936622619628906e-05s
Believability | Calculation of trust value for statusnet-spip-org took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-spip-org took 3.2899539470672607s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.2532994747161865s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.29425048828125e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-spraci-org took 2.436344861984253s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.2742910385131836s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00012230873107910156s
Believability | Calculation of trust value for statusnet-ssweeny-net took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-ssweeny-net took 5.186753511428833s
Availability | SPARQL endpoint availability check for statusnet-status-net took 8.606910705566406e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.28626489639282227s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020194053649902344s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00021958351135253906s
Believability | Calculation of trust value for statusnet-status-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-status-net took 3.5432331562042236s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 6.818771362304688e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2540721893310547s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.022978544235229492s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.3882598876953125e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.3956375122070312s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.25722670555114746s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.021890878677368164s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 0.0001125335693359375s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.46425461769104s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 8.654594421386719e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.26307034492492676s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.0001327991485595703s
Believability | Calculation of trust value for statusnet-thelovebug-org took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-thelovebug-org took 2.4396491050720215s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 8.7738037109375e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.27324581146240234s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.021390438079833984s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 8.511543273925781e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-thornton2-com took 5.147617340087891s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 6.389617919921875e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.24680829048156738s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.02069091796875s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00010919570922851562s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.584141254425049s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.25385427474975586s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020365476608276367s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 4.00543212890625e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-tl1n-com took 3.493598461151123s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 8.916854858398438e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.29246091842651367s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.020501136779785156s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.651878356933594e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 5.125999450683594e-05s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.592660427093506s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.2777369022369385s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.021019935607910156s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 4.124641418457031e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.7154722213745117s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.124641418457031e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.2498185634613037s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.02080225944519043s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0009698867797851562s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 3.62396240234375e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 1.239776611328125e-05s
INFO | --- Analysis for steak took 2.6636478900909424s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 4.220008850097656e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.23545551300048828s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.435943603515625e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 1.1444091796875e-05s
INFO | --- Analysis for stitch-rameau took 3.958004951477051s
Availability | SPARQL endpoint availability check for Stone Tech Square took 1.1737139225006104s
Availability | VoID file availability check for Stone Tech Square took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.27397680282592773s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.02256298065185547s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.33514404296875e-05s
Believability | Calculation of trust value for Stone Tech Square took 1.1920928955078125e-05s
INFO | --- Analysis for stone-tech-square-data took 5.353981256484985s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 8.58306884765625e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.25488734245300293s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.020863056182861328s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 3.314018249511719e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 1.239776611328125e-05s
INFO | --- Analysis for strukturovan--popisy-z-fda took 2.8935303688049316s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.45314478874206543s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0007410049438476562s
Extra | Recovery of all triples for STW Thesaurus for Economics took 30.41720485687256s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.1032648086547852s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.6959364414215088s
Interoperability | New terms check for STW Thesaurus for Economics took 1.5305871963500977s
Versatility | Languages check for STW Thesaurus for Economics took 1.5474615097045898s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.5042650699615479s
Security | Check HTTPS for STW Thesaurus for Economics took 0.16364789009094238s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.218705415725708s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.24382472038269043s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.23139595985412598s
License | MR license check for STW Thesaurus for Economics took 0.21352887153625488s
License | HR license check for STW Thesaurus for Economics took 2.5548298358917236s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.19241571426391602s
Understandability | Number of label check for STW Thesaurus for Economics took 0.6803879737854004s
Understandability | URI regex check for STW Thesaurus for Economics took 0.4602220058441162s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.2237224578857422s
Verifiability | Authors check for STW Thesaurus for Economics took 0.23212742805480957s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.21448206901550293s
Performance | Throughput check for STW Thesaurus for Economics took 10.957649230957031s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7022311687469482s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.20840096473693848s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.217604398727417s
Interlinking | skos check for STW Thesaurus for Economics took 0.2993006706237793s
Interlinking | skos check for STW Thesaurus for Economics took 0.31969571113586426s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.20134544372558594s
Currency | Creation date check for STW Thesaurus for Economics took 0.4765901565551758s
Currency | Modification date check for STW Thesaurus for Economics took 0.4458186626434326s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 7.0086894035339355s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 3.21366286277771s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.2326045036315918s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.23620152473449707s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.23212432861328125s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 8.738095045089722s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0473682880401611s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.3407340049743652s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.23794245719909668s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.2417941093444824s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 1.7834677696228027s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.3613741397857666s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.358248233795166s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6192913055419922s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.2224876880645752s
Security | Sign check for STW Thesaurus for Economics took 0.2560153007507324s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 2505.111832380295s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 1.1651012897491455s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.5979504585266113s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00011754035949707031s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 2.928081512451172s
Believability | Calculation of trust value for STW Thesaurus for Economics took 1.1920928955078125e-05s
INFO | --- Analysis for stw-thesaurus-for-economics took 2620.656861782074s
Availability | SPARQL endpoint availability check for SudershanTech took 4.744529724121094e-05s
Availability | VoID file availability check for SudershanTech took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.67138671875s
Reputation | Calculation of the PageRank for SudershanTech took 0.020596981048583984s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 2.9325485229492188e-05s
Believability | Calculation of trust value for SudershanTech took 7.152557373046875e-06s
INFO | --- Analysis for SudershanTech took 3.993712902069092s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.8941068649291992s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0007383823394775391s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.6935837268829346s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.02075505256652832s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.863739013671875e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 1.2874603271484375e-05s
INFO | --- Analysis for sudocfr took 25.829399347305298s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 1.0360777378082275s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0006749629974365234s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 23.78328227996826s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.6542000770568848s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.439455270767212s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 2.7960009574890137s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 3.0665628910064697s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.1425933837890625s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5248749256134033s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5311200618743896s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5317392349243164s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5583136081695557s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 7.06386661529541s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.5759882926940918s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.6981377601623535s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.050318717956543s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5282046794891357s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.548102855682373s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5747971534729004s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.707653284072876s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 6.937980651855469e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5450994968414307s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5528438091278076s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5976924896240234s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5601820945739746s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5643348693847656s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.0990030765533447s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.1149592399597168s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 35.67334604263306s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5460362434387207s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5364170074462891s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.4975700378417969s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 2.959280490875244s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.381824254989624s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.5720598697662354s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 30.7291841506958s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.142883539199829s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.40011620521545s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 19.83205008506775s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 3.020242214202881s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.5968265533447266s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5617363452911377s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4400.0287663936615s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 3.1270952224731445s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.020966768264770508s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 7.915496826171875e-05s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 1.430511474609375e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 1.239776611328125e-05s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 7961.068476200104s
Availability | SPARQL endpoint availability check for Surge Radio took 9.655952453613281e-05s
Availability | VoID file availability check for Surge Radio took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.28531360626220703s
Reputation | Calculation of the PageRank for Surge Radio took 0.02064800262451172s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.654594421386719e-05s
Believability | Calculation of trust value for Surge Radio took 1.1682510375976562e-05s
INFO | --- Analysis for surge-radio took 5.793574094772339s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 9.894371032714844e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.3461277484893799s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.0210726261138916s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.170967102050781e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 1.2874603271484375e-05s
INFO | --- Analysis for SWAT took 206.99800443649292s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 8.678436279296875e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.47975635528564453s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.7571449279785156s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020734310150146484s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 7.43865966796875e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 1.239776611328125e-05s
INFO | --- Analysis for swedish-open-cultural-heritage took 7.2844343185424805s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.094935417175293s
Availability | VoID file availability check for SweFN-RDF took 0.0012056827545166016s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.29434919357299805s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.022329092025756836s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.7670135498046875e-05s
Believability | Calculation of trust value for SweFN-RDF took 1.0967254638671875e-05s
INFO | --- Analysis for swefn-rdf took 6.180694818496704s
Availability | SPARQL endpoint availability check for SwetoDblp took 9.059906005859375e-05s
Availability | VoID file availability check for SwetoDblp took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.23694777488708496s
Reputation | Calculation of the PageRank for SwetoDblp took 0.020760297775268555s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.7670135498046875e-05s
Believability | Calculation of trust value for SwetoDblp took 1.049041748046875e-05s
INFO | --- Analysis for sweto-dblp took 23.254251718521118s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.5652735233306885s
Availability | VoID file availability check for Swift Vocabulary took 0.0005450248718261719s
Extra | Recovery of all triples for Swift Vocabulary took 2.2059106826782227s
Performance | Total latancy measurement for Swift Vocabulary took 1.0704221725463867s
Amount of data | Number of triples check for Swift Vocabulary took 0.23104023933410645s
Interoperability | New terms check for Swift Vocabulary took 1.5963709354400635s
Versatility | Languages check for Swift Vocabulary took 0.2389371395111084s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.24209952354431152s
Interpretability | RDF structures check for Swift Vocabulary took 0.25324034690856934s
Versatility | Serialization formats check for Swift Vocabulary took 0.20571613311767578s
Availability | RDF dump link check for Swift Vocabulary took 0.20729637145996094s
License | MR license check for Swift Vocabulary took 0.2099616527557373s
License | HR license check for Swift Vocabulary took 0.2421863079071045s
Amount of data | Number of property check for Swift Vocabulary took 0.2492532730102539s
Understandability | Number of label check for Swift Vocabulary took 0.2533457279205322s
Understandability | URI regex check for Swift Vocabulary took 0.46024012565612793s
Understandability | Vocabs check for Swift Vocabulary took 0.25316810607910156s
Verifiability | Authors check for Swift Vocabulary took 0.2598435878753662s
Verifiability | Publishers check for Swift Vocabulary took 0.23070144653320312s
Performance | Throughput check for Swift Vocabulary took 11.73091745376587s
Amount of data | Check the number of entities for Swift Vocabulary took 8.273124694824219e-05s
Verifiability | Contribs. check for Swift Vocabulary took 0.22912025451660156s
Interlinking | sameAs chians check for Swift Vocabulary took 0.24250411987304688s
Interlinking | skos check for Swift Vocabulary took 0.2300863265991211s
Interlinking | skos check for Swift Vocabulary took 0.22365355491638184s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.23294830322265625s
Currency | Creation date check for Swift Vocabulary took 0.4221498966217041s
Currency | Modification date check for Swift Vocabulary took 0.4896087646484375s
Rep.Conc. | URIs length for Swift Vocabulary took 0.7663283348083496s
Interoperability | New vocabularies check for Swift Vocabulary took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.246368408203125s
Accuracy | Check Functional Property for Swift Vocabulary took 0.24935388565063477s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.2408301830291748s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.383575439453125s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.001999378204345703s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.03562164306640625s
Consistency | Disjoint class check for Swift Vocabulary took 0.2248687744140625s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.5179762840270996s
Consistency | Misplaced classes for Swift Vocabulary took 0.2751467227935791s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.64223313331604s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.3409571647644043s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.6109509468078613s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.025810956954956055s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.21668791770935059s
Security | Sign check for Swift Vocabulary took 0.18611907958984375s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 1068.6003856658936s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.527198314666748s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.02129983901977539s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 8.320808410644531e-05s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 3.0994415283203125e-06s
Believability | Calculation of trust value for Swift Vocabulary took 1.4066696166992188e-05s
INFO | --- Analysis for Swift took 1120.6713421344757s
Availability | SPARQL endpoint availability check for SymbolicData took 8.702278137207031e-05s
Availability | VoID file availability check for SymbolicData took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.31127309799194336s
Reputation | Calculation of the PageRank for SymbolicData took 0.021300554275512695s
Interlinking | Calculation of Degree of Connection for SymbolicData took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 3.266334533691406e-05s
Believability | Calculation of trust value for SymbolicData took 1.3113021850585938e-05s
INFO | --- Analysis for symbolicdata took 4.6395180225372314s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 6.651878356933594e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0008008480072021484s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.6695184707641602s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020925521850585938s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.814697265625e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 1.239776611328125e-05s
INFO | --- Analysis for symptoms-in-chinese took 52.97602367401123s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.430133581161499s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0007011890411376953s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.5198662281036377s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.9460265636444092s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 52.14707350730896s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 19.24816584587097s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.20372438430786133s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 5.371562242507935s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.11160445213317871s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.4851498603820801s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.2551424503326416s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.19465851783752441s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.3517289161682129s
License | HR license check for National Digital Data Archive of Hungary (partial) took 55.11999845504761s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.5455493927001953s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 37.66685914993286s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.4311838150024414s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.20211386680603027s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.1924724578857422s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.2382955551147461s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.744365215301514s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 3.314018249511719e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.7237176895141602s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.823957920074463s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5756795406341553s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5786399841308594s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.5489745140075684s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 2.9720804691314697s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 2.9061102867126465s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 66.13103985786438s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.32491278648376465s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.22646641731262207s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0012257099151611328s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0014486312866210938s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.2158522605895996s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 45.35008239746094s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.2781691551208496s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.6543703079223633s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.3191444873809814s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 46.967851877212524s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.0018651485443115234s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.436664342880249s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.21213960647583008s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 23.581989765167236s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 10.45177674293518s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.020617246627807617s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 0.00011539459228515625s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 1.33514404296875e-05s
INFO | --- Analysis for sztaki-lod took 570.032247543335s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.00010776519775390625s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.693087100982666s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.021001577377319336s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.221366882324219e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 1.3113021850585938e-05s
INFO | --- Analysis for t4gm-info took 3.8134937286376953s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.267692565917969e-05s
Availability | VoID file availability check for tags2con delicious took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.28144097328186035s
Reputation | Calculation of the PageRank for tags2con delicious took 0.02325272560119629s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.267692565917969e-05s
Believability | Calculation of trust value for tags2con delicious took 1.2159347534179688e-05s
INFO | --- Analysis for tags2con-delicious took 44.619500398635864s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 262.67449140548706s
Availability | VoID file availability check for Taiwan geographic names took 0.00077056884765625s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.7071142196655273s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.02102828025817871s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 5.602836608886719e-05s
Believability | Calculation of trust value for Taiwan geographic names took 1.1682510375976562e-05s
INFO | --- Analysis for taiwan-geographic-names took 669.1129107475281s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 8.463859558105469e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.26963019371032715s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.020691871643066406s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.512901306152344e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 1.1682510375976562e-05s
INFO | --- Analysis for talis-openlibrary took 4.81499171257019s
Availability | SPARQL endpoint availability check for TalkBank took 8.153915405273438e-05s
Availability | VoID file availability check for TalkBank took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for TalkBank took 0.2541513442993164s
Reputation | Calculation of the PageRank for TalkBank took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for TalkBank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TalkBank took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for TalkBank took 2.9802322387695312e-05s
Believability | Calculation of trust value for TalkBank took 1.0967254638671875e-05s
INFO | --- Analysis for talkbank took 3.362299919128418s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.8335845470428467s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.26865196228027344s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.02159285545349121s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00012159347534179688s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 1.0967254638671875e-05s
INFO | --- Analysis for taxonconcept took 13.403141975402832s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 6.031990051269531e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.25846004486083984s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.022889137268066406s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 7.939338684082031e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.1444091796875e-05s
INFO | --- Analysis for taxonconcept-assets took 3.1578760147094727s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 8.606910705566406e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.2640805244445801s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.021190404891967773s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 4.863739013671875e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 1.1444091796875e-05s
INFO | --- Analysis for taxonconcept-occurences took 2.691450595855713s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.8863959312438965s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.2949981689453125s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 4.76837158203125e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 1.1920928955078125e-05s
INFO | --- Analysis for taxref-ld took 7.58353853225708s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 261.1077558994293s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0003509521484375s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.2937326431274414s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.021012306213378906s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 4.029273986816406e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.2874603271484375e-05s
INFO | --- Analysis for tcga took 539.5673031806946s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3884279727935791s
Availability | VoID file availability check for TCGA Roadmap took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.2639577388763428s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.021083354949951172s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.772445678710938e-05s
Believability | Calculation of trust value for TCGA Roadmap took 1.0251998901367188e-05s
INFO | --- Analysis for tcga-roadmap took 6.812677383422852s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.2403833866119385s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.2910611629486084s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.02136063575744629s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00011897087097167969s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for tcmgenedit_dataset took 138.39240503311157s
Availability | SPARQL endpoint availability check for TDS took 7.486343383789062e-05s
Availability | VoID file availability check for TDS took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for TDS took 0.22997808456420898s
Reputation | Calculation of the PageRank for TDS took 0.020782470703125s
Interlinking | Calculation of Degree of Connection for TDS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for TDS took 4.076957702636719e-05s
Believability | Calculation of trust value for TDS took 9.059906005859375e-06s
INFO | --- Analysis for tds took 5.869632720947266s
Availability | SPARQL endpoint availability check for TED Talks took 4.696846008300781e-05s
Availability | VoID file availability check for TED Talks took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for TED Talks took 0.25352907180786133s
Reputation | Calculation of the PageRank for TED Talks took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for TED Talks took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TED Talks took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for TED Talks took 3.123283386230469e-05s
Believability | Calculation of trust value for TED Talks took 7.62939453125e-06s
INFO | --- Analysis for ted-talks took 3.629213809967041s
Availability | SPARQL endpoint availability check for TEKORD took 4.482269287109375e-05s
Availability | VoID file availability check for TEKORD took 0.0006773471832275391s
Completeness | Calculation of interlinking completeness for TEKORD took 0.2586994171142578s
Reputation | Calculation of the PageRank for TEKORD took 0.021131515502929688s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for TEKORD took 5.269050598144531e-05s
Believability | Calculation of trust value for TEKORD took 1.0728836059570312e-05s
INFO | --- Analysis for tekord took 5.221235752105713s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 3.3160240650177s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0008056163787841797s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.2370154857635498s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.021590232849121094s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0010156631469726562s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00013303756713867188s
Believability | Calculation of trust value for Telegraphis Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for telegraphis took 9.669793844223022s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.38690185546875e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0003533363342285156s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.26555347442626953s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.02083420753479004s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.510185241699219e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 8.344650268554688e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 13.727972984313965s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.23941874504089355s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.020914554595947266s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.895148754119873s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 4.076957702636719e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 2.6485960483551025s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.021348953247070312s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0008420944213867188s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 3.266334533691406e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for terminesp took 11.440653085708618s
Availability | SPARQL endpoint availability check for Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology took 0.00039505958557128906s
Completeness | Calculation of interlinking completeness for Ontology took 0.6770048141479492s
Reputation | Calculation of the PageRank for Ontology took 0.02134990692138672s
Interlinking | Calculation of Degree of Connection for Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0010814666748046875s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.743171691894531e-05s
Believability | Calculation of trust value for Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for Terrorist_attack took 3.7132620811462402s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 8.630752563476562e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.2641944885253906s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.02069234848022461s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.170967102050781e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 9.298324584960938e-06s
INFO | --- Analysis for Terrorist_Attack_1 took 5.932178974151611s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 4.5299530029296875e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.27392053604125977s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.021126508712768555s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 3.0994415283203125e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 7.62939453125e-06s
INFO | --- Analysis for tesauro-materias-bupm took 6.5754358768463135s
Availability | SPARQL endpoint availability check for Teseo took 4.982948303222656e-05s
Availability | VoID file availability check for Teseo took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Teseo took 0.2773854732513428s
Reputation | Calculation of the PageRank for Teseo took 0.020775556564331055s
Interlinking | Calculation of Degree of Connection for Teseo took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Teseo took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Teseo took 3.457069396972656e-05s
Believability | Calculation of trust value for Teseo took 1.2636184692382812e-05s
INFO | --- Analysis for teseo took 4.73080587387085s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 4.267692565917969e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 6.402771234512329s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0220947265625s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.170967102050781e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.239776611328125e-05s
INFO | --- Analysis for Tesla_Deaths took 11.332098007202148s
Availability | SPARQL endpoint availability check for test took 4.315376281738281e-05s
Availability | VoID file availability check for test took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for test took 0.2641487121582031s
Reputation | Calculation of the PageRank for test took 0.020809650421142578s
Interlinking | Calculation of Degree of Connection for test took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for test took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for test took 2.86102294921875e-05s
Believability | Calculation of trust value for test took 7.152557373046875e-06s
INFO | --- Analysis for test took 2.7066731452941895s
Availability | SPARQL endpoint availability check for Test took 4.2438507080078125e-05s
Availability | VoID file availability check for Test took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Test took 0.2527012825012207s
Reputation | Calculation of the PageRank for Test took 0.020861148834228516s
Interlinking | Calculation of Degree of Connection for Test took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Test took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Test took 3.4332275390625e-05s
Believability | Calculation of trust value for Test took 8.58306884765625e-06s
INFO | --- Analysis for Test took 7.969139099121094s
Availability | SPARQL endpoint availability check for test-svu took 20.178900480270386s
Availability | VoID file availability check for test-svu took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for test-svu took 0.26880884170532227s
Reputation | Calculation of the PageRank for test-svu took 0.020957469940185547s
Interlinking | Calculation of Degree of Connection for test-svu took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.147125244140625e-05s
Believability | Calculation of trust value for test-svu took 1.3589859008789062e-05s
INFO | --- Analysis for test-svu took 52.496392250061035s
Availability | SPARQL endpoint availability check for Test took 4.363059997558594e-05s
Availability | VoID file availability check for Test took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for Test took 0.29118871688842773s
Reputation | Calculation of the PageRank for Test took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for Test took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Test took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Test took 3.0517578125e-05s
Believability | Calculation of trust value for Test took 7.152557373046875e-06s
INFO | --- Analysis for Test_ took 3.5794267654418945s
Availability | SPARQL endpoint availability check for xxxxx took 261.45989966392517s
Availability | VoID file availability check for xxxxx took 0.0008480548858642578s
Completeness | Calculation of interlinking completeness for xxxxx took 0.2818632125854492s
Reputation | Calculation of the PageRank for xxxxx took 0.020757675170898438s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for xxxxx took 5.1021575927734375e-05s
Believability | Calculation of trust value for xxxxx took 1.5020370483398438e-05s
INFO | --- Analysis for testee took 798.5247237682343s
Availability | SPARQL endpoint availability check for Texai Lexicon took 5.1975250244140625e-05s
Availability | VoID file availability check for Texai Lexicon took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.6966369152069092s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.020946502685546875s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 2.8848648071289062e-05s
Believability | Calculation of trust value for Texai Lexicon took 1.2874603271484375e-05s
INFO | --- Analysis for texai_lexicon took 5.787557363510132s
Availability | SPARQL endpoint availability check for tharawat magazine took 6.270408630371094e-05s
Availability | VoID file availability check for tharawat magazine took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.2657351493835449s
Reputation | Calculation of the PageRank for tharawat magazine took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00010204315185546875s
Believability | Calculation of trust value for tharawat magazine took 1.1682510375976562e-05s
INFO | --- Analysis for tharawat-magazine-com took 4.373642444610596s
Availability | SPARQL endpoint availability check for The CIARD RING took 8.177757263183594e-05s
Availability | VoID file availability check for The CIARD RING took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.6768546104431152s
Reputation | Calculation of the PageRank for The CIARD RING took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0008127689361572266s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 3.0279159545898438e-05s
Believability | Calculation of trust value for The CIARD RING took 1.2159347534179688e-05s
INFO | --- Analysis for the-ciard-ring took 3.291806221008301s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 1.4809770584106445s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.27377748489379883s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.02207159996032715s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.719329833984375e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 1.1920928955078125e-05s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 8.552656412124634s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.6462531089782715s
Availability | VoID file availability check for The European Library Open Dataset took 0.0006606578826904297s
Extra | Recovery of all triples for The European Library Open Dataset took 1.273695945739746s
Performance | Total latancy measurement for The European Library Open Dataset took 1.3514771461486816s
Amount of data | Number of triples check for The European Library Open Dataset took 30.19505286216736s
Versatility | Languages check for The European Library Open Dataset took 0.24320650100708008s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.235249996185303s
Interpretability | RDF structures check for The European Library Open Dataset took 0.2683067321777344s
Versatility | Serialization formats check for The European Library Open Dataset took 0.2388765811920166s
Availability | RDF dump link check for The European Library Open Dataset took 0.2802000045776367s
License | MR license check for The European Library Open Dataset took 0.2095203399658203s
License | HR license check for The European Library Open Dataset took 0.2206113338470459s
Amount of data | Number of property check for The European Library Open Dataset took 0.24053049087524414s
Understandability | Number of label check for The European Library Open Dataset took 0.7129065990447998s
Understandability | URI regex check for The European Library Open Dataset took 0.45728611946105957s
Understandability | Vocabs check for The European Library Open Dataset took 0.2638700008392334s
Verifiability | Authors check for The European Library Open Dataset took 0.22954487800598145s
Verifiability | Publishers check for The European Library Open Dataset took 0.22628235816955566s
Performance | Throughput check for The European Library Open Dataset took 10.891668319702148s
Amount of data | Check the number of entities for The European Library Open Dataset took 4.410743713378906e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.22544479370117188s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.27427053451538086s
Interlinking | skos check for The European Library Open Dataset took 0.27568578720092773s
Interlinking | skos check for The European Library Open Dataset took 0.24617791175842285s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.2298438549041748s
Currency | Creation date check for The European Library Open Dataset took 0.46820664405822754s
Currency | Modification date check for The European Library Open Dataset took 0.4989497661590576s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.51412796974182s
Interoperability | New vocabularies check for The European Library Open Dataset took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.24463939666748047s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 0.7746944427490234s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.027973175048828125s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.028051376342773438s
Consistency | Disjoint class check for The European Library Open Dataset took 0.2353353500366211s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.46542191505432s
Consistency | Misplaced classes for The European Library Open Dataset took 0.36376953125s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.8287205696105957s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.2921652793884277s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.518093585968018s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03260946273803711s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.29610419273376465s
Security | Sign check for The European Library Open Dataset took 0.21379590034484863s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 13.987890243530273s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.3362538814544678s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.02096724510192871s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.437301635742188e-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 7.3909759521484375e-06s
INFO | --- Analysis for the-european-library-open-dataset took 402.4024667739868s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 0.7744667530059814s
Availability | VoID file availability check for The Eurostat Linked Data took 0.00035953521728515625s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.6778490543365479s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.020752429962158203s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 9.608268737792969e-05s
Believability | Calculation of trust value for The Eurostat Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for the-eurostat-linked-data took 7.725081443786621s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 8.296966552734375e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.24807167053222656s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 3.0994415283203125e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.1205673217773438e-05s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 3.319133996963501s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 8.893013000488281e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0004215240478515625s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.2617347240447998s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.022011280059814453s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.52587890625e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.748603820800781e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 1.049041748046875e-05s
INFO | --- Analysis for the-living-lod-cloud took 51.04192304611206s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 8.082389831542969e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.2546970844268799s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.02046942710876465s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 3.0994415283203125e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 1.0967254638671875e-05s
INFO | --- Analysis for the-midi-linked-data-cloud took 3.8266336917877197s
Availability | SPARQL endpoint availability check for The View From took 0.09609270095825195s
Availability | VoID file availability check for The View From took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for The View From took 0.27975010871887207s
Reputation | Calculation of the PageRank for The View From took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for The View From took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for The View From took 8.225440979003906e-05s
Believability | Calculation of trust value for The View From took 1.1682510375976562e-05s
INFO | --- Analysis for the-view-from took 3.0318360328674316s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 1.7136471271514893s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.26306700706481934s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.147125244140625e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 9.775161743164062e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 5.811617136001587s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 1.122565507888794s
Availability | VoID file availability check for Open data of Uzbekistan took 0.001149892807006836s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.2922356128692627s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.021059513092041016s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.0040740966796875e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.0251998901367188e-05s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 7.560963869094849s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.267692565917969e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.250307559967041s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.000102996826171875s
Believability | Calculation of trust value for The Content Wrangler took 1.049041748046875e-05s
INFO | --- Analysis for thecontentwrangler-com took 2.795931100845337s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 5.316734313964844e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.23718810081481934s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020926713943481445s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 3.1948089599609375e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 1.1444091796875e-05s
INFO | --- Analysis for thesaurus-bncf took 2.806422710418701s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.267692565917969e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.2556755542755127s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.022558212280273438s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.0279159545898438e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 1.2636184692382812e-05s
INFO | --- Analysis for thesaurus-datenwissen took 2.368215560913086s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 3.159407138824463s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.25450897216796875s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.02234339714050293s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.414817810058594e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 1.2159347534179688e-05s
INFO | --- Analysis for thesaurus-w took 17.943697452545166s
Availability | SPARQL endpoint availability check for theses.fr took 8.749961853027344e-05s
Availability | VoID file availability check for theses.fr took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for theses.fr took 0.24982285499572754s
Reputation | Calculation of the PageRank for theses.fr took 0.021636247634887695s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.8160552978515625e-05s
Believability | Calculation of trust value for theses.fr took 1.1205673217773438e-05s
INFO | --- Analysis for thesesfr took 4.111419916152954s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.3392181396484375e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.24882936477661133s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.021270751953125s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.4809112548828125e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.1682510375976562e-05s
INFO | --- Analysis for Thinkphile took 2.3949530124664307s
Availability | SPARQL endpoint availability check for ThIST took 263.94228172302246s
Availability | VoID file availability check for ThIST took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for ThIST took 0.7263662815093994s
Reputation | Calculation of the PageRank for ThIST took 0.02117156982421875s
Interlinking | Calculation of Degree of Connection for ThIST took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for ThIST took 9.202957153320312e-05s
Believability | Calculation of trust value for ThIST took 7.772445678710938e-05s
INFO | --- Analysis for thist took 561.9880719184875s
Availability | SPARQL endpoint availability check for TIP took 40.03158187866211s
Availability | VoID file availability check for TIP took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for TIP took 0.27591371536254883s
Reputation | Calculation of the PageRank for TIP took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for TIP took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00011157989501953125s
Believability | Calculation of trust value for TIP took 9.775161743164062e-06s
INFO | --- Analysis for tip took 103.80833315849304s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 8.893013000488281e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0006921291351318359s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.6937053203582764s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.02200794219970703s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.457069396972656e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 1.1682510375976562e-05s
INFO | --- Analysis for TOPMODEL took 26.338937044143677s
Availability | SPARQL endpoint availability check for Tourpedia took 4.506111145019531e-05s
Availability | VoID file availability check for Tourpedia took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.26787662506103516s
Reputation | Calculation of the PageRank for Tourpedia took 0.022559642791748047s
Interlinking | Calculation of Degree of Connection for Tourpedia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Tourpedia took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 3.3855438232421875e-05s
Believability | Calculation of trust value for Tourpedia took 1.1444091796875e-05s
INFO | --- Analysis for tourpedia took 3.3110198974609375s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.339097023010254s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.2397902011871338s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.024445056915283203s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0008246898651123047s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 4.029273986816406e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 1.2159347534179688e-05s
INFO | --- Analysis for TP-data took 8.444976091384888s
Availability | SPARQL endpoint availability check for Trackloaded Linked Open Data took 2.9968979358673096s
Availability | VoID file availability check for Trackloaded Linked Open Data took 0.0005962848663330078s
Extra | Recovery of all triples for Trackloaded Linked Open Data took 2.2227838039398193s
Performance | Total latancy measurement for Trackloaded Linked Open Data took 5.26998496055603s
Amount of data | Number of triples check for Trackloaded Linked Open Data took 1.8190584182739258s
Interoperability | New terms check for Trackloaded Linked Open Data took 6.726048707962036s
Versatility | Languages check for Trackloaded Linked Open Data took 1.9701488018035889s
Interpretability | Number of blank nodes check for Trackloaded Linked Open Data took 2.1764633655548096s
Interpretability | RDF structures check for Trackloaded Linked Open Data took 1.621582269668579s
Versatility | Serialization formats check for Trackloaded Linked Open Data took 2.7264626026153564s
Availability | RDF dump link check for Trackloaded Linked Open Data took 2.4168245792388916s
License | MR license check for Trackloaded Linked Open Data took 7.87080454826355s
License | HR license check for Trackloaded Linked Open Data took 13.740498542785645s
Amount of data | Number of property check for Trackloaded Linked Open Data took 15.083552360534668s
Understandability | Number of label check for Trackloaded Linked Open Data took 7.021744966506958s
Understandability | URI regex check for Trackloaded Linked Open Data took 5.453738212585449s
Understandability | Vocabs check for Trackloaded Linked Open Data took 2.0547847747802734s
Verifiability | Authors check for Trackloaded Linked Open Data took 3.7714295387268066s
Verifiability | Publishers check for Trackloaded Linked Open Data took 2.3009915351867676s
Performance | Throughput check for Trackloaded Linked Open Data took 18.448554039001465s
Amount of data | Check the number of entities for Trackloaded Linked Open Data took 7.653236389160156e-05s
Verifiability | Contribs. check for Trackloaded Linked Open Data took 0.7061004638671875s
Interlinking | sameAs chians check for Trackloaded Linked Open Data took 1.0018658638000488s
Interlinking | skos check for Trackloaded Linked Open Data took 0.6919333934783936s
Interlinking | skos check for Trackloaded Linked Open Data took 0.7104041576385498s
Timeliness | dataset update frequency check for Trackloaded Linked Open Data took 0.5994031429290771s
Currency | Creation date check for Trackloaded Linked Open Data took 1.3698501586914062s
Currency | Modification date check for Trackloaded Linked Open Data took 1.5024139881134033s
Rep.Conc. | URIs length for Trackloaded Linked Open Data took 1.5055224895477295s
Interoperability | New vocabularies check for Trackloaded Linked Open Data took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Trackloaded Linked Open Data took 0.8621175289154053s
Consistency | Disjoint class check for Trackloaded Linked Open Data took 0.8115065097808838s
Consistency | Check Ontology hijacking for Trackloaded Linked Open Data took 0.7978405952453613s
Consistency | Check Invalid usage of undefined properties for Trackloaded Linked Open Data took 2.4404587745666504s
Conciseness | Check Extensional conciseness for Trackloaded Linked Open Data took 0.00013947486877441406s
Security | Sign check for Trackloaded Linked Open Data took 1.4840307235717773s
Completeness | Calculation of interlinking completeness for Trackloaded Linked Open Data took 0.8471999168395996s
Reputation | Calculation of the PageRank for Trackloaded Linked Open Data took 0.021378517150878906s
Interlinking | Calculation of Degree of Connection for Trackloaded Linked Open Data took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Trackloaded Linked Open Data took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Trackloaded Linked Open Data took 1.6927719116210938e-05s
Interoperability | Check the re-using of existing vocabs for Trackloaded Linked Open Data took 1.1920928955078125e-06s
Believability | Calculation of trust value for Trackloaded Linked Open Data took 1.1682510375976562e-05s
INFO | --- Analysis for trackloaded took 151.21769785881042s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 1.491105318069458s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.23938465118408203s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.020614147186279297s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.649162292480469e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 9.5367431640625e-06s
INFO | --- Analysis for traditional-korean-medicine took 5.4938859939575195s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.22223782539367676s
Availability | VoID file availability check for Traffic Scotland took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.5890100002288818s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.409385681152344e-05s
Believability | Calculation of trust value for Traffic Scotland took 5.4836273193359375e-06s
INFO | --- Analysis for traffic-scotland took 3.65333890914917s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.12215781211853027s
Availability | VoID file availability check for Transparency International Linked Data took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.262115478515625s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.02015209197998047s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010395050048828125s
Believability | Calculation of trust value for Transparency International Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for transparency-linked-data took 2.513319730758667s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.7675986289978027s
Availability | VoID file availability check for transport.data.gov.uk took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.2688751220703125s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 8.96453857421875e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 5.0067901611328125e-06s
INFO | --- Analysis for transport-data-gov-uk took 3.9860479831695557s
Availability | SPARQL endpoint availability check for OpenUpLabs Transport took 6.604194641113281e-05s
Availability | VoID file availability check for OpenUpLabs Transport took 0.00054931640625s
Completeness | Calculation of interlinking completeness for OpenUpLabs Transport took 0.27428698539733887s
Reputation | Calculation of the PageRank for OpenUpLabs Transport took 0.0218808650970459s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Transport took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Transport took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Transport took 2.8133392333984375e-05s
Believability | Calculation of trust value for OpenUpLabs Transport took 1.1205673217773438e-05s
INFO | --- Analysis for transport-openuplabs took 2.864462375640869s
Availability | SPARQL endpoint availability check for Trelios took 0.0001327991485595703s
Availability | VoID file availability check for Trelios took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Trelios took 0.2515084743499756s
Reputation | Calculation of the PageRank for Trelios took 0.021021366119384766s
Interlinking | Calculation of Degree of Connection for Trelios took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.1444091796875e-05s
Believability | Calculation of trust value for Trelios took 1.1205673217773438e-05s
INFO | --- Analysis for Trelios took 2.393693685531616s
Availability | SPARQL endpoint availability check for Twarql took 10.582350969314575s
Availability | VoID file availability check for Twarql took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for Twarql took 0.24522662162780762s
Reputation | Calculation of the PageRank for Twarql took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for Twarql took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.318092346191406e-05s
Believability | Calculation of trust value for Twarql took 1.2159347534179688e-05s
INFO | --- Analysis for twarql took 13.03818941116333s
Availability | SPARQL endpoint availability check for TWC Data-gov took 0.00012612342834472656s
Availability | VoID file availability check for TWC Data-gov took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.2748727798461914s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.022223234176635742s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0010845661163330078s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.600120544433594e-05s
Believability | Calculation of trust value for TWC Data-gov took 8.58306884765625e-06s
INFO | --- Analysis for twc-data-gov took 12.90728759765625s
Availability | SPARQL endpoint availability check for Tetherless World Constellation Demonstrations took 8.535385131835938e-05s
Availability | VoID file availability check for Tetherless World Constellation Demonstrations took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Tetherless World Constellation Demonstrations took 0.28413867950439453s
Reputation | Calculation of the PageRank for Tetherless World Constellation Demonstrations took 0.020860671997070312s
Interlinking | Calculation of Degree of Connection for Tetherless World Constellation Demonstrations took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Tetherless World Constellation Demonstrations took 0.0008111000061035156s
Interlinking | Calculation of Clustering coefficient for Tetherless World Constellation Demonstrations took 3.3855438232421875e-05s
Believability | Calculation of trust value for Tetherless World Constellation Demonstrations took 1.2874603271484375e-05s
INFO | --- Analysis for twc-demos took 2.9598135948181152s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.15326452255249023s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.2890503406524658s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.02065300941467285s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.52587890625e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 2.8848648071289062e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 1.1920928955078125e-05s
INFO | --- Analysis for twc-healthdata took 24.822061777114868s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.145964622497559s
Availability | VoID file availability check for Instance Hub (all) took 0.00032639503479003906s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.2839467525482178s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.02066659927368164s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 8.821487426757812e-05s
Believability | Calculation of trust value for Instance Hub (all) took 1.1444091796875e-05s
INFO | --- Analysis for twc-hub took 90.88474559783936s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.1359245777130127s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.30799245834350586s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.022218704223632812s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.0001049041748046875s
Believability | Calculation of trust value for IEEE VIS Source Data took 1.1444091796875e-05s
INFO | --- Analysis for twc-ieeevis took 114.58057451248169s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 4.2438507080078125e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.2547907829284668s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 8.654594421386719e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 9.5367431640625e-06s
INFO | --- Analysis for twc-logd took 2.5318996906280518s
Availability | SPARQL endpoint availability check for twc-opendap took 0.12731695175170898s
Availability | VoID file availability check for twc-opendap took 0.0002994537353515625s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.27997732162475586s
Reputation | Calculation of the PageRank for twc-opendap took 0.020768404006958008s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 7.843971252441406e-05s
Believability | Calculation of trust value for twc-opendap took 1.2636184692382812e-05s
INFO | --- Analysis for twc-opendap took 61.961382150650024s
Availability | SPARQL endpoint availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 4.172325134277344e-05s
Availability | VoID file availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.3111734390258789s
Reputation | Calculation of the PageRank for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.020743846893310547s
Interlinking | Calculation of Degree of Connection for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 3.504753112792969e-05s
Believability | Calculation of trust value for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 1.3113021850585938e-05s
INFO | --- Analysis for tweetskb took 2.920135259628296s
Availability | SPARQL endpoint availability check for Twitter Linked Data Service took 4.2438507080078125e-05s
Availability | VoID file availability check for Twitter Linked Data Service took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Twitter Linked Data Service took 0.26001715660095215s
Reputation | Calculation of the PageRank for Twitter Linked Data Service took 0.020465612411499023s
Interlinking | Calculation of Degree of Connection for Twitter Linked Data Service took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Twitter Linked Data Service took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Twitter Linked Data Service took 2.8848648071289062e-05s
Believability | Calculation of trust value for Twitter Linked Data Service took 1.3589859008789062e-05s
INFO | --- Analysis for twitter-lids took 2.913832664489746s
Availability | SPARQL endpoint availability check for typepad took 4.172325134277344e-05s
Availability | VoID file availability check for typepad took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for typepad took 0.2757298946380615s
Reputation | Calculation of the PageRank for typepad took 0.020212411880493164s
Interlinking | Calculation of Degree of Connection for typepad took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for typepad took 4.792213439941406e-05s
Believability | Calculation of trust value for typepad took 1.2636184692382812e-05s
INFO | --- Analysis for typepad took 3.7250874042510986s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.8570811748504639s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.24867677688598633s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.02065110206604004s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.029273986816406e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.3113021850585938e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 4.571552038192749s
Availability | SPARQL endpoint availability check for Uberblic.org took 4.407016277313232s
Availability | VoID file availability check for Uberblic.org took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.258342981338501s
Reputation | Calculation of the PageRank for Uberblic.org took 0.020752429962158203s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00011706352233886719s
Believability | Calculation of trust value for Uberblic.org took 7.3909759521484375e-06s
INFO | --- Analysis for uberblic took 9.954990148544312s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.614499568939209s
Availability | VoID file availability check for UDante in LiLa took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.2572948932647705s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.02249741554260254s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 3.409385681152344e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.1205673217773438e-05s
INFO | --- Analysis for UDante took 4.127262115478516s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 0.8921308517456055s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.3035116195678711s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.020360708236694336s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 3.0517578125e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for ufo took 4.541069507598877s
Availability | SPARQL endpoint availability check for Uganda Disasters took 8.749961853027344e-05s
Availability | VoID file availability check for Uganda Disasters took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.2660403251647949s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.020427227020263672s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 4.57763671875e-05s
Believability | Calculation of trust value for Uganda Disasters took 1.2874603271484375e-05s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.414609909057617s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.06676864624023438s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.29486918449401855s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.020853519439697266s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.00012755393981933594s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for uis-linked-data took 2.5428969860076904s
Availability | SPARQL endpoint availability check for UK Legislation took 4.076957702636719e-05s
Availability | VoID file availability check for UK Legislation took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.2649397850036621s
Reputation | Calculation of the PageRank for UK Legislation took 0.022279739379882812s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.845329284667969e-05s
Believability | Calculation of trust value for UK Legislation took 8.344650268554688e-06s
INFO | --- Analysis for uk-legislation-api took 3.0699617862701416s
Availability | SPARQL endpoint availability check for UK Postcodes took 4.5299530029296875e-05s
Availability | VoID file availability check for UK Postcodes took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.2788240909576416s
Reputation | Calculation of the PageRank for UK Postcodes took 0.022560596466064453s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.793571472167969e-05s
Believability | Calculation of trust value for UK Postcodes took 1.1682510375976562e-05s
INFO | --- Analysis for uk-postcodes took 22.377188444137573s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 4.220008850097656e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.27678394317626953s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.020572662353515625s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00012159347534179688s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.1682510375976562e-05s
INFO | --- Analysis for umbel took 6.817287921905518s
Availability | SPARQL endpoint availability check for UMTHES took 7.510185241699219e-05s
Availability | VoID file availability check for UMTHES took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for UMTHES took 0.25581789016723633s
Reputation | Calculation of the PageRank for UMTHES took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for UMTHES took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UMTHES took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for UMTHES took 4.649162292480469e-05s
Believability | Calculation of trust value for UMTHES took 9.298324584960938e-06s
INFO | --- Analysis for umthes took 3.5783534049987793s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 4.613757371902466s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.25339841842651367s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.02094244956970215s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.218650817871094e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 5.4836273193359375e-06s
INFO | --- Analysis for un-hazardous-numbers took 15.438993692398071s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.267692565917969e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.27267956733703613s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.0203244686126709s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 2.8371810913085938e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 1.1682510375976562e-05s
INFO | --- Analysis for unesco-thesaurus took 2.9019737243652344s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.2494032382965088s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.022631168365478516s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 2.9325485229492188e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 1.33514404296875e-05s
INFO | --- Analysis for unescothes took 4.294526815414429s
Availability | SPARQL endpoint availability check for UniProt took 2.256814479827881s
Availability | VoID file availability check for UniProt took 0.001140594482421875s
Extra | Recovery of all triples for UniProt took 77.58769702911377s
Performance | Total latancy measurement for UniProt took 4.320499658584595s
Amount of data | Number of triples check for UniProt took 0.4293687343597412s
Interoperability | New terms check for UniProt took 1.7008874416351318s
Versatility | Languages check for UniProt took 1.8790555000305176s
Interpretability | Number of blank nodes check for UniProt took 1.5352156162261963s
Interpretability | RDF structures check for UniProt took 1.4639267921447754s
Versatility | Serialization formats check for UniProt took 1.7199475765228271s
Availability | RDF dump link check for UniProt took 0.2701280117034912s
License | MR license check for UniProt took 1.1427149772644043s
License | HR license check for UniProt took 300.1542236804962s
Amount of data | Number of property check for UniProt took 0.08376622200012207s
Understandability | Number of label check for UniProt took 42.85997462272644s
Understandability | URI regex check for UniProt took 0.5431747436523438s
Understandability | Vocabs check for UniProt took 0.620685338973999s
Verifiability | Authors check for UniProt took 1.1475741863250732s
Verifiability | Publishers check for UniProt took 1.0960736274719238s
Performance | Throughput check for UniProt took 22.08465886116028s
Amount of data | Check the number of entities for UniProt took 7.271766662597656e-05s
Verifiability | Contribs. check for UniProt took 0.6947894096374512s
Interlinking | sameAs chians check for UniProt took 0.37882280349731445s
Interlinking | skos check for UniProt took 0.8008913993835449s
Interlinking | skos check for UniProt took 0.6586763858795166s
Timeliness | dataset update frequency check for UniProt took 1.1679773330688477s
Currency | Creation date check for UniProt took 1.2490942478179932s
Currency | Modification date check for UniProt took 1.363753318786621s
Rep.Conc. | URIs length for UniProt took 140.68802452087402s
Interoperability | New vocabularies check for UniProt took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for UniProt took 0.23059368133544922s
Accuracy | Check Functional Property for UniProt took 0.3195183277130127s
Accuracy | Check Inverse Functional Property for UniProt took 0.3032212257385254s
Accuracy | Check Empty annotation labels for UniProt took 28.871597051620483s
Accuracy | Check White space in annotation for UniProt took 2.6679091453552246s
Accuracy | Check Datatype consistency for UniProt took 7.204777002334595s
Consistency | Disjoint class check for UniProt took 0.31789517402648926s
Consistency | Check Misplaced properties for UniProt took 9.890578746795654s
Consistency | Check Ontology hijacking for UniProt took 31.74994730949402s
Consistency | Check Invalid usage of undefined classes for UniProt took 18744.257278442383s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.932692050933838s
Conciseness | Check Extensional conciseness for UniProt took 2.627122640609741s
Conciseness | Check Intensional conciseness for UniProt took 0.6153125762939453s
Security | Sign check for UniProt took 0.6679537296295166s
Availability | Check URIs Dereferenciability for UniProt took 4.184879779815674s
Completeness | Calculation of interlinking completeness for UniProt took 1.6119582653045654s
Reputation | Calculation of the PageRank for UniProt took 0.02168869972229004s
Interlinking | Calculation of Degree of Connection for UniProt took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0008003711700439453s
Interlinking | Calculation of Clustering coefficient for UniProt took 5.3882598876953125e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 2.384185791015625e-06s
Believability | Calculation of trust value for UniProt took 1.33514404296875e-05s
INFO | --- Analysis for UniProt took 19928.593774795532s
Availability | SPARQL endpoint availability check for UniProt took 2.250999689102173s
Availability | VoID file availability check for UniProt took 0.0006182193756103516s
Extra | Recovery of all triples for UniProt took 14.739135026931763s
Performance | Total latancy measurement for UniProt took 5.783118724822998s
Amount of data | Number of triples check for UniProt took 0.5830755233764648s
Versatility | Languages check for UniProt took 1.3211824893951416s
Interpretability | Number of blank nodes check for UniProt took 1.922227144241333s
Security | Check HTTPS for UniProt took 2.1583411693573s
Interpretability | RDF structures check for UniProt took 0.13984107971191406s
Versatility | Serialization formats check for UniProt took 0.1608881950378418s
Availability | RDF dump link check for UniProt took 0.13901948928833008s
License | MR license check for UniProt took 0.14578509330749512s
License | HR license check for UniProt took 0.15618443489074707s
Amount of data | Number of property check for UniProt took 0.15398097038269043s
Understandability | Number of label check for UniProt took 0.15784621238708496s
Understandability | URI regex check for UniProt took 0.2929368019104004s
Understandability | Vocabs check for UniProt took 0.13769292831420898s
Verifiability | Authors check for UniProt took 0.14072918891906738s
Verifiability | Publishers check for UniProt took 0.13751435279846191s
Performance | Throughput check for UniProt took 27.24516487121582s
Amount of data | Check the number of entities for UniProt took 5.91278076171875e-05s
Verifiability | Contribs. check for UniProt took 0.17467331886291504s
Interlinking | sameAs chians check for UniProt took 0.15174579620361328s
Interlinking | skos check for UniProt took 0.14173388481140137s
Interlinking | skos check for UniProt took 0.14055824279785156s
Timeliness | dataset update frequency check for UniProt took 0.14566874504089355s
Currency | Creation date check for UniProt took 0.2717726230621338s
Currency | Modification date check for UniProt took 0.29122447967529297s
Rep.Conc. | URIs length for UniProt took 114.67702531814575s
Interoperability | New vocabularies check for UniProt took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.13584423065185547s
Accuracy | Check Datatype consistency for UniProt took 7.265772581100464s
Consistency | Disjoint class check for UniProt took 0.14701294898986816s
Consistency | Check Ontology hijacking for UniProt took 0.15018391609191895s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.8187098503112793s
Conciseness | Check Extensional conciseness for UniProt took 2.6909902095794678s
Security | Sign check for UniProt took 0.13731050491333008s
Availability | Check URIs Dereferenciability for UniProt took 3.7666211128234863s
Completeness | Calculation of interlinking completeness for UniProt took 1.2636897563934326s
Reputation | Calculation of the PageRank for UniProt took 0.02113628387451172s
Interlinking | Calculation of Degree of Connection for UniProt took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for UniProt took 6.246566772460938e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 1.1920928955078125e-06s
Believability | Calculation of trust value for UniProt took 1.239776611328125e-05s
INFO | --- Analysis for uniprot took 726.8360755443573s
Availability | SPARQL endpoint availability check for UniProt citations took 4.124641418457031e-05s
Availability | VoID file availability check for UniProt citations took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for UniProt citations took 0.2666192054748535s
Reputation | Calculation of the PageRank for UniProt citations took 0.02211737632751465s
Interlinking | Calculation of Degree of Connection for UniProt citations took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UniProt citations took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for UniProt citations took 3.5762786865234375e-05s
Believability | Calculation of trust value for UniProt citations took 1.239776611328125e-05s
INFO | --- Analysis for uniprot-citations took 4.981464385986328s
Availability | SPARQL endpoint availability check for UniProt databases took 4.267692565917969e-05s
Availability | VoID file availability check for UniProt databases took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for UniProt databases took 0.25124239921569824s
Reputation | Calculation of the PageRank for UniProt databases took 0.020831584930419922s
Interlinking | Calculation of Degree of Connection for UniProt databases took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UniProt databases took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for UniProt databases took 3.147125244140625e-05s
Believability | Calculation of trust value for UniProt databases took 1.2159347534179688e-05s
INFO | --- Analysis for uniprot-databases took 4.1121368408203125s
Availability | SPARQL endpoint availability check for uniprot-metadata took 8.416175842285156e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.24595212936401367s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.021264076232910156s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 7.462501525878906e-05s
Believability | Calculation of trust value for uniprot-metadata took 1.2159347534179688e-05s
INFO | --- Analysis for uniprot-metadata took 4.122379541397095s
Availability | SPARQL endpoint availability check for UniProtKB Taxonomy took 4.00543212890625e-05s
Availability | VoID file availability check for UniProtKB Taxonomy took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for UniProtKB Taxonomy took 0.27329349517822266s
Reputation | Calculation of the PageRank for UniProtKB Taxonomy took 0.020934104919433594s
Interlinking | Calculation of Degree of Connection for UniProtKB Taxonomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UniProtKB Taxonomy took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for UniProtKB Taxonomy took 3.170967102050781e-05s
Believability | Calculation of trust value for UniProtKB Taxonomy took 1.1444091796875e-05s
INFO | --- Analysis for uniprot-taxonomy took 2.8336784839630127s
Availability | SPARQL endpoint availability check for UniProt UniParc took 4.2438507080078125e-05s
Availability | VoID file availability check for UniProt UniParc took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for UniProt UniParc took 0.251849889755249s
Reputation | Calculation of the PageRank for UniProt UniParc took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for UniProt UniParc took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for UniProt UniParc took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for UniProt UniParc took 3.0517578125e-05s
Believability | Calculation of trust value for UniProt UniParc took 1.1444091796875e-05s
INFO | --- Analysis for uniprot-uniparc took 2.857208490371704s
Availability | SPARQL endpoint availability check for UniProt UniPathway took 4.124641418457031e-05s
Availability | VoID file availability check for UniProt UniPathway took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for UniProt UniPathway took 0.26109933853149414s
Reputation | Calculation of the PageRank for UniProt UniPathway took 0.022678136825561523s
Interlinking | Calculation of Degree of Connection for UniProt UniPathway took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UniProt UniPathway took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for UniProt UniPathway took 2.9325485229492188e-05s
Believability | Calculation of trust value for UniProt UniPathway took 1.1920928955078125e-05s
INFO | --- Analysis for uniprot-unipathway took 2.8972530364990234s
Availability | SPARQL endpoint availability check for UniProtKB took 2.0176267623901367s
Availability | VoID file availability check for UniProtKB took 0.0005762577056884766s
Extra | Recovery of all triples for UniProtKB took 17.973886966705322s
Performance | Total latancy measurement for UniProtKB took 4.348367929458618s
Amount of data | Number of triples check for UniProtKB took 0.4462454319000244s
Interoperability | New terms check for UniProtKB took 1.69905424118042s
Versatility | Languages check for UniProtKB took 1.3793613910675049s
Interpretability | Number of blank nodes check for UniProtKB took 1.4991166591644287s
Interpretability | RDF structures check for UniProtKB took 1.5182890892028809s
Versatility | Serialization formats check for UniProtKB took 1.762110948562622s
Availability | RDF dump link check for UniProtKB took 0.35058093070983887s
License | MR license check for UniProtKB took 1.1142568588256836s
License | HR license check for UniProtKB took 300.1110894680023s
Amount of data | Number of property check for UniProtKB took 0.1510605812072754s
Understandability | Number of label check for UniProtKB took 44.48058366775513s
Understandability | URI regex check for UniProtKB took 0.5492715835571289s
Understandability | Vocabs check for UniProtKB took 0.6689608097076416s
Verifiability | Authors check for UniProtKB took 1.194382667541504s
Verifiability | Publishers check for UniProtKB took 0.9694631099700928s
Performance | Throughput check for UniProtKB took 21.866125345230103s
Amount of data | Check the number of entities for UniProtKB took 6.818771362304688e-05s
Verifiability | Contribs. check for UniProtKB took 0.6081664562225342s
Interlinking | sameAs chians check for UniProtKB took 0.32599449157714844s
Interlinking | skos check for UniProtKB took 0.8596687316894531s
Interlinking | skos check for UniProtKB took 0.6693220138549805s
Timeliness | dataset update frequency check for UniProtKB took 1.1871051788330078s
Currency | Creation date check for UniProtKB took 1.2386481761932373s
Currency | Modification date check for UniProtKB took 1.2681927680969238s
Rep.Conc. | URIs length for UniProtKB took 113.20190286636353s
Interoperability | New vocabularies check for UniProtKB took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.22127676010131836s
Accuracy | Check Functional Property for UniProtKB took 0.2622063159942627s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.2525606155395508s
Accuracy | Check Empty annotation labels for UniProtKB took 34.640357971191406s
Accuracy | Check White space in annotation for UniProtKB took 2.6651177406311035s
Accuracy | Check Datatype consistency for UniProtKB took 7.271398544311523s
Consistency | Disjoint class check for UniProtKB took 0.4107551574707031s
Consistency | Check Misplaced properties for UniProtKB took 4.858339071273804s
Consistency | Check Ontology hijacking for UniProtKB took 6.826361417770386s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 18374.17770075798s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 2.029726982116699s
Conciseness | Check Extensional conciseness for UniProtKB took 2.6494140625s
Conciseness | Check Intensional conciseness for UniProtKB took 0.6301834583282471s
Security | Sign check for UniProtKB took 0.6810777187347412s
Availability | Check URIs Dereferenciability for UniProtKB took 4.026892185211182s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.34093737602233887s
Reputation | Calculation of the PageRank for UniProtKB took 0.02123236656188965s
Interlinking | Calculation of Degree of Connection for UniProtKB took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 7.414817810058594e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 2.1457672119140625e-06s
Believability | Calculation of trust value for UniProtKB took 1.33514404296875e-05s
INFO | --- Analysis for uniprotkb took 19384.25978088379s
Availability | SPARQL endpoint availability check for UniProt UniRef took 8.511543273925781e-05s
Availability | VoID file availability check for UniProt UniRef took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for UniProt UniRef took 0.2655785083770752s
Reputation | Calculation of the PageRank for UniProt UniRef took 0.021972179412841797s
Interlinking | Calculation of Degree of Connection for UniProt UniRef took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UniProt UniRef took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for UniProt UniRef took 3.266334533691406e-05s
Believability | Calculation of trust value for UniProt UniRef took 1.1444091796875e-05s
INFO | --- Analysis for uniref took 3.7549524307250977s
Availability | SPARQL endpoint availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 3.9577484130859375e-05s
Availability | VoID file availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.24358677864074707s
Reputation | Calculation of the PageRank for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.022156238555908203s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 3.170967102050781e-05s
Believability | Calculation of trust value for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 1.0728836059570312e-05s
INFO | --- Analysis for unistat-kis-2011-2012-in-rdf-key-information-set-uk-universities took 2.788161516189575s
Availability | SPARQL endpoint availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 3.981590270996094e-05s
Availability | VoID file availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.24846601486206055s
Reputation | Calculation of the PageRank for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 3.0994415283203125e-05s
Believability | Calculation of trust value for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 1.1444091796875e-05s
INFO | --- Analysis for unistat-kis-in-rdf-key-information-set-uk-universities took 2.8569536209106445s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 0.00011396408081054688s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.27736806869506836s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.02067255973815918s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007100105285644531s
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.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 13.317660570144653s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 9.179115295410156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.000705718994140625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.27901268005371094s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.020947694778442383s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 3.742506742477417s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 8.440017700195312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.27588963508605957s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.020930051803588867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0009670257568359375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 4.8160552978515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.192461729049683s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 8.416175842285156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.2770259380340576s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.020664453506469727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.216399192810059s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0009253025054931641s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.2591893672943115s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.020957469940185547s
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.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 4.482269287109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 2.09808349609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 13.203068256378174s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 8.749961853027344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.2765953540802002s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.02069258689880371s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 13.164536237716675s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0007619857788085938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.27787089347839355s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.02128434181213379s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 3.89850115776062s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 4.57763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0008602142333984375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.27120518684387207s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.02116870880126953s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0010633468627929688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 5.1975250244140625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.05993390083313s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0008590221405029297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.2890658378601074s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.020739078521728516s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.103294134140015s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0007433891296386719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.2523772716522217s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.02076268196105957s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 5.984306335449219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.06527042388916s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 0.0001068115234375s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0007696151733398438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.2725074291229248s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 12.976047992706299s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0007801055908203125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.25114893913269043s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.02043771743774414s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 12.957330703735352s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.26154160499572754s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-danish took 3.7779505252838135s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 8.58306884765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.28072333335876465s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.022948503494262695s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.150012969970703s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.2664487361907959s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.021083831787109375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.982948303222656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 13.033046245574951s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 9.703636169433594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.2607119083404541s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.02140188217163086s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-english took 13.034564733505249s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 5.125999450683594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.25521254539489746s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.02079010009765625s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.052358388900757s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 4.649162292480469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0007638931274414062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.2658376693725586s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.020943880081176758s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 3.0517578125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 13.121142387390137s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 4.601478576660156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0007665157318115234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.30199241638183594s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.02083611488342285s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 13.079339265823364s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 9.036064147949219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.2565305233001709s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020901203155517578s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 6.103515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 3.610511302947998s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 8.869171142578125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0007474422454833984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.2585451602935791s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.021414756774902344s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 12.928163528442383s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.2820625305175781s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.021386146545410156s
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.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.271039009094238s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0007870197296142578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.26667118072509766s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.020537853240966797s
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.000762939453125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.179097652435303s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.00037932395935058594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.25733304023742676s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.020749568939208984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 3.5109846591949463s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 8.797645568847656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.2763025760650635s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.02163243293762207s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-german took 4.20600700378418s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 0.00010275840759277344s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.25904059410095215s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.020941972732543945s
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.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 3.6350858211517334s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 7.152557373046875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.27510666847229004s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.020583629608154297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-greek took 3.649435520172119s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0007526874542236328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.2572166919708252s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.02064037322998047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.027915477752686s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0006608963012695312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.2753639221191406s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.02085733413696289s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.168899059295654s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 8.344650268554688e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.000339508056640625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.2912425994873047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.02077341079711914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 3.8468503952026367s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 8.463859558105469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.2534012794494629s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.0208280086517334s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 2.956390380859375e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.147173881530762s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 6.771087646484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.2727084159851074s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.020661354064941406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-irish took 4.037115097045898s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 5.0067901611328125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.24824857711791992s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-italian took 13.055585384368896s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 6.985664367675781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.2543449401855469s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.021056652069091797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.8160552978515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.115439176559448s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.24170851707458496s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 3.5420656204223633s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 6.771087646484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.2519843578338623s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 13.139078617095947s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.24730730056762695s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.020543336868286133s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin took 3.811911106109619s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0009860992431640625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.25221753120422363s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 12.912502527236938s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.2764616012573242s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.02148127555847168s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 12.977788209915161s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 8.630752563476562e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0007364749908447266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.2438952922821045s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.0206758975982666s
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.0007159709930419922s
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.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.160223722457886s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 8.559226989746094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.24905967712402344s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.02064371109008789s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 12.95600175857544s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.00010013580322265625s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.25191426277160645s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.020813465118408203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.058842420578003s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.27567195892333984s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-persian took 3.840278387069702s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.2569389343261719s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.02091050148010254s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.073698043823242s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.25582289695739746s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.02069544792175293s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 4.8160552978515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 12.633681535720825s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.25755810737609863s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020932674407958984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 12.842863082885742s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.23984742164611816s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.020929336547851562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 12.999634504318237s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.2454061508178711s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020791292190551758s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 5.7220458984375e-06s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.05126953125s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.25968146324157715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.02090907096862793s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.08860158920288s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0003135204315185547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.23427963256835938s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.020614147186279297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 3.4128808975219727s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.00043201446533203125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.2738661766052246s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.1055588722229s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 4.839897155761719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.2571718692779541s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.02076864242553711s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.018115758895874s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.2528839111328125s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.020790576934814453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.040091514587402s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.34479689598083496s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.020792245864868164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 12.99524211883545s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.2500944137573242s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.02098226547241211s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 12.95893383026123s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 4.76837158203125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.2636854648590088s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.020603179931640625s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 12.824892044067383s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.2485213279724121s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.02093219757080078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 3.7859580516815186s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 8.654594421386719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.29217076301574707s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.022526025772094727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 3.58699893951416s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.23393583297729492s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.022424697875976562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 13.23975944519043s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0006985664367675781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.30547404289245605s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.244130373001099s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 6.890296936035156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.2396411895751953s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.020640850067138672s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.118340730667114s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.26694822311401367s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.02115654945373535s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 13.246115446090698s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 8.940696716308594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.23692774772644043s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.021681547164916992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 13.20341444015503s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.2579686641693115s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 6.341934204101562e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.032407522201538s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 5.793571472167969e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.24288535118103027s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.021109580993652344s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 7.009506225585938e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 1.2636184692382812e-05s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 6.899571180343628s
Availability | SPARQL endpoint availability check for Universitat Pompeu Fabra - linked data took 4.220008850097656e-05s
Availability | VoID file availability check for Universitat Pompeu Fabra - linked data took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for Universitat Pompeu Fabra - linked data took 0.2624192237854004s
Reputation | Calculation of the PageRank for Universitat Pompeu Fabra - linked data took 0.021115779876708984s
Interlinking | Calculation of Degree of Connection for Universitat Pompeu Fabra - linked data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universitat Pompeu Fabra - linked data took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Universitat Pompeu Fabra - linked data took 3.2901763916015625e-05s
Believability | Calculation of trust value for Universitat Pompeu Fabra - linked data took 1.2874603271484375e-05s
INFO | --- Analysis for universitat-pompeu-fabra-linked-data took 2.777418851852417s
Availability | SPARQL endpoint availability check for University of Bristol took 4.1484832763671875e-05s
Availability | VoID file availability check for University of Bristol took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for University of Bristol took 0.2577941417694092s
Reputation | Calculation of the PageRank for University of Bristol took 0.02138209342956543s
Interlinking | Calculation of Degree of Connection for University of Bristol took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for University of Bristol took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for University of Bristol took 3.409385681152344e-05s
Believability | Calculation of trust value for University of Bristol took 1.3113021850585938e-05s
INFO | --- Analysis for university-of-bristol took 2.8730154037475586s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 4.267692565917969e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.24805545806884766s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.02070784568786621s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 5.221366882324219e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.3828277587890625e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 2.885701894760132s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 9.226799011230469e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.24817538261413574s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.020987510681152344s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.933906555175781e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 1.3589859008789062e-05s
INFO | --- Analysis for university-sussex-reading-lists took 2.5404272079467773s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 5.837414979934692s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.27556371688842773s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.020853757858276367s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 7.009506225585938e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 1.3589859008789062e-05s
INFO | --- Analysis for unodc took 14.608423709869385s
Availability | SPARQL endpoint availability check for Super Ontology took 0.00010657310485839844s
Availability | VoID file availability check for Super Ontology took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.26384902000427246s
Reputation | Calculation of the PageRank for Super Ontology took 0.022136449813842773s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 8.392333984375e-05s
Believability | Calculation of trust value for Super Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for upper-ontology took 8.62619400024414s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 0.965693473815918s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.2569093704223633s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.021288633346557617s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.6716461181640625e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 1.239776611328125e-05s
INFO | --- Analysis for Upper_Ontology took 3.9384565353393555s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 6.771087646484375e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.25057268142700195s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.02123236656188965s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 3.24249267578125e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 1.1920928955078125e-05s
INFO | --- Analysis for Urban_Atlas_ took 2.309983968734741s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 0.628253698348999s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.0005171298980712891s
Extra | Recovery of all triples for Urban Atlas dataset @PSNC took 126.07141494750977s
Performance | Total latancy measurement for Urban Atlas dataset @PSNC took 1.0036697387695312s
Amount of data | Number of triples check for Urban Atlas dataset @PSNC took 9.856690645217896s
Interoperability | New terms check for Urban Atlas dataset @PSNC took 14.225118398666382s
Versatility | Languages check for Urban Atlas dataset @PSNC took 300.21819949150085s
Interpretability | Number of blank nodes check for Urban Atlas dataset @PSNC took 2.1036746501922607s
Interpretability | RDF structures check for Urban Atlas dataset @PSNC took 0.3143022060394287s
Versatility | Serialization formats check for Urban Atlas dataset @PSNC took 7.2487688064575195s
Availability | RDF dump link check for Urban Atlas dataset @PSNC took 0.35465455055236816s
License | MR license check for Urban Atlas dataset @PSNC took 0.8172397613525391s
License | HR license check for Urban Atlas dataset @PSNC took 300.26211762428284s
Amount of data | Number of property check for Urban Atlas dataset @PSNC took 0.21337318420410156s
Understandability | Number of label check for Urban Atlas dataset @PSNC took 2.7093653678894043s
Understandability | URI regex check for Urban Atlas dataset @PSNC took 0.9638807773590088s
Understandability | Vocabs check for Urban Atlas dataset @PSNC took 0.540412187576294s
Verifiability | Authors check for Urban Atlas dataset @PSNC took 0.20029830932617188s
Verifiability | Publishers check for Urban Atlas dataset @PSNC took 0.2598412036895752s
Performance | Throughput check for Urban Atlas dataset @PSNC took 11.57462739944458s
Amount of data | Check the number of entities for Urban Atlas dataset @PSNC took 3.266334533691406e-05s
Verifiability | Contribs. check for Urban Atlas dataset @PSNC took 0.19824624061584473s
Interlinking | sameAs chians check for Urban Atlas dataset @PSNC took 0.1847519874572754s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.5011272430419922s
Interlinking | skos check for Urban Atlas dataset @PSNC took 0.4027547836303711s
Timeliness | dataset update frequency check for Urban Atlas dataset @PSNC took 4.938386678695679s
Currency | Creation date check for Urban Atlas dataset @PSNC took 0.49193835258483887s
Currency | Modification date check for Urban Atlas dataset @PSNC took 0.28139615058898926s
Rep.Conc. | URIs length for Urban Atlas dataset @PSNC took 161.8387987613678s
Interoperability | New vocabularies check for Urban Atlas dataset @PSNC took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Urban Atlas dataset @PSNC took 0.20313119888305664s
Accuracy | Check Functional Property for Urban Atlas dataset @PSNC took 0.3880496025085449s
Accuracy | Check Inverse Functional Property for Urban Atlas dataset @PSNC took 0.40969324111938477s
Accuracy | Check Empty annotation labels for Urban Atlas dataset @PSNC took 42.936150789260864s
Accuracy | Check White space in annotation for Urban Atlas dataset @PSNC took 2.64140248298645s
Accuracy | Check Datatype consistency for Urban Atlas dataset @PSNC took 2.5912961959838867s
Consistency | Disjoint class check for Urban Atlas dataset @PSNC took 0.18384313583374023s
Consistency | Check Misplaced properties for Urban Atlas dataset @PSNC took 87.3120653629303s
Consistency | Misplaced classes for Urban Atlas dataset @PSNC took 8.336702585220337s
Consistency | Check Ontology hijacking for Urban Atlas dataset @PSNC took 32.81772828102112s
Consistency | Check Invalid usage of undefined classes for Urban Atlas dataset @PSNC took 1.3228623867034912s
Consistency | Check Invalid usage of undefined properties for Urban Atlas dataset @PSNC took 87.67706441879272s
Conciseness | Check Extensional conciseness for Urban Atlas dataset @PSNC took 2.6924896240234375s
Conciseness | Check Intensional conciseness for Urban Atlas dataset @PSNC took 0.5297946929931641s
Security | Sign check for Urban Atlas dataset @PSNC took 1.2171602249145508s
Availability | Check URIs Dereferenciability for Urban Atlas dataset @PSNC took 13.784534692764282s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.6568746566772461s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.021291732788085938s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 4.839897155761719e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 4.0531158447265625e-05s
Interoperability | Check the re-using of existing vocabs for Urban Atlas dataset @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for Urban_Atlas_Dataset took 2304.1372649669647s
Availability | SPARQL endpoint availability check for URIBurner took 1.7393574714660645s
Availability | VoID file availability check for URIBurner took 0.0006213188171386719s
Extra | Recovery of all triples for URIBurner took 122.68669009208679s
Performance | Total latancy measurement for URIBurner took 2.768497943878174s
Amount of data | Number of triples check for URIBurner took 4.098721265792847s
Interoperability | New terms check for URIBurner took 38.51328802108765s
Versatility | Languages check for URIBurner took 122.20116090774536s
Interpretability | Number of blank nodes check for URIBurner took 1.9191689491271973s
Security | Check HTTPS for URIBurner took 0.9005587100982666s
Interpretability | RDF structures check for URIBurner took 2.4517898559570312s
Versatility | Serialization formats check for URIBurner took 6.659525156021118s
Availability | RDF dump link check for URIBurner took 49.252392292022705s
License | MR license check for URIBurner took 1.2736966609954834s
License | HR license check for URIBurner took 120.70100736618042s
Amount of data | Number of property check for URIBurner took 0.7285478115081787s
Understandability | Number of label check for URIBurner took 4.25303053855896s
Understandability | URI regex check for URIBurner took 1.2356836795806885s
Understandability | Vocabs check for URIBurner took 0.6240267753601074s
Verifiability | Authors check for URIBurner took 1.833726167678833s
Verifiability | Publishers check for URIBurner took 0.5990612506866455s
Performance | Throughput check for URIBurner took 10.64522933959961s
Amount of data | Check the number of entities for URIBurner took 8.606910705566406e-05s
Verifiability | Contribs. check for URIBurner took 0.6227502822875977s
Interlinking | sameAs chians check for URIBurner took 1.4150505065917969s
Interlinking | skos check for URIBurner took 0.944509744644165s
Interlinking | skos check for URIBurner took 0.5280311107635498s
Timeliness | dataset update frequency check for URIBurner took 1.12717604637146s
Currency | Creation date check for URIBurner took 3.7204272747039795s
Currency | Modification date check for URIBurner took 0.7855110168457031s
Rep.Conc. | URIs length for URIBurner took 112.80301237106323s
Interoperability | New vocabularies check for URIBurner took 26.570507287979126s
Consistency | Deprecated classes/propertiers check for URIBurner took 0.6089556217193604s
Accuracy | Check Functional Property for URIBurner took 0.5702300071716309s
Accuracy | Check Inverse Functional Property for URIBurner took 0.5672385692596436s
Accuracy | Check Empty annotation labels for URIBurner took 55.48891019821167s
Accuracy | Check White space in annotation for URIBurner took 0.18622565269470215s
Consistency | Disjoint class check for URIBurner took 0.6044135093688965s
Consistency | Check Misplaced properties for URIBurner took 386.8929831981659s
Consistency | Misplaced classes for URIBurner took 55.844871282577515s
Consistency | Check Ontology hijacking for URIBurner took 57.065369844436646s
Consistency | Check Invalid usage of undefined properties for URIBurner took 58.674779653549194s
Conciseness | Check Extensional conciseness for URIBurner took 0.00012612342834472656s
Conciseness | Check Intensional conciseness for URIBurner took 110.16417169570923s
Security | Sign check for URIBurner took 0.7589256763458252s
Completeness | Calculation of interlinking completeness for URIBurner took 1.4569694995880127s
Reputation | Calculation of the PageRank for URIBurner took 0.021825551986694336s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for URIBurner took 0.00010800361633300781s
Interoperability | Check the re-using of existing vocabs for URIBurner took 25.462071418762207s
Believability | Calculation of trust value for URIBurner took 7.62939453125e-06s
INFO | --- Analysis for uriburner took 11430.643096923828s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.4345855712890625e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.26355934143066406s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02044844627380371s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.0517578125e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.2636184692382812e-05s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 2.738802909851074s
Availability | SPARQL endpoint availability check for Legija Stranaca took 4.291534423828125e-05s
Availability | VoID file availability check for Legija Stranaca took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.26366186141967773s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.020126819610595703s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 2.9087066650390625e-05s
Believability | Calculation of trust value for Legija Stranaca took 1.2874603271484375e-05s
INFO | --- Analysis for Uros_Legija_Susa took 2.317537546157837s
Availability | SPARQL endpoint availability check for Legija took 4.1961669921875e-05s
Availability | VoID file availability check for Legija took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for Legija took 0.2707695960998535s
Reputation | Calculation of the PageRank for Legija took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for Legija took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Legija took 0.0009636878967285156s
Interlinking | Calculation of Clustering coefficient for Legija took 3.528594970703125e-05s
Believability | Calculation of trust value for Legija took 1.1444091796875e-05s
INFO | --- Analysis for Uros_Susa took 2.7171990871429443s
Availability | SPARQL endpoint availability check for US Political Violence took 3.933906555175781e-05s
Availability | VoID file availability check for US Political Violence took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for US Political Violence took 0.24894356727600098s
Reputation | Calculation of the PageRank for US Political Violence took 0.020321369171142578s
Interlinking | Calculation of Degree of Connection for US Political Violence took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for US Political Violence took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for US Political Violence took 3.075599670410156e-05s
Believability | Calculation of trust value for US Political Violence took 1.0251998901367188e-05s
INFO | --- Analysis for us-political-violence took 2.847074508666992s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.3743896484375s
Availability | VoID file availability check for USAGE review corpus took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.2410109043121338s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.02066493034362793s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 2.9802322387695312e-05s
Believability | Calculation of trust value for USAGE review corpus took 1.1205673217773438e-05s
INFO | --- Analysis for usage-review-corpus took 3.5396687984466553s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 5.79810357093811s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.2587902545928955s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.020333528518676758s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.700920104980469e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 1.1444091796875e-05s
INFO | --- Analysis for utpl-lod took 10.861656904220581s
Availability | SPARQL endpoint availability check for Výkazy zisku a ztrát obcí ČR took 4.291534423828125e-05s
Availability | VoID file availability check for Výkazy zisku a ztrát obcí ČR took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Výkazy zisku a ztrát obcí ČR took 0.2624502182006836s
Reputation | Calculation of the PageRank for Výkazy zisku a ztrát obcí ČR took 0.02036571502685547s
Interlinking | Calculation of Degree of Connection for Výkazy zisku a ztrát obcí ČR took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Výkazy zisku a ztrát obcí ČR took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Výkazy zisku a ztrát obcí ČR took 2.8133392333984375e-05s
Believability | Calculation of trust value for Výkazy zisku a ztrát obcí ČR took 1.0967254638671875e-05s
INFO | --- Analysis for v-kazy-zisku-a-ztr-t-obc---r took 2.8345422744750977s
Availability | SPARQL endpoint availability check for terrorist attack took 4.124641418457031e-05s
Availability | VoID file availability check for terrorist attack took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.24620509147644043s
Reputation | Calculation of the PageRank for terrorist attack took 0.021738767623901367s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 2.9087066650390625e-05s
Believability | Calculation of trust value for terrorist attack took 1.1444091796875e-05s
INFO | --- Analysis for varsha took 4.041532754898071s
Availability | SPARQL endpoint availability check for VA took 8.273124694824219e-05s
Availability | VoID file availability check for VA took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for VA took 0.24668312072753906s
Reputation | Calculation of the PageRank for VA took 0.0227506160736084s
Interlinking | Calculation of Degree of Connection for VA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VA took 0.0008440017700195312s
Interlinking | Calculation of Clustering coefficient for VA took 2.9802322387695312e-05s
Believability | Calculation of trust value for VA took 1.1205673217773438e-05s
INFO | --- Analysis for Vehicule_Autonome took 2.6780526638031006s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 0.6470763683319092s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.26236891746520996s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 3.6716461181640625e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 1.0251998901367188e-05s
INFO | --- Analysis for VelezIndexTotiusArtis took 3.9919466972351074s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 6.535386323928833s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.25015807151794434s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.020235300064086914s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 8.273124694824219e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 1.1205673217773438e-05s
INFO | --- Analysis for verrijktkoninkrijk took 15.595091819763184s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 4.220008850097656e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.25477099418640137s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.0001723766326904297s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.3113021850585938e-05s
INFO | --- Analysis for viaf took 20.210785627365112s
Availability | SPARQL endpoint availability check for Vías Públicas de Zaragoza (Localización) took 5.984306335449219e-05s
Availability | VoID file availability check for Vías Públicas de Zaragoza (Localización) took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Vías Públicas de Zaragoza (Localización) took 0.2504160404205322s
Reputation | Calculation of the PageRank for Vías Públicas de Zaragoza (Localización) took 0.020725250244140625s
Interlinking | Calculation of Degree of Connection for Vías Públicas de Zaragoza (Localización) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Vías Públicas de Zaragoza (Localización) took 0.0010166168212890625s
Interlinking | Calculation of Clustering coefficient for Vías Públicas de Zaragoza (Localización) took 3.933906555175781e-05s
Believability | Calculation of trust value for Vías Públicas de Zaragoza (Localización) took 1.2159347534179688e-05s
INFO | --- Analysis for vias-publicas-zaragoza took 2.836329221725464s
Availability | SPARQL endpoint availability check for Vihar Exports took 4.315376281738281e-05s
Availability | VoID file availability check for Vihar Exports took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.24680852890014648s
Reputation | Calculation of the PageRank for Vihar Exports took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 3.0040740966796875e-05s
Believability | Calculation of trust value for Vihar Exports took 1.3589859008789062e-05s
INFO | --- Analysis for Vihar_Exports took 2.3095569610595703s
Availability | SPARQL endpoint availability check for vimeo.videoobject took 0.00010323524475097656s
Availability | VoID file availability check for vimeo.videoobject took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for vimeo.videoobject took 0.2836427688598633s
Reputation | Calculation of the PageRank for vimeo.videoobject took 0.0207366943359375s
Interlinking | Calculation of Degree of Connection for vimeo.videoobject took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for vimeo.videoobject took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for vimeo.videoobject took 3.0994415283203125e-05s
Believability | Calculation of trust value for vimeo.videoobject took 7.3909759521484375e-06s
INFO | --- Analysis for vimeo_videoobject took 2.892116069793701s
Availability | SPARQL endpoint availability check for VIVO took 4.124641418457031e-05s
Availability | VoID file availability check for VIVO took 0.0012035369873046875s
Completeness | Calculation of interlinking completeness for VIVO took 0.2505621910095215s
Reputation | Calculation of the PageRank for VIVO took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for VIVO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for VIVO took 6.747245788574219e-05s
Believability | Calculation of trust value for VIVO took 1.1682510375976562e-05s
INFO | --- Analysis for vivo took 4.710402011871338s
Availability | SPARQL endpoint availability check for VIVO Cornell took 4.2438507080078125e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0007750988006591797s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.2537224292755127s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.022724628448486328s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 7.939338684082031e-05s
Believability | Calculation of trust value for VIVO Cornell took 1.1682510375976562e-05s
INFO | --- Analysis for vivo-cornell-university took 5.6642842292785645s
Availability | SPARQL endpoint availability check for VIVO CU-Boulder took 4.1484832763671875e-05s
Availability | VoID file availability check for VIVO CU-Boulder took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for VIVO CU-Boulder took 0.2631351947784424s
Reputation | Calculation of the PageRank for VIVO CU-Boulder took 0.020680904388427734s
Interlinking | Calculation of Degree of Connection for VIVO CU-Boulder took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for VIVO CU-Boulder took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for VIVO CU-Boulder took 3.170967102050781e-05s
Believability | Calculation of trust value for VIVO CU-Boulder took 1.2874603271484375e-05s
INFO | --- Analysis for vivo-cu-boulder took 2.852947950363159s
Availability | SPARQL endpoint availability check for VIVO Indiana took 9.1552734375e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.2506542205810547s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.02031397819519043s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 7.987022399902344e-05s
Believability | Calculation of trust value for VIVO Indiana took 1.2636184692382812e-05s
INFO | --- Analysis for vivo-indiana-university took 2.9646527767181396s
Availability | SPARQL endpoint availability check for VIVO Ponce took 9.775161743164062e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.26249098777770996s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.020193099975585938s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.933906555175781e-05s
Believability | Calculation of trust value for VIVO Ponce took 1.52587890625e-05s
INFO | --- Analysis for vivo-ponce took 2.923809051513672s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 8.845329284667969e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.25206756591796875s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.020438671112060547s
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.0007171630859375s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.552436828613281e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 1.2636184692382812e-05s
INFO | --- Analysis for vivo-scripps-research-institute took 2.7865800857543945s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 4.220008850097656e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.26407814025878906s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.020339012145996094s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.274482727050781e-05s
Believability | Calculation of trust value for VIVO University of Florida took 1.1444091796875e-05s
INFO | --- Analysis for vivo-university-of-florida took 2.536900043487549s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 4.100799560546875e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.25185537338256836s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.0224456787109375s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.6716461181640625e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 1.1682510375976562e-05s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 2.7249741554260254s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 4.267692565917969e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.24746203422546387s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.023255109786987305s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0010476112365722656s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 4.410743713378906e-05s
Believability | Calculation of trust value for VIVO WUSTL took 1.1444091796875e-05s
INFO | --- Analysis for vivo-wustl took 2.723076343536377s
Availability | SPARQL endpoint availability check for vivo2doi took 4.1961669921875e-05s
Availability | VoID file availability check for vivo2doi took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.2732381820678711s
Reputation | Calculation of the PageRank for vivo2doi took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 6.818771362304688e-05s
Believability | Calculation of trust value for vivo2doi took 1.1682510375976562e-05s
INFO | --- Analysis for vivo2doi took 33.30476522445679s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 4.601478576660156e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.2884399890899658s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.020867586135864258s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 7.557868957519531e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 1.1444091796875e-05s
INFO | --- Analysis for vu-wordnet took 14.321741580963135s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.12649774551391602s
Availability | VoID file availability check for vulnerapedia took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.24719977378845215s
Reputation | Calculation of the PageRank for vulnerapedia took 0.02066516876220703s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 6.723403930664062e-05s
Believability | Calculation of trust value for vulnerapedia took 1.0967254638671875e-05s
INFO | --- Analysis for vulnerapedia took 2.897951364517212s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 5.7220458984375e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.24907159805297852s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.02054882049560547s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.0967254638671875e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.239776611328125e-05s
INFO | --- Analysis for VVASIAK took 2.3061959743499756s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 0.0001323223114013672s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.2715284824371338s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.021365642547607422s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.266334533691406e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 1.049041748046875e-05s
INFO | --- Analysis for Vyvasta took 2.368727207183838s
Availability | SPARQL endpoint availability check for W3C took 3.981590270996094e-05s
Availability | VoID file availability check for W3C took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for W3C took 0.24715209007263184s
Reputation | Calculation of the PageRank for W3C took 0.022937297821044922s
Interlinking | Calculation of Degree of Connection for W3C took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for W3C took 0.0001361370086669922s
Believability | Calculation of trust value for W3C took 1.2636184692382812e-05s
INFO | --- Analysis for w3c took 2.8074233531951904s
Availability | SPARQL endpoint availability check for W3C Provenance Incubator Group Vocabulary Mappings took 4.410743713378906e-05s
Availability | VoID file availability check for W3C Provenance Incubator Group Vocabulary Mappings took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for W3C Provenance Incubator Group Vocabulary Mappings took 0.2586476802825928s
Reputation | Calculation of the PageRank for W3C Provenance Incubator Group Vocabulary Mappings took 0.020888805389404297s
Interlinking | Calculation of Degree of Connection for W3C Provenance Incubator Group Vocabulary Mappings took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for W3C Provenance Incubator Group Vocabulary Mappings took 0.0013682842254638672s
Interlinking | Calculation of Clustering coefficient for W3C Provenance Incubator Group Vocabulary Mappings took 5.316734313964844e-05s
Believability | Calculation of trust value for W3C Provenance Incubator Group Vocabulary Mappings took 1.0728836059570312e-05s
INFO | --- Analysis for w3c-provenance-incubator-group-vocabulary-mappings took 2.8100838661193848s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 8.606910705566406e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.24682378768920898s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.021001815795898438s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00011134147644042969s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 1.0251998901367188e-05s
INFO | --- Analysis for w3c-wordnet took 3.9406979084014893s
Availability | SPARQL endpoint availability check for WarSampo took 0.34297633171081543s
Availability | VoID file availability check for WarSampo took 0.0008077621459960938s
Extra | Recovery of all triples for WarSampo took 25.94592571258545s
Performance | Total latancy measurement for WarSampo took 0.814706563949585s
Amount of data | Number of triples check for WarSampo took 18.016578435897827s
Interoperability | New terms check for WarSampo took 3.941645622253418s
Versatility | Languages check for WarSampo took 52.690197229385376s
Interpretability | Number of blank nodes check for WarSampo took 18.000667095184326s
Security | Check HTTPS for WarSampo took 0.423053503036499s
Interpretability | RDF structures check for WarSampo took 0.16946935653686523s
Versatility | Serialization formats check for WarSampo took 0.16531753540039062s
Availability | RDF dump link check for WarSampo took 1.1913847923278809s
License | MR license check for WarSampo took 0.17703771591186523s
License | HR license check for WarSampo took 43.97716665267944s
Amount of data | Number of property check for WarSampo took 0.1744706630706787s
Understandability | Number of label check for WarSampo took 9.695868968963623s
Understandability | URI regex check for WarSampo took 0.35091352462768555s
Understandability | Vocabs check for WarSampo took 0.17232394218444824s
Verifiability | Authors check for WarSampo took 0.17247748374938965s
Verifiability | Publishers check for WarSampo took 0.1828927993774414s
Performance | Throughput check for WarSampo took 10.621431112289429s
Amount of data | Check the number of entities for WarSampo took 15.32257080078125s
Verifiability | Contribs. check for WarSampo took 0.17986583709716797s
Interlinking | sameAs chians check for WarSampo took 0.1809554100036621s
Interlinking | skos check for WarSampo took 0.1889021396636963s
Interlinking | skos check for WarSampo took 0.16901659965515137s
Timeliness | dataset update frequency check for WarSampo took 0.17452502250671387s
Currency | Creation date check for WarSampo took 0.36887216567993164s
Currency | Modification date check for WarSampo took 0.3715393543243408s
Rep.Conc. | URIs length for WarSampo took 48.67232012748718s
Interoperability | New vocabularies check for WarSampo took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.16571307182312012s
Accuracy | Check Functional Property for WarSampo took 0.17423224449157715s
Accuracy | Check Inverse Functional Property for WarSampo took 0.18010568618774414s
Accuracy | Check Empty annotation labels for WarSampo took 12.089888572692871s
Accuracy | Check White space in annotation for WarSampo took 2.212980270385742s
Accuracy | Check Datatype consistency for WarSampo took 5.346095085144043s
Consistency | Disjoint class check for WarSampo took 0.15860486030578613s
Consistency | Check Misplaced properties for WarSampo took 19.890750885009766s
Consistency | Check Ontology hijacking for WarSampo took 19.50456976890564s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.4474565982818604s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.6765925884246826s
Conciseness | Check Extensional conciseness for WarSampo took 2.8091228008270264s
Conciseness | Check Intensional conciseness for WarSampo took 0.2760756015777588s
Security | Sign check for WarSampo took 0.21050024032592773s
Availability | Check URIs Dereferenciability for WarSampo took 2.74253511428833s
Completeness | Calculation of interlinking completeness for WarSampo took 0.3912343978881836s
Reputation | Calculation of the PageRank for WarSampo took 0.021082401275634766s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for WarSampo took 8.821487426757812e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 2.384185791015625e-06s
Believability | Calculation of trust value for WarSampo took 7.867813110351562e-06s
INFO | --- Analysis for warsampo took 1007.9433770179749s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.3359534740448s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.2433164119720459s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.02065277099609375s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 7.581710815429688e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 6.198883056640625e-06s
INFO | --- Analysis for wasabi took 54.32309889793396s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 0.5788004398345947s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.0004627704620361328s
Extra | Recovery of all triples for FAO water areas classification as linked data @PSNC took 117.00636219978333s
Performance | Total latancy measurement for FAO water areas classification as linked data @PSNC took 0.9260015487670898s
Amount of data | Number of triples check for FAO water areas classification as linked data @PSNC took 9.58638858795166s
Interoperability | New terms check for FAO water areas classification as linked data @PSNC took 14.332871913909912s
Versatility | Languages check for FAO water areas classification as linked data @PSNC took 300.1748991012573s
Interpretability | Number of blank nodes check for FAO water areas classification as linked data @PSNC took 2.2083256244659424s
Interpretability | RDF structures check for FAO water areas classification as linked data @PSNC took 0.3385953903198242s
Versatility | Serialization formats check for FAO water areas classification as linked data @PSNC took 9.081632614135742s
Availability | RDF dump link check for FAO water areas classification as linked data @PSNC took 0.3407440185546875s
License | MR license check for FAO water areas classification as linked data @PSNC took 0.855522632598877s
License | HR license check for FAO water areas classification as linked data @PSNC took 300.2134702205658s
Amount of data | Number of property check for FAO water areas classification as linked data @PSNC took 0.2308647632598877s
Understandability | Number of label check for FAO water areas classification as linked data @PSNC took 2.306067705154419s
Understandability | URI regex check for FAO water areas classification as linked data @PSNC took 0.9057021141052246s
Understandability | Vocabs check for FAO water areas classification as linked data @PSNC took 0.5108036994934082s
Verifiability | Authors check for FAO water areas classification as linked data @PSNC took 0.21059846878051758s
Verifiability | Publishers check for FAO water areas classification as linked data @PSNC took 0.26383042335510254s
Performance | Throughput check for FAO water areas classification as linked data @PSNC took 11.505509376525879s
Amount of data | Check the number of entities for FAO water areas classification as linked data @PSNC took 7.224082946777344e-05s
Verifiability | Contribs. check for FAO water areas classification as linked data @PSNC took 0.18471002578735352s
Interlinking | sameAs chians check for FAO water areas classification as linked data @PSNC took 0.21201682090759277s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.4277381896972656s
Interlinking | skos check for FAO water areas classification as linked data @PSNC took 0.41779565811157227s
Timeliness | dataset update frequency check for FAO water areas classification as linked data @PSNC took 4.747650623321533s
Currency | Creation date check for FAO water areas classification as linked data @PSNC took 0.46123528480529785s
Currency | Modification date check for FAO water areas classification as linked data @PSNC took 0.26925134658813477s
Rep.Conc. | URIs length for FAO water areas classification as linked data @PSNC took 156.1090428829193s
Interoperability | New vocabularies check for FAO water areas classification as linked data @PSNC took 2.3126602172851562e-05s
Consistency | Deprecated classes/propertiers check for FAO water areas classification as linked data @PSNC took 0.18242883682250977s
Accuracy | Check Functional Property for FAO water areas classification as linked data @PSNC took 0.42755126953125s
Accuracy | Check Inverse Functional Property for FAO water areas classification as linked data @PSNC took 0.45067334175109863s
Accuracy | Check Empty annotation labels for FAO water areas classification as linked data @PSNC took 45.24365997314453s
Accuracy | Check White space in annotation for FAO water areas classification as linked data @PSNC took 2.6801366806030273s
Accuracy | Check Datatype consistency for FAO water areas classification as linked data @PSNC took 2.6188199520111084s
Consistency | Disjoint class check for FAO water areas classification as linked data @PSNC took 0.19313502311706543s
Consistency | Check Misplaced properties for FAO water areas classification as linked data @PSNC took 86.99756336212158s
Consistency | Misplaced classes for FAO water areas classification as linked data @PSNC took 8.331379175186157s
Consistency | Check Ontology hijacking for FAO water areas classification as linked data @PSNC took 29.51398491859436s
Consistency | Check Invalid usage of undefined classes for FAO water areas classification as linked data @PSNC took 1.376218557357788s
Consistency | Check Invalid usage of undefined properties for FAO water areas classification as linked data @PSNC took 88.96876096725464s
Conciseness | Check Extensional conciseness for FAO water areas classification as linked data @PSNC took 2.698335647583008s
Conciseness | Check Intensional conciseness for FAO water areas classification as linked data @PSNC took 0.579380989074707s
Security | Sign check for FAO water areas classification as linked data @PSNC took 1.1707394123077393s
Availability | Check URIs Dereferenciability for FAO water areas classification as linked data @PSNC took 13.888201236724854s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.3578321933746338s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.02090620994567871s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 4.029273986816406e-05s
Interoperability | Check the re-using of existing vocabs for FAO water areas classification as linked data @PSNC took 5.9604644775390625e-06s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 5.7220458984375e-06s
INFO | --- Analysis for Water_Areas_Classification took 2286.088142633438s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 0.17716240882873535s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.00047898292541503906s
Extra | Recovery of all triples for Water buffer dataset from Czech Republic @PSNC took 118.26980376243591s
Performance | Total latancy measurement for Water buffer dataset from Czech Republic @PSNC took 0.9710242748260498s
Amount of data | Number of triples check for Water buffer dataset from Czech Republic @PSNC took 9.2369966506958s
Interoperability | New terms check for Water buffer dataset from Czech Republic @PSNC took 14.16929292678833s
Versatility | Languages check for Water buffer dataset from Czech Republic @PSNC took 300.25153040885925s
Interpretability | Number of blank nodes check for Water buffer dataset from Czech Republic @PSNC took 2.061394214630127s
Interpretability | RDF structures check for Water buffer dataset from Czech Republic @PSNC took 0.39275598526000977s
Versatility | Serialization formats check for Water buffer dataset from Czech Republic @PSNC took 15.16639494895935s
Availability | RDF dump link check for Water buffer dataset from Czech Republic @PSNC took 0.2831101417541504s
License | MR license check for Water buffer dataset from Czech Republic @PSNC took 0.6158351898193359s
License | HR license check for Water buffer dataset from Czech Republic @PSNC took 300.25071930885315s
Amount of data | Number of property check for Water buffer dataset from Czech Republic @PSNC took 0.22149109840393066s
Understandability | Number of label check for Water buffer dataset from Czech Republic @PSNC took 2.8340718746185303s
Understandability | URI regex check for Water buffer dataset from Czech Republic @PSNC took 1.0148019790649414s
Understandability | Vocabs check for Water buffer dataset from Czech Republic @PSNC took 0.5124895572662354s
Verifiability | Authors check for Water buffer dataset from Czech Republic @PSNC took 0.19234704971313477s
Verifiability | Publishers check for Water buffer dataset from Czech Republic @PSNC took 0.2525217533111572s
Performance | Throughput check for Water buffer dataset from Czech Republic @PSNC took 11.2677481174469s
Amount of data | Check the number of entities for Water buffer dataset from Czech Republic @PSNC took 7.319450378417969e-05s
Verifiability | Contribs. check for Water buffer dataset from Czech Republic @PSNC took 0.19910883903503418s
Interlinking | sameAs chians check for Water buffer dataset from Czech Republic @PSNC took 0.18317651748657227s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.46593546867370605s
Interlinking | skos check for Water buffer dataset from Czech Republic @PSNC took 0.453845739364624s
Timeliness | dataset update frequency check for Water buffer dataset from Czech Republic @PSNC took 5.990034103393555s
Currency | Creation date check for Water buffer dataset from Czech Republic @PSNC took 0.48097848892211914s
Currency | Modification date check for Water buffer dataset from Czech Republic @PSNC took 0.2641429901123047s
Rep.Conc. | URIs length for Water buffer dataset from Czech Republic @PSNC took 153.21198177337646s
Interoperability | New vocabularies check for Water buffer dataset from Czech Republic @PSNC took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Water buffer dataset from Czech Republic @PSNC took 0.18773841857910156s
Accuracy | Check Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.4058399200439453s
Accuracy | Check Inverse Functional Property for Water buffer dataset from Czech Republic @PSNC took 0.3998434543609619s
Accuracy | Check Empty annotation labels for Water buffer dataset from Czech Republic @PSNC took 39.906636238098145s
Accuracy | Check White space in annotation for Water buffer dataset from Czech Republic @PSNC took 2.672414541244507s
Accuracy | Check Datatype consistency for Water buffer dataset from Czech Republic @PSNC took 2.652195692062378s
Consistency | Disjoint class check for Water buffer dataset from Czech Republic @PSNC took 0.20819377899169922s
Consistency | Check Misplaced properties for Water buffer dataset from Czech Republic @PSNC took 87.28018760681152s
Consistency | Misplaced classes for Water buffer dataset from Czech Republic @PSNC took 8.413645029067993s
Consistency | Check Ontology hijacking for Water buffer dataset from Czech Republic @PSNC took 37.46278476715088s
Consistency | Check Invalid usage of undefined classes for Water buffer dataset from Czech Republic @PSNC took 1.4421775341033936s
Consistency | Check Invalid usage of undefined properties for Water buffer dataset from Czech Republic @PSNC took 88.53581714630127s
Conciseness | Check Extensional conciseness for Water buffer dataset from Czech Republic @PSNC took 2.7659318447113037s
Conciseness | Check Intensional conciseness for Water buffer dataset from Czech Republic @PSNC took 0.594611406326294s
Security | Sign check for Water buffer dataset from Czech Republic @PSNC took 1.1657013893127441s
Availability | Check URIs Dereferenciability for Water buffer dataset from Czech Republic @PSNC took 13.960287094116211s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.8828256130218506s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.02117776870727539s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 4.1484832763671875e-05s
Interoperability | Check the re-using of existing vocabs for Water buffer dataset from Czech Republic @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 1.1205673217773438e-05s
INFO | --- Analysis for Water_Buffer took 2297.7261288166046s
Availability | SPARQL endpoint availability check for WebIsALOD took 0.2611808776855469s
Availability | VoID file availability check for WebIsALOD took 0.0005915164947509766s
Extra | Recovery of all triples for WebIsALOD took 1.6167242527008057s
Performance | Total latancy measurement for WebIsALOD took 0.5371708869934082s
Amount of data | Number of triples check for WebIsALOD took 19.353164196014404s
Interoperability | New terms check for WebIsALOD took 18.661682844161987s
Versatility | Languages check for WebIsALOD took 61.45815849304199s
Interpretability | Number of blank nodes check for WebIsALOD took 0.07526803016662598s
Interpretability | RDF structures check for WebIsALOD took 0.1576366424560547s
Versatility | Serialization formats check for WebIsALOD took 0.09010100364685059s
Availability | RDF dump link check for WebIsALOD took 1.4414775371551514s
License | MR license check for WebIsALOD took 0.10654377937316895s
License | HR license check for WebIsALOD took 21.088119983673096s
Amount of data | Number of property check for WebIsALOD took 0.09122323989868164s
Understandability | Number of label check for WebIsALOD took 0.3268554210662842s
Understandability | URI regex check for WebIsALOD took 0.1762385368347168s
Understandability | Vocabs check for WebIsALOD took 0.09787154197692871s
Verifiability | Authors check for WebIsALOD took 0.11000680923461914s
Verifiability | Publishers check for WebIsALOD took 0.1085965633392334s
Performance | Throughput check for WebIsALOD took 10.43813943862915s
Amount of data | Check the number of entities for WebIsALOD took 7.200241088867188e-05s
Verifiability | Contribs. check for WebIsALOD took 0.11563944816589355s
Interlinking | sameAs chians check for WebIsALOD took 0.14828252792358398s
Interlinking | skos check for WebIsALOD took 0.11038565635681152s
Interlinking | skos check for WebIsALOD took 0.07374858856201172s
Timeliness | dataset update frequency check for WebIsALOD took 0.09229564666748047s
Currency | Creation date check for WebIsALOD took 0.1800382137298584s
Currency | Modification date check for WebIsALOD took 0.18672537803649902s
Rep.Conc. | URIs length for WebIsALOD took 80.37737846374512s
Interoperability | New vocabularies check for WebIsALOD took 2.5651462078094482s
Consistency | Deprecated classes/propertiers check for WebIsALOD took 0.08150291442871094s
Accuracy | Check Functional Property for WebIsALOD took 0.10939860343933105s
Accuracy | Check Inverse Functional Property for WebIsALOD took 0.14525914192199707s
Accuracy | Check Empty annotation labels for WebIsALOD took 0.4666409492492676s
Accuracy | Check White space in annotation for WebIsALOD took 0.030092477798461914s
Accuracy | Check Datatype consistency for WebIsALOD took 0.02896595001220703s
Consistency | Disjoint class check for WebIsALOD took 0.10460448265075684s
Consistency | Check Misplaced properties for WebIsALOD took 60.90954899787903s
Consistency | Misplaced classes for WebIsALOD took 0.21291875839233398s
Consistency | Check Ontology hijacking for WebIsALOD took 2.0096256732940674s
Consistency | Check Invalid usage of undefined classes for WebIsALOD took 1.6031677722930908s
Consistency | Check Invalid usage of undefined properties for WebIsALOD took 62.16514492034912s
Conciseness | Check Extensional conciseness for WebIsALOD took 0.03331279754638672s
Conciseness | Check Intensional conciseness for WebIsALOD took 0.125518798828125s
Security | Sign check for WebIsALOD took 0.0901792049407959s
Availability | Check URIs Dereferenciability for WebIsALOD took 14.52422547340393s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.7636144161224365s
Reputation | Calculation of the PageRank for WebIsALOD took 0.02234482765197754s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 9.274482727050781e-05s
Interoperability | Check the re-using of existing vocabs for WebIsALOD took 2.363407850265503s
Believability | Calculation of trust value for WebIsALOD took 1.33514404296875e-05s
INFO | --- Analysis for webisalod took 528.9772374629974s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 4.4345855712890625e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.2814822196960449s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.020679712295532227s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 3.6716461181640625e-05s
Believability | Calculation of trust value for webnmasunotraveler took 7.62939453125e-06s
INFO | --- Analysis for webnmasunotraveler took 8.617476463317871s
Availability | SPARQL endpoint availability check for Whisky Circle took 4.315376281738281e-05s
Availability | VoID file availability check for Whisky Circle took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.25165557861328125s
Reputation | Calculation of the PageRank for Whisky Circle took 0.022161483764648438s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00010418891906738281s
Believability | Calculation of trust value for Whisky Circle took 1.239776611328125e-05s
INFO | --- Analysis for whisky-circle-info took 7.140979051589966s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 17.808950424194336s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.0008413791656494141s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.24834942817687988s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.020830631256103516s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 4.267692565917969e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 1.239776611328125e-05s
INFO | --- Analysis for WHOnto took 34.954166412353516s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.2630023956298828s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.02111530303955078s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for whonto took 8.37511420249939s
Availability | SPARQL endpoint availability check for Wikidata took 0.7510461807250977s
Availability | VoID file availability check for Wikidata took 0.0005953311920166016s
Extra | Recovery of all triples for Wikidata took 22.60704207420349s
Performance | Total latancy measurement for Wikidata took 1.2997732162475586s
Amount of data | Number of triples check for Wikidata took 65.37552642822266s
Interoperability | New terms check for Wikidata took 2.132239580154419s
Versatility | Languages check for Wikidata took 65.19926977157593s
Interpretability | Number of blank nodes check for Wikidata took 65.20279693603516s
Interpretability | RDF structures check for Wikidata took 0.4688234329223633s
Versatility | Serialization formats check for Wikidata took 0.35028529167175293s
Availability | RDF dump link check for Wikidata took 0.21387171745300293s
License | MR license check for Wikidata took 0.24575519561767578s
License | HR license check for Wikidata took 65.21138668060303s
Amount of data | Number of property check for Wikidata took 0.31255078315734863s
Understandability | Number of label check for Wikidata took 65.20062470436096s
Understandability | URI regex check for Wikidata took 0.5551247596740723s
Understandability | Vocabs check for Wikidata took 0.33783626556396484s
Verifiability | Authors check for Wikidata took 0.2058274745941162s
Verifiability | Publishers check for Wikidata took 0.21380138397216797s
Performance | Throughput check for Wikidata took 11.868505954742432s
Amount of data | Check the number of entities for Wikidata took 6.747245788574219e-05s
Verifiability | Contribs. check for Wikidata took 0.21831369400024414s
Interlinking | sameAs chians check for Wikidata took 17.95768141746521s
Interlinking | skos check for Wikidata took 0.2154216766357422s
Interlinking | skos check for Wikidata took 0.11446499824523926s
Timeliness | dataset update frequency check for Wikidata took 0.22774624824523926s
Currency | Creation date check for Wikidata took 0.42467832565307617s
Currency | Modification date check for Wikidata took 0.4575002193450928s
Rep.Conc. | URIs length for Wikidata took 33.13854122161865s
Interoperability | New vocabularies check for Wikidata took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Wikidata took 0.21378517150878906s
Accuracy | Check Empty annotation labels for Wikidata took 11.967516660690308s
Accuracy | Check White space in annotation for Wikidata took 2.6491618156433105s
Accuracy | Check Datatype consistency for Wikidata took 4.522154808044434s
Consistency | Disjoint class check for Wikidata took 0.22235369682312012s
Consistency | Check Misplaced properties for Wikidata took 14.05532956123352s
Consistency | Misplaced classes for Wikidata took 8.871282577514648s
Consistency | Check Ontology hijacking for Wikidata took 46.457016706466675s
Consistency | Check Invalid usage of undefined classes for Wikidata took 1.3994271755218506s
Consistency | Check Invalid usage of undefined properties for Wikidata took 4.2864391803741455s
Conciseness | Check Extensional conciseness for Wikidata took 2.8213911056518555s
Conciseness | Check Intensional conciseness for Wikidata took 1.7599570751190186s
Security | Sign check for Wikidata took 0.32079076766967773s
Availability | Check URIs Dereferenciability for Wikidata took 19.231322050094604s
Completeness | Calculation of interlinking completeness for Wikidata took 0.4009113311767578s
Reputation | Calculation of the PageRank for Wikidata took 0.021672964096069336s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.0003142356872558594s
Interoperability | Check the re-using of existing vocabs for Wikidata took 1.9073486328125e-06s
Believability | Calculation of trust value for Wikidata took 9.5367431640625e-06s
INFO | --- Analysis for wikidata took 968.4091231822968s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 0.0001049041748046875s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.2460947036743164s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.02084183692932129s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 7.152557373046875e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 1.2874603271484375e-05s
INFO | --- Analysis for wikilinks-rdf-nif took 2.850494861602783s
Availability | SPARQL endpoint availability check for WikiPathways took 4.744529724121094e-05s
Availability | VoID file availability check for WikiPathways took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.27123427391052246s
Reputation | Calculation of the PageRank for WikiPathways took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 3.0279159545898438e-05s
Believability | Calculation of trust value for WikiPathways took 1.2159347534179688e-05s
INFO | --- Analysis for wikipathways took 2.8946189880371094s
Availability | SPARQL endpoint availability check for WikiWord Thesaurus Data took 8.249282836914062e-05s
Availability | VoID file availability check for WikiWord Thesaurus Data took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for WikiWord Thesaurus Data took 0.2739858627319336s
Reputation | Calculation of the PageRank for WikiWord Thesaurus Data took 0.02202916145324707s
Interlinking | Calculation of Degree of Connection for WikiWord Thesaurus Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for WikiWord Thesaurus Data took 0.0008819103240966797s
Interlinking | Calculation of Clustering coefficient for WikiWord Thesaurus Data took 3.4809112548828125e-05s
Believability | Calculation of trust value for WikiWord Thesaurus Data took 1.33514404296875e-05s
INFO | --- Analysis for wikiword_thesaurus took 2.865967273712158s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.2821488380432129s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.2609825134277344s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.320808410644531e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 1.5020370483398438e-05s
INFO | --- Analysis for wiktionary-dbpedia-org took 4.248386383056641s
Availability | SPARQL endpoint availability check for Wings workflow provenance dataset took 7.700920104980469e-05s
Availability | VoID file availability check for Wings workflow provenance dataset took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Wings workflow provenance dataset took 0.27138233184814453s
Reputation | Calculation of the PageRank for Wings workflow provenance dataset took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for Wings workflow provenance dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Wings workflow provenance dataset took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Wings workflow provenance dataset took 3.170967102050781e-05s
Believability | Calculation of trust value for Wings workflow provenance dataset took 7.867813110351562e-06s
INFO | --- Analysis for wings-workflow-provenance-dataset took 2.8025314807891846s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2723746299743652s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.25908613204956055s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.020730972290039062s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.0994415283203125e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 1.2636184692382812e-05s
INFO | --- Analysis for wl-kg took 3.893807888031006s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 4.315376281738281e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.23975706100463867s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.02065873146057129s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 7.367134094238281e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 1.1920928955078125e-05s
INFO | --- Analysis for wn-wiki-instances took 3.0211117267608643s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.13025569915771484s
Availability | VoID file availability check for World Loanword Database took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.2621016502380371s
Reputation | Calculation of the PageRank for World Loanword Database took 0.021867990493774414s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0009191036224365234s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 8.511543273925781e-05s
Believability | Calculation of trust value for World Loanword Database took 1.239776611328125e-05s
INFO | --- Analysis for wold took 2.8021795749664307s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 4.57763671875e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.2432725429534912s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 3.075599670410156e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.33514404296875e-05s
INFO | --- Analysis for woodtrick took 3.0056705474853516s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 0.5261187553405762s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.26404523849487305s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.020951271057128906s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0009124279022216797s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 5.340576171875e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for WordFormationLatin took 4.021403074264526s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 8.821487426757812e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.27459001541137695s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.0001049041748046875s
Believability | Calculation of trust value for WordLift Blog EN took 1.239776611328125e-05s
INFO | --- Analysis for wordlift-io-blog-en took 2.822774887084961s
Availability | SPARQL endpoint availability check for WordLift IT took 4.315376281738281e-05s
Availability | VoID file availability check for WordLift IT took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.2568037509918213s
Reputation | Calculation of the PageRank for WordLift IT took 0.02270364761352539s
Interlinking | Calculation of Degree of Connection for WordLift IT took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for WordLift IT took 0.0009801387786865234s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00012183189392089844s
Believability | Calculation of trust value for WordLift IT took 1.2636184692382812e-05s
INFO | --- Analysis for wordlift-io-blog-it took 2.713186264038086s
Availability | SPARQL endpoint availability check for Wordnet took 0.0001227855682373047s
Availability | VoID file availability check for Wordnet took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Wordnet took 0.25037384033203125s
Reputation | Calculation of the PageRank for Wordnet took 0.021613359451293945s
Interlinking | Calculation of Degree of Connection for Wordnet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Wordnet took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Wordnet took 4.1484832763671875e-05s
Believability | Calculation of trust value for Wordnet took 1.239776611328125e-05s
INFO | --- Analysis for wordnet took 3.0044331550598145s
Availability | SPARQL endpoint availability check for WordNet-RDF took 4.1961669921875e-05s
Availability | VoID file availability check for WordNet-RDF took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.24782204627990723s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.250640869140625e-05s
Believability | Calculation of trust value for WordNet-RDF took 1.3113021850585938e-05s
INFO | --- Analysis for wordnet-rdf took 2.3148343563079834s
Availability | SPARQL endpoint availability check for wordpress took 4.649162292480469e-05s
Availability | VoID file availability check for wordpress took 0.0007688999176025391s
Completeness | Calculation of interlinking completeness for wordpress took 0.25731372833251953s
Reputation | Calculation of the PageRank for wordpress took 0.020928144454956055s
Interlinking | Calculation of Degree of Connection for wordpress took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for wordpress took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.821487426757812e-05s
Believability | Calculation of trust value for wordpress took 1.2874603271484375e-05s
INFO | --- Analysis for wordpress took 2.537400245666504s
Availability | SPARQL endpoint availability check for wordpress.post took 5.054473876953125e-05s
Availability | VoID file availability check for wordpress.post took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for wordpress.post took 0.2592020034790039s
Reputation | Calculation of the PageRank for wordpress.post took 0.020873308181762695s
Interlinking | Calculation of Degree of Connection for wordpress.post took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for wordpress.post took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for wordpress.post took 3.0040740966796875e-05s
Believability | Calculation of trust value for wordpress.post took 1.1682510375976562e-05s
INFO | --- Analysis for wordpress_post took 2.782315492630005s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 0.48364877700805664s
Availability | VoID file availability check for World Bank Linked Data took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.27811741828918457s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00012183189392089844s
Believability | Calculation of trust value for World Bank Linked Data took 1.0013580322265625e-05s
INFO | --- Analysis for world-bank-linked-data took 3.0054845809936523s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 0.8690023422241211s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.23378300666809082s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.020620346069335938s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.273124694824219e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 8.106231689453125e-06s
INFO | --- Analysis for world-factbook-fu-berlin took 5.052342653274536s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 4.1961669921875e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.27124762535095215s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.02188277244567871s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.416175842285156e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 1.0013580322265625e-05s
INFO | --- Analysis for world-wide-web-foundation took 5.610456228256226s
Availability | SPARQL endpoint availability check for WikiPathways took 4.220008850097656e-05s
Availability | VoID file availability check for WikiPathways took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.2647285461425781s
Reputation | Calculation of the PageRank for WikiPathways took 0.020739078521728516s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 3.123283386230469e-05s
Believability | Calculation of trust value for WikiPathways took 1.33514404296875e-05s
INFO | --- Analysis for wp took 2.863659143447876s
Availability | SPARQL endpoint availability check for wunderground.weatherreport took 4.315376281738281e-05s
Availability | VoID file availability check for wunderground.weatherreport took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for wunderground.weatherreport took 0.2622981071472168s
Reputation | Calculation of the PageRank for wunderground.weatherreport took 0.022222518920898438s
Interlinking | Calculation of Degree of Connection for wunderground.weatherreport took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for wunderground.weatherreport took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for wunderground.weatherreport took 3.0279159545898438e-05s
Believability | Calculation of trust value for wunderground.weatherreport took 1.2636184692382812e-05s
INFO | --- Analysis for wunderground_weatherreport took 2.8917815685272217s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.3105480670928955s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.01918339729309082s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 6.37038254737854s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.8344111442565918s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.20588922500610352s
Interoperability | New terms check for World War 1 as Linked Open Data took 1.9471349716186523s
Versatility | Languages check for World War 1 as Linked Open Data took 0.5046234130859375s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.21336150169372559s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.4245879650115967s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.2932150363922119s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.22606754302978516s
Availability | RDF dump link check for World War 1 as Linked Open Data took 6.9651830196380615s
License | MR license check for World War 1 as Linked Open Data took 0.17226696014404297s
License | HR license check for World War 1 as Linked Open Data took 1.6627330780029297s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.17551541328430176s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.6649878025054932s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.3509407043457031s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.21261215209960938s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.1812431812286377s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.16471290588378906s
Performance | Throughput check for World War 1 as Linked Open Data took 10.94536018371582s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.07014083862304688s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.17026114463806152s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.20263290405273438s
Interlinking | skos check for World War 1 as Linked Open Data took 0.16671967506408691s
Interlinking | skos check for World War 1 as Linked Open Data took 0.15394997596740723s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.18902897834777832s
Currency | Creation date check for World War 1 as Linked Open Data took 0.32598161697387695s
Currency | Modification date check for World War 1 as Linked Open Data took 0.17393159866333008s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 2.025899648666382s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 6.499100208282471s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.21432995796203613s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.17088937759399414s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.177565336227417s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.1855218410491943s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.04962921142578125s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.3122889995574951s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.17639660835266113s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.6049048900604248s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.0995664596557617s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.3395936489105225s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.5814125537872314s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.1967918872833252s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 1.1941032409667969s
Security | Sign check for World War 1 as Linked Open Data took 0.22067952156066895s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 7.61635684967041s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.25320911407470703s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.02071094512939453s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 8.702278137207031e-05s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 6.007530927658081s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 1.3113021850585938e-05s
INFO | --- Analysis for ww1lod took 96.90845346450806s
Availability | SPARQL endpoint availability check for XlendiAmphorae took 6.270408630371094e-05s
Availability | VoID file availability check for XlendiAmphorae took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for XlendiAmphorae took 0.28757548332214355s
Reputation | Calculation of the PageRank for XlendiAmphorae took 0.020966053009033203s
Interlinking | Calculation of Degree of Connection for XlendiAmphorae took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for XlendiAmphorae took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for XlendiAmphorae took 4.3392181396484375e-05s
Believability | Calculation of trust value for XlendiAmphorae took 1.3113021850585938e-05s
INFO | --- Analysis for xlendiamphorae took 2.955345392227173s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.3078114986419678s
Availability | VoID file availability check for xLiD-Lexica took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.2505197525024414s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.021939516067504883s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 7.534027099609375e-05s
Believability | Calculation of trust value for xLiD-Lexica took 1.2159347534179688e-05s
INFO | --- Analysis for xlid-lexica took 3.979135274887085s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 4.458427429199219e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.25939178466796875s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 4.1484832763671875e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 1.1682510375976562e-05s
INFO | --- Analysis for xwn took 2.6779189109802246s
Availability | SPARQL endpoint availability check for xxx took 4.38690185546875e-05s
Availability | VoID file availability check for xxx took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for xxx took 0.24668169021606445s
Reputation | Calculation of the PageRank for xxx took 0.020823001861572266s
Interlinking | Calculation of Degree of Connection for xxx took 3.4809112548828125e-05s
Interlinking | Calculation of Centrality for xxx took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for xxx took 3.0517578125e-05s
Believability | Calculation of trust value for xxx took 1.2874603271484375e-05s
INFO | --- Analysis for xx took 2.265907049179077s
Availability | SPARQL endpoint availability check for YAGO took 4.1961669921875e-05s
Availability | VoID file availability check for YAGO took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for YAGO took 0.2619509696960449s
Reputation | Calculation of the PageRank for YAGO took 0.02099132537841797s
Interlinking | Calculation of Degree of Connection for YAGO took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.00013113021850585938s
Believability | Calculation of trust value for YAGO took 1.1920928955078125e-05s
INFO | --- Analysis for yago took 4.16296648979187s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 4.431434392929077s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.2943990230560303s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.020893096923828125s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 7.581710815429688e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 1.1682510375976562e-05s
INFO | --- Analysis for yahoo_geoplanet took 17.189118146896362s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.1393134593963623s
Availability | VoID file availability check for Yale Senselab took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.25989675521850586s
Reputation | Calculation of the PageRank for Yale Senselab took 0.021161556243896484s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 3.838539123535156e-05s
Believability | Calculation of trust value for Yale Senselab took 9.5367431640625e-06s
INFO | --- Analysis for yale_senselab took 11.006488561630249s
Availability | SPARQL endpoint availability check for test-dapp-2 took 8.273124694824219e-05s
Availability | VoID file availability check for test-dapp-2 took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.2499096393585205s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.021068572998046875s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 3.075599670410156e-05s
Believability | Calculation of trust value for test-dapp-2 took 9.5367431640625e-06s
INFO | --- Analysis for yordhis took 2.389979362487793s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 0.8663601875305176s
Availability | VoID file availability check for Yovisto - academic video search took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.3898911476135254s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.021746158599853516s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.604194641113281e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 9.775161743164062e-06s
INFO | --- Analysis for yovisto took 26.3126699924469s
Availability | SPARQL endpoint availability check for Yleinen suomalainen asiasanasto - YSA took 9.298324584960938e-05s
Availability | VoID file availability check for Yleinen suomalainen asiasanasto - YSA took 0.0008459091186523438s
Completeness | Calculation of interlinking completeness for Yleinen suomalainen asiasanasto - YSA took 0.260833740234375s
Reputation | Calculation of the PageRank for Yleinen suomalainen asiasanasto - YSA took 0.02102351188659668s
Interlinking | Calculation of Degree of Connection for Yleinen suomalainen asiasanasto - YSA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Yleinen suomalainen asiasanasto - YSA took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Yleinen suomalainen asiasanasto - YSA took 3.4332275390625e-05s
Believability | Calculation of trust value for Yleinen suomalainen asiasanasto - YSA took 1.239776611328125e-05s
INFO | --- Analysis for ysa took 4.277946710586548s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0006253719329833984s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.27460193634033203s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.435943603515625e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 1.049041748046875e-05s
INFO | --- Analysis for yso took 4.0732996463775635s
Availability | SPARQL endpoint availability check for yso-fi-allars took 4.2438507080078125e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.252286434173584s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.022651195526123047s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.337860107421875e-05s
Believability | Calculation of trust value for yso-fi-allars took 1.3589859008789062e-05s
INFO | --- Analysis for yso-fi-allars took 2.8030011653900146s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 4.4345855712890625e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.2641012668609619s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.021036386489868164s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.528594970703125e-05s
Believability | Calculation of trust value for yso-fi-ysa took 1.2874603271484375e-05s
INFO | --- Analysis for yso-fi-ysa took 3.2470972537994385s
Availability | SPARQL endpoint availability check for YSO places took 0.7019293308258057s
Availability | VoID file availability check for YSO places took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for YSO places took 0.2702808380126953s
Reputation | Calculation of the PageRank for YSO places took 0.021906137466430664s
Interlinking | Calculation of Degree of Connection for YSO places took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for YSO places took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for YSO places took 3.2901763916015625e-05s
Believability | Calculation of trust value for YSO places took 1.0728836059570312e-05s
INFO | --- Analysis for yso-paikat took 4.264256000518799s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 8.845329284667969e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0007712841033935547s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.25128602981567383s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.020939111709594727s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 4.553794860839844e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 1.0013580322265625e-05s
INFO | --- Analysis for zaragoza-datosabiertos took 7.644352436065674s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 8.702278137207031e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.25486135482788086s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.02100396156311035s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.552436828613281e-05s
Believability | Calculation of trust value for zaragoza_turruta took 1.2159347534179688e-05s
INFO | --- Analysis for zaragoza_turruta took 2.483229398727417s
Availability | SPARQL endpoint availability check for ZBW Labs took 8.821487426757812e-05s
Availability | VoID file availability check for ZBW Labs took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.23973989486694336s
Reputation | Calculation of the PageRank for ZBW Labs took 0.021199941635131836s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 6.747245788574219e-05s
Believability | Calculation of trust value for ZBW Labs took 1.2874603271484375e-05s
INFO | --- Analysis for zbw-labs took 3.3281524181365967s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.15084266662597656s
Availability | VoID file availability check for 20th Century Press Archives took 0.0005466938018798828s
Extra | Recovery of all triples for 20th Century Press Archives took 65.10130763053894s
Performance | Total latancy measurement for 20th Century Press Archives took 0.7424716949462891s
Amount of data | Number of triples check for 20th Century Press Archives took 1.7869255542755127s
Interoperability | New terms check for 20th Century Press Archives took 1.5987005233764648s
Versatility | Languages check for 20th Century Press Archives took 3.4438719749450684s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.9727368354797363s
Interpretability | RDF structures check for 20th Century Press Archives took 0.16086626052856445s
Versatility | Serialization formats check for 20th Century Press Archives took 0.12750005722045898s
Availability | RDF dump link check for 20th Century Press Archives took 0.139448881149292s
License | MR license check for 20th Century Press Archives took 0.13037633895874023s
License | HR license check for 20th Century Press Archives took 6.185900449752808s
Amount of data | Number of property check for 20th Century Press Archives took 0.17216730117797852s
Understandability | Number of label check for 20th Century Press Archives took 0.7779109477996826s
Understandability | URI regex check for 20th Century Press Archives took 0.2686152458190918s
Understandability | Vocabs check for 20th Century Press Archives took 0.12702155113220215s
Verifiability | Authors check for 20th Century Press Archives took 0.13682866096496582s
Verifiability | Publishers check for 20th Century Press Archives took 0.13674163818359375s
Performance | Throughput check for 20th Century Press Archives took 10.701937198638916s
Amount of data | Check the number of entities for 20th Century Press Archives took 6.842613220214844e-05s
Verifiability | Contribs. check for 20th Century Press Archives took 0.1564955711364746s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.1409306526184082s
Interlinking | skos check for 20th Century Press Archives took 0.20576691627502441s
Interlinking | skos check for 20th Century Press Archives took 0.20683646202087402s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.13332223892211914s
Currency | Creation date check for 20th Century Press Archives took 0.2931852340698242s
Currency | Modification date check for 20th Century Press Archives took 0.29801297187805176s
Rep.Conc. | URIs length for 20th Century Press Archives took 15.843560218811035s
Interoperability | New vocabularies check for 20th Century Press Archives took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.12824797630310059s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.13632869720458984s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.1472175121307373s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 4.836744785308838s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8755056858062744s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 3.9872026443481445s
Consistency | Disjoint class check for 20th Century Press Archives took 0.16584396362304688s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.2225515842437744s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.619664430618286s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 7.006749391555786s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.5305252075195312s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.766648292541504s
Security | Sign check for 20th Century Press Archives took 0.1587820053100586s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 1029.8272759914398s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.9378187656402588s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.021658658981323242s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 6.151199340820312e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00011658668518066406s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 1.9073486328125e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 1.33514404296875e-05s
INFO | --- Analysis for zbw-pressemappe20 took 1190.8647847175598s
Availability | SPARQL endpoint availability check for zhishi.lemon took 8.845329284667969e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.2628333568572998s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.021364927291870117s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 5.054473876953125e-05s
Believability | Calculation of trust value for zhishi.lemon took 1.4781951904296875e-05s
INFO | --- Analysis for zhishi-lemon took 24.490215301513672s
Availability | SPARQL endpoint availability check for Zhishi.me took 10.46342396736145s
Availability | VoID file availability check for Zhishi.me took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.2650117874145508s
Reputation | Calculation of the PageRank for Zhishi.me took 0.02153921127319336s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0008106231689453125s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 7.390975952148438e-05s
Believability | Calculation of trust value for Zhishi.me took 1.1920928955078125e-05s
INFO | --- Analysis for zhishi-me took 15.291069030761719s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.267692565917969e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.27662158012390137s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.021205663681030273s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 9.107589721679688e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 1.33514404296875e-05s
INFO | --- Analysis for zitgist-musicbrainz took 2.928760051727295s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 9.512901306152344e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.2532186508178711s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.02085089683532715s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 2.7894973754882812e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 1.3589859008789062e-05s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 2.622533082962036s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.3639559745788574s
Availability | VoID file availability check for performing-arts.ch took 0.0005104541778564453s
Extra | Recovery of all triples for performing-arts.ch took 15.922816753387451s
Performance | Total latancy measurement for performing-arts.ch took 0.751978874206543s
Amount of data | Number of triples check for performing-arts.ch took 36.96359968185425s
Interoperability | New terms check for performing-arts.ch took 1.505361557006836s
Versatility | Languages check for performing-arts.ch took 60.14006733894348s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.15099287033081s
Interpretability | RDF structures check for performing-arts.ch took 0.1481778621673584s
Versatility | Serialization formats check for performing-arts.ch took 0.17227768898010254s
Availability | RDF dump link check for performing-arts.ch took 0.16195225715637207s
License | MR license check for performing-arts.ch took 1.3372328281402588s
License | HR license check for performing-arts.ch took 51.592079162597656s
Amount of data | Number of property check for performing-arts.ch took 0.18968892097473145s
Understandability | Number of label check for performing-arts.ch took 2.8407578468322754s
Understandability | URI regex check for performing-arts.ch took 0.31331634521484375s
Understandability | Vocabs check for performing-arts.ch took 0.1612091064453125s
Verifiability | Authors check for performing-arts.ch took 0.14790010452270508s
Verifiability | Publishers check for performing-arts.ch took 0.15952014923095703s
Performance | Throughput check for performing-arts.ch took 10.722282409667969s
Amount of data | Check the number of entities for performing-arts.ch took 3.2901763916015625e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.14267492294311523s
Interlinking | sameAs chians check for performing-arts.ch took 0.6236686706542969s
Interlinking | skos check for performing-arts.ch took 0.16663002967834473s
Interlinking | skos check for performing-arts.ch took 0.14720797538757324s
Timeliness | dataset update frequency check for performing-arts.ch took 0.16238975524902344s
Currency | Creation date check for performing-arts.ch took 0.316601037979126s
Currency | Modification date check for performing-arts.ch took 0.3854694366455078s
Rep.Conc. | URIs length for performing-arts.ch took 19.42061996459961s
Interoperability | New vocabularies check for performing-arts.ch took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.15776491165161133s
Accuracy | Check Functional Property for performing-arts.ch took 0.15517640113830566s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.16742610931396484s
Accuracy | Check Empty annotation labels for performing-arts.ch took 10.701746940612793s
Accuracy | Check White space in annotation for performing-arts.ch took 2.5470032691955566s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.786743879318237s
Consistency | Disjoint class check for performing-arts.ch took 0.17499041557312012s
Consistency | Check Misplaced properties for performing-arts.ch took 0.38842201232910156s
Consistency | Misplaced classes for performing-arts.ch took 8.489924192428589s
Consistency | Check Ontology hijacking for performing-arts.ch took 32.010839223861694s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 15963.905156612396s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 3.981170177459717s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.8671634197235107s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.26602959632873535s
Security | Sign check for performing-arts.ch took 0.41436004638671875s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.278809070587158s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.8537447452545166s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.021185874938964844s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.3589859008789062e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 2.1457672119140625e-06s
Believability | Calculation of trust value for performing-arts.ch took 1.1920928955078125e-05s
INFO | --- Analysis for performing-arts.ch took 16711.61080121994s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.518303632736206s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.2732698917388916s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.021404266357421875s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.5735626220703125e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 1.1205673217773438e-05s
INFO | --- Analysis for The-AA-Thesaurus took 10.008286476135254s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.5483849048614502s
Availability | VoID file availability check for MiMoTextBase took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.2758293151855469s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.022220373153686523s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.239776611328125e-05s
Believability | Calculation of trust value for MiMoTextBase took 9.298324584960938e-06s
INFO | --- Analysis for MiMoTextBase took 6.66463565826416s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.5886797904968262s
Availability | VoID file availability check for National Library of Sweden took 0.0005660057067871094s
Extra | Recovery of all triples for National Library of Sweden took 14.609724998474121s
Performance | Total latancy measurement for National Library of Sweden took 1.0542356967926025s
Amount of data | Number of triples check for National Library of Sweden took 24.660666942596436s
Interoperability | New terms check for National Library of Sweden took 15.611595869064331s
Versatility | Languages check for National Library of Sweden took 0.2017529010772705s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.2334659099579s
Interpretability | RDF structures check for National Library of Sweden took 0.3117823600769043s
Versatility | Serialization formats check for National Library of Sweden took 0.2760155200958252s
Availability | RDF dump link check for National Library of Sweden took 0.2170724868774414s
License | MR license check for National Library of Sweden took 0.3481323719024658s
License | HR license check for National Library of Sweden took 0.2736966609954834s
Amount of data | Number of property check for National Library of Sweden took 0.20328903198242188s
Understandability | Number of label check for National Library of Sweden took 0.4832930564880371s
Understandability | URI regex check for National Library of Sweden took 0.4836602210998535s
Understandability | Vocabs check for National Library of Sweden took 0.20203447341918945s
Verifiability | Authors check for National Library of Sweden took 0.22466158866882324s
Verifiability | Publishers check for National Library of Sweden took 0.24737763404846191s
Performance | Throughput check for National Library of Sweden took 10.659407138824463s
Amount of data | Check the number of entities for National Library of Sweden took 7.653236389160156e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.27477121353149414s
Interlinking | sameAs chians check for National Library of Sweden took 0.2460024356842041s
Interlinking | skos check for National Library of Sweden took 0.4291718006134033s
Interlinking | skos check for National Library of Sweden took 0.2028789520263672s
Timeliness | dataset update frequency check for National Library of Sweden took 0.22632575035095215s
Currency | Creation date check for National Library of Sweden took 0.4660451412200928s
Currency | Modification date check for National Library of Sweden took 0.4373643398284912s
Rep.Conc. | URIs length for National Library of Sweden took 82.00461506843567s
Interoperability | New vocabularies check for National Library of Sweden took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.2115471363067627s
Accuracy | Check Functional Property for National Library of Sweden took 0.24831700325012207s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.22226476669311523s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.27156662940979004s
Consistency | Disjoint class check for National Library of Sweden took 0.20002985000610352s
Consistency | Check Misplaced properties for National Library of Sweden took 61.52485370635986s
Consistency | Misplaced classes for National Library of Sweden took 1.132293462753296s
Consistency | Check Ontology hijacking for National Library of Sweden took 5.741234540939331s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.2930595874786377s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 62.49319791793823s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.28473448753356934s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.37125086784362793s
Security | Sign check for National Library of Sweden took 0.3015024662017822s
Availability | Check URIs Dereferenciability for National Library of Sweden took 1473.4115197658539s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 1.5234804153442383s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.020745515823364258s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 2.193450927734375e-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.2636184692382812e-05s
INFO | --- Analysis for NLS took 2563.3532819747925s
Availability | SPARQL endpoint availability check for Japan Search took 2.028107166290283s
Availability | VoID file availability check for Japan Search took 0.0006463527679443359s
Extra | Recovery of all triples for Japan Search took 3.5172924995422363s
Performance | Total latancy measurement for Japan Search took 3.0925517082214355s
Amount of data | Number of triples check for Japan Search took 5.0066916942596436s
Interoperability | New terms check for Japan Search took 3.7779457569122314s
Versatility | Languages check for Japan Search took 0.764711856842041s
Interpretability | Number of blank nodes check for Japan Search took 10.298478364944458s
Interpretability | RDF structures check for Japan Search took 0.4988827705383301s
Versatility | Serialization formats check for Japan Search took 0.5058705806732178s
Availability | RDF dump link check for Japan Search took 0.33292675018310547s
License | MR license check for Japan Search took 1.407209873199463s
License | HR license check for Japan Search took 10.317638397216797s
Amount of data | Number of property check for Japan Search took 0.7223498821258545s
Understandability | Number of label check for Japan Search took 2.706951379776001s
Understandability | URI regex check for Japan Search took 0.6346969604492188s
Understandability | Vocabs check for Japan Search took 0.7405266761779785s
Verifiability | Authors check for Japan Search took 0.3382387161254883s
Verifiability | Publishers check for Japan Search took 0.2628493309020996s
Performance | Throughput check for Japan Search took 11.514472484588623s
Amount of data | Check the number of entities for Japan Search took 7.200241088867188e-05s
Verifiability | Contribs. check for Japan Search took 0.28565001487731934s
Interlinking | sameAs chians check for Japan Search took 0.32094669342041016s
Interlinking | skos check for Japan Search took 0.3651394844055176s
Interlinking | skos check for Japan Search took 0.28349971771240234s
Timeliness | dataset update frequency check for Japan Search took 0.45525312423706055s
Currency | Creation date check for Japan Search took 0.593829870223999s
Currency | Modification date check for Japan Search took 0.5310726165771484s
Rep.Conc. | URIs length for Japan Search took 13.70344614982605s
Interoperability | New vocabularies check for Japan Search took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.7126402854919434s
Accuracy | Check Empty annotation labels for Japan Search took 0.6551501750946045s
Accuracy | Check White space in annotation for Japan Search took 0.029534578323364258s
Accuracy | Check Datatype consistency for Japan Search took 0.029020309448242188s
Consistency | Disjoint class check for Japan Search took 0.30546140670776367s
Consistency | Check Misplaced properties for Japan Search took 10.803014039993286s
Consistency | Misplaced classes for Japan Search took 1.0588500499725342s
Consistency | Check Ontology hijacking for Japan Search took 3.491844654083252s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.3098633289337158s
Consistency | Check Invalid usage of undefined properties for Japan Search took 12.311804294586182s
Conciseness | Check Extensional conciseness for Japan Search took 0.03554987907409668s
Conciseness | Check Intensional conciseness for Japan Search took 0.5121002197265625s
Security | Sign check for Japan Search took 0.7642593383789062s
Availability | Check URIs Dereferenciability for Japan Search took 13.072684288024902s
Completeness | Calculation of interlinking completeness for Japan Search took 0.6583611965179443s
Reputation | Calculation of the PageRank for Japan Search took 0.020978927612304688s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Japan Search took 1.9073486328125e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 1.1920928955078125e-06s
Believability | Calculation of trust value for Japan Search took 6.198883056640625e-06s
INFO | --- Analysis for Japan-Search took 1950.4570977687836s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 60.02665662765503s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 32.2948784828186s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.021069765090942383s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 2.002716064453125e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.6450881958007812e-05s
INFO | --- Analysis for Rijksmuseum took 456.86900305747986s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 60.02964448928833s
Availability | VoID file availability check for Finnish Public Libraries took 0.0008168220520019531s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 32.27699589729309s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.02116870880126953s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 2.002716064453125e-05s
Believability | Calculation of trust value for Finnish Public Libraries took 1.5735626220703125e-05s
INFO | --- Analysis for FI-Library took 476.8219916820526s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 60.02525997161865s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0009257793426513672s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 32.28691816329956s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.021210670471191406s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.3828277587890625e-05s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 1.0967254638671875e-05s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 553.9314093589783s
Availability | SPARQL endpoint availability check for National Library Netherlands took 60.02738070487976s
Availability | VoID file availability check for National Library Netherlands took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 46.15064740180969s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.02155590057373047s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 1.9311904907226562e-05s
Believability | Calculation of trust value for National Library Netherlands took 1.5735626220703125e-05s
INFO | --- Analysis for National-Library-Netherlands took 749.4134826660156s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 60.02768397331238s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 60.02829122543335s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.020923614501953125s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.8596649169921875e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.6927719116210938e-05s
INFO | --- Analysis for Antique-Renaissance took 726.4955985546112s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 60.01972579956055s
Availability | VoID file availability check for ARTSDATA.CA took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 60.024593353271484s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.02092576026916504s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.4781951904296875e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 1.5735626220703125e-05s
INFO | --- Analysis for ARTSDATA-CA took 740.3349328041077s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 60.02502489089966s
Availability | VoID file availability check for Architecture of Knowledge took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 60.02638244628906s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.02124953269958496s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.4781951904296875e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 9.059906005859375e-06s
INFO | --- Analysis for ArCo took 760.3509805202484s
Availability | SPARQL endpoint availability check for ConfermentSampo took 60.02587580680847s
Availability | VoID file availability check for ConfermentSampo took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 60.02327752113342s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.020899295806884766s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.621246337890625e-05s
Believability | Calculation of trust value for ConfermentSampo took 1.6689300537109375e-05s
INFO | --- Analysis for ConfermentSampo took 720.326904296875s
Availability | SPARQL endpoint availability check for Museum Finland took 60.02432084083557s
Availability | VoID file availability check for Museum Finland took 0.0003876686096191406s
Completeness | Calculation of interlinking completeness for Museum Finland took 60.0263090133667s
Reputation | Calculation of the PageRank for Museum Finland took 0.021341323852539062s
Interlinking | Calculation of Degree of Connection for Museum Finland took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.9311904907226562e-05s
Believability | Calculation of trust value for Museum Finland took 1.33514404296875e-05s
INFO | --- Analysis for FI-Museum took 720.3230381011963s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 60.02328085899353s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 60.02259564399719s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.0967254638671875e-05s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 9.775161743164062e-06s
INFO | --- Analysis for MMM took 760.3445346355438s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 60.02532482147217s
Availability | VoID file availability check for Semantic Kalevala took 0.0009250640869140625s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 60.02159786224365s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.021180152893066406s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.3828277587890625e-05s
Believability | Calculation of trust value for Semantic Kalevala took 1.3828277587890625e-05s
