Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.792213439941406e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0007772445678710938s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.26671862602233887s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.522197961807251s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.0003535747528076172s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 6.67572021484375e-06s
INFO | --- Analysis for 0080-3626 took 7.321669816970825s
Availability | SPARQL endpoint availability check for 土地利用图 took 4.4345855712890625e-05s
Availability | VoID file availability check for 土地利用图 took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.25347256660461426s
Reputation | Calculation of the PageRank for 土地利用图 took 0.019875764846801758s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0006821155548095703s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 2.7418136596679688e-05s
Believability | Calculation of trust value for 土地利用图 took 7.3909759521484375e-06s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 2.811635971069336s
Availability | SPARQL endpoint availability check for 113322 took 4.291534423828125e-05s
Availability | VoID file availability check for 113322 took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for 113322 took 0.7430312633514404s
Reputation | Calculation of the PageRank for 113322 took 0.01979351043701172s
Interlinking | Calculation of Degree of Connection for 113322 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 113322 took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for 113322 took 2.8371810913085938e-05s
Believability | Calculation of trust value for 113322 took 1.2159347534179688e-05s
INFO | --- Analysis for 11 took 5.262523174285889s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.315376281738281e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.2569742202758789s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.020106792449951172s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 2.9087066650390625e-05s
Believability | Calculation of trust value for Korepetycje Buki took 6.9141387939453125e-06s
INFO | --- Analysis for 12323 took 2.3430049419403076s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.053981781005859375s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.27544713020324707s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020273208618164062s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 9.107589721679688e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 6.9141387939453125e-06s
INFO | --- Analysis for 2000-us-census-rdf took 2.4494378566741943s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.6574406623840332s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.28341245651245117s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020061492919921875s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.790855407714844e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 4.5299530029296875e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 5.844833135604858s
Availability | SPARQL endpoint availability check for Open Data Web took 0.9449031352996826s
Availability | VoID file availability check for Open Data Web took 0.000244140625s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.23939871788024902s
Reputation | Calculation of the PageRank for Open Data Web took 0.020183324813842773s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.361701965332031e-05s
Believability | Calculation of trust value for Open Data Web took 6.9141387939453125e-06s
INFO | --- Analysis for _data.odw.tw took 3.298689365386963s
Availability | SPARQL endpoint availability check for 土地利用 took 4.506111145019531e-05s
Availability | VoID file availability check for 土地利用 took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.25239109992980957s
Reputation | Calculation of the PageRank for 土地利用 took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for 土地利用 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.0279159545898438e-05s
Believability | Calculation of trust value for 土地利用 took 7.62939453125e-06s
INFO | --- Analysis for _data1.odw.tw took 2.3254904747009277s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.3392181396484375e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0004115104675292969s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.2390000820159912s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020400047302246094s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 3.4809112548828125e-05s
Believability | Calculation of trust value for 土地利用模型 took 7.62939453125e-06s
INFO | --- Analysis for _data2.odw.tw took 4.886936902999878s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.315376281738281e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0003628730773925781s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.24831700325012207s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02018451690673828s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.956390380859375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.67572021484375e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 3.6013364791870117s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.482269287109375e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.2667810916900635s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020185232162475586s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 2.9802322387695312e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 6.9141387939453125e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 3.0494277477264404s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 5.125999450683594e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.2691471576690674s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020189523696899414s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 2.9802322387695312e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 5.0067901611328125e-06s
INFO | --- Analysis for A1 took 2.7867374420166016s
Availability | SPARQL endpoint availability check for SummerOlympics took 1.7276279926300049s
Availability | VoID file availability check for SummerOlympics took 0.0003712177276611328s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.2684504985809326s
Reputation | Calculation of the PageRank for SummerOlympics took 0.02000594139099121s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0008118152618408203s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.389617919921875e-05s
Believability | Calculation of trust value for SummerOlympics took 7.152557373046875e-06s
INFO | --- Analysis for abc took 8.911332368850708s
Availability | SPARQL endpoint availability check for Test_m took 4.1484832763671875e-05s
Availability | VoID file availability check for Test_m took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Test_m took 0.263455867767334s
Reputation | Calculation of the PageRank for Test_m took 0.020343303680419922s
Interlinking | Calculation of Degree of Connection for Test_m took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.170967102050781e-05s
Believability | Calculation of trust value for Test_m took 7.3909759521484375e-06s
INFO | --- Analysis for ABC took 2.3205904960632324s
Availability | SPARQL endpoint availability check for my intro took 4.4345855712890625e-05s
Availability | VoID file availability check for my intro took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for my intro took 0.2618687152862549s
Reputation | Calculation of the PageRank for my intro took 0.020108461380004883s
Interlinking | Calculation of Degree of Connection for my intro took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for my intro took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for my intro took 3.0517578125e-05s
Believability | Calculation of trust value for my intro took 6.67572021484375e-06s
INFO | --- Analysis for abhay_intro took 2.301168918609619s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.5731830596923828s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.2539834976196289s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.0001049041748046875s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for abs-linked-data took 2.9357783794403076s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 5.602836608886719e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.00031876564025878906s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.2591125965118408s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.020166873931884766s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 3.0040740966796875e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 1.3113021850585938e-05s
INFO | --- Analysis for academic-offer-of-unl took 2.854048013687134s
Availability | SPARQL endpoint availability check for AcadOnto took 6.961822509765625e-05s
Availability | VoID file availability check for AcadOnto took 0.000579833984375s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.27848196029663086s
Reputation | Calculation of the PageRank for AcadOnto took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.24249267578125e-05s
Believability | Calculation of trust value for AcadOnto took 7.62939453125e-06s
INFO | --- Analysis for acadonto took 2.9063422679901123s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.535021781921387s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007612705230712891s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.2610616683959961s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0203094482421875s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.410743713378906e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 5.7220458984375e-06s
INFO | --- Analysis for acorn-sat took 36.0578088760376s
Availability | SPARQL endpoint availability check for Addgene took 4.38690185546875e-05s
Availability | VoID file availability check for Addgene took 0.0008807182312011719s
Completeness | Calculation of interlinking completeness for Addgene took 0.2478334903717041s
Reputation | Calculation of the PageRank for Addgene took 0.020331859588623047s
Interlinking | Calculation of Degree of Connection for Addgene took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.552436828613281e-05s
Believability | Calculation of trust value for Addgene took 7.62939453125e-06s
INFO | --- Analysis for addgene took 15.456508874893188s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.57763671875e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0008084774017333984s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.26981282234191895s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.584426879882812e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 6.9141387939453125e-06s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 9.47997522354126s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.5151278972625732s
Availability | VoID file availability check for AEMET metereological dataset took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.25736141204833984s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020538330078125s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0011281967163085938s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 4.8160552978515625e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 7.62939453125e-06s
INFO | --- Analysis for aemet took 4.724029302597046s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.7206878662109375e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.26665759086608887s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.020401716232299805s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 3.123283386230469e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 7.867813110351562e-06s
INFO | --- Analysis for agenda-de-zaragoza took 2.8515756130218506s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.11835741996765137s
Availability | VoID file availability check for AgriNepalData took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.2651090621948242s
Reputation | Calculation of the PageRank for AgriNepalData took 0.021140336990356445s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.43865966796875e-05s
Believability | Calculation of trust value for AgriNepalData took 7.867813110351562e-06s
INFO | --- Analysis for agrinepaldata took 2.6007187366485596s
Availability | SPARQL endpoint availability check for AGRIS took 261.0539891719818s
Availability | VoID file availability check for AGRIS took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for AGRIS took 0.26171135902404785s
Reputation | Calculation of the PageRank for AGRIS took 0.020269393920898438s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for AGRIS took 8.058547973632812e-05s
Believability | Calculation of trust value for AGRIS took 7.867813110351562e-06s
INFO | --- Analysis for agris took 556.3054111003876s
Availability | SPARQL endpoint availability check for AGROVOC took 0.2151482105255127s
Availability | VoID file availability check for AGROVOC took 0.0006108283996582031s
Extra | Recovery of all triples for AGROVOC took 65.11179566383362s
Performance | Total latancy measurement for AGROVOC took 0.4433326721191406s
Amount of data | Number of triples check for AGROVOC took 98.99897193908691s
Interoperability | New terms check for AGROVOC took 3.4567291736602783s
Versatility | Languages check for AGROVOC took 146.74095487594604s
Interpretability | Number of blank nodes check for AGROVOC took 57.186654567718506s
Interpretability | RDF structures check for AGROVOC took 0.0767970085144043s
Versatility | Serialization formats check for AGROVOC took 0.08797264099121094s
Availability | RDF dump link check for AGROVOC took 0.08709716796875s
License | MR license check for AGROVOC took 0.07749605178833008s
License | HR license check for AGROVOC took 0.6751251220703125s
Amount of data | Number of property check for AGROVOC took 0.07463955879211426s
Understandability | Number of label check for AGROVOC took 69.17225742340088s
Understandability | URI regex check for AGROVOC took 0.18992018699645996s
Understandability | Vocabs check for AGROVOC took 0.08732914924621582s
Verifiability | Authors check for AGROVOC took 0.09940075874328613s
Verifiability | Publishers check for AGROVOC took 0.08640098571777344s
Performance | Throughput check for AGROVOC took 10.456241369247437s
Amount of data | Check the number of entities for AGROVOC took 0.00011324882507324219s
Verifiability | Contribs. check for AGROVOC took 0.08593153953552246s
Interlinking | sameAs chians check for AGROVOC took 0.0746755599975586s
Interlinking | skos check for AGROVOC took 7.767704725265503s
Interlinking | skos check for AGROVOC took 3.6145479679107666s
Timeliness | dataset update frequency check for AGROVOC took 0.0873720645904541s
Currency | Creation date check for AGROVOC took 0.16150307655334473s
Currency | Modification date check for AGROVOC took 0.16347908973693848s
Rep.Conc. | URIs length for AGROVOC took 124.35667300224304s
Interoperability | New vocabularies check for AGROVOC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.08639764785766602s
Accuracy | Check Functional Property for AGROVOC took 0.09758949279785156s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.08871197700500488s
Accuracy | Check Empty annotation labels for AGROVOC took 20.933465480804443s
Accuracy | Check White space in annotation for AGROVOC took 2.970113754272461s
Accuracy | Check Datatype consistency for AGROVOC took 4.652428865432739s
Consistency | Disjoint class check for AGROVOC took 0.13994598388671875s
Consistency | Check Misplaced properties for AGROVOC took 21.948418140411377s
Consistency | Check Ontology hijacking for AGROVOC took 64.39148473739624s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.4674785137176514s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 35.14723348617554s
Conciseness | Check Extensional conciseness for AGROVOC took 2.567164421081543s
Conciseness | Check Intensional conciseness for AGROVOC took 0.10552430152893066s
Security | Sign check for AGROVOC took 0.09805798530578613s
Availability | Check URIs Dereferenciability for AGROVOC took 3.786956310272217s
Completeness | Calculation of interlinking completeness for AGROVOC took 1.2829816341400146s
Reputation | Calculation of the PageRank for AGROVOC took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00012421607971191406s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.9073486328125e-06s
Believability | Calculation of trust value for AGROVOC took 6.9141387939453125e-06s
INFO | --- Analysis for agrovoc took 1462.4305078983307s
Availability | SPARQL endpoint availability check for AGROVOC took 4.220008850097656e-05s
Availability | VoID file availability check for AGROVOC took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.2857062816619873s
Reputation | Calculation of the PageRank for AGROVOC took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.841255187988281e-05s
Believability | Calculation of trust value for AGROVOC took 7.3909759521484375e-06s
INFO | --- Analysis for agrovoc-skos took 3.834761619567871s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.3613746166229248s
Availability | VoID file availability check for Analytics India Magazine took 0.0005548000335693359s
Extra | Recovery of all triples for Analytics India Magazine took 2.5818030834198s
Performance | Total latancy measurement for Analytics India Magazine took 3.3853416442871094s
Amount of data | Number of triples check for Analytics India Magazine took 1.377321720123291s
Versatility | Languages check for Analytics India Magazine took 1.3717241287231445s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.597489595413208s
Interpretability | RDF structures check for Analytics India Magazine took 1.4100828170776367s
Versatility | Serialization formats check for Analytics India Magazine took 1.3096296787261963s
Availability | RDF dump link check for Analytics India Magazine took 1.2370641231536865s
License | MR license check for Analytics India Magazine took 1.2651708126068115s
License | HR license check for Analytics India Magazine took 1.2369601726531982s
Amount of data | Number of property check for Analytics India Magazine took 1.1998274326324463s
Understandability | Number of label check for Analytics India Magazine took 1.3233013153076172s
Understandability | URI regex check for Analytics India Magazine took 2.8863425254821777s
Understandability | Vocabs check for Analytics India Magazine took 1.2485911846160889s
Verifiability | Authors check for Analytics India Magazine took 1.303023099899292s
Verifiability | Publishers check for Analytics India Magazine took 1.238330602645874s
Performance | Throughput check for Analytics India Magazine took 17.529873371124268s
Amount of data | Check the number of entities for Analytics India Magazine took 0.00010228157043457031s
Verifiability | Contribs. check for Analytics India Magazine took 1.3057847023010254s
Interlinking | sameAs chians check for Analytics India Magazine took 1.3166954517364502s
Interlinking | skos check for Analytics India Magazine took 1.2440752983093262s
Interlinking | skos check for Analytics India Magazine took 1.2044501304626465s
Timeliness | dataset update frequency check for Analytics India Magazine took 1.2530362606048584s
Currency | Creation date check for Analytics India Magazine took 2.658409357070923s
Currency | Modification date check for Analytics India Magazine took 2.862067461013794s
Rep.Conc. | URIs length for Analytics India Magazine took 2.5321478843688965s
Interoperability | New vocabularies check for Analytics India Magazine took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 1.3145523071289062s
Consistency | Disjoint class check for Analytics India Magazine took 1.2253105640411377s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.2464730739593506s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 2.6728031635284424s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.0001392364501953125s
Security | Sign check for Analytics India Magazine took 1.1883833408355713s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.27080750465393066s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 4.076957702636719e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 9.5367431640625e-07s
Believability | Calculation of trust value for Analytics India Magazine took 7.62939453125e-06s
INFO | --- Analysis for AIM took 110.12307000160217s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 0.0001327991485595703s
Availability | VoID file availability check for All India Survey of Higher Education took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.25898027420043945s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.02017998695373535s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0008056163787841797s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.1948089599609375e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 6.9141387939453125e-06s
INFO | --- Analysis for AISHE took 2.8408048152923584s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.315376281738281e-05s
Availability | VoID file availability check for  equipment ontology took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.2714731693267822s
Reputation | Calculation of the PageRank for  equipment ontology took 0.020351886749267578s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 2.9087066650390625e-05s
Believability | Calculation of trust value for  equipment ontology took 1.1682510375976562e-05s
INFO | --- Analysis for akash took 2.829625368118286s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.220008850097656e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.000274658203125s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.26769161224365234s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.020143747329711914s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 2.9087066650390625e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 1.239776611328125e-05s
INFO | --- Analysis for aksworg took 2.9615139961242676s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.172325134277344e-05s
Availability | VoID file availability check for AlchemyAPI took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.3059687614440918s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.020565509796142578s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0008549690246582031s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 3.552436828613281e-05s
Believability | Calculation of trust value for AlchemyAPI took 8.106231689453125e-06s
INFO | --- Analysis for alchemyapi took 3.017241954803467s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 5.412101745605469e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.25757884979248047s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.02026200294494629s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 2.8848648071289062e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 7.867813110351562e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.88774037361145s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.10447359085083s
Availability | VoID file availability check for aliada-scanbit-net took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.24179673194885254s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020165205001831055s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00011563301086425781s
Believability | Calculation of trust value for aliada-scanbit-net took 7.152557373046875e-06s
INFO | --- Analysis for aliada-scanbit-net took 4.552636384963989s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.1484832763671875e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.27649903297424316s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.020054101943969727s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 2.9087066650390625e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 7.3909759521484375e-06s
INFO | --- Analysis for allen-brain-atlas took 2.952888250350952s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 1.5106570720672607s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006322860717773438s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 138.6550805568695s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.6939897537231445s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.394862413406372s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.4909121990203857s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.093829870224s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.814998149871826s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8848435878753662s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.5677433013916016s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.625807523727417s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5304689407348633s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.5572412014007568s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 33.90640997886658s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5798921585083008s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.7919034957885742s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.0856468677520752s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.542710542678833s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6093029975891113s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5408694744110107s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.726029872894287s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 0.00010991096496582031s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5473217964172363s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5484445095062256s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5511453151702881s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6042094230651855s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.5480573177337646s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.0748746395111084s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.0939102172851562s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 54.786253452301025s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 1.6534008979797363s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5340402126312256s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6622319221496582s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6466526985168457s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 35.58680438995361s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.0037412643432617s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.6274755001068115s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.5851364135742188s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.685116052627563s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.93610692024231s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 32.04420566558838s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.3795573711395264s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.467925786972046s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.74633526802063s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8132576942443848s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5412304401397705s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 13271.466792106628s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 1.5304896831512451s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.022485733032226562s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 8.20159912109375e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 1.4704818725585938s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 9.059906005859375e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 14024.65301156044s
Availability | SPARQL endpoint availability check for Alojamientos took 4.220008850097656e-05s
Availability | VoID file availability check for Alojamientos took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.262768030166626s
Reputation | Calculation of the PageRank for Alojamientos took 0.020218610763549805s
Interlinking | Calculation of Degree of Connection for Alojamientos took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Alojamientos took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 2.8848648071289062e-05s
Believability | Calculation of trust value for Alojamientos took 6.9141387939453125e-06s
INFO | --- Analysis for alojamientos-zaragoza took 3.7576003074645996s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.4190335273742676s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.00040912628173828125s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.24326586723327637s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.02031993865966797s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.7670135498046875e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.0251998901367188e-05s
INFO | --- Analysis for alpino-rdf took 3.8210248947143555s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.3392181396484375e-05s
Availability | VoID file availability check for AAT-atawil took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.24637079238891602s
Reputation | Calculation of the PageRank for AAT-atawil took 0.020229816436767578s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 2.9325485229492188e-05s
Believability | Calculation of trust value for AAT-atawil took 6.9141387939453125e-06s
INFO | --- Analysis for Altawil took 2.2898199558258057s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 5.412101745605469e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.239976167678833s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 3.075599670410156e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 7.62939453125e-06s
INFO | --- Analysis for am-collections-online took 2.824007034301758s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.315376281738281e-05s
Availability | VoID file availability check for Amer Nejma took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.2448582649230957s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020282983779907227s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.170967102050781e-05s
Believability | Calculation of trust value for Amer Nejma took 6.198883056640625e-06s
INFO | --- Analysis for Amer_Nejma took 2.3147950172424316s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.24085617065429688s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.147125244140625e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 8.58306884765625e-06s
INFO | --- Analysis for amon took 2.815215826034546s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7381148338317871s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.2496805191040039s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00011301040649414062s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 7.3909759521484375e-06s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.6629157066345215s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 4.1484832763671875e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.26763486862182617s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.0201718807220459s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.361701965332031e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 6.67572021484375e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.918776750564575s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.172325134277344e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.27201175689697266s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.02079463005065918s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 3.1948089599609375e-05s
Believability | Calculation of trust value for Animal Diversity Web took 7.867813110351562e-06s
INFO | --- Analysis for animal-diversity-web took 2.8569281101226807s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.5299530029296875e-05s
Availability | VoID file availability check for Anime Dataset took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.2836284637451172s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020273685455322266s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for Anime Dataset took 1.7404556274414062e-05s
INFO | --- Analysis for Anime took 3.958014726638794s
Availability | SPARQL endpoint availability check for ANNO took 4.410743713378906e-05s
Availability | VoID file availability check for ANNO took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for ANNO took 0.2558610439300537s
Reputation | Calculation of the PageRank for ANNO took 0.020653963088989258s
Interlinking | Calculation of Degree of Connection for ANNO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ANNO took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.2901763916015625e-05s
Believability | Calculation of trust value for ANNO took 7.62939453125e-06s
INFO | --- Analysis for anno took 7.991005897521973s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 5.507469177246094e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.2528543472290039s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020322799682617188s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.867813110351562e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 7.62939453125e-06s
INFO | --- Analysis for AntiqueCarsCollection took 4.409276485443115s
Availability | SPARQL endpoint availability check for apache took 4.291534423828125e-05s
Availability | VoID file availability check for apache took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for apache took 0.28471827507019043s
Reputation | Calculation of the PageRank for apache took 0.02039170265197754s
Interlinking | Calculation of Degree of Connection for apache took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for apache took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for apache took 5.650520324707031e-05s
Believability | Calculation of trust value for apache took 5.7220458984375e-06s
INFO | --- Analysis for apache took 3.286560535430908s
Availability | SPARQL endpoint availability check for Apertium RDF took 8.0108642578125e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.257112979888916s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020471811294555664s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf took 8.549742937088013s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.2671220302581787s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020698070526123047s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 5.862842321395874s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.601478576660156e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.2823295593261719s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020760059356689453s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007107257843017578s
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 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.719843626022339s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.5299530029296875e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.24792098999023438s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-en-es took 5.489218473434448s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 5.2928924560546875e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.2514231204986572s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.02021622657775879s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 5.868869781494141s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 9.250640869140625e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.26932549476623535s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020444154739379883s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.7206878662109375e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 6.285043954849243s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.26941370964050293s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02026987075805664s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.100799560546875e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 5.581212759017944s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.744529724121094e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.25209593772888184s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.02079606056213379s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0009112358093261719s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 5.269050598144531e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.524524688720703s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 9.226799011230469e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.2557802200317383s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.02033257484436035s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.5299530029296875e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.561917066574097s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.27368855476379395s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020210742950439453s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.570338726043701s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 5.91278076171875e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.00041794776916503906s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.2545042037963867s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.02021503448486328s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.492600917816162s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0008547306060791016s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.25825071334838867s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.9114227294921875e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 24.819069623947144s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.2803633213043213s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020214080810546875s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 6.000215291976929s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0012192726135253906s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.26343607902526855s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020140409469604492s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.538632392883301s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 6.914138793945312e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.2783331871032715s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02043318748474121s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.5268635749816895s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0006372928619384766s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.2540576457977295s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02053046226501465s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0009791851043701172s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 5.054473876953125e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 5.528881549835205s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.2697315216064453s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.9591064453125e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 5.6023101806640625s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0007178783416748047s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.25339341163635254s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.02052474021911621s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 5.1021575927734375e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.5987443923950195s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.28478479385375977s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.021306991577148438s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.982948303222656e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 5.580706834793091s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.2601783275604248s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020188570022583008s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 8.58306884765625e-06s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.5845489501953125s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0006103515625s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2621734142303467s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.02024221420288086s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 5.46876859664917s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.9114227294921875e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.25822019577026367s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020359277725219727s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.524773359298706s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.24446773529052734s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020339250564575195s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.232337951660156s
Availability | SPARQL endpoint availability check for AragoDBPedia took 1.0052211284637451s
Availability | VoID file availability check for AragoDBPedia took 0.0011157989501953125s
Extra | Recovery of all triples for AragoDBPedia took 4.200073957443237s
Performance | Total latancy measurement for AragoDBPedia took 1.8891119956970215s
Amount of data | Number of triples check for AragoDBPedia took 0.7493042945861816s
Interoperability | New terms check for AragoDBPedia took 2.0552327632904053s
Versatility | Languages check for AragoDBPedia took 60.44520115852356s
Interpretability | Number of blank nodes check for AragoDBPedia took 4.263701915740967s
Security | Check HTTPS for AragoDBPedia took 0.24859285354614258s
Interpretability | RDF structures check for AragoDBPedia took 0.5591247081756592s
Versatility | Serialization formats check for AragoDBPedia took 1.0423061847686768s
Availability | RDF dump link check for AragoDBPedia took 0.38997530937194824s
License | MR license check for AragoDBPedia took 0.7630476951599121s
License | HR license check for AragoDBPedia took 7.209039211273193s
Amount of data | Number of property check for AragoDBPedia took 0.383469820022583s
Understandability | Number of label check for AragoDBPedia took 0.6146037578582764s
Understandability | URI regex check for AragoDBPedia took 0.9158501625061035s
Understandability | Vocabs check for AragoDBPedia took 0.4595952033996582s
Verifiability | Authors check for AragoDBPedia took 0.49746131896972656s
Verifiability | Publishers check for AragoDBPedia took 0.3994131088256836s
Performance | Throughput check for AragoDBPedia took 11.364328145980835s
Amount of data | Check the number of entities for AragoDBPedia took 8.392333984375e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.5024118423461914s
Interlinking | sameAs chians check for AragoDBPedia took 0.4605541229248047s
Interlinking | skos check for AragoDBPedia took 0.6480755805969238s
Interlinking | skos check for AragoDBPedia took 0.36639976501464844s
Timeliness | dataset update frequency check for AragoDBPedia took 0.8959851264953613s
Currency | Creation date check for AragoDBPedia took 1.780503511428833s
Currency | Modification date check for AragoDBPedia took 0.8016421794891357s
Rep.Conc. | URIs length for AragoDBPedia took 5.459298849105835s
Interoperability | New vocabularies check for AragoDBPedia took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.3690311908721924s
Accuracy | Check Functional Property for AragoDBPedia took 0.5068049430847168s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.527606725692749s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.2387540340423584s
Accuracy | Check White space in annotation for AragoDBPedia took 0.029622316360473633s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.028132200241088867s
Consistency | Disjoint class check for AragoDBPedia took 0.41818952560424805s
Consistency | Check Misplaced properties for AragoDBPedia took 4.799879312515259s
Consistency | Misplaced classes for AragoDBPedia took 0.6043331623077393s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.5568294525146484s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.3028345108032227s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.388272285461426s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.0350193977355957s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.5783016681671143s
Security | Sign check for AragoDBPedia took 0.6900875568389893s
Availability | Check URIs Dereferenciability for AragoDBPedia took 2961.4189734458923s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 1.0579566955566406s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.020317554473876953s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 4.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for AragoDBPedia took 5.245208740234375e-06s
INFO | --- Analysis for aragodbpedia took 15299.972439050674s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.32869553565979s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.6899471282958984s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020467758178710938s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 4.8160552978515625e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for archiveshub-linkeddata took 84.65494155883789s
Availability | SPARQL endpoint availability check for Archivi ISMA took 7.009506225585938e-05s
Availability | VoID file availability check for Archivi ISMA took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.7058384418487549s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 2.9087066650390625e-05s
Believability | Calculation of trust value for Archivi ISMA took 5.9604644775390625e-06s
INFO | --- Analysis for archivio-isma took 3.777733564376831s
Availability | SPARQL endpoint availability check for ARIADNE took 4.1961669921875e-05s
Availability | VoID file availability check for ARIADNE took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.2579808235168457s
Reputation | Calculation of the PageRank for ARIADNE took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 2.8371810913085938e-05s
Believability | Calculation of trust value for ARIADNE took 8.106231689453125e-06s
INFO | --- Analysis for ariadne took 2.9255030155181885s
Availability | SPARQL endpoint availability check for Aristotle University took 4.0531158447265625e-05s
Availability | VoID file availability check for Aristotle University took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.2814640998840332s
Reputation | Calculation of the PageRank for Aristotle University took 0.0202178955078125s
Interlinking | Calculation of Degree of Connection for Aristotle University took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 2.9802322387695312e-05s
Believability | Calculation of trust value for Aristotle University took 6.9141387939453125e-06s
INFO | --- Analysis for aristotle-university took 2.9238929748535156s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 5.222092151641846s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.25762939453125s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020731210708618164s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.0994415283203125e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 6.198883056640625e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 20.77701425552368s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.2438507080078125e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.2746589183807373s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 6.9141387939453125e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 2.906087636947632s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.951758861541748s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.27477025985717773s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.02024221420288086s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.6716461181640625e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 6.9141387939453125e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 16.724063634872437s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 5.650520324707031e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007078647613525391s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.2712984085083008s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020534753799438477s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0001049041748046875s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 11.905726194381714s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.220008850097656e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0006253719329833984s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.2524840831756592s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020589113235473633s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010180473327636719s
Believability | Calculation of trust value for Arthroscopy community took 6.67572021484375e-06s
INFO | --- Analysis for arthroscopy took 11.444946527481079s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.7270469665527344s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0005724430084228516s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 32.39552330970764s
Performance | Total latancy measurement for Wikidata entry for Art × Science International took 1.308459997177124s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 65.20240068435669s
Interoperability | New terms check for Wikidata entry for Art × Science International took 1.9803483486175537s
Versatility | Languages check for Wikidata entry for Art × Science International took 60.465603828430176s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 65.20126867294312s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.37447142601013184s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.21769952774047852s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.22878694534301758s
License | MR license check for Wikidata entry for Art × Science International took 0.2052922248840332s
License | HR license check for Wikidata entry for Art × Science International took 65.21111345291138s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.3414885997772217s
Understandability | Number of label check for Wikidata entry for Art × Science International took 60.21434426307678s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.7031583786010742s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.2262742519378662s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.21488356590270996s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.22544121742248535s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 7.677078247070312e-05s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.22296380996704102s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 28.982162952423096s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.2090775966644287s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.12445950508117676s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.4529719352722168s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.7291226387023926s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.6246902942657471s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 29.253933906555176s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.2113511562347412s
Accuracy | Check Empty annotation labels for Wikidata entry for Art × Science International took 12.197890758514404s
Accuracy | Check White space in annotation for Wikidata entry for Art × Science International took 2.660766363143921s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.69230842590332s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.20807623863220215s
Consistency | Check Misplaced properties for Wikidata entry for Art × Science International took 22.94743514060974s
Consistency | Misplaced classes for Wikidata entry for Art × Science International took 9.092740535736084s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 25.113657236099243s
Consistency | Check Invalid usage of undefined classes for Wikidata entry for Art × Science International took 1.3670997619628906s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 16.15985107421875s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.834348201751709s
Conciseness | Check Intensional conciseness for Wikidata entry for Art × Science International took 1.9256956577301025s
Security | Sign check for Wikidata entry for Art × Science International took 0.21420931816101074s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 9.590555429458618s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.7542824745178223s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.02077937126159668s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.430511474609375e-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 7.867813110351562e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 901.0475459098816s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.6969869136810303s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.7101035118103027s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020571231842041016s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.273124694824219e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 13.498718023300171s
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.1141746044158936s
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.0005409717559814453s
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.26723647117614746s
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.0203704833984375s
Interlinking | Calculation of Degree of Connection for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.987022399902344e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 10.146087169647217s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.110605478286743s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.2641589641571045s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.298324584960938e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 11.505343437194824s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.1503169536590576s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.25740528106689453s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020341873168945312s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.172325134277344e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-CRB took 13.017313003540039s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.13840651512146s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.27608203887939453s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020180702209472656s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.036064147949219e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 10.539548397064209s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.1308681964874268s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.292248010635376s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020093679428100586s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.457069396972656e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-DQOT took 11.476204633712769s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.110389232635498s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2583000659942627s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0203249454498291s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.20159912109375e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 11.563569784164429s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 2.8497154712677s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.24985527992248535s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020244121551513672s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.296966552734375e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 13.728904485702515s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.1385626792907715s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.2680373191833496s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.020272016525268555s
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.049041748046875e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.4836273193359375e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 10.576445579528809s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.1147782802581787s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007364749908447266s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.2656705379486084s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.02023172378540039s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.078315734863281e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 10.60139012336731s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.467597484588623s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.265824556350708s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.02201533317565918s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0008516311645507812s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.580352783203125e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 9.059906005859375e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 14.410563945770264s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.1229066848754883s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.2871742248535156s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.02125835418701172s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.390975952148438e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 10.215440034866333s
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.134455680847168s
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.0007064342498779297s
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.24322223663330078s
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.021703481674194336s
Interlinking | Calculation of Degree of Connection for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 8.535385131835938e-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 8.58306884765625e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 11.534685373306274s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.1324362754821777s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0007014274597167969s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.26277899742126465s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.02049541473388672s
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.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.506111145019531e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC_-_DNB took 10.148031949996948s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.38690185546875e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2601914405822754s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 7.510185241699219e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 7.62939453125e-06s
INFO | --- Analysis for asit took 8.52572512626648s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.3392181396484375e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.26810121536254883s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.020357370376586914s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 4.029273986816406e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 6.4373016357421875e-06s
INFO | --- Analysis for asjp took 4.7357683181762695s
Availability | SPARQL endpoint availability check for ASN:US took 2.8966610431671143s
Availability | VoID file availability check for ASN:US took 0.000457763671875s
Completeness | Calculation of interlinking completeness for ASN:US took 0.2640035152435303s
Reputation | Calculation of the PageRank for ASN:US took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0010051727294921875s
Interlinking | Calculation of Clustering coefficient for ASN:US took 8.249282836914062e-05s
Believability | Calculation of trust value for ASN:US took 5.245208740234375e-06s
INFO | --- Analysis for asn-us took 14.70501184463501s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.4345855712890625e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.2645301818847656s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.02030634880065918s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 2.9087066650390625e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 4.76837158203125e-06s
INFO | --- Analysis for aspire-mmu took 4.426271438598633s
Availability | SPARQL endpoint availability check for associations took 4.4345855712890625e-05s
Availability | VoID file availability check for associations took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for associations took 0.27051734924316406s
Reputation | Calculation of the PageRank for associations took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for associations took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for associations took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for associations took 6.699562072753906e-05s
Believability | Calculation of trust value for associations took 7.62939453125e-06s
INFO | --- Analysis for associations took 7.750667095184326s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 5.555152893066406e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.2834279537200928s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 3.1948089599609375e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 8.344650268554688e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 2.939042568206787s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.267692565917969e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.25406956672668457s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.02025890350341797s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.940696716308594e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 7.3909759521484375e-06s
INFO | --- Analysis for athelia-rfid took 7.426160097122192s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.0531158447265625e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.2809414863586426s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020462512969970703s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 3.790855407714844e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for aueb-linked-open-data took 2.9085495471954346s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.7283320426940918s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.2660839557647705s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.0201416015625s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.9604644775390625e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 8.58306884765625e-06s
INFO | --- Analysis for AugustiniConfessiones took 4.532025337219238s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.5547654628753662s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.24244999885559082s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020323514938354492s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.988380432128906e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 7.3909759521484375e-06s
INFO | --- Analysis for austrian_ski_racers took 3.5690531730651855s
Availability | SPARQL endpoint availability check for AVsOnto took 4.4345855712890625e-05s
Availability | VoID file availability check for AVsOnto took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.24512767791748047s
Reputation | Calculation of the PageRank for AVsOnto took 0.021278858184814453s
Interlinking | Calculation of Degree of Connection for AVsOnto took 3.266334533691406e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0008728504180908203s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.933906555175781e-05s
Believability | Calculation of trust value for AVsOnto took 7.152557373046875e-06s
INFO | --- Analysis for AVsOnto took 3.2485697269439697s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 30.212352514266968s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.31931066513061523s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.033927202224731445s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0013206005096435547s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.00019288063049316406s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.7220458984375e-06s
INFO | --- Analysis for b3kat took 153.03598856925964s
Availability | SPARQL endpoint availability check for BabelNet took 0.552617073059082s
Availability | VoID file availability check for BabelNet took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for BabelNet took 0.2561948299407959s
Reputation | Calculation of the PageRank for BabelNet took 0.02061295509338379s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001766681671142578s
Believability | Calculation of trust value for BabelNet took 7.3909759521484375e-06s
INFO | --- Analysis for babelnet took 4.336116313934326s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 5.745887756347656e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0004057884216308594s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.2640979290008545s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020501375198364258s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bacevicius.lt took 8.106231689453125e-06s
INFO | --- Analysis for Bacevicius.lt took 2.327056884765625s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.41612744331359863s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.25504326820373535s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.6253204345703125e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 7.3909759521484375e-06s
INFO | --- Analysis for bag took 5.09992790222168s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.3643629550933838s
Availability | VoID file availability check for 红色经典歌曲 took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.27203965187072754s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020209074020385742s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.1948089599609375e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.867813110351562e-06s
INFO | --- Analysis for baixue took 2.7650976181030273s
Availability | SPARQL endpoint availability check for baixue composer took 4.9114227294921875e-05s
Availability | VoID file availability check for baixue composer took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for baixue composer took 0.2559342384338379s
Reputation | Calculation of the PageRank for baixue composer took 0.020320653915405273s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.695487976074219e-05s
Believability | Calculation of trust value for baixue composer took 7.3909759521484375e-06s
INFO | --- Analysis for baixue_composer took 2.8379149436950684s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.38690185546875e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2571263313293457s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020314455032348633s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.147125244140625e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 8.106231689453125e-06s
INFO | --- Analysis for baixue_imagery took 2.631572723388672s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.38690185546875e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006642341613769531s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2531743049621582s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020302295684814453s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.956390380859375e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1444091796875e-05s
INFO | --- Analysis for baixue_imagery1 took 4.186573028564453s
Availability | SPARQL endpoint availability check for BAMS took 4.744529724121094e-05s
Availability | VoID file availability check for BAMS took 0.00031948089599609375s
Completeness | Calculation of interlinking completeness for BAMS took 0.273301362991333s
Reputation | Calculation of the PageRank for BAMS took 0.02413034439086914s
Interlinking | Calculation of Degree of Connection for BAMS took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0009360313415527344s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.7670135498046875e-05s
Believability | Calculation of trust value for BAMS took 8.344650268554688e-06s
INFO | --- Analysis for bams took 2.809420108795166s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 4.363059997558594e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.2564408779144287s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 7.3909759521484375e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.4510750770568848s
Availability | SPARQL endpoint availability check for BBC Music took 0.4535958766937256s
Availability | VoID file availability check for BBC Music took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for BBC Music took 0.24648833274841309s
Reputation | Calculation of the PageRank for BBC Music took 0.020462512969970703s
Interlinking | Calculation of Degree of Connection for BBC Music took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BBC Music took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.0001323223114013672s
Believability | Calculation of trust value for BBC Music took 6.4373016357421875e-06s
INFO | --- Analysis for bbc-music took 3.40132212638855s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.24744033813476562s
Availability | VoID file availability check for BBC Programmes took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.29445719718933105s
Reputation | Calculation of the PageRank for BBC Programmes took 0.02023148536682129s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010180473327636719s
Believability | Calculation of trust value for BBC Programmes took 7.867813110351562e-06s
INFO | --- Analysis for bbc-programmes took 10.236351728439331s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.21913695335388184s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.2726578712463379s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010180473327636719s
Believability | Calculation of trust value for BBC Wildlife Finder took 7.3909759521484375e-06s
INFO | --- Analysis for bbc-wildlife-finder took 9.376530647277832s
Availability | SPARQL endpoint availability check for BBOP took 4.076957702636719e-05s
Availability | VoID file availability check for BBOP took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for BBOP took 0.2549283504486084s
Reputation | Calculation of the PageRank for BBOP took 0.020225048065185547s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.956390380859375e-05s
Believability | Calculation of trust value for BBOP took 7.3909759521484375e-06s
INFO | --- Analysis for bbop took 2.83894681930542s
Availability | SPARQL endpoint availability check for BBOP took 4.839897155761719e-05s
Availability | VoID file availability check for BBOP took 0.0007936954498291016s
Completeness | Calculation of interlinking completeness for BBOP took 0.2514512538909912s
Reputation | Calculation of the PageRank for BBOP took 0.020807981491088867s
Interlinking | Calculation of Degree of Connection for BBOP took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.0279159545898438e-05s
Believability | Calculation of trust value for BBOP took 9.775161743164062e-06s
INFO | --- Analysis for bbop-selected took 19.888421535491943s
Availability | SPARQL endpoint availability check for Bdgp took 1.098505973815918s
Availability | VoID file availability check for Bdgp took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Bdgp took 0.2779512405395508s
Reputation | Calculation of the PageRank for Bdgp took 0.020219087600708008s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bdgp took 6.9141387939453125e-06s
INFO | --- Analysis for bdgp took 4.6194353103637695s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.220008850097656e-05s
Availability | VoID file availability check for Bendev Junior took 0.00063323974609375s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.2508089542388916s
Reputation | Calculation of the PageRank for Bendev Junior took 0.02013421058654785s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 2.86102294921875e-05s
Believability | Calculation of trust value for Bendev Junior took 6.67572021484375e-06s
INFO | --- Analysis for bendevoficial took 3.5907509326934814s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 6.1403186321258545s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.2547428607940674s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.02065420150756836s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.295608520507812e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 5.4836273193359375e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 17.48886799812317s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.1961669921875e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.00034809112548828125s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.26447486877441406s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020598888397216797s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 3.218650817871094e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 6.9141387939453125e-06s
INFO | --- Analysis for berlin-offener-haushalt took 2.856123447418213s
Availability | SPARQL endpoint availability check for berlios took 4.1484832763671875e-05s
Availability | VoID file availability check for berlios took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for berlios took 0.2696349620819092s
Reputation | Calculation of the PageRank for berlios took 0.020390987396240234s
Interlinking | Calculation of Degree of Connection for berlios took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for berlios took 9.34600830078125e-05s
Believability | Calculation of trust value for berlios took 7.3909759521484375e-06s
INFO | --- Analysis for berlios took 2.78875994682312s
Availability | SPARQL endpoint availability check for Between Our Worlds took 4.506111145019531e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.30438780784606934s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020209074020385742s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.771087646484375e-05s
Believability | Calculation of trust value for Between Our Worlds took 3.24249267578125e-05s
INFO | --- Analysis for betweenourworlds took 8.56977105140686s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.10758209228515625s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.25390148162841797s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.846687316894531e-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.463716506958008s
Availability | SPARQL endpoint availability check for BibBase took 0.0921776294708252s
Availability | VoID file availability check for BibBase took 0.00043773651123046875s
Completeness | Calculation of interlinking completeness for BibBase took 0.2665374279022217s
Reputation | Calculation of the PageRank for BibBase took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for BibBase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.870529174804688e-05s
Believability | Calculation of trust value for BibBase took 5.9604644775390625e-06s
INFO | --- Analysis for bibbase took 2.515535354614258s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 5.4836273193359375e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.29631757736206055s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.03094339370727539s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0010516643524169922s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.0001361370086669922s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 7.3909759521484375e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 8.46479845046997s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.410743713378906e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.2653036117553711s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.02072596549987793s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010156631469726562s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 6.9141387939453125e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 8.32445216178894s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 5.7697296142578125e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.2666172981262207s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0205228328704834s
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.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.1948089599609375e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.82114839553833s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.1961669921875e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.2589907646179199s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.02017498016357422s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.457069396972656e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 6.9141387939453125e-06s
INFO | --- Analysis for BibSonomy took 9.35829496383667s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 5.555152893066406e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.2576618194580078s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020185470581054688s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.24249267578125e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 6.9141387939453125e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 5.40460991859436s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 5.8650970458984375e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.000579833984375s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.27712178230285645s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.075599670410156e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 7.867813110351562e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.6511263847351074s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 6.699562072753906e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.2622520923614502s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.8359904289245605s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.870110273361206s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0006680488586425781s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 19.95635986328125s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.46698713302612305s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 44.58348727226257s
Interoperability | New terms check for Bio2RDF::Affymetrix took 42.215866804122925s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.10420274734497s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.11330652236938477s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.2996394634246826s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.17267560958862305s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 2.2818777561187744s
License | MR license check for Bio2RDF::Affymetrix took 0.43300962448120117s
License | HR license check for Bio2RDF::Affymetrix took 60.08890128135681s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.11419248580932617s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.68607211112976s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.31571030616760254s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.10502266883850098s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.10739636421203613s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.1047513484954834s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.678606271743774s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 74.20227909088135s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.6156351566314697s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.20783472061157227s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.6236026287078857s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.18745994567871094s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.10416626930236816s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.21553349494934082s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.20422792434692383s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 108.19007873535156s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 16.202154636383057s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.2591431140899658s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.11578249931335449s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.12248468399047852s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 6.223778247833252s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8781514167785645s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6323635578155518s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.2294447422027588s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 65.44742393493652s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.281423807144165s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 5.81567645072937s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.316744089126587s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.41707444190979s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7123425006866455s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.2977774143218994s
Security | Sign check for Bio2RDF::Affymetrix took 0.11480474472045898s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 16.267151355743408s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.929633617401123s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020301342010498047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010085105895996094s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 14.669081449508667s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-affymetrix took 1034.4308896064758s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.4731311798095703s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0006473064422607422s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 18.01615834236145s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2926597595214844s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 43.39235544204712s
Interoperability | New terms check for Bio2RDF::Biomodels took 40.48802900314331s
Versatility | Languages check for Bio2RDF::Biomodels took 60.25945854187012s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2690732479095459s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.154618501663208s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.3462028503417969s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.28615546226501465s
Availability | RDF dump link check for Bio2RDF::Biomodels took 2.173201084136963s
License | MR license check for Bio2RDF::Biomodels took 0.6323482990264893s
License | HR license check for Bio2RDF::Biomodels took 60.27023959159851s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.26563549041748047s
Understandability | Number of label check for Bio2RDF::Biomodels took 9.275327444076538s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5627210140228271s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2653968334197998s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.2369387149810791s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.257767915725708s
Performance | Throughput check for Bio2RDF::Biomodels took 11.620536804199219s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 74.51763343811035s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.5819175243377686s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.3627007007598877s
Interlinking | skos check for Bio2RDF::Biomodels took 0.8335511684417725s
Interlinking | skos check for Bio2RDF::Biomodels took 0.33481931686401367s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.27060508728027344s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5376663208007812s
Currency | Modification date check for Bio2RDF::Biomodels took 0.48964691162109375s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 109.74316811561584s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 13.293651342391968s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.40506696701049805s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.27354907989501953s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.27321743965148926s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 6.535802364349365s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.883795976638794s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6569006443023682s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.40978097915649414s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.02471089363098s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.431551933288574s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 5.877466440200806s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.3079514503479004s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.579816579818726s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7072007656097412s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.45970606803894043s
Security | Sign check for Bio2RDF::Biomodels took 0.25653862953186035s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 20.009823083877563s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 1.378936529159546s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.02043747901916504s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0006768703460693359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00013875961303710938s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 14.372178554534912s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-biomodels took 1042.711971282959s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.2514951229095459s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.147125244140625e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 4.805425405502319s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.46807003021240234s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0007448196411132812s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 18.356720209121704s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2514004707336426s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 43.62739372253418s
Interoperability | New terms check for Bio2RDF::Bioportal took 40.98081111907959s
Versatility | Languages check for Bio2RDF::Bioportal took 60.260650396347046s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.26745176315307617s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.16046929359436035s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.33761072158813477s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.33276867866516113s
Availability | RDF dump link check for Bio2RDF::Bioportal took 2.480578899383545s
License | MR license check for Bio2RDF::Bioportal took 0.49623894691467285s
License | HR license check for Bio2RDF::Bioportal took 60.237014293670654s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2380664348602295s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.399219751358032s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.5799775123596191s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.24619579315185547s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.26920413970947266s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.2568240165710449s
Performance | Throughput check for Bio2RDF::Bioportal took 11.47529149055481s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 76.2438759803772s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.5875263214111328s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.3796119689941406s
Interlinking | skos check for Bio2RDF::Bioportal took 0.7367038726806641s
Interlinking | skos check for Bio2RDF::Bioportal took 0.35048389434814453s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.2510831356048584s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5046627521514893s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5131607055664062s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 108.37467980384827s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 14.381223678588867s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.44825053215026855s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.281726598739624s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.26767921447753906s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 6.48998498916626s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8798742294311523s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6761922836303711s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.4309570789337158s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.53634929656982s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.4253599643707275s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.024808883666992s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.3077497482299805s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.57521343231201s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7122218608856201s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.4016764163970947s
Security | Sign check for Bio2RDF::Bioportal took 0.26425671577453613s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 15.875925779342651s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 1.5832011699676514s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.00041747093200683594s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 15.440760135650635s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1050.5332033634186s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.14128828048706055s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.3191847801208496s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020216941833496094s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.173683166503906e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-chembl took 16.852495193481445s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.466325044631958s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0006320476531982422s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 18.923848390579224s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2387416362762451s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 45.880274295806885s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 39.93283820152283s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.248618841171265s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.2622213363647461s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.15436029434204102s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.26413583755493164s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.3101541996002197s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 2.3055663108825684s
License | MR license check for Bio2RDF::Clinicaltrials took 0.48420166969299316s
License | HR license check for Bio2RDF::Clinicaltrials took 60.251325845718384s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.24773550033569336s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 9.876087427139282s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5815021991729736s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.26153993606567383s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.259798526763916s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.25562024116516113s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.486522197723389s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 76.72690224647522s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.5911433696746826s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.3564913272857666s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 1.0264275074005127s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3448662757873535s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.26319313049316406s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5026421546936035s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5172924995422363s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 108.30297422409058s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 11.947354316711426s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.4230039119720459s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.2828855514526367s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.2426302433013916s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 6.5014729499816895s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8881704807281494s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6445209980010986s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.280820369720459s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.44038486480713s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.4236650466918945s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.8182549476623535s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.2930142879486084s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.51730942726135s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7028286457061768s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.4535064697265625s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.2804756164550781s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 15.629202365875244s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 1.1072840690612793s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.602836608886719e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 12.291151523590088s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1035.603518486023s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.47624635696411133s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0005736351013183594s
Extra | Recovery of all triples for Bio2RDF::Ctd took 17.884512186050415s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2316439151763916s
Amount of data | Number of triples check for Bio2RDF::Ctd took 44.23836159706116s
Interoperability | New terms check for Bio2RDF::Ctd took 41.70785164833069s
Versatility | Languages check for Bio2RDF::Ctd took 60.25224804878235s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.27483344078063965s
Security | Check HTTPS for Bio2RDF::Ctd took 0.14617204666137695s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.45078611373901367s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.31365299224853516s
Availability | RDF dump link check for Bio2RDF::Ctd took 2.4057509899139404s
License | MR license check for Bio2RDF::Ctd took 0.5962724685668945s
License | HR license check for Bio2RDF::Ctd took 60.260923862457275s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2438669204711914s
Understandability | Number of label check for Bio2RDF::Ctd took 9.916087627410889s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5687968730926514s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.23579120635986328s
Verifiability | Authors check for Bio2RDF::Ctd took 0.2607583999633789s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.24402379989624023s
Performance | Throughput check for Bio2RDF::Ctd took 10.368060827255249s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 74.02120661735535s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.7896349430084229s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.3784146308898926s
Interlinking | skos check for Bio2RDF::Ctd took 0.8101246356964111s
Interlinking | skos check for Bio2RDF::Ctd took 0.39836835861206055s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.2628602981567383s
Currency | Creation date check for Bio2RDF::Ctd took 0.5328712463378906s
Currency | Modification date check for Bio2RDF::Ctd took 0.49144768714904785s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 108.2078537940979s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 12.604467153549194s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.3984203338623047s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.28770971298217773s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.24893689155578613s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 6.834993362426758s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8786582946777344s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.641838788986206s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.5084364414215088s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.68028569221497s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.4187722206115723s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.218194484710693s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3091089725494385s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.552212953567505s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7104628086090088s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.41843318939208984s
Security | Sign check for Bio2RDF::Ctd took 0.2692885398864746s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 16.238637924194336s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 1.4900050163269043s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020152568817138672s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0006802082061767578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 12.98587703704834s
Believability | Calculation of trust value for Bio2RDF::Ctd took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-ctd took 1044.650351524353s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.220008850097656e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.6794407367706299s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0009100437164306641s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.602836608886719e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 9.5367431640625e-06s
INFO | --- Analysis for bio2rdf-dataset took 4.343033075332642s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.4712965488433838s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0006582736968994141s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 18.28931736946106s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2339324951171875s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 44.77190446853638s
Interoperability | New terms check for Bio2RDF::Dbsnp took 40.48964166641235s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.262789249420166s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.2679305076599121s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.14486360549926758s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.2519948482513428s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.31905245780944824s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 2.3857579231262207s
License | MR license check for Bio2RDF::Dbsnp took 0.46396565437316895s
License | HR license check for Bio2RDF::Dbsnp took 60.25883936882019s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.26477861404418945s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.196110725402832s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5777010917663574s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.24347639083862305s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2513751983642578s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.24579739570617676s
Performance | Throughput check for Bio2RDF::Dbsnp took 12.106389284133911s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 78.32656407356262s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.6812975406646729s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.36574745178222656s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.6826498508453369s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.34775304794311523s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.24430561065673828s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5313150882720947s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5130140781402588s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 108.35134387016296s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 12.894457340240479s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4271888732910156s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.28423547744750977s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.2578165531158447s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 6.789361953735352s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8835625648498535s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6650373935699463s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.3850836753845215s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.13767957687378s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.416027307510376s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.0433549880981445s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.2708756923675537s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.558738231658936s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7135646343231201s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.44705915451049805s
Security | Sign check for Bio2RDF::Dbsnp took 0.27449750900268555s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 16.500007152557373s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 1.3439977169036865s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.05718994140625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 12.583711862564087s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 1040.231914281845s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.4499173164367676s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0004291534423828125s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 18.682756662368774s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2645061016082764s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 44.37448287010193s
Interoperability | New terms check for Bio2RDF::Drugbank took 40.12653422355652s
Versatility | Languages check for Bio2RDF::Drugbank took 60.26721453666687s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.28542065620422363s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.15540671348571777s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.48067545890808105s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.29831910133361816s
Availability | RDF dump link check for Bio2RDF::Drugbank took 2.46502423286438s
License | MR license check for Bio2RDF::Drugbank took 0.4983694553375244s
License | HR license check for Bio2RDF::Drugbank took 60.26107120513916s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.2727820873260498s
Understandability | Number of label check for Bio2RDF::Drugbank took 10.286216735839844s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5964155197143555s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.2660491466522217s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.2740285396575928s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.26385021209716797s
Performance | Throughput check for Bio2RDF::Drugbank took 11.024129390716553s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 74.46774768829346s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.5961425304412842s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.3798069953918457s
Interlinking | skos check for Bio2RDF::Drugbank took 0.7383270263671875s
Interlinking | skos check for Bio2RDF::Drugbank took 0.3458092212677002s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2484757900238037s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5130062103271484s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5052578449249268s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 107.94969606399536s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 12.776948690414429s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4478111267089844s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.5741119384765625s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.2781565189361572s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 7.248277902603149s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8809170722961426s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6658785343170166s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.4331026077270508s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.04290318489075s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.4456279277801514s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.155450344085693s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.3240454196929932s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.537018060684204s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.6988599300384521s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.42801690101623535s
Security | Sign check for Bio2RDF::Drugbank took 0.2900867462158203s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 16.06934356689453s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.5220296382904053s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020300626754760742s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00011229515075683594s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 11.641855716705322s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-drugbank took 1035.4455833435059s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.5000176429748535s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0005936622619628906s
Extra | Recovery of all triples for Bio2RDF::Genage took 18.027743339538574s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.251793622970581s
Amount of data | Number of triples check for Bio2RDF::Genage took 43.781723976135254s
Interoperability | New terms check for Bio2RDF::Genage took 39.98963379859924s
Versatility | Languages check for Bio2RDF::Genage took 60.24623394012451s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.26707887649536133s
Security | Check HTTPS for Bio2RDF::Genage took 0.1557331085205078s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.25412487983703613s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.29912447929382324s
Availability | RDF dump link check for Bio2RDF::Genage took 2.2215893268585205s
License | MR license check for Bio2RDF::Genage took 0.4855363368988037s
License | HR license check for Bio2RDF::Genage took 60.23925852775574s
Amount of data | Number of property check for Bio2RDF::Genage took 0.2491903305053711s
Understandability | Number of label check for Bio2RDF::Genage took 9.973000764846802s
Understandability | URI regex check for Bio2RDF::Genage took 0.5952024459838867s
Understandability | Vocabs check for Bio2RDF::Genage took 0.2502927780151367s
Verifiability | Authors check for Bio2RDF::Genage took 0.28969383239746094s
Verifiability | Publishers check for Bio2RDF::Genage took 0.2664608955383301s
Performance | Throughput check for Bio2RDF::Genage took 11.72448468208313s
Amount of data | Check the number of entities for Bio2RDF::Genage took 75.19597959518433s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.6626632213592529s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.3536550998687744s
Interlinking | skos check for Bio2RDF::Genage took 0.89668869972229s
Interlinking | skos check for Bio2RDF::Genage took 0.35207033157348633s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2603790760040283s
Currency | Creation date check for Bio2RDF::Genage took 0.49427318572998047s
Currency | Modification date check for Bio2RDF::Genage took 0.5213353633880615s
Rep.Conc. | URIs length for Bio2RDF::Genage took 110.79142022132874s
Interoperability | New vocabularies check for Bio2RDF::Genage took 12.373729944229126s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.4182300567626953s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.29918766021728516s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.27973484992980957s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 6.831453323364258s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8836159706115723s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.7010693550109863s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.42522525787353516s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.32073092460632s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.4505276679992676s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.555680990219116s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.2889864444732666s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.575427293777466s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7223303318023682s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.4348146915435791s
Security | Sign check for Bio2RDF::Genage took 0.29642415046691895s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 16.40938448905945s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 1.2950937747955322s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020450592041015625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.008148193359375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 15.231424570083618s
Believability | Calculation of trust value for Bio2RDF::Genage took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-genage took 1040.9990119934082s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 4.291534423828125e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.257601261138916s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 7.271766662597656e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-genbank took 4.237288475036621s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.4740021228790283s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006844997406005859s
Extra | Recovery of all triples for Bio2RDF::Gendr took 21.176257610321045s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2642390727996826s
Amount of data | Number of triples check for Bio2RDF::Gendr took 43.88941764831543s
Interoperability | New terms check for Bio2RDF::Gendr took 42.71573805809021s
Versatility | Languages check for Bio2RDF::Gendr took 60.24957203865051s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.26661086082458496s
Security | Check HTTPS for Bio2RDF::Gendr took 0.15653657913208008s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.6270804405212402s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.288743257522583s
Availability | RDF dump link check for Bio2RDF::Gendr took 2.6670923233032227s
License | MR license check for Bio2RDF::Gendr took 0.4725840091705322s
License | HR license check for Bio2RDF::Gendr took 60.24028491973877s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.23431682586669922s
Understandability | Number of label check for Bio2RDF::Gendr took 9.525792360305786s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5694582462310791s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.2582738399505615s
Verifiability | Authors check for Bio2RDF::Gendr took 0.2517118453979492s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2630898952484131s
Performance | Throughput check for Bio2RDF::Gendr took 11.109584093093872s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 76.15372371673584s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.7613821029663086s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.3759732246398926s
Interlinking | skos check for Bio2RDF::Gendr took 0.8318221569061279s
Interlinking | skos check for Bio2RDF::Gendr took 0.33664965629577637s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.26192402839660645s
Currency | Creation date check for Bio2RDF::Gendr took 0.4924044609069824s
Currency | Modification date check for Bio2RDF::Gendr took 0.5081470012664795s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 107.527902841568s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 13.788633108139038s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.4279506206512451s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.2849135398864746s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2798621654510498s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 6.415632724761963s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8772873878479004s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6407263278961182s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.4424915313720703s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 64.97193026542664s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.425713300704956s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.507096767425537s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.311638355255127s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.52499175071716s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7105710506439209s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.4457240104675293s
Security | Sign check for Bio2RDF::Gendr took 0.28002142906188965s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 16.09696936607361s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.9459912776947021s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.7220458984375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 11.532854318618774s
Believability | Calculation of trust value for Bio2RDF::Gendr took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-gendr took 1041.0776433944702s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.47521042823791504s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0006313323974609375s
Extra | Recovery of all triples for Bio2RDF::Goa took 17.883127212524414s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2464194297790527s
Amount of data | Number of triples check for Bio2RDF::Goa took 43.71150088310242s
Interoperability | New terms check for Bio2RDF::Goa took 40.538474321365356s
Versatility | Languages check for Bio2RDF::Goa took 60.2358775138855s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.26690244674682617s
Security | Check HTTPS for Bio2RDF::Goa took 0.1573498249053955s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.4724769592285156s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.3244352340698242s
Availability | RDF dump link check for Bio2RDF::Goa took 2.3058457374572754s
License | MR license check for Bio2RDF::Goa took 0.35454344749450684s
License | HR license check for Bio2RDF::Goa took 60.25319695472717s
Amount of data | Number of property check for Bio2RDF::Goa took 0.23450112342834473s
Understandability | Number of label check for Bio2RDF::Goa took 10.822283267974854s
Understandability | URI regex check for Bio2RDF::Goa took 0.5853860378265381s
Understandability | Vocabs check for Bio2RDF::Goa took 0.25220775604248047s
Verifiability | Authors check for Bio2RDF::Goa took 0.2533111572265625s
Verifiability | Publishers check for Bio2RDF::Goa took 0.25528812408447266s
Performance | Throughput check for Bio2RDF::Goa took 11.194677114486694s
Amount of data | Check the number of entities for Bio2RDF::Goa took 78.32681012153625s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.5611734390258789s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.384335994720459s
Interlinking | skos check for Bio2RDF::Goa took 0.9544751644134521s
Interlinking | skos check for Bio2RDF::Goa took 0.334918737411499s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.2602229118347168s
Currency | Creation date check for Bio2RDF::Goa took 0.49901390075683594s
Currency | Modification date check for Bio2RDF::Goa took 0.4992825984954834s
Rep.Conc. | URIs length for Bio2RDF::Goa took 107.80304527282715s
Interoperability | New vocabularies check for Bio2RDF::Goa took 13.171566724777222s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.44061994552612305s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.28098130226135254s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.26726841926574707s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 6.802801132202148s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8786594867706299s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6823832988739014s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.49564099311828613s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.45590209960938s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.364309549331665s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.336293935775757s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.2852802276611328s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.55713200569153s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.713759183883667s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.4327666759490967s
Security | Sign check for Bio2RDF::Goa took 0.27939343452453613s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 16.379446506500244s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.9698951244354248s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020379066467285156s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 5.6743621826171875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 17.812172651290894s
Believability | Calculation of trust value for Bio2RDF::Goa took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-goa took 1051.9614534378052s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.49039602279663086s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0006055831909179688s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 18.314117670059204s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2476675510406494s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 43.891438484191895s
Interoperability | New terms check for Bio2RDF::Hgnc took 40.09977650642395s
Versatility | Languages check for Bio2RDF::Hgnc took 60.24502778053284s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.27506422996520996s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.16436123847961426s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.5597379207611084s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.3000197410583496s
Availability | RDF dump link check for Bio2RDF::Hgnc took 2.6315090656280518s
License | MR license check for Bio2RDF::Hgnc took 0.36698460578918457s
License | HR license check for Bio2RDF::Hgnc took 60.25641655921936s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.2634098529815674s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.840665578842163s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5952887535095215s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.2643725872039795s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.24397945404052734s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.23958396911621094s
Performance | Throughput check for Bio2RDF::Hgnc took 11.943260192871094s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 79.3103461265564s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.759601354598999s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.3713836669921875s
Interlinking | skos check for Bio2RDF::Hgnc took 0.9556493759155273s
Interlinking | skos check for Bio2RDF::Hgnc took 0.33623337745666504s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.25205016136169434s
Currency | Creation date check for Bio2RDF::Hgnc took 0.4940669536590576s
Currency | Modification date check for Bio2RDF::Hgnc took 0.503230094909668s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 109.87164974212646s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 13.178611755371094s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.4072082042694092s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.28443264961242676s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.2717139720916748s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.107638597488403s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8879363536834717s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6538717746734619s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.4123804569244385s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.35645842552185s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.4619827270507812s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.13477349281311s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.3179452419281006s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.573349475860596s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7123489379882812s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.43536972999572754s
Security | Sign check for Bio2RDF::Hgnc took 0.2519569396972656s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 16.363022089004517s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 1.5688002109527588s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.02396392822265625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.0001201629638671875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 11.391953945159912s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-hgnc took 1044.65025806427s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.494154691696167s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.00036907196044921875s
Extra | Recovery of all triples for Bio2RDF::Homologene took 20.029330253601074s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2452125549316406s
Amount of data | Number of triples check for Bio2RDF::Homologene took 43.12022590637207s
Interoperability | New terms check for Bio2RDF::Homologene took 43.294909715652466s
Versatility | Languages check for Bio2RDF::Homologene took 60.25199913978577s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.2898733615875244s
Security | Check HTTPS for Bio2RDF::Homologene took 0.16797208786010742s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.2659578323364258s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.31981444358825684s
Availability | RDF dump link check for Bio2RDF::Homologene took 2.480518341064453s
License | MR license check for Bio2RDF::Homologene took 0.4769918918609619s
License | HR license check for Bio2RDF::Homologene took 60.251909494400024s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.25188398361206055s
Understandability | Number of label check for Bio2RDF::Homologene took 9.890127420425415s
Understandability | URI regex check for Bio2RDF::Homologene took 0.6200294494628906s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.2569613456726074s
Verifiability | Authors check for Bio2RDF::Homologene took 0.25246572494506836s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.2705414295196533s
Performance | Throughput check for Bio2RDF::Homologene took 11.705808162689209s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 76.23888659477234s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.5826859474182129s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.36539125442504883s
Interlinking | skos check for Bio2RDF::Homologene took 0.8282265663146973s
Interlinking | skos check for Bio2RDF::Homologene took 0.3543400764465332s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.26777148246765137s
Currency | Creation date check for Bio2RDF::Homologene took 0.4775834083557129s
Currency | Modification date check for Bio2RDF::Homologene took 0.493988037109375s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 108.80538249015808s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 11.573851108551025s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.43480944633483887s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.268707275390625s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.28939294815063477s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 7.227535724639893s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8801095485687256s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.7029261589050293s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.5071182250976562s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.55713129043579s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.3317978382110596s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.574146509170532s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.2911818027496338s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.53211688995361s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7106189727783203s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.43834710121154785s
Security | Sign check for Bio2RDF::Homologene took 0.2642819881439209s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 15.340893268585205s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 1.3144128322601318s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020285844802856445s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.888938903808594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 12.207765817642212s
Believability | Calculation of trust value for Bio2RDF::Homologene took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-homologene took 1043.0139038562775s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.23889923095703125s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.020813941955566406s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 3.4332275390625e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 5.9604644775390625e-06s
INFO | --- Analysis for bio2rdf-inoh took 3.7504544258117676s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.49178266525268555s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0005667209625244141s
Extra | Recovery of all triples for Bio2RDF::Interpro took 19.21424150466919s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2328987121582031s
Amount of data | Number of triples check for Bio2RDF::Interpro took 44.62593936920166s
Interoperability | New terms check for Bio2RDF::Interpro took 42.82521319389343s
Versatility | Languages check for Bio2RDF::Interpro took 60.23608422279358s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.2620558738708496s
Security | Check HTTPS for Bio2RDF::Interpro took 0.15689396858215332s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.5940155982971191s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.36360621452331543s
Availability | RDF dump link check for Bio2RDF::Interpro took 2.5110154151916504s
License | MR license check for Bio2RDF::Interpro took 0.4495408535003662s
License | HR license check for Bio2RDF::Interpro took 60.255698680877686s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.24880266189575195s
Understandability | Number of label check for Bio2RDF::Interpro took 9.31285309791565s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5993528366088867s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.25457763671875s
Verifiability | Authors check for Bio2RDF::Interpro took 0.26654958724975586s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.252732515335083s
Performance | Throughput check for Bio2RDF::Interpro took 11.106816053390503s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 75.93745851516724s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.5835998058319092s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.35727643966674805s
Interlinking | skos check for Bio2RDF::Interpro took 0.7439637184143066s
Interlinking | skos check for Bio2RDF::Interpro took 0.3409426212310791s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2671680450439453s
Currency | Creation date check for Bio2RDF::Interpro took 0.5063290596008301s
Currency | Modification date check for Bio2RDF::Interpro took 0.522374153137207s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 110.16729784011841s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 13.485809087753296s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.4410581588745117s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.2908475399017334s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2768566608428955s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 6.983136892318726s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8783080577850342s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.636091947555542s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.43493127822875977s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.21710968017578s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.39156436920166s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.573618412017822s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.2690155506134033s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.52451992034912s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7108573913574219s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.43292927742004395s
Security | Sign check for Bio2RDF::Interpro took 0.2660989761352539s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 17.366495847702026s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.9554855823516846s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.02030205726623535s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00011563301086425781s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 13.899537801742554s
Believability | Calculation of trust value for Bio2RDF::Interpro took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-interpro took 1051.3964912891388s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.14264154434204102s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.342487096786499s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.02026844024658203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.367134094238281e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-iproclass took 17.240802526474s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.4869191646575928s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0005486011505126953s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 19.186994075775146s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2340638637542725s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 44.002344369888306s
Interoperability | New terms check for Bio2RDF::Irefindex took 40.89915323257446s
Versatility | Languages check for Bio2RDF::Irefindex took 60.25486707687378s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.2723076343536377s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.14303278923034668s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.5665440559387207s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.3196432590484619s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.2568233013153076s
License | MR license check for Bio2RDF::Irefindex took 0.47408413887023926s
License | HR license check for Bio2RDF::Irefindex took 60.24247097969055s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.2536900043487549s
Understandability | Number of label check for Bio2RDF::Irefindex took 9.526516199111938s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.598388671875s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.2391643524169922s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.24717402458190918s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.23620820045471191s
Performance | Throughput check for Bio2RDF::Irefindex took 11.251274824142456s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 78.18827748298645s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.5669426918029785s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.38265228271484375s
Interlinking | skos check for Bio2RDF::Irefindex took 0.7844028472900391s
Interlinking | skos check for Bio2RDF::Irefindex took 0.33654117584228516s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.2538168430328369s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5054202079772949s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5057849884033203s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 109.03350877761841s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 12.266639947891235s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.44478869438171387s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.27913355827331543s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.2630023956298828s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 7.1663007736206055s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8816056251525879s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6364598274230957s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.5014123916625977s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.42943120002747s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.3994903564453125s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.423874616622925s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.303971290588379s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.553900957107544s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7176947593688965s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.442183256149292s
Security | Sign check for Bio2RDF::Irefindex took 0.2765979766845703s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 19.39646029472351s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.8959722518920898s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.02017688751220703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.702278137207031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 11.469418287277222s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-irefindex took 1041.2864866256714s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 4.291534423828125e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.7064409255981445s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.02016735076904297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.937980651855469e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-kegg took 5.056696653366089s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.458427429199219e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.256270170211792s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.218650817871094e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 3.3265864849090576s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.1425323486328125s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2832002639770508s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.02030158042907715s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.337860107421875e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 9.624261617660522s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.49614405632019043s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0006461143493652344s
Extra | Recovery of all triples for Bio2RDF::Lsr took 18.250563621520996s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2349011898040771s
Amount of data | Number of triples check for Bio2RDF::Lsr took 43.37142992019653s
Interoperability | New terms check for Bio2RDF::Lsr took 40.32046127319336s
Versatility | Languages check for Bio2RDF::Lsr took 60.23269248008728s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.2673025131225586s
Security | Check HTTPS for Bio2RDF::Lsr took 0.16751813888549805s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.4695420265197754s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.3123314380645752s
Availability | RDF dump link check for Bio2RDF::Lsr took 2.3992204666137695s
License | MR license check for Bio2RDF::Lsr took 0.5050866603851318s
License | HR license check for Bio2RDF::Lsr took 60.28228712081909s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.24847650527954102s
Understandability | Number of label check for Bio2RDF::Lsr took 9.889652013778687s
Understandability | URI regex check for Bio2RDF::Lsr took 0.5652899742126465s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.26027965545654297s
Verifiability | Authors check for Bio2RDF::Lsr took 0.260634183883667s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.260772705078125s
Performance | Throughput check for Bio2RDF::Lsr took 11.167504072189331s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 75.77356934547424s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.5798091888427734s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.34615516662597656s
Interlinking | skos check for Bio2RDF::Lsr took 0.8417773246765137s
Interlinking | skos check for Bio2RDF::Lsr took 0.35381007194519043s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.2577505111694336s
Currency | Creation date check for Bio2RDF::Lsr took 0.4947652816772461s
Currency | Modification date check for Bio2RDF::Lsr took 0.502824068069458s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 111.77946662902832s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 12.196166753768921s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.40172696113586426s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.26216793060302734s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.27242612838745117s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 6.620749235153198s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.880274772644043s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6577231884002686s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.3972163200378418s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.04867959022522s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.387244701385498s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.0447962284088135s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.2973906993865967s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.507428884506226s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7036466598510742s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.4064211845397949s
Security | Sign check for Bio2RDF::Lsr took 0.27252197265625s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 18.200824975967407s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 1.4755797386169434s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02030634880065918s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.245208740234375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 12.637609481811523s
Believability | Calculation of trust value for Bio2RDF::Lsr took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-lsr took 1039.9013814926147s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.4737067222595215s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0008320808410644531s
Extra | Recovery of all triples for Bio2RDF::Mesh took 18.14982271194458s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2151820659637451s
Amount of data | Number of triples check for Bio2RDF::Mesh took 44.44300436973572s
Interoperability | New terms check for Bio2RDF::Mesh took 40.309691190719604s
Versatility | Languages check for Bio2RDF::Mesh took 60.25596904754639s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.27484655380249023s
Security | Check HTTPS for Bio2RDF::Mesh took 0.15382814407348633s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.3800809383392334s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.3472621440887451s
Availability | RDF dump link check for Bio2RDF::Mesh took 2.4238157272338867s
License | MR license check for Bio2RDF::Mesh took 0.589043140411377s
License | HR license check for Bio2RDF::Mesh took 60.237160205841064s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.26578664779663086s
Understandability | Number of label check for Bio2RDF::Mesh took 9.966430187225342s
Understandability | URI regex check for Bio2RDF::Mesh took 0.6025362014770508s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.27068138122558594s
Verifiability | Authors check for Bio2RDF::Mesh took 0.24131011962890625s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.26637887954711914s
Performance | Throughput check for Bio2RDF::Mesh took 11.238322734832764s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 76.64054894447327s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.569737434387207s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.37598228454589844s
Interlinking | skos check for Bio2RDF::Mesh took 0.8431508541107178s
Interlinking | skos check for Bio2RDF::Mesh took 0.33983612060546875s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.2524392604827881s
Currency | Creation date check for Bio2RDF::Mesh took 0.5172970294952393s
Currency | Modification date check for Bio2RDF::Mesh took 0.5024254322052002s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 107.45445990562439s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 12.460923910140991s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.40430188179016113s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2745535373687744s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.2770271301269531s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 7.270450592041016s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8784053325653076s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6618058681488037s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.45395755767822266s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 64.90343117713928s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.3734500408172607s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.0276875495910645s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.2853705883026123s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.58475470542908s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.7016627788543701s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.44251394271850586s
Security | Sign check for Bio2RDF::Mesh took 0.2679104804992676s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 18.184590816497803s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 1.2707936763763428s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.02042865753173828s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0008852481842041016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 8.344650268554688e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 12.5052490234375s
Believability | Calculation of trust value for Bio2RDF::Mesh took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-mesh took 1038.7975199222565s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 1.273315191268921s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0006239414215087891s
Extra | Recovery of all triples for Bio2RDF::Mgi took 18.67600393295288s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2173564434051514s
Amount of data | Number of triples check for Bio2RDF::Mgi took 43.22757577896118s
Interoperability | New terms check for Bio2RDF::Mgi took 40.460108041763306s
Versatility | Languages check for Bio2RDF::Mgi took 60.24376845359802s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.27161216735839844s
Security | Check HTTPS for Bio2RDF::Mgi took 0.16408467292785645s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.8527040481567383s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.30971193313598633s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.5255730152130127s
License | MR license check for Bio2RDF::Mgi took 0.5167717933654785s
License | HR license check for Bio2RDF::Mgi took 60.25132465362549s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.26967406272888184s
Understandability | Number of label check for Bio2RDF::Mgi took 9.600335836410522s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5824193954467773s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.24964642524719238s
Verifiability | Authors check for Bio2RDF::Mgi took 0.2624852657318115s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.23544669151306152s
Performance | Throughput check for Bio2RDF::Mgi took 10.793205976486206s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 80.73156762123108s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.7592544555664062s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.3826744556427002s
Interlinking | skos check for Bio2RDF::Mgi took 0.7818272113800049s
Interlinking | skos check for Bio2RDF::Mgi took 0.3453202247619629s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.2664332389831543s
Currency | Creation date check for Bio2RDF::Mgi took 0.49057555198669434s
Currency | Modification date check for Bio2RDF::Mgi took 0.5027799606323242s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 110.66924810409546s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 12.449249744415283s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.45981836318969727s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.2687854766845703s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.25507497787475586s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 6.832679510116577s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8740589618682861s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6727490425109863s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.3927292823791504s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.15092039108276s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.4445688724517822s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 5.9949631690979s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3239800930023193s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.56619572639465s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7198524475097656s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.40578174591064453s
Security | Sign check for Bio2RDF::Mgi took 0.25165271759033203s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 18.101288080215454s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.9152011871337891s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.0204160213470459s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.822845458984375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 12.285908222198486s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-mgi took 1050.4629917144775s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.47965025901794434s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0006117820739746094s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 18.0537052154541s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2253055572509766s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 43.25499176979065s
Interoperability | New terms check for Bio2RDF::Ncbigene took 40.598010540008545s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.24390649795532s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.26422691345214844s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.14522099494934082s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.6694018840789795s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.3048417568206787s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 2.2949066162109375s
License | MR license check for Bio2RDF::Ncbigene took 0.47878289222717285s
License | HR license check for Bio2RDF::Ncbigene took 60.23610043525696s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.267305850982666s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.21530532836914s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.581852912902832s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.23627686500549316s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.24289822578430176s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.2378854751586914s
Performance | Throughput check for Bio2RDF::Ncbigene took 10.976213932037354s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 79.48531985282898s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.5756502151489258s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.36028051376342773s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.5364429950714111s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.35354042053222656s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.2675497531890869s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5037026405334473s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.4955422878265381s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 107.36678338050842s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 11.992220878601074s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.4192354679107666s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.28629398345947266s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.24432706832885742s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.008733034133911s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8810865879058838s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6405479907989502s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.3841736316680908s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.07041549682617s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.403940200805664s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 5.913354396820068s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.3062946796417236s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.524274826049805s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7050442695617676s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.42494869232177734s
Security | Sign check for Bio2RDF::Ncbigene took 0.24475550651550293s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 18.955501794815063s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 1.3739910125732422s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.021119356155395508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012564659118652344s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 11.90343189239502s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 1044.5247342586517s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.48833227157592773s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0006482601165771484s
Extra | Recovery of all triples for Bio2RDF::Ndc took 18.565150499343872s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2715206146240234s
Amount of data | Number of triples check for Bio2RDF::Ndc took 44.41934132575989s
Interoperability | New terms check for Bio2RDF::Ndc took 41.18465781211853s
Versatility | Languages check for Bio2RDF::Ndc took 60.24920582771301s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.2848207950592041s
Security | Check HTTPS for Bio2RDF::Ndc took 0.16848301887512207s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.2792959213256836s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.32781982421875s
Availability | RDF dump link check for Bio2RDF::Ndc took 2.5165820121765137s
License | MR license check for Bio2RDF::Ndc took 0.4576244354248047s
License | HR license check for Bio2RDF::Ndc took 60.256020307540894s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.24330806732177734s
Understandability | Number of label check for Bio2RDF::Ndc took 9.532767057418823s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5839025974273682s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.2729172706604004s
Verifiability | Authors check for Bio2RDF::Ndc took 0.26746463775634766s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.2582275867462158s
Performance | Throughput check for Bio2RDF::Ndc took 11.302587747573853s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 79.79800605773926s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.7303824424743652s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.33834171295166016s
Interlinking | skos check for Bio2RDF::Ndc took 1.042501449584961s
Interlinking | skos check for Bio2RDF::Ndc took 0.3545560836791992s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.24694561958312988s
Currency | Creation date check for Bio2RDF::Ndc took 0.5174686908721924s
Currency | Modification date check for Bio2RDF::Ndc took 0.5066380500793457s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 108.8492910861969s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 12.984126806259155s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.4397852420806885s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2642343044281006s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.2582523822784424s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 6.700284242630005s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8783330917358398s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.640939474105835s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.44966936111450195s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.17309951782227s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.404982089996338s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.2112627029418945s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.2830595970153809s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.5638632774353s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7419991493225098s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.42040562629699707s
Security | Sign check for Bio2RDF::Ndc took 0.2864081859588623s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 18.2211754322052s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 1.4618732929229736s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020549297332763672s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.650520324707031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 12.896013736724854s
Believability | Calculation of trust value for Bio2RDF::Ndc took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-ndc took 1048.625337600708s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.601478576660156e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.6995713710784912s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.0206911563873291s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.504753112792969e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-netpath took 4.279414415359497s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.13908863067626953s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.2574758529663086s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-nextprot took 3.333728075027466s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.45685791969299316s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0006458759307861328s
Extra | Recovery of all triples for Bio2RDF::Omim took 19.086283206939697s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.2158312797546387s
Amount of data | Number of triples check for Bio2RDF::Omim took 43.80175447463989s
Interoperability | New terms check for Bio2RDF::Omim took 41.27596735954285s
Versatility | Languages check for Bio2RDF::Omim took 60.249751806259155s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.26767826080322266s
Security | Check HTTPS for Bio2RDF::Omim took 0.15627169609069824s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.3421599864959717s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.2925419807434082s
Availability | RDF dump link check for Bio2RDF::Omim took 2.389930486679077s
License | MR license check for Bio2RDF::Omim took 0.4583768844604492s
License | HR license check for Bio2RDF::Omim took 60.25831389427185s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2525205612182617s
Understandability | Number of label check for Bio2RDF::Omim took 9.366038799285889s
Understandability | URI regex check for Bio2RDF::Omim took 0.5843439102172852s
Understandability | Vocabs check for Bio2RDF::Omim took 0.23519062995910645s
Verifiability | Authors check for Bio2RDF::Omim took 0.23845171928405762s
Verifiability | Publishers check for Bio2RDF::Omim took 0.25115036964416504s
Performance | Throughput check for Bio2RDF::Omim took 11.929588794708252s
Amount of data | Check the number of entities for Bio2RDF::Omim took 79.07014203071594s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.5694773197174072s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.39040470123291016s
Interlinking | skos check for Bio2RDF::Omim took 1.0116145610809326s
Interlinking | skos check for Bio2RDF::Omim took 0.3407399654388428s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.27168941497802734s
Currency | Creation date check for Bio2RDF::Omim took 0.5382516384124756s
Currency | Modification date check for Bio2RDF::Omim took 0.5157690048217773s
Rep.Conc. | URIs length for Bio2RDF::Omim took 111.94616985321045s
Interoperability | New vocabularies check for Bio2RDF::Omim took 12.28157639503479s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.39177799224853516s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.2963869571685791s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.2898991107940674s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 6.70878529548645s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8832910060882568s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6546821594238281s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.28976869583129883s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 64.8373281955719s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.3973004817962646s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.235265731811523s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.2716939449310303s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.51587891578674s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.704796552658081s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.4068431854248047s
Security | Sign check for Bio2RDF::Omim took 0.27872610092163086s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 18.01231098175049s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 1.2687220573425293s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.023039579391479492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.0001270771026611328s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 11.928355693817139s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-omim took 1045.5762345790863s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.363059997558594e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0007226467132568359s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.2634434700012207s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020397663116455078s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.291534423828125e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 3.6200151443481445s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.4682013988494873s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0006563663482666016s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 18.930166721343994s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2630393505096436s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 44.27020287513733s
Interoperability | New terms check for Bio2RDF::Orphanet took 42.84454035758972s
Versatility | Languages check for Bio2RDF::Orphanet took 60.240854263305664s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.26725196838378906s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.16714215278625488s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.5174858570098877s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.33097052574157715s
Availability | RDF dump link check for Bio2RDF::Orphanet took 2.4498772621154785s
License | MR license check for Bio2RDF::Orphanet took 0.4963393211364746s
License | HR license check for Bio2RDF::Orphanet took 60.24908232688904s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.2583036422729492s
Understandability | Number of label check for Bio2RDF::Orphanet took 9.362208366394043s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5769205093383789s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.24774622917175293s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.26145482063293457s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.2527303695678711s
Performance | Throughput check for Bio2RDF::Orphanet took 11.46043872833252s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 74.57337284088135s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.5965697765350342s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.3588390350341797s
Interlinking | skos check for Bio2RDF::Orphanet took 0.8995583057403564s
Interlinking | skos check for Bio2RDF::Orphanet took 0.37314653396606445s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.2759268283843994s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5218751430511475s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5326766967773438s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 109.9367949962616s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 12.792517900466919s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.4567129611968994s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.28686046600341797s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.28448486328125s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 7.3215837478637695s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8866879940032959s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6817858219146729s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.45092272758483887s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.098965883255s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.404780387878418s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.671693563461304s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.302703857421875s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.551657915115356s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7283179759979248s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.4280741214752197s
Security | Sign check for Bio2RDF::Orphanet took 0.2674570083618164s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 19.392966985702515s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.9262869358062744s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.020258188247680664s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 7.724761962890625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 12.624707221984863s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1049.1233394145966s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.14238381385803223s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0007262229919433594s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.2716033458709717s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020064592361450195s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.2901763916015625e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 9.829528331756592s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.4942913055419922s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0002944469451904297s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 18.485774517059326s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.232790470123291s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 44.86512470245361s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 40.18618607521057s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.22931122779846s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.25850820541381836s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.1662614345550537s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.5850543975830078s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.31087708473205566s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 2.115389585494995s
License | MR license check for Bio2RDF::Pharmgkb took 0.48860597610473633s
License | HR license check for Bio2RDF::Pharmgkb took 60.25056576728821s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.24996161460876465s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 10.415165662765503s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5886468887329102s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.24927306175231934s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.24461126327514648s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.24518299102783203s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.32782244682312s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 80.35456371307373s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.5696718692779541s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.33907127380371094s
Interlinking | skos check for Bio2RDF::Pharmgkb took 1.011047601699829s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.37407851219177246s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.2560150623321533s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5295734405517578s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5183179378509521s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 107.17040300369263s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 12.009878396987915s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.4413735866546631s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.2677929401397705s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.28789544105529785s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 6.918603181838989s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8778252601623535s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6518385410308838s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.4313218593597412s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 64.97182846069336s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.4216017723083496s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.662470102310181s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.3015601634979248s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.54623985290527s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7122564315795898s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.4585270881652832s
Security | Sign check for Bio2RDF::Pharmgkb took 0.25034523010253906s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 18.90129780769348s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.9069840908050537s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.020364761352539062s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 8.225440979003906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 12.458313465118408s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 1049.7694840431213s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.363059997558594e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.6971662044525146s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.020035266876220703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.4332275390625e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 4.605623722076416s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.00035953521728515625s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.25701284408569336s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.020834922790527344s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-pid took 3.2544796466827393s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 4.6253204345703125e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.27538561820983887s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.020277738571166992s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 2.809933662414551s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 1.2692060470581055s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0006096363067626953s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 18.456973791122437s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2244012355804443s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 43.67954182624817s
Interoperability | New terms check for Bio2RDF::Pubmed took 42.38125395774841s
Versatility | Languages check for Bio2RDF::Pubmed took 60.25457835197449s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.2663450241088867s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.14796710014343262s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.6399915218353271s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.3166532516479492s
Availability | RDF dump link check for Bio2RDF::Pubmed took 2.267812967300415s
License | MR license check for Bio2RDF::Pubmed took 0.4894895553588867s
License | HR license check for Bio2RDF::Pubmed took 60.26842951774597s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.26749706268310547s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.777878522872925s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5593945980072021s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.2455158233642578s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.2672243118286133s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.2591409683227539s
Performance | Throughput check for Bio2RDF::Pubmed took 10.600451946258545s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 74.430819272995s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.5744619369506836s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.36489248275756836s
Interlinking | skos check for Bio2RDF::Pubmed took 0.8616135120391846s
Interlinking | skos check for Bio2RDF::Pubmed took 0.3497042655944824s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2499372959136963s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5217978954315186s
Currency | Modification date check for Bio2RDF::Pubmed took 0.4998490810394287s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 107.62436556816101s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 12.645035743713379s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.4277489185333252s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.29284214973449707s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.2921264171600342s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 7.415859699249268s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8786499500274658s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6488540172576904s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.4152214527130127s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.04174780845642s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.4290688037872314s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.195331811904907s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.319516897201538s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.5519323348999s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.726726770401001s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.42794084548950195s
Security | Sign check for Bio2RDF::Pubmed took 0.24838876724243164s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 19.239047050476074s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 1.032304048538208s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.0001392364501953125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 12.931145668029785s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1042.2345740795135s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 4.267692565917969e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.2863953113555908s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.02014946937561035s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0006804466247558594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 6.961822509765625e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-reactome took 3.8266992568969727s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.26735448837280273s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.02030181884765625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.173683166503906e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-rhea took 3.789818525314331s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.1497640609741211s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.37697744369506836s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 8.249282836914062e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-sabiork took 12.454540491104126s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 1.3036127090454102s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0006477832794189453s
Extra | Recovery of all triples for Bio2RDF::Sgd took 18.77827215194702s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2481369972229004s
Amount of data | Number of triples check for Bio2RDF::Sgd took 44.20765924453735s
Interoperability | New terms check for Bio2RDF::Sgd took 40.695629358291626s
Versatility | Languages check for Bio2RDF::Sgd took 60.238789558410645s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.2796213626861572s
Security | Check HTTPS for Bio2RDF::Sgd took 0.15627026557922363s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.7483632564544678s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.3463616371154785s
Availability | RDF dump link check for Bio2RDF::Sgd took 2.469465732574463s
License | MR license check for Bio2RDF::Sgd took 0.5315465927124023s
License | HR license check for Bio2RDF::Sgd took 60.24929976463318s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.251162052154541s
Understandability | Number of label check for Bio2RDF::Sgd took 9.90070629119873s
Understandability | URI regex check for Bio2RDF::Sgd took 0.5616927146911621s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.25593066215515137s
Verifiability | Authors check for Bio2RDF::Sgd took 0.23410797119140625s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.245314359664917s
Performance | Throughput check for Bio2RDF::Sgd took 12.151575803756714s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 77.66457033157349s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.5493385791778564s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.3506484031677246s
Interlinking | skos check for Bio2RDF::Sgd took 0.6681547164916992s
Interlinking | skos check for Bio2RDF::Sgd took 0.3509409427642822s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2590181827545166s
Currency | Creation date check for Bio2RDF::Sgd took 0.501516580581665s
Currency | Modification date check for Bio2RDF::Sgd took 0.4836094379425049s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 106.61755466461182s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 12.803174495697021s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.4278564453125s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2768898010253906s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.26326656341552734s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.599128723144531s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.8828451633453369s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6999895572662354s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.34864282608032227s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 64.7183289527893s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.4199883937835693s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.19939661026001s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.301586389541626s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.57228398323059s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7187669277191162s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.40592145919799805s
Security | Sign check for Bio2RDF::Sgd took 0.27323389053344727s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 17.920732975006104s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.8646056652069092s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020290613174438477s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00011157989501953125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 13.457384824752808s
Believability | Calculation of trust value for Bio2RDF::Sgd took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-sgd took 1039.7759029865265s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 6.985664367675781e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.2583611011505127s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020273685455322266s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.647804260253906e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 4.8768322467803955s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.48165369033813477s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0006229877471923828s
Extra | Recovery of all triples for Bio2RDF::Sider took 18.30719017982483s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2457575798034668s
Amount of data | Number of triples check for Bio2RDF::Sider took 43.631235122680664s
Interoperability | New terms check for Bio2RDF::Sider took 41.04613471031189s
Versatility | Languages check for Bio2RDF::Sider took 60.22931241989136s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.27588915824890137s
Security | Check HTTPS for Bio2RDF::Sider took 0.1539440155029297s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.37113404273986816s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.2965857982635498s
Availability | RDF dump link check for Bio2RDF::Sider took 2.3486649990081787s
License | MR license check for Bio2RDF::Sider took 0.4807920455932617s
License | HR license check for Bio2RDF::Sider took 60.250373125076294s
Amount of data | Number of property check for Bio2RDF::Sider took 0.2618584632873535s
Understandability | Number of label check for Bio2RDF::Sider took 9.829526424407959s
Understandability | URI regex check for Bio2RDF::Sider took 0.5849487781524658s
Understandability | Vocabs check for Bio2RDF::Sider took 0.24288058280944824s
Verifiability | Authors check for Bio2RDF::Sider took 0.2650890350341797s
Verifiability | Publishers check for Bio2RDF::Sider took 0.2503838539123535s
Performance | Throughput check for Bio2RDF::Sider took 11.232010841369629s
Amount of data | Check the number of entities for Bio2RDF::Sider took 82.6794490814209s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.7363662719726562s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.3698275089263916s
Interlinking | skos check for Bio2RDF::Sider took 0.8052432537078857s
Interlinking | skos check for Bio2RDF::Sider took 0.34488582611083984s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.2539644241333008s
Currency | Creation date check for Bio2RDF::Sider took 0.5176053047180176s
Currency | Modification date check for Bio2RDF::Sider took 0.49144554138183594s
Rep.Conc. | URIs length for Bio2RDF::Sider took 107.69288539886475s
Interoperability | New vocabularies check for Bio2RDF::Sider took 12.229396104812622s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.41236090660095215s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.2753164768218994s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2714505195617676s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 6.315465211868286s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8810479640960693s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6448135375976562s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.37116575241088867s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 64.8799979686737s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.3785922527313232s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.659111738204956s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.2504560947418213s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.48744249343872s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.6977572441101074s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.4486842155456543s
Security | Sign check for Bio2RDF::Sider took 0.2582674026489258s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 19.971938133239746s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.9952678680419922s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.02183246612548828s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 3.838539123535156e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 12.889589548110962s
Believability | Calculation of trust value for Bio2RDF::Sider took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-sider took 1050.7185430526733s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 7.224082946777344e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.283510684967041s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.019948959350585938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-spike took 4.19989800453186s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.220008850097656e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.26770687103271484s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020982980728149414s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.553794860839844e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-taxon took 2.5531210899353027s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.4764885902404785s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.00051116943359375s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 18.091365337371826s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2350189685821533s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 43.60941767692566s
Interoperability | New terms check for Bio2RDF::Taxonomy took 40.64645218849182s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.23617768287659s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2735419273376465s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.15820002555847168s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.24323105812072754s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.3290271759033203s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 2.419419288635254s
License | MR license check for Bio2RDF::Taxonomy took 0.533715009689331s
License | HR license check for Bio2RDF::Taxonomy took 60.24955701828003s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.2633974552154541s
Understandability | Number of label check for Bio2RDF::Taxonomy took 10.348358154296875s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.6094167232513428s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.266416072845459s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.26517486572265625s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.27892518043518066s
Performance | Throughput check for Bio2RDF::Taxonomy took 10.765456199645996s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 79.55881857872009s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.5627660751342773s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.37428832054138184s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.767275333404541s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.37520933151245117s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.26070356369018555s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5181467533111572s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5029404163360596s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 108.17250347137451s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 11.8065345287323s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4242899417877197s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.2866358757019043s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.27598071098327637s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 7.046373128890991s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8813691139221191s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6797060966491699s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.5172057151794434s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 64.88114476203918s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.459012269973755s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.629128456115723s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.3200483322143555s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.50406861305237s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7029221057891846s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.43686866760253906s
Security | Sign check for Bio2RDF::Taxonomy took 0.26285696029663086s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 18.470086336135864s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 1.3531506061553955s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010776519775390625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 13.607439041137695s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 1049.2137670516968s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.956322193145752s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.3054392337799072s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.021152257919311523s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 18.23923921585083s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.49043774604797363s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0006146430969238281s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 18.59098982810974s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.2324573993682861s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 43.67191195487976s
Interoperability | New terms check for Bio2RDF::Wormbase took 39.98942565917969s
Versatility | Languages check for Bio2RDF::Wormbase took 60.252015352249146s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.287858247756958s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.15499067306518555s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.7446038722991943s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.3198678493499756s
Availability | RDF dump link check for Bio2RDF::Wormbase took 2.3237144947052s
License | MR license check for Bio2RDF::Wormbase took 0.6064276695251465s
License | HR license check for Bio2RDF::Wormbase took 60.24069857597351s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.2711622714996338s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.338071584701538s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.6220064163208008s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.2630448341369629s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.2665445804595947s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.2631263732910156s
Performance | Throughput check for Bio2RDF::Wormbase took 10.764960289001465s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 82.15820074081421s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 1.057898759841919s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.26768016815185547s
Interlinking | skos check for Bio2RDF::Wormbase took 1.0133392810821533s
Interlinking | skos check for Bio2RDF::Wormbase took 0.33194541931152344s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.25726938247680664s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5219767093658447s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5033767223358154s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 107.64728546142578s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 14.812904119491577s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.40265583992004395s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.24416661262512207s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.2765054702758789s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 6.763978719711304s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8801887035369873s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6558921337127686s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.47158288955688477s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 64.90495610237122s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.3986728191375732s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.173541307449341s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.2681622505187988s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.52209997177124s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7032999992370605s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.4379723072052002s
Security | Sign check for Bio2RDF::Wormbase took 0.2667276859283447s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 19.469576120376587s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 1.005997896194458s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020251750946044922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 12.630040168762207s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-wormbase took 1050.8378863334656s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 4.4345855712890625e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.0007641315460205078s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.2704002857208252s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.02005767822265625s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.3828277587890625e-05s
Believability | Calculation of trust value for Biografías y Vidas took 7.152557373046875e-06s
INFO | --- Analysis for biografiasyvidas took 4.537888765335083s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.6034469604492188s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.23957324028015137s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020414113998413086s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007214546203613281s
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 5.0067901611328125e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.3849825859069824s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.25604844093322754s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.020636320114135742s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 3.62396240234375e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for biolit took 2.8663182258605957s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 4.1961669921875e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.277907133102417s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020688772201538086s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.076957702636719e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 7.62939453125e-06s
INFO | --- Analysis for biolod-pdb took 7.266740798950195s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.6285383701324463s
Availability | VoID file availability check for BioModels RDF took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.25438356399536133s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 4.124641418457031e-05s
Believability | Calculation of trust value for BioModels RDF took 7.867813110351562e-06s
INFO | --- Analysis for biomodels-rdf took 4.071129083633423s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.205379009246826s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007116794586181641s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2609751224517822s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020341157913208008s
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.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.3855438232421875e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 8.106231689453125e-06s
INFO | --- Analysis for Biop took 6.127884864807129s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 5.221366882324219e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.26573777198791504s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02067089080810547s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.933906555175781e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 7.867813110351562e-06s
INFO | --- Analysis for Bioportal took 2.4951541423797607s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.38690185546875e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.2746548652648926s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.0205385684967041s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006051063537597656s
Believability | Calculation of trust value for Amphibian gross anatomy took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-aao took 4.512115716934204s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.291534423828125e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.2604224681854248s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0002911090850830078s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-aba took 4.141628980636597s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2814443111419678s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015475749969482422s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-acgt took 4.189481258392334s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.3392181396484375e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0007493495941162109s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.267716646194458s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020409584045410156s
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.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.00035881996154785156s
Believability | Calculation of trust value for Animal natural history and life history took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-adw took 3.7780089378356934s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0004048347473144531s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.2856273651123047s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.0205230712890625s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.00046896934509277344s
Believability | Calculation of trust value for Anatomical Entity Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-aeo took 4.3979926109313965s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0007240772247314453s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.2640962600708008s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.02138662338256836s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0009486675262451172s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0011911392211914062s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-aero took 3.867669105529785s
Availability | SPARQL endpoint availability check for AI/RHEUM took 5.0067901611328125e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.2588951587677002s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.02022528648376465s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004010200500488281s
Believability | Calculation of trust value for AI/RHEUM took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-air took 4.0773608684539795s
Availability | SPARQL endpoint availability check for Amino Acid took 4.1961669921875e-05s
Availability | VoID file availability check for Amino Acid took 0.0007486343383789062s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.25469326972961426s
Reputation | Calculation of the PageRank for Amino Acid took 0.020388364791870117s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00025534629821777344s
Believability | Calculation of trust value for Amino Acid took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-amino-acid took 4.280835390090942s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.25602054595947266s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020186662673950195s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.00028228759765625s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-apo took 4.045621156692505s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.410743713378906e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.00036716461181640625s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.2804102897644043s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020290613174438477s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00025272369384765625s
Believability | Calculation of trust value for African Traditional Medicine took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-atmo took 4.250404357910156s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.315376281738281e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.2455458641052246s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020268678665161133s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.369850158691406e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ato took 4.144599437713623s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 5.602836608886719e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.2680232524871826s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020427703857421875s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0008957386016845703s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0014603137969970703s
Believability | Calculation of trust value for BioAssay Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bao took 4.0141921043396s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.410743713378906e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.26053929328918457s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020133495330810547s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003707408905029297s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 3.985384941101074s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.26553964614868164s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.020587921142578125s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003323554992675781s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bcgo took 4.027524709701538s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0007336139678955078s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.29453539848327637s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.02022266387939453s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014123916625976562s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bdo took 3.932657480239868s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.24072813987731934s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020414113998413086s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005080699920654297s
Believability | Calculation of trust value for Basic Formal Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bfo took 4.181803464889526s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.363059997558594e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0007984638214111328s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.27953195571899414s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020306825637817383s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007081031799316406s
Believability | Calculation of trust value for Bleeding History Phenotype took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bho took 4.2317962646484375s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.38690185546875e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.269789457321167s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020536422729492188s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004470348358154297s
Believability | Calculation of trust value for Bilateria anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bila took 4.129011392593384s
Availability | SPARQL endpoint availability check for BIRNLex took 4.291534423828125e-05s
Availability | VoID file availability check for BIRNLex took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.25984835624694824s
Reputation | Calculation of the PageRank for BIRNLex took 0.02089667320251465s
Interlinking | Calculation of Degree of Connection for BIRNLex took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0015223026275634766s
Believability | Calculation of trust value for BIRNLex took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-birnlex took 4.115295648574829s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0007226467132568359s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.24934625625610352s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007581710815429688s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bootstrep took 4.031541347503662s
Availability | SPARQL endpoint availability check for BioPAX took 4.172325134277344e-05s
Availability | VoID file availability check for BioPAX took 0.0008218288421630859s
Completeness | Calculation of interlinking completeness for BioPAX took 0.25627565383911133s
Reputation | Calculation of the PageRank for BioPAX took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.846687316894531e-05s
Believability | Calculation of trust value for BioPAX took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bp took 4.160221576690674s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 5.745887756347656e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.2583603858947754s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.02032327651977539s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003368854522705078s
Believability | Calculation of trust value for Biomedical Resource Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bro_x1 took 4.092617988586426s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.26796913146972656s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.02083110809326172s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.0002148151397705078s
Believability | Calculation of trust value for Spatial Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-bspo took 4.082102298736572s
Availability | SPARQL endpoint availability check for BioTop took 4.6253204345703125e-05s
Availability | VoID file availability check for BioTop took 0.0007905960083007812s
Completeness | Calculation of interlinking completeness for BioTop took 0.27237534523010254s
Reputation | Calculation of the PageRank for BioTop took 0.02091240882873535s
Interlinking | Calculation of Degree of Connection for BioTop took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006973743438720703s
Believability | Calculation of trust value for BioTop took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bt took 4.406623601913452s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.38690185546875e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.27598047256469727s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008802413940429688s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bto took 3.9329211711883545s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 8.320808410644531e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0007739067077636719s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3023707866668701s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018558502197265625s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-canco took 4.390732526779175s
Availability | SPARQL endpoint availability check for CAO took 4.315376281738281e-05s
Availability | VoID file availability check for CAO took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for CAO took 0.27112817764282227s
Reputation | Calculation of the PageRank for CAO took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for CAO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0005948543548583984s
Believability | Calculation of trust value for CAO took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cao took 3.8665850162506104s
Availability | SPARQL endpoint availability check for CareLex took 4.5299530029296875e-05s
Availability | VoID file availability check for CareLex took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for CareLex took 0.25539660453796387s
Reputation | Calculation of the PageRank for CareLex took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for CareLex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.507469177246094e-05s
Believability | Calculation of trust value for CareLex took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-carelex took 3.9367101192474365s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.27117466926574707s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020606279373168945s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007793903350830078s
Believability | Calculation of trust value for Cell Cycle Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cco took 3.8798084259033203s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.2734413146972656s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00024628639221191406s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-cdao took 4.02227258682251s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.3392181396484375e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2742171287536621s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.02027750015258789s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007760524749755859s
Believability | Calculation of trust value for Chemical entities of biological interest took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-chebi took 3.9884755611419678s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.4345855712890625e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0006346702575683594s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.26229262351989746s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020776033401489258s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.00026798248291015625s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 4.257559537887573s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.26749682426452637s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.02014017105102539s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007491111755371094s
Believability | Calculation of trust value for Chemical Information Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-cheminf took 3.8521323204040527s
Availability | SPARQL endpoint availability check for Cell type took 4.458427429199219e-05s
Availability | VoID file availability check for Cell type took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for Cell type took 0.2783811092376709s
Reputation | Calculation of the PageRank for Cell type took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for Cell type took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.00037026405334472656s
Believability | Calculation of trust value for Cell type took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cl took 4.248456716537476s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.2685384750366211s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020099639892578125s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008118152618408203s
Believability | Calculation of trust value for Cell Line Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-clo took 4.191529035568237s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 5.1021575927734375e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.2436363697052002s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00016927719116210938s
Believability | Calculation of trust value for Clinical Measurement Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-cmo took 3.9731459617614746s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0007443428039550781s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.25398731231689453s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00020432472229003906s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cno took 3.868370771408081s
Availability | SPARQL endpoint availability check for Wheat trait took 4.291534423828125e-05s
Availability | VoID file availability check for Wheat trait took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.2732541561126709s
Reputation | Calculation of the PageRank for Wheat trait took 0.021666526794433594s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.9604644775390625e-05s
Believability | Calculation of trust value for Wheat trait took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-co_wheat took 4.349795341491699s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.673004150390625e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.25713276863098145s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.00033974647521972656s
Believability | Calculation of trust value for Cognitive Atlas took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cogat took 3.9849867820739746s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.25577616691589355s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007350444793701172s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-cogpo took 3.8803627490997314s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 8.797645568847656e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0007300376892089844s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.2558176517486572s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.02047586441040039s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004088878631591797s
Believability | Calculation of trust value for Current Procedural Terminology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-cpt took 4.218518018722534s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.553794860839844e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0007538795471191406s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.30501747131347656s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017621517181396484s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-csp took 4.383625507354736s
Availability | SPARQL endpoint availability check for COSTART took 4.363059997558594e-05s
Availability | VoID file availability check for COSTART took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for COSTART took 0.2702014446258545s
Reputation | Calculation of the PageRank for COSTART took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009868144989013672s
Believability | Calculation of trust value for COSTART took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cst took 4.258767366409302s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 5.173683166503906e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0007236003875732422s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.2507805824279785s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.02050328254699707s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005083084106445312s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ctcae took 4.3951096534729s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.291534423828125e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.2556626796722412s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.00042748451232910156s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ctx took 4.323261737823486s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.315376281738281e-05s
Availability | VoID file availability check for Dendritic cell took 0.0007381439208984375s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.27644824981689453s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00029277801513671875s
Believability | Calculation of trust value for Dendritic cell took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-dc_cl took 3.947619915008545s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.482269287109375e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.2592132091522217s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.869171142578125e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ddanat took 3.920283317565918s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 6.127357482910156e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.25518226623535156s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020739078521728516s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007109642028808594s
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 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ddi took 4.018012046813965s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 9.179115295410156e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.25414299964904785s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 9.417533874511719e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-diagnosticont took 3.944730520248413s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.2694685459136963s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020509004592895508s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00016546249389648438s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 4.172924280166626s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Human disease ontology took 0.0006921291351318359s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2683603763580322s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020282268524169922s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006053447723388672s
Believability | Calculation of trust value for Human disease ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-doid took 4.152532339096069s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.792213439941406e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.255298376083374s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.020909786224365234s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008525848388671875s
Believability | Calculation of trust value for Electrocardiography Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ecg took 3.996701240539551s
Availability | SPARQL endpoint availability check for Evidence codes took 4.291534423828125e-05s
Availability | VoID file availability check for Evidence codes took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2784132957458496s
Reputation | Calculation of the PageRank for Evidence codes took 0.02069091796875s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.3855438232421875e-05s
Believability | Calculation of trust value for Evidence codes took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-eco took 4.035162925720215s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3302769660949707s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.001737356185913086s
Believability | Calculation of trust value for Experimental Factor Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-efo took 4.276206970214844s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.3392181396484375e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0007026195526123047s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.2749614715576172s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.02062702178955078s
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.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011832714080810547s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ehda took 3.9585680961608887s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.2438507080078125e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.2417757511138916s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.02085280418395996s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007138252258300781s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ehdaa took 4.789832592010498s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.4345855712890625e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.26769185066223145s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020328998565673828s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005130767822265625s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 4.282627105712891s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.363059997558594e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.2709157466888428s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.1948089599609375e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-emap took 3.9577271938323975s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Environment Ontology took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.24504375457763672s
Reputation | Calculation of the PageRank for Environment Ontology took 0.020476102828979492s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00038743019104003906s
Believability | Calculation of trust value for Environment Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-envo took 4.078539609909058s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.291534423828125e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.2408890724182129s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020529508590698242s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00028896331787109375s
Believability | Calculation of trust value for Plant environmental conditions took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-eo took 3.871173143386841s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.26070356369018555s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0011911392211914062s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ep took 3.8999271392822266s
Availability | SPARQL endpoint availability check for Epilepsy took 4.291534423828125e-05s
Availability | VoID file availability check for Epilepsy took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.27747130393981934s
Reputation | Calculation of the PageRank for Epilepsy took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001347064971923828s
Believability | Calculation of trust value for Epilepsy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-epileponto took 4.092911720275879s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.410743713378906e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.2671346664428711s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020555734634399414s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011851787567138672s
Believability | Calculation of trust value for eagle-i research resource ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ero took 3.864593029022217s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.3392181396484375e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.2676825523376465s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020832061767578125s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011060237884521484s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ev took 3.8396875858306885s
Availability | SPARQL endpoint availability check for ExO took 4.363059997558594e-05s
Availability | VoID file availability check for ExO took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for ExO took 0.2673361301422119s
Reputation | Calculation of the PageRank for ExO took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for ExO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00024628639221191406s
Believability | Calculation of trust value for ExO took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-exo took 4.2219719886779785s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.291534423828125e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0007097721099853516s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.24560952186584473s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020374059677124023s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011181831359863281s
Believability | Calculation of trust value for Fungal gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fao took 4.065607070922852s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.8160552978515625e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.2942843437194824s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.0001914501190185547s
Believability | Calculation of trust value for Biological imaging methods took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-fbbi took 4.555781841278076s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 9.179115295410156e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.2470691204071045s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020616769790649414s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006265640258789062s
Believability | Calculation of trust value for Drosophila gross anatomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-fbbt took 4.290155649185181s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.3392181396484375e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.2724595069885254s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02046370506286621s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004181861877441406s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fbcv took 4.1855549812316895s
Availability | SPARQL endpoint availability check for Drosophila development took 4.1961669921875e-05s
Availability | VoID file availability check for Drosophila development took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2911112308502197s
Reputation | Calculation of the PageRank for Drosophila development took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.6253204345703125e-05s
Believability | Calculation of trust value for Drosophila development took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fbdv took 4.359206199645996s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.267692565917969e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.2933375835418701s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003871917724609375s
Believability | Calculation of trust value for Fly taxonomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-fbsp took 3.9518115520477295s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.291534423828125e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.2515904903411865s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020508766174316406s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.0002200603485107422s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 4.012812614440918s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.2689957618713379s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.00039315223693847656s
Believability | Calculation of trust value for Family Health History Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fhho took 4.082238674163818s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.29352331161499023s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010409355163574219s
Believability | Calculation of trust value for Influenza Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-flu took 4.159731149673462s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 5.8650970458984375e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.2511758804321289s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.0202789306640625s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.389617919921875e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fma took 3.9093713760375977s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.2553098201751709s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020746469497680664s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.0001342296600341797s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fypo took 3.9827418327331543s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.28172826766967773s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.02051401138305664s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 8.893013000488281e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-geospecies took 3.9996917247772217s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.2599625587463379s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016379356384277344s
Believability | Calculation of trust value for General Formal Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gfo took 3.9824373722076416s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.410743713378906e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.2534811496734619s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006067752838134766s
Believability | Calculation of trust value for General Formal Ontology: Biology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gfo-bio took 4.053890228271484s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.315376281738281e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0008068084716796875s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.2808101177215576s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008630752563476562s
Believability | Calculation of trust value for Gene Ontology Extension took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-go_x1 took 4.062413454055786s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Gene Ontology took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.25871777534484863s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020946025848388672s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008504390716552734s
Believability | Calculation of trust value for Gene Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-go_x2 took 3.889800786972046s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.363059997558594e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0006103515625s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.2698178291320801s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.020464181900024414s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.1948089599609375e-05s
Believability | Calculation of trust value for Cereal Plant Development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-gro took 3.924374580383301s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 5.030632019042969e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.269639253616333s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020163536071777344s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.00042366981506347656s
Believability | Calculation of trust value for Cereal plant gross anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-gro_x1 took 3.975048065185547s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2411961555480957s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007476806640625s
Believability | Calculation of trust value for Gene Regulation Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-gro_x2 took 4.027503252029419s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0007364749908447266s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2608487606048584s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005428791046142578s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hao took 3.935269594192505s
Availability | SPARQL endpoint availability check for HCPCS took 4.3392181396484375e-05s
Availability | VoID file availability check for HCPCS took 0.0007498264312744141s
Completeness | Calculation of interlinking completeness for HCPCS took 0.24371027946472168s
Reputation | Calculation of the PageRank for HCPCS took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0010149478912353516s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002956390380859375s
Believability | Calculation of trust value for HCPCS took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-hcpcs took 4.051793098449707s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.482269287109375e-05s
Availability | VoID file availability check for Health Level Seven took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.2525668144226074s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020548105239868164s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.001348733901977539s
Believability | Calculation of trust value for Health Level Seven took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-hl7 took 4.04539942741394s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.315376281738281e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.26825404167175293s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020215511322021484s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00034308433532714844s
Believability | Calculation of trust value for HEALTH_INDICATORS took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-hlth_indics took 4.132314920425415s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 5.53131103515625e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0007543563842773438s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.260622501373291s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.218650817871094e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hom took 3.9755027294158936s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.267692565917969e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0008323192596435547s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.25793933868408203s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.695487976074219e-05s
Believability | Calculation of trust value for HOM-HARVARD took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hom_harvard took 4.089554786682129s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.2703588008880615s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020514726638793945s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006201267242431641s
Believability | Calculation of trust value for Human Phenotype Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hp_x1 took 4.023883581161499s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0007770061492919922s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.2595174312591553s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020834922790527344s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.001051187515258789s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-hpio took 3.803941488265991s
Availability | SPARQL endpoint availability check for HUGO took 4.3392181396484375e-05s
Availability | VoID file availability check for HUGO took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for HUGO took 0.2627708911895752s
Reputation | Calculation of the PageRank for HUGO took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for HUGO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.82012939453125e-05s
Believability | Calculation of trust value for HUGO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hugo took 3.949842691421509s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0007627010345458984s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.27957820892333984s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006620883941650391s
Believability | Calculation of trust value for Information Artifact Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-iao took 4.474717617034912s
Availability | SPARQL endpoint availability check for ICD10 took 4.315376281738281e-05s
Availability | VoID file availability check for ICD10 took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for ICD10 took 0.2836153507232666s
Reputation | Calculation of the PageRank for ICD10 took 0.020136356353759766s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0007929801940917969s
Believability | Calculation of trust value for ICD10 took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icd10 took 3.984192371368408s
Availability | SPARQL endpoint availability check for ICD10CM took 8.726119995117188e-05s
Availability | VoID file availability check for ICD10CM took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.2518284320831299s
Reputation | Calculation of the PageRank for ICD10CM took 0.02024102210998535s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006020069122314453s
Believability | Calculation of trust value for ICD10CM took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-icd10cm took 3.8754777908325195s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.4345855712890625e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.26691579818725586s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020688533782958984s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00014710426330566406s
Believability | Calculation of trust value for ICD-10-PCS took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icd10pcs took 4.732142686843872s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.220008850097656e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.2588536739349365s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020344257354736328s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006349086761474609s
Believability | Calculation of trust value for International Classification of Diseases took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icd9cm took 3.918565273284912s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.3392181396484375e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0009131431579589844s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.26628565788269043s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020365476608276367s
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.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004489421844482422s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icf_x1 took 4.048085927963257s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.291534423828125e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.2578713893890381s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.020297765731811523s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012195110321044922s
Believability | Calculation of trust value for International Classification for Nursing Practice took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icnp took 3.9703891277313232s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 7.843971252441406e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.26665258407592773s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020198345184326172s
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.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004565715789794922s
Believability | Calculation of trust value for International Classification of Primary Care took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icpc took 4.3870790004730225s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.291534423828125e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2572312355041504s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.02027273178100586s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008854866027832031s
Believability | Calculation of trust value for ICPC-2 PLUS took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icpc2p took 3.838135004043579s
Availability | SPARQL endpoint availability check for ICPS Network took 4.124641418457031e-05s
Availability | VoID file availability check for ICPS Network took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.25995850563049316s
Reputation | Calculation of the PageRank for ICPS Network took 0.020070552825927734s
Interlinking | Calculation of Degree of Connection for ICPS Network took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00022602081298828125s
Believability | Calculation of trust value for ICPS Network took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icps took 4.183413743972778s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.2386629581451416s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008971691131591797s
Believability | Calculation of trust value for Infectious Disease Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ido took 3.9399452209472656s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2816810607910156s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.02019667625427246s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011425018310546875s
Believability | Calculation of trust value for Brucellosis Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-idobru took 3.8956165313720703s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0007791519165039062s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.25068211555480957s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013544559478759766s
Believability | Calculation of trust value for Malaria Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-idomal took 3.9690608978271484s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.38690185546875e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.26066017150878906s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020359039306640625s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003161430358886719s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-iev took 4.090558290481567s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.291534423828125e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.25797176361083984s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00015926361083984375s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-imgt took 3.935375452041626s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.315376281738281e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.26769518852233887s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020504474639892578s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005481243133544922s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-imr took 4.056726455688477s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.25925350189208984s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.021220684051513672s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007872581481933594s
Believability | Calculation of trust value for Interaction Network Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ino took 4.084521055221558s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.38690185546875e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0007166862487792969s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2563056945800781s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 2.8371810913085938e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-invertebrata took 3.9518518447875977s
Availability | SPARQL endpoint availability check for IxnO took 4.3392181396484375e-05s
Availability | VoID file availability check for IxnO took 0.0003764629364013672s
Completeness | Calculation of interlinking completeness for IxnO took 0.3026254177093506s
Reputation | Calculation of the PageRank for IxnO took 0.0203244686126709s
Interlinking | Calculation of Degree of Connection for IxnO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00019121170043945312s
Believability | Calculation of trust value for IxnO took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ixno took 4.542001485824585s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.291534423828125e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0016727447509765625s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.24219441413879395s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.02014017105102539s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0003819465637207031s
Believability | Calculation of trust value for SysMO-JERM took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-jerm took 3.940457820892334s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.27335691452026367s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-kisao took 3.7774078845977783s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.38690185546875e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.26004672050476074s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.02052927017211914s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00020885467529296875s
Believability | Calculation of trust value for Loggerhead nesting took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-lhn took 4.091315746307373s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0007140636444091797s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.27049756050109863s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.0205991268157959s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00021004676818847656s
Believability | Calculation of trust value for Lipid Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-lipro took 3.807358980178833s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.2438507080078125e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.30171895027160645s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.02086472511291504s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018548965454101562s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-lnc took 4.295899152755737s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.601478576660156e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2679283618927002s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0008375644683837891s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0007297992706298828s
Believability | Calculation of trust value for Mouse adult gross anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ma took 3.9338624477386475s
Availability | SPARQL endpoint availability check for Multiple alignment took 6.008148193359375e-05s
Availability | VoID file availability check for Multiple alignment took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.2496960163116455s
Reputation | Calculation of the PageRank for Multiple alignment took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00021910667419433594s
Believability | Calculation of trust value for Multiple alignment took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mao took 3.713473081588745s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.38690185546875e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0007350444793701172s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.26198434829711914s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020318269729614258s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007023811340332031s
Believability | Calculation of trust value for Minimal anatomical terminology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mat took 3.847020387649536s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.458427429199219e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.2410283088684082s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.0203707218170166s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004165172576904297s
Believability | Calculation of trust value for Breast tissue cell lines took 1.4543533325195312e-05s
INFO | --- Analysis for bioportal-mcbcc took 3.8783626556396484s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Cell line ontology took 0.0007371902465820312s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.24830365180969238s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.000751495361328125s
Believability | Calculation of trust value for Cell line ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mccl took 3.850442409515381s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Cell line ontology took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2676355838775635s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020749330520629883s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014536380767822266s
Believability | Calculation of trust value for Cell line ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 4.038738965988159s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.57763671875e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.2660551071166992s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.02029895782470703s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002338886260986328s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mcv took 4.174386978149414s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.410743713378906e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.23723673820495605s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.021535396575927734s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0010006427764892578s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.0002200603485107422s
Believability | Calculation of trust value for Master Drug Data Base took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mddb took 4.217946290969849s
Availability | SPARQL endpoint availability check for MedDRA took 4.38690185546875e-05s
Availability | VoID file availability check for MedDRA took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for MedDRA took 0.26758575439453125s
Reputation | Calculation of the PageRank for MedDRA took 0.020212173461914062s
Interlinking | Calculation of Degree of Connection for MedDRA took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011436939239501953s
Believability | Calculation of trust value for MedDRA took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mdr took 3.9970362186431885s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 8.749961853027344e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.2555992603302002s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02020740509033203s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.000885009765625s
Believability | Calculation of trust value for MedlinePlus Health Topics took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-medlineplus took 4.007723569869995s
Availability | SPARQL endpoint availability check for MeGO took 4.3392181396484375e-05s
Availability | VoID file availability check for MeGO took 0.0004131793975830078s
Completeness | Calculation of interlinking completeness for MeGO took 0.2584216594696045s
Reputation | Calculation of the PageRank for MeGO took 0.020353078842163086s
Interlinking | Calculation of Degree of Connection for MeGO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00015115737915039062s
Believability | Calculation of trust value for MeGO took 3.170967102050781e-05s
INFO | --- Analysis for bioportal-mego took 3.9769270420074463s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 6.866455078125e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.32074904441833496s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020207881927490234s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0017936229705810547s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mesh-owl took 4.573750972747803s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0006914138793945312s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.26604175567626953s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020360469818115234s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006406307220458984s
Believability | Calculation of trust value for Mental Functioning Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mf took 3.9463424682617188s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.315376281738281e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0006985664367675781s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.2693610191345215s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.02028179168701172s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005481243133544922s
Believability | Calculation of trust value for Medaka fish anatomy and development took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mfo took 4.225327968597412s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.29291415214538574s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0009067058563232422s
Believability | Calculation of trust value for Emotion Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mfoem took 4.322136640548706s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0007395744323730469s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.243513822555542s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.022391319274902344s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.0001327991485595703s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-mhc took 3.877842426300049s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.220008850097656e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0007112026214599609s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.2672722339630127s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006656646728515625s
Believability | Calculation of trust value for Protein-protein interaction took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mi took 4.104053020477295s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.3392181396484375e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0007674694061279297s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2657310962677002s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020534992218017578s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007474422454833984s
Believability | Calculation of trust value for Mosquito insecticide resistance took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-miro took 4.002225160598755s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.2482151985168457s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020389795303344727s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001366138458251953s
Believability | Calculation of trust value for Measurement Method Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mmo took 4.046910285949707s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for MGED Ontology took 0.0006799697875976562s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.28119468688964844s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020577430725097656s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003819465637207031s
Believability | Calculation of trust value for MGED Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mo took 4.000621318817139s
Availability | SPARQL endpoint availability check for Protein modification took 4.172325134277344e-05s
Availability | VoID file availability check for Protein modification took 0.0007526874542236328s
Completeness | Calculation of interlinking completeness for Protein modification took 0.23775005340576172s
Reputation | Calculation of the PageRank for Protein modification took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002193450927734375s
Believability | Calculation of trust value for Protein modification took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mod took 4.196125745773315s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.267692565917969e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0007383823394775391s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.337263822555542s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020196914672851562s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006878376007080078s
Believability | Calculation of trust value for Mammalian phenotype took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mp took 4.4320292472839355s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.315376281738281e-05s
Availability | VoID file availability check for Mouse pathology took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.2690908908843994s
Reputation | Calculation of the PageRank for Mouse pathology took 0.020377159118652344s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.00046634674072265625s
Believability | Calculation of trust value for Mouse pathology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mpath took 3.8256914615631104s
Availability | SPARQL endpoint availability check for Mass spectrometry took 5.7220458984375e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.2552816867828369s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020508766174316406s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.000354766845703125s
Believability | Calculation of trust value for Mass spectrometry took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ms took 4.267130374908447s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 7.891654968261719e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.31531739234924316s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020279407501220703s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018453598022460938s
Believability | Calculation of trust value for Medical Subject Headings took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-msh took 5.13742470741272s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.482269287109375e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.27062153816223145s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020618915557861328s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00017452239990234375s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mthch took 4.342238187789917s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0007255077362060547s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.2455289363861084s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020583152770996094s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007877349853515625s
Believability | Calculation of trust value for Natural Products Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-natpro took 3.921457529067993s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 6.818771362304688e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2457571029663086s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020122528076171875s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008223056793212891s
Believability | Calculation of trust value for NCBI organismal classification took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 4.345584392547607s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 5.602836608886719e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0007448196411132812s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.29714274406433105s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.021548032760620117s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0009937286376953125s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0022814273834228516s
Believability | Calculation of trust value for NCI Thesaurus took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ncit took 4.711559057235718s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.2438507080078125e-05s
Availability | VoID file availability check for National Drug Data File took 0.000797271728515625s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.26767635345458984s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02091693878173828s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006475448608398438s
Believability | Calculation of trust value for National Drug Data File took 1.5497207641601562e-05s
INFO | --- Analysis for bioportal-nddf took 3.9814953804016113s
Availability | SPARQL endpoint availability check for National Drug File took 4.410743713378906e-05s
Availability | VoID file availability check for National Drug File took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for National Drug File took 0.26633358001708984s
Reputation | Calculation of the PageRank for National Drug File took 0.0203707218170166s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012292861938476562s
Believability | Calculation of trust value for National Drug File took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ndfrt took 3.8752317428588867s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.267692565917969e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.24910712242126465s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.020299196243286133s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011780261993408203s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 4.036097288131714s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.28693199157714844s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020232439041137695s
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.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006766319274902344s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-neomark took 3.993880271911621s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.3392181396484375e-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.24876928329467773s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020421266555786133s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00012493133544921875s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-neomarkontology took 3.887403726577759s
Availability | SPARQL endpoint availability check for NIFSTD took 4.2438507080078125e-05s
Availability | VoID file availability check for NIFSTD took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.3300032615661621s
Reputation | Calculation of the PageRank for NIFSTD took 0.02046656608581543s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0019183158874511719s
Believability | Calculation of trust value for NIFSTD took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nif took 4.3296613693237305s
Availability | SPARQL endpoint availability check for NIF Cell took 4.291534423828125e-05s
Availability | VoID file availability check for NIF Cell took 0.00035071372985839844s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.2715787887573242s
Reputation | Calculation of the PageRank for NIF Cell took 0.02045416831970215s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013947486877441406s
Believability | Calculation of trust value for NIF Cell took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nif_cell took 3.886334180831909s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 9.894371032714844e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0013043880462646484s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.25211620330810547s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0013806819915771484s
Believability | Calculation of trust value for NIF Dysfunction took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 4.182284832000732s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.24054551124572754s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005476474761962891s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 1.71661376953125e-05s
INFO | --- Analysis for bioportal-nigo took 4.144871473312378s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.267692565917969e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.24920916557312012s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.02045726776123047s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005483627319335938s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-nmr took 3.916165828704834s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.2699434757232666s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.020226716995239258s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00010967254638671875s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nonrctontology took 4.004891395568848s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.24794578552246094s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011658668518066406s
Believability | Calculation of trust value for NanoParticle Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-npo took 4.255547046661377s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.26615142822265625s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020342111587524414s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007216930389404297s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-oae took 4.162232875823975s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.673004150390625e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.2473440170288086s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.020518779754638672s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014617443084716797s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-obi took 4.235771417617798s
Availability | SPARQL endpoint availability check for OBOE took 4.8160552978515625e-05s
Availability | VoID file availability check for OBOE took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for OBOE took 0.2762751579284668s
Reputation | Calculation of the PageRank for OBOE took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for OBOE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00010991096496582031s
Believability | Calculation of trust value for OBOE took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-oboe took 4.110896110534668s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.220008850097656e-05s
Availability | VoID file availability check for OBOE SBC took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.2813606262207031s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020528554916381836s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007662773132324219s
Believability | Calculation of trust value for OBOE SBC took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 4.007385492324829s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.410743713378906e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0007569789886474609s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.24752569198608398s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.021960735321044922s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 4.649162292480469e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0007221698760986328s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ocre took 4.0244855880737305s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 5.6743621826171875e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.29136180877685547s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008289813995361328s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-odgi took 4.0964484214782715s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2658069133758545s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008671283721923828s
Believability | Calculation of trust value for Ontology for Genetic Interval took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ogi took 4.153501510620117s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 5.793571472167969e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.250241756439209s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020343780517578125s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0002818107604980469s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ogmd took 4.3755412101745605s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.5299530029296875e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0007581710815429688s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.2645270824432373s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.02054882049560547s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006709098815917969s
Believability | Calculation of trust value for Ontology for General Medical Science took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ogms took 4.139702320098877s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.172325134277344e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0007433891296386719s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.2697279453277588s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011608600616455078s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-omim took 4.276524305343628s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.482269287109375e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.26952481269836426s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020481109619140625s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003790855407714844s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-omit took 4.080885171890259s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.363059997558594e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.26811838150024414s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006058216094970703s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-omrse took 2.3182532787323s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.5299530029296875e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.2408599853515625s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020367145538330078s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007772445678710938s
Believability | Calculation of trust value for Ontology of Data Mining took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ontodm took 4.019574880599976s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.506111145019531e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.2395925521850586s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020360708236694336s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00024175643920898438s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ontodt took 4.096954584121704s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.267692565917969e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.2554283142089844s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020354270935058594s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0005857944488525391s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-ontoorpha took 4.306142330169678s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 8.344650268554688e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.25498461723327637s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009474754333496094s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-opl took 4.02792501449585s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.172325134277344e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.2695636749267578s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008845329284667969s
Believability | Calculation of trust value for Phenotypic quality took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-pato took 4.313356876373291s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.220008850097656e-05s
Availability | VoID file availability check for Physician Data Query took 0.0003600120544433594s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.27529358863830566s
Reputation | Calculation of the PageRank for Physician Data Query took 0.02026653289794922s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008037090301513672s
Believability | Calculation of trust value for Physician Data Query took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pdq took 4.0659520626068115s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.3392181396484375e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.2489640712738037s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020206928253173828s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007734298706054688s
Believability | Calculation of trust value for Pediatric Terminology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-pedterm took 4.01242470741272s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 5.054473876953125e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.27471065521240234s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020399808883666992s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00020170211791992188s
Believability | Calculation of trust value for Parasite Experiment Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-peo took 3.991670846939087s
Availability | SPARQL endpoint availability check for PHARE took 4.315376281738281e-05s
Availability | VoID file availability check for PHARE took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for PHARE took 0.29212474822998047s
Reputation | Calculation of the PageRank for PHARE took 0.021714448928833008s
Interlinking | Calculation of Degree of Connection for PHARE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006844997406005859s
Believability | Calculation of trust value for PHARE took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-phare took 4.130978584289551s
Availability | SPARQL endpoint availability check for PKO_Re took 4.9114227294921875e-05s
Availability | VoID file availability check for PKO_Re took 0.0007305145263671875s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.2549302577972412s
Reputation | Calculation of the PageRank for PKO_Re took 0.020148277282714844s
Interlinking | Calculation of Degree of Connection for PKO_Re took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00016450881958007812s
Believability | Calculation of trust value for PKO_Re took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pko took 4.151780128479004s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for PMA 2010 took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.27040696144104004s
Reputation | Calculation of the PageRank for PMA 2010 took 0.02026510238647461s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009114742279052734s
Believability | Calculation of trust value for PMA 2010 took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pma took 4.004542589187622s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.601478576660156e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0006730556488037109s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.2641880512237549s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020607471466064453s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00016832351684570312s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pmr took 3.909306049346924s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.363059997558594e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0007343292236328125s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.254849910736084s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.02064037322998047s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0003914833068847656s
Believability | Calculation of trust value for Plant Anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-po took 4.239565372467041s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 4.38690185546875e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2508118152618408s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020668506622314453s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 7.009506225585938e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-po_x1 took 3.9517574310302734s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Plant Ontology took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.2643089294433594s
Reputation | Calculation of the PageRank for Plant Ontology took 0.0207366943359375s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004661083221435547s
Believability | Calculation of trust value for Plant Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-po_x2 took 4.310492038726807s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 6.4849853515625e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.24908995628356934s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.0202639102935791s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.00064849853515625s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-pr took 3.9223172664642334s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.76837158203125e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0007810592651367188s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.24896740913391113s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00026702880859375s
Believability | Calculation of trust value for Proteomics data and process provenance took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-propreo took 3.8711001873016357s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Pathway ontology took 0.0004127025604248047s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.2488870620727539s
Reputation | Calculation of the PageRank for Pathway ontology took 0.02021622657775879s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012803077697753906s
Believability | Calculation of trust value for Pathway ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pw took 4.245097398757935s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.24155497550964355s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020606279373168945s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.409385681152344e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-qibo took 3.7829105854034424s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.482269287109375e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007789134979248047s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.31041526794433594s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020686626434326172s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017631053924560547s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rcd took 4.366010427474976s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0007569789886474609s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.26540637016296387s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.020499467849731445s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00012969970703125s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-rctontology took 4.265057325363159s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.2940852642059326s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020320892333984375s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.918212890625e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-repo took 3.946843147277832s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.1961669921875e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0007352828979492188s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.2459099292755127s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.0001919269561767578s
Believability | Calculation of trust value for Physico-chemical process took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-rex took 4.292199373245239s
Availability | SPARQL endpoint availability check for RadLex took 4.291534423828125e-05s
Availability | VoID file availability check for RadLex took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for RadLex took 0.2685863971710205s
Reputation | Calculation of the PageRank for RadLex took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for RadLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0014872550964355469s
Believability | Calculation of trust value for RadLex took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-rid took 3.991986036300659s
Availability | SPARQL endpoint availability check for RNA ontology took 4.458427429199219e-05s
Availability | VoID file availability check for RNA ontology took 0.0007920265197753906s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.23985695838928223s
Reputation | Calculation of the PageRank for RNA ontology took 0.020464181900024414s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0010271072387695312s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0006754398345947266s
Believability | Calculation of trust value for RNA ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-rnao took 3.813380479812622s
Availability | SPARQL endpoint availability check for Role Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Role Ontology took 0.0007932186126708984s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.24808716773986816s
Reputation | Calculation of the PageRank for Role Ontology took 0.020257234573364258s
Interlinking | Calculation of Degree of Connection for Role Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00018930435180664062s
Believability | Calculation of trust value for Role Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-roleo took 3.8645410537719727s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.25638437271118164s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.021452903747558594s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00018453598022460938s
Believability | Calculation of trust value for Rat Strain Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rs took 3.9306998252868652s
Availability | SPARQL endpoint availability check for RxNORM took 4.3392181396484375e-05s
Availability | VoID file availability check for RxNORM took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for RxNORM took 0.24619626998901367s
Reputation | Calculation of the PageRank for RxNORM took 0.020205259323120117s
Interlinking | Calculation of Degree of Connection for RxNORM took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RxNORM took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0005977153778076172s
Believability | Calculation of trust value for RxNORM took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rxnorm took 4.218490839004517s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.1961669921875e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.2684352397918701s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.020725488662719727s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0011119842529296875s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-sao took 3.8255889415740967s
Availability | SPARQL endpoint availability check for Systems Biology took 4.2438507080078125e-05s
Availability | VoID file availability check for Systems Biology took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.25034356117248535s
Reputation | Calculation of the PageRank for Systems Biology took 0.020145654678344727s
Interlinking | Calculation of Degree of Connection for Systems Biology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.000469207763671875s
Believability | Calculation of trust value for Systems Biology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sbo took 3.898895263671875s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.9591064453125e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.2678983211517334s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.020349979400634766s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.0001049041748046875s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sbro took 4.341058015823364s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.935264587402344e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.25365424156188965s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.001317739486694336s
Believability | Calculation of trust value for Sleep Domain Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sdo took 4.024624586105347s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 8.296966552734375e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0007183551788330078s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2626528739929199s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.021144628524780273s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0004410743713378906s
Believability | Calculation of trust value for Sample processing and separation techniques took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sep took 4.015122413635254s
Availability | SPARQL endpoint availability check for Student Health Record took 4.2438507080078125e-05s
Availability | VoID file availability check for Student Health Record took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.26674485206604004s
Reputation | Calculation of the PageRank for Student Health Record took 0.020640850067138672s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004703998565673828s
Believability | Calculation of trust value for Student Health Record took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-shr took 3.9312143325805664s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.2555708885192871s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020554780960083008s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.001322031021118164s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-sio took 4.688277006149292s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.3392181396484375e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.27805399894714355s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00020599365234375s
Believability | Calculation of trust value for Situation-Based Access Control took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sitbac took 3.8217005729675293s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.792213439941406e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.00037288665771484375s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3182997703552246s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020175933837890625s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.001897573471069336s
Believability | Calculation of trust value for SNOMED Clinical Terms took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-snomedct took 4.573010206222534s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.2560460567474365s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020170927047729492s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006785392761230469s
Believability | Calculation of trust value for SNP-Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-snpo took 4.593577861785889s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.5299530029296875e-05s
Availability | VoID file availability check for Sequence types and features took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.3235485553741455s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020050764083862305s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005900859832763672s
Believability | Calculation of trust value for Sequence types and features took 3.170967102050781e-05s
INFO | --- Analysis for bioportal-so_x1 took 4.375051975250244s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 4.2438507080078125e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0006837844848632812s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.31260013580322266s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.02733588218688965s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015583038330078125s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-sopharm took 4.593639612197876s
Availability | SPARQL endpoint availability check for SoyOntology took 4.2438507080078125e-05s
Availability | VoID file availability check for SoyOntology took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.24783849716186523s
Reputation | Calculation of the PageRank for SoyOntology took 0.020133495330810547s
Interlinking | Calculation of Degree of Connection for SoyOntology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00012350082397460938s
Believability | Calculation of trust value for SoyOntology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-soy took 4.270240783691406s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for Spider Ontology took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.2513549327850342s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020210742950439453s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00041675567626953125s
Believability | Calculation of trust value for Spider Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-spd took 3.986135721206665s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.25399303436279297s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0002727508544921875s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-spto took 3.9426982402801514s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.2492079734802246s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004563331604003906s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sso took 3.955223798751831s
Availability | SPARQL endpoint availability check for Software Ontology took 7.82012939453125e-05s
Availability | VoID file availability check for Software Ontology took 0.0007774829864501953s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.25769686698913574s
Reputation | Calculation of the PageRank for Software Ontology took 0.02053070068359375s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0004153251647949219s
Believability | Calculation of trust value for Software Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-swo took 3.943472385406494s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.267692565917969e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0007565021514892578s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.2670869827270508s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.02020406723022461s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002617835998535156s
Believability | Calculation of trust value for Tick gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-tads took 3.7832322120666504s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.28180789947509766s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008697509765625s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tao took 4.121434688568115s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.3392181396484375e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0007023811340332031s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.24782681465148926s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.726119995117188e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-taxrank took 4.185253858566284s
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.0008153915405273438s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.25707578659057617s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.915496826171875e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-teddy took 4.071969985961914s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0006773471832275391s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.26399755477905273s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.021182775497436523s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008313655853271484s
Believability | Calculation of trust value for Time Event Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-teo took 4.275091648101807s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.38690185546875e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.2663443088531494s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020178794860839844s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0004024505615234375s
Believability | Calculation of trust value for Mosquito gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-tgma took 4.242989778518677s
Availability | SPARQL endpoint availability check for thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for thesaurus took 0.0003266334533691406s
Completeness | Calculation of interlinking completeness for thesaurus took 0.2776799201965332s
Reputation | Calculation of the PageRank for thesaurus took 0.02042531967163086s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.67572021484375e-05s
Believability | Calculation of trust value for thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-thesaurus took 3.77020001411438s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.482269287109375e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0007762908935546875s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.2665989398956299s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020402908325195312s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003383159637451172s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 4.164255857467651s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.27265262603759766s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.021514177322387695s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008215904235839844s
Believability | Calculation of trust value for Translational Medicine Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-tmo took 4.082722187042236s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.2524087429046631s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.02042698860168457s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015926361083984375s
Believability | Calculation of trust value for Plant Trait Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-to took 3.9482462406158447s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.839897155761719e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0007612705230712891s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.26746654510498047s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.02011704444885254s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00018548965454101562s
Believability | Calculation of trust value for TOK_Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-tok took 4.467565536499023s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0007312297821044922s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.25465917587280273s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020209789276123047s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.0001933574676513672s
Believability | Calculation of trust value for Teleost taxonomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tto took 4.127847909927368s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 7.033348083496094e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.25312185287475586s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020396709442138672s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.001004934310913086s
Believability | Calculation of trust value for Uber anatomy ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-uberon took 4.0939319133758545s
Availability | SPARQL endpoint availability check for Units Ontology took 5.435943603515625e-05s
Availability | VoID file availability check for Units Ontology took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.2627902030944824s
Reputation | Calculation of the PageRank for Units Ontology took 0.020281314849853516s
Interlinking | Calculation of Degree of Connection for Units Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00021958351135253906s
Believability | Calculation of trust value for Units Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-unitsontology took 6.077542304992676s
Availability | SPARQL endpoint availability check for Units of measurement took 4.38690185546875e-05s
Availability | VoID file availability check for Units of measurement took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.2670888900756836s
Reputation | Calculation of the PageRank for Units of measurement took 0.020162582397460938s
Interlinking | Calculation of Degree of Connection for Units of measurement took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00028514862060546875s
Believability | Calculation of trust value for Units of measurement took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-uo took 4.2518603801727295s
Availability | SPARQL endpoint availability check for VANDF took 5.888938903808594e-05s
Availability | VoID file availability check for VANDF took 0.0007307529449462891s
Completeness | Calculation of interlinking completeness for VANDF took 0.2754995822906494s
Reputation | Calculation of the PageRank for VANDF took 0.020533084869384766s
Interlinking | Calculation of Degree of Connection for VANDF took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007174015045166016s
Believability | Calculation of trust value for VANDF took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vandf took 4.133308172225952s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.265242338180542s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020101308822631836s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004227161407470703s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-vao took 4.307992219924927s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.38690185546875e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.2585899829864502s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020288944244384766s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006291866302490234s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-vhog took 4.224262714385986s
Availability | SPARQL endpoint availability check for VIVO took 4.172325134277344e-05s
Availability | VoID file availability check for VIVO took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for VIVO took 0.26611757278442383s
Reputation | Calculation of the PageRank for VIVO took 0.02300715446472168s
Interlinking | Calculation of Degree of Connection for VIVO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for VIVO took 0.001001596450805664s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0004951953887939453s
Believability | Calculation of trust value for VIVO took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-vivo took 3.9978744983673096s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0007166862487792969s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.2665977478027344s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.02001023292541504s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012607574462890625s
Believability | Calculation of trust value for Vaccine Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-vo took 3.8961069583892822s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.839897155761719e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.2647402286529541s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020760059356689453s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020241737365722656s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vt took 4.021814584732056s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 7.748603820800781e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.2719151973724365s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020426511764526367s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005056858062744141s
Believability | Calculation of trust value for C. elegans gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-wbbt took 4.033646106719971s
Availability | SPARQL endpoint availability check for C. elegans development took 4.649162292480469e-05s
Availability | VoID file availability check for C. elegans development took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.2675807476043701s
Reputation | Calculation of the PageRank for C. elegans development took 0.020671367645263672s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.839897155761719e-05s
Believability | Calculation of trust value for C. elegans development took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-wbls took 4.112606048583984s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 9.012222290039062e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.2583913803100586s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.96453857421875e-05s
Believability | Calculation of trust value for C. elegans phenotype took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-wbphenotype took 4.246480703353882s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.315376281738281e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.2546541690826416s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020427703857421875s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005879402160644531s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-who took 3.9398610591888428s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.220008850097656e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0007112026214599609s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2692265510559082s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.02050328254699707s
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.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006916522979736328s
Believability | Calculation of trust value for Xenopus anatomy and development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-xao took 3.875136137008667s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.257706880569458s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.0203554630279541s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00023984909057617188s
Believability | Calculation of trust value for Experimental Conditions Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-xco took 3.945188522338867s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.291534423828125e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0007402896881103516s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.2456498146057129s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020145416259765625s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002562999725341797s
Believability | Calculation of trust value for Yeast phenotypes took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ypo took 4.044176816940308s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.172325134277344e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0007178783416748047s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.26235413551330566s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.02079486846923828s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.001039743423461914s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0010759830474853516s
Believability | Calculation of trust value for Zebrafish anatomy and development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-zfa took 4.004436016082764s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.315376281738281e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.26842379570007324s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.02036309242248535s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.86102294921875e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.1444091796875e-05s
INFO | --- Analysis for Bioportal_link took 3.5555405616760254s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.401625394821167s
Availability | VoID file availability check for BioSamples RDF took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.30316972732543945s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020173311233520508s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 4.029273986816406e-05s
Believability | Calculation of trust value for BioSamples RDF took 6.67572021484375e-06s
INFO | --- Analysis for biosamples-rdf took 3.4348762035369873s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.09289717674255371s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0003612041473388672s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.25865840911865234s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011515617370605469s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for bis-linked-data took 2.4624722003936768s
Availability | SPARQL endpoint availability check for Bitzi took 4.172325134277344e-05s
Availability | VoID file availability check for Bitzi took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for Bitzi took 0.25881385803222656s
Reputation | Calculation of the PageRank for Bitzi took 0.020338773727416992s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Bitzi took 3.170967102050781e-05s
Believability | Calculation of trust value for Bitzi took 7.3909759521484375e-06s
INFO | --- Analysis for bitzi took 2.8792617321014404s
Availability | SPARQL endpoint availability check for BizkaiSense took 4.220008850097656e-05s
Availability | VoID file availability check for BizkaiSense took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.2415904998779297s
Reputation | Calculation of the PageRank for BizkaiSense took 0.0202486515045166s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 2.9087066650390625e-05s
Believability | Calculation of trust value for BizkaiSense took 6.67572021484375e-06s
INFO | --- Analysis for bizkaisense took 2.787980079650879s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.2438507080078125e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2755293846130371s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020672321319580078s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.218650817871094e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.71661376953125e-05s
INFO | --- Analysis for blabla-itemlist took 2.9498400688171387s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.315376281738281e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2691192626953125s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.021762847900390625s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0009748935699462891s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 4.029273986816406e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.62939453125e-06s
INFO | --- Analysis for blabla_itemlist took 2.9158878326416016s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.38690185546875e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.24486732482910156s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007343292236328125s
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 4.360678195953369s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.3044681549072266s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.2916126251220703s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.02108168601989746s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.866455078125e-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.603148698806763s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.2076270580291748s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006215572357177734s
Extra | Recovery of all triples for Thesaurus BNCF took 43.734416246414185s
Performance | Total latancy measurement for Thesaurus BNCF took 0.5458672046661377s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6288108825683594s
Interoperability | New terms check for Thesaurus BNCF took 1.4432346820831299s
Versatility | Languages check for Thesaurus BNCF took 7.858498573303223s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.8870091438293457s
Security | Check HTTPS for Thesaurus BNCF took 0.08408093452453613s
Interpretability | RDF structures check for Thesaurus BNCF took 0.09766459465026855s
Versatility | Serialization formats check for Thesaurus BNCF took 0.09070920944213867s
Availability | RDF dump link check for Thesaurus BNCF took 0.0929100513458252s
License | MR license check for Thesaurus BNCF took 0.09321212768554688s
License | HR license check for Thesaurus BNCF took 0.17418313026428223s
Amount of data | Number of property check for Thesaurus BNCF took 0.09052562713623047s
Understandability | Number of label check for Thesaurus BNCF took 0.23532605171203613s
Understandability | URI regex check for Thesaurus BNCF took 0.19480204582214355s
Understandability | Vocabs check for Thesaurus BNCF took 0.09538888931274414s
Verifiability | Authors check for Thesaurus BNCF took 0.08878898620605469s
Verifiability | Publishers check for Thesaurus BNCF took 0.08687567710876465s
Performance | Throughput check for Thesaurus BNCF took 10.807393789291382s
Amount of data | Check the number of entities for Thesaurus BNCF took 6.914138793945312e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.10525894165039062s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.11028814315795898s
Interlinking | skos check for Thesaurus BNCF took 0.14703869819641113s
Interlinking | skos check for Thesaurus BNCF took 0.1569514274597168s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.09035634994506836s
Currency | Creation date check for Thesaurus BNCF took 0.22084784507751465s
Currency | Modification date check for Thesaurus BNCF took 0.17365264892578125s
Rep.Conc. | URIs length for Thesaurus BNCF took 25.036903142929077s
Interoperability | New vocabularies check for Thesaurus BNCF took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.0878751277923584s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.14087986946105957s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.09837722778320312s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 11.75003981590271s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.4955596923828125s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.919562339782715s
Consistency | Disjoint class check for Thesaurus BNCF took 0.09826850891113281s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.818943977355957s
Consistency | Misplaced classes for Thesaurus BNCF took 6.728768825531006s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 7.742431640625s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.3990540504455566s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.1384544372558594s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.3955817222595215s
Security | Sign check for Thesaurus BNCF took 0.08755755424499512s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 21.2291738986969s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.3137025833129883s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020208358764648438s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 4.124641418457031e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 6.914138793945312e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 7.62939453125e-06s
INFO | --- Analysis for bncf-ns took 181.92767357826233s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 20.697935342788696s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007355213165283203s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 33.81594657897949s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 79.79149842262268s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.247080326080322s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.154171466827393s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 84.03639888763428s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.225991487503052s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 10.852096796035767s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 24.845516681671143s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 19.515832901000977s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 30.35187268257141s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.294856548309326s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 75.42008543014526s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 23.804348945617676s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.320738077163696s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.5824878215789795s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 29.12079644203186s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.374683618545532s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 28.10240936279297s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.337860107421875e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 21.75775718688965s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.194544315338135s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.306493043899536s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 26.021734714508057s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.70248556137085s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 49.52977418899536s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 25.315635204315186s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 41.38926100730896s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 30.344557285308838s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.36145305633545s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.681995868682861s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 20.915024042129517s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030052661895751953s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.805741310119629s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 36.555461406707764s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.245206832885742s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.69869875907898s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 38.18319344520569s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.00013875961303710938s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.305935859680176s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.52397918701172s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0744249820709229s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0211942195892334s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.435943603515625e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.1457672119140625e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.821487426757812e-06s
INFO | --- Analysis for bpr took 4182.931329250336s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 8.726119995117188e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.26105451583862305s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020247697830200195s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 6.866455078125e-05s
Believability | Calculation of trust value for Brazilian Politicians took 4.5299530029296875e-06s
INFO | --- Analysis for brazilian-politicians took 4.384291648864746s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.1961669921875e-05s
Availability | VoID file availability check for BrazilianCities took 0.00022292137145996094s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.6799888610839844s
Reputation | Calculation of the PageRank for BrazilianCities took 0.020685911178588867s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.24249267578125e-05s
Believability | Calculation of trust value for BrazilianCities took 7.152557373046875e-06s
INFO | --- Analysis for braziliancities took 3.7764041423797607s
Availability | SPARQL endpoint availability check for Bricklink took 4.239256858825684s
Availability | VoID file availability check for Bricklink took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for Bricklink took 0.23808574676513672s
Reputation | Calculation of the PageRank for Bricklink took 0.02018141746520996s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.628036499023438e-05s
Believability | Calculation of trust value for Bricklink took 7.152557373046875e-06s
INFO | --- Analysis for bricklink took 14.001555681228638s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.119037866592407s
Availability | VoID file availability check for British Museum Collection took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.3149571418762207s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020367860794067383s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 2.8133392333984375e-05s
Believability | Calculation of trust value for British Museum Collection took 1.1205673217773438e-05s
INFO | --- Analysis for british-museum-collection took 73.25537300109863s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.696846008300781e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.26810574531555176s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.172325134277344e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 7.867813110351562e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.4203078746795654s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.124641418457031e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.25914859771728516s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.0205533504486084s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 2.9325485229492188e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 1.1682510375976562e-05s
INFO | --- Analysis for bsv took 2.8449020385742188s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.7823493480682373s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0008568763732910156s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.25293517112731934s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.5735626220703125e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.152557373046875e-06s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 7.255237102508545s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 8.177757263183594e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.2614114284515381s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.020049095153808594s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 3.266334533691406e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 7.3909759521484375e-06s
INFO | --- Analysis for bund-offener-haushalt took 2.879404306411743s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 4.124641418457031e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.26274943351745605s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 3.24249267578125e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 7.152557373046875e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 2.924018383026123s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.2960236072540283s
Availability | VoID file availability check for business.data.gov.uk took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.2660675048828125s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.078315734863281e-05s
Believability | Calculation of trust value for business.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for business-data-gov-uk took 2.879364490509033s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 1.0126330852508545s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.26335573196411133s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.020283222198486328s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 4.8160552978515625e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 7.3909759521484375e-06s
INFO | --- Analysis for BVMC took 5.091094017028809s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 5.340576171875e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.28278183937072754s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.218650817871094e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 7.62939453125e-06s
INFO | --- Analysis for cabbage took 2.8288211822509766s
Availability | SPARQL endpoint availability check for cablegate took 1.4017515182495117s
Availability | VoID file availability check for cablegate took 0.0007002353668212891s
Completeness | Calculation of interlinking completeness for cablegate took 0.2499098777770996s
Reputation | Calculation of the PageRank for cablegate took 0.020155906677246094s
Interlinking | Calculation of Degree of Connection for cablegate took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.818771362304688e-05s
Believability | Calculation of trust value for cablegate took 7.62939453125e-06s
INFO | --- Analysis for cablegate took 16.027220249176025s
Availability | SPARQL endpoint availability check for Calames took 4.315376281738281e-05s
Availability | VoID file availability check for Calames took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for Calames took 0.24704718589782715s
Reputation | Calculation of the PageRank for Calames took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for Calames took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Calames took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Calames took 3.719329833984375e-05s
Believability | Calculation of trust value for Calames took 7.62939453125e-06s
INFO | --- Analysis for calames took 4.0889365673065186s
Availability | SPARQL endpoint availability check for CaLiGraph took 1.2429463863372803s
Availability | VoID file availability check for CaLiGraph took 0.00027108192443847656s
Extra | Recovery of all triples for CaLiGraph took 1.5219306945800781s
Performance | Total latancy measurement for CaLiGraph took 1.2118756771087646s
Amount of data | Number of triples check for CaLiGraph took 12.419569730758667s
Interoperability | New terms check for CaLiGraph took 1.9750492572784424s
Versatility | Languages check for CaLiGraph took 60.336381673812866s
Interpretability | Number of blank nodes check for CaLiGraph took 0.23497915267944336s
Security | Check HTTPS for CaLiGraph took 0.15152788162231445s
Interpretability | RDF structures check for CaLiGraph took 0.2501673698425293s
Versatility | Serialization formats check for CaLiGraph took 0.23940730094909668s
Availability | RDF dump link check for CaLiGraph took 0.22191476821899414s
License | MR license check for CaLiGraph took 0.25848960876464844s
License | HR license check for CaLiGraph took 60.310102224349976s
Amount of data | Number of property check for CaLiGraph took 33.520400047302246s
Understandability | Number of label check for CaLiGraph took 56.22216486930847s
Understandability | URI regex check for CaLiGraph took 5.35637092590332s
Understandability | Vocabs check for CaLiGraph took 0.25176310539245605s
Verifiability | Authors check for CaLiGraph took 28.418970346450806s
Verifiability | Publishers check for CaLiGraph took 11.521917819976807s
Performance | Throughput check for CaLiGraph took 46.74989676475525s
Amount of data | Check the number of entities for CaLiGraph took 0.013996362686157227s
Verifiability | Contribs. check for CaLiGraph took 0.26660919189453125s
Interlinking | sameAs chians check for CaLiGraph took 0.6731574535369873s
Interlinking | skos check for CaLiGraph took 0.24266815185546875s
Interlinking | skos check for CaLiGraph took 0.22500038146972656s
Timeliness | dataset update frequency check for CaLiGraph took 0.27617621421813965s
Currency | Creation date check for CaLiGraph took 0.468733549118042s
Currency | Modification date check for CaLiGraph took 0.47792840003967285s
Rep.Conc. | URIs length for CaLiGraph took 60.97953224182129s
Interoperability | New vocabularies check for CaLiGraph took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.23645234107971191s
Accuracy | Check Functional Property for CaLiGraph took 0.23032522201538086s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2388167381286621s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5515313148498535s
Accuracy | Check White space in annotation for CaLiGraph took 0.026241540908813477s
Accuracy | Check Datatype consistency for CaLiGraph took 0.04965925216674805s
Consistency | Disjoint class check for CaLiGraph took 0.2581045627593994s
Consistency | Check Misplaced properties for CaLiGraph took 60.8945586681366s
Consistency | Misplaced classes for CaLiGraph took 0.50140380859375s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9511303901672363s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2641236782073975s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.55488634109497s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03330659866333008s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.42923998832702637s
Security | Sign check for CaLiGraph took 1.2836761474609375s
Availability | Check URIs Dereferenciability for CaLiGraph took 18.540753602981567s
Completeness | Calculation of interlinking completeness for CaLiGraph took 1.3391683101654053s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.5762786865234375e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 7.62939453125e-06s
INFO | --- Analysis for CaLiGraph took 1664.4594633579254s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.2380201816558838s
Availability | VoID file availability check for CaLiGraph took 0.0005807876586914062s
Extra | Recovery of all triples for CaLiGraph took 1.2119395732879639s
Performance | Total latancy measurement for CaLiGraph took 1.1392052173614502s
Amount of data | Number of triples check for CaLiGraph took 12.293299198150635s
Interoperability | New terms check for CaLiGraph took 1.8682215213775635s
Versatility | Languages check for CaLiGraph took 60.248465061187744s
Interpretability | Number of blank nodes check for CaLiGraph took 0.24751806259155273s
Security | Check HTTPS for CaLiGraph took 0.17083072662353516s
Interpretability | RDF structures check for CaLiGraph took 0.24700307846069336s
Versatility | Serialization formats check for CaLiGraph took 0.2718076705932617s
Availability | RDF dump link check for CaLiGraph took 0.23786234855651855s
License | MR license check for CaLiGraph took 0.24175071716308594s
License | HR license check for CaLiGraph took 60.26005530357361s
Amount of data | Number of property check for CaLiGraph took 0.3139302730560303s
Understandability | Number of label check for CaLiGraph took 3.0622220039367676s
Understandability | URI regex check for CaLiGraph took 0.46549415588378906s
Understandability | Vocabs check for CaLiGraph took 0.22924542427062988s
Verifiability | Authors check for CaLiGraph took 0.23610591888427734s
Verifiability | Publishers check for CaLiGraph took 0.23075270652770996s
Performance | Throughput check for CaLiGraph took 11.490105152130127s
Amount of data | Check the number of entities for CaLiGraph took 0.014897346496582031s
Verifiability | Contribs. check for CaLiGraph took 0.2943994998931885s
Interlinking | sameAs chians check for CaLiGraph took 0.6640238761901855s
Interlinking | skos check for CaLiGraph took 0.27764010429382324s
Interlinking | skos check for CaLiGraph took 0.26701998710632324s
Timeliness | dataset update frequency check for CaLiGraph took 0.2607865333557129s
Currency | Creation date check for CaLiGraph took 0.5113081932067871s
Currency | Modification date check for CaLiGraph took 0.4957387447357178s
Rep.Conc. | URIs length for CaLiGraph took 60.989859104156494s
Interoperability | New vocabularies check for CaLiGraph took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.22052335739135742s
Accuracy | Check Functional Property for CaLiGraph took 0.2380695343017578s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.26737451553344727s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5930817127227783s
Accuracy | Check White space in annotation for CaLiGraph took 0.026213645935058594s
Accuracy | Check Datatype consistency for CaLiGraph took 0.04925847053527832s
Consistency | Disjoint class check for CaLiGraph took 0.28934693336486816s
Consistency | Check Misplaced properties for CaLiGraph took 61.0869140625s
Consistency | Misplaced classes for CaLiGraph took 0.44457077980041504s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9372048377990723s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2631690502166748s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.640644788742065s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03028130531311035s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4482593536376953s
Security | Sign check for CaLiGraph took 0.24068069458007812s
Availability | Check URIs Dereferenciability for CaLiGraph took 20.977664947509766s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.7402870655059814s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020565032958984375s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 8.344650268554688e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.1920928955078125e-06s
Believability | Calculation of trust value for CaLiGraph took 6.9141387939453125e-06s
INFO | --- Analysis for caligraph took 1496.8494927883148s
Availability | SPARQL endpoint availability check for can-link took 4.553794860839844e-05s
Availability | VoID file availability check for can-link took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for can-link took 0.2746009826660156s
Reputation | Calculation of the PageRank for can-link took 0.020294666290283203s
Interlinking | Calculation of Degree of Connection for can-link took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for can-link took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for can-link took 3.0279159545898438e-05s
Believability | Calculation of trust value for can-link took 1.3113021850585938e-05s
INFO | --- Analysis for can-link took 4.208703994750977s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.06835508346557617s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.2677748203277588s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 7.62939453125e-06s
INFO | --- Analysis for cap-italy-rdf took 3.443882703781128s
Availability | SPARQL endpoint availability check for person took 4.172325134277344e-05s
Availability | VoID file availability check for person took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for person took 0.2658700942993164s
Reputation | Calculation of the PageRank for person took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for person took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for person took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for person took 2.956390380859375e-05s
Believability | Calculation of trust value for person took 6.9141387939453125e-06s
INFO | --- Analysis for card took 2.389512777328491s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.267692565917969e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.24461078643798828s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020339012145996094s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.838539123535156e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 7.62939453125e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 2.9161975383758545s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.2438507080078125e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.0002884864807128906s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.25724291801452637s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020442724227905273s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.075599670410156e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 7.3909759521484375e-06s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 2.9943108558654785s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.9885365962982178s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.26718688011169434s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.0200498104095459s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 3.457069396972656e-05s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 3.8881945610046387s
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.0006115436553955078s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.2710607051849365s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010418891906738281s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 6.67572021484375e-06s
INFO | --- Analysis for ce4r took 39.28508424758911s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.468228816986084s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0002849102020263672s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.158710241317749s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.7605962753295898s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2747511863708496s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6615145206451416s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.125892162323s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16758108139038086s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.39817118644714355s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15985918045043945s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14990448951721191s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.26118922233581543s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.33710789680480957s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15935420989990234s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2994964122772217s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3319966793060303s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17208242416381836s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.25971198081970215s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1802525520324707s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.866100072860718s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.128715515136719e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.23682093620300293s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20709824562072754s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3199329376220703s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1634361743927002s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17828917503356934s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3915112018585205s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.37496352195739746s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.094985246658325s
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.16155600547790527s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.30290699005126953s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.3191535472869873s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.5996904373168945s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.029531002044677734s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.026869773864746094s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.41103148460388184s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.2342464923858643s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.9148733615875244s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.2556354999542236s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.4803600311279297s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.029738426208496094s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.20020246505737305s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1538238525390625s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2538.1726038455963s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 1.0528056621551514s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 7.3909759521484375e-06s
INFO | --- Analysis for ceo took 2664.267674922943s
Availability | SPARQL endpoint availability check for Charging Stations took 4.839897155761719e-05s
Availability | VoID file availability check for Charging Stations took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.6942315101623535s
Reputation | Calculation of the PageRank for Charging Stations took 0.02045154571533203s
Interlinking | Calculation of Degree of Connection for Charging Stations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 2.9325485229492188e-05s
Believability | Calculation of trust value for Charging Stations took 7.152557373046875e-06s
INFO | --- Analysis for charging-stations took 4.211131811141968s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.38690185546875e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.2840232849121094s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020422935485839844s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0009765625s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 4.1961669921875e-05s
Believability | Calculation of trust value for Chat Game corpus took 6.9141387939453125e-06s
INFO | --- Analysis for chat-game-corpus took 12.455815315246582s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 7.319450378417969e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.2773270606994629s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.02016425132751465s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.361701965332031e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 7.3909759521484375e-06s
INFO | --- Analysis for chebi took 3.342688798904419s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 6.604194641113281e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0008039474487304688s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.7311902046203613s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.4836273193359375e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 7.152557373046875e-06s
INFO | --- Analysis for chem2bio2rdf took 133.8746485710144s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.5749869346618652s
Availability | VoID file availability check for ChEMBL RDF took 0.00042366981506347656s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.24866366386413574s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.02096104621887207s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.412101745605469e-05s
Believability | Calculation of trust value for ChEMBL RDF took 6.67572021484375e-06s
INFO | --- Analysis for chembl-rdf took 3.545675277709961s
Availability | SPARQL endpoint availability check for chemdb  dataset took 0.7698194980621338s
Availability | VoID file availability check for chemdb  dataset took 0.0002713203430175781s
Extra | Recovery of all triples for chemdb  dataset took 10.141038179397583s
Performance | Total latancy measurement for chemdb  dataset took 2.505955934524536s
Amount of data | Number of triples check for chemdb  dataset took 0.526716947555542s
Interoperability | New terms check for chemdb  dataset took 3.4741294384002686s
Versatility | Languages check for chemdb  dataset took 27.774460792541504s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.4942805767059326s
Interpretability | RDF structures check for chemdb  dataset took 0.7816348075866699s
Versatility | Serialization formats check for chemdb  dataset took 1.3973994255065918s
Availability | RDF dump link check for chemdb  dataset took 0.7813031673431396s
License | MR license check for chemdb  dataset took 2.7062387466430664s
License | HR license check for chemdb  dataset took 3.956077814102173s
Amount of data | Number of property check for chemdb  dataset took 0.4999806880950928s
Understandability | Number of label check for chemdb  dataset took 4.740642309188843s
Understandability | URI regex check for chemdb  dataset took 1.8987886905670166s
Understandability | Vocabs check for chemdb  dataset took 0.7881736755371094s
Verifiability | Authors check for chemdb  dataset took 1.0560388565063477s
Verifiability | Publishers check for chemdb  dataset took 0.7849454879760742s
Performance | Throughput check for chemdb  dataset took 13.36557412147522s
Amount of data | Check the number of entities for chemdb  dataset took 7.581710815429688e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.7766103744506836s
Interlinking | sameAs chians check for chemdb  dataset took 1.0853168964385986s
Interlinking | skos check for chemdb  dataset took 1.8736329078674316s
Interlinking | skos check for chemdb  dataset took 0.4831979274749756s
Timeliness | dataset update frequency check for chemdb  dataset took 1.0580484867095947s
Currency | Creation date check for chemdb  dataset took 1.3148131370544434s
Currency | Modification date check for chemdb  dataset took 1.0069935321807861s
Rep.Conc. | URIs length for chemdb  dataset took 2.9576070308685303s
Interoperability | New vocabularies check for chemdb  dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5013401508331299s
Accuracy | Check Functional Property for chemdb  dataset took 0.7572462558746338s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.7514944076538086s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.150718927383423s
Accuracy | Check White space in annotation for chemdb  dataset took 0.030188560485839844s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03298544883728027s
Consistency | Disjoint class check for chemdb  dataset took 0.7863168716430664s
Consistency | Check Misplaced properties for chemdb  dataset took 1.2142908573150635s
Consistency | Misplaced classes for chemdb  dataset took 0.5811240673065186s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.407048225402832s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.2972209453582764s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 1.974867582321167s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.032172203063964844s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5050442218780518s
Security | Sign check for chemdb  dataset took 2.0621776580810547s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2529.1902656555176s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 1.520667314529419s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.152557373046875e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb  dataset took 7.867813110351562e-06s
INFO | --- Analysis for chemdb-basicInfo took 4600.794798612595s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.4982428550720215s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0005128383636474609s
Extra | Recovery of all triples for chemdb estimated properties dataset took 13.254075288772583s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.4896771907806396s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.514014720916748s
Interoperability | New terms check for chemdb estimated properties dataset took 3.9054410457611084s
Versatility | Languages check for chemdb estimated properties dataset took 27.61512303352356s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5081329345703125s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.49930524826049805s
Versatility | Serialization formats check for chemdb estimated properties dataset took 1.343764305114746s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.7779042720794678s
License | MR license check for chemdb estimated properties dataset took 2.7634031772613525s
License | HR license check for chemdb estimated properties dataset took 3.9843227863311768s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5006022453308105s
Understandability | Number of label check for chemdb estimated properties dataset took 4.627578496932983s
Understandability | URI regex check for chemdb estimated properties dataset took 1.8655693531036377s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.8087253570556641s
Verifiability | Authors check for chemdb estimated properties dataset took 1.060906171798706s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.7754855155944824s
Performance | Throughput check for chemdb estimated properties dataset took 13.427159070968628s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 7.486343383789062e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.7834291458129883s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 1.057631015777588s
Interlinking | skos check for chemdb estimated properties dataset took 1.8845996856689453s
Interlinking | skos check for chemdb estimated properties dataset took 0.511467456817627s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 1.0528948307037354s
Currency | Creation date check for chemdb estimated properties dataset took 1.1912095546722412s
Currency | Modification date check for chemdb estimated properties dataset took 0.9713373184204102s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 3.4129250049591064s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.5012638568878174s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.7359287738800049s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.7340652942657471s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 3.2992117404937744s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.029621601104736328s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03363490104675293s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.795565128326416s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.2004201412200928s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.5855288505554199s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 3.8661625385284424s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.3013134002685547s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 1.9954304695129395s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03572201728820801s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.49163269996643066s
Security | Sign check for chemdb estimated properties dataset took 1.8604989051818848s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2525.7992153167725s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 1.5260140895843506s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 4.863739013671875e-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 7.62939453125e-06s
INFO | --- Analysis for chemdb-estimatedProperties took 4579.360002756119s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.49298095703125s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0002377033233642578s
Extra | Recovery of all triples for chemdb phase transition dataset took 9.089184761047363s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.477900505065918s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5206058025360107s
Interoperability | New terms check for chemdb phase transition dataset took 3.916630744934082s
Versatility | Languages check for chemdb phase transition dataset took 25.988435983657837s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.4960148334503174s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5095293521881104s
Versatility | Serialization formats check for chemdb phase transition dataset took 1.3641130924224854s
Availability | RDF dump link check for chemdb phase transition dataset took 0.6125061511993408s
License | MR license check for chemdb phase transition dataset took 2.8120007514953613s
License | HR license check for chemdb phase transition dataset took 4.044278621673584s
Amount of data | Number of property check for chemdb phase transition dataset took 0.4929025173187256s
Understandability | Number of label check for chemdb phase transition dataset took 4.866378545761108s
Understandability | URI regex check for chemdb phase transition dataset took 1.8406214714050293s
Understandability | Vocabs check for chemdb phase transition dataset took 0.7899501323699951s
Verifiability | Authors check for chemdb phase transition dataset took 1.056232213973999s
Verifiability | Publishers check for chemdb phase transition dataset took 0.7711672782897949s
Performance | Throughput check for chemdb phase transition dataset took 13.868872880935669s
Amount of data | Check the number of entities for chemdb phase transition dataset took 7.152557373046875e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.7788951396942139s
Interlinking | sameAs chians check for chemdb phase transition dataset took 1.0571556091308594s
Interlinking | skos check for chemdb phase transition dataset took 1.883087158203125s
Interlinking | skos check for chemdb phase transition dataset took 0.49937915802001953s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 1.0565500259399414s
Currency | Creation date check for chemdb phase transition dataset took 1.3054516315460205s
Currency | Modification date check for chemdb phase transition dataset took 0.9941082000732422s
Rep.Conc. | URIs length for chemdb phase transition dataset took 3.35290265083313s
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.48178601264953613s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.7515885829925537s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.7523972988128662s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 3.1494555473327637s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.03006601333618164s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03428006172180176s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.8042399883270264s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2015290260314941s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.5928158760070801s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 3.9227237701416016s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.2685699462890625s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 1.9545881748199463s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.033199310302734375s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.49662113189697266s
Security | Sign check for chemdb phase transition dataset took 1.9007785320281982s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2530.7074756622314s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 1.5826647281646729s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.020797252655029297s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 5.078315734863281e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.3113021850585938e-05s
INFO | --- Analysis for chemdb-phaseTransition took 4545.22399187088s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.48297739028930664s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0002605915069580078s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 9.105558395385742s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.478804349899292s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5269653797149658s
Interoperability | New terms check for chemdb thermochemistry dataset took 3.9069550037384033s
Versatility | Languages check for chemdb thermochemistry dataset took 25.826789617538452s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.48827576637268066s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5060453414916992s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 1.370366096496582s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.6081435680389404s
License | MR license check for chemdb thermochemistry dataset took 2.872138738632202s
License | HR license check for chemdb thermochemistry dataset took 4.027244806289673s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.49976015090942383s
Understandability | Number of label check for chemdb thermochemistry dataset took 4.738843202590942s
Understandability | URI regex check for chemdb thermochemistry dataset took 1.8724288940429688s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.6837997436523438s
Verifiability | Authors check for chemdb thermochemistry dataset took 1.0600881576538086s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.7657711505889893s
Performance | Throughput check for chemdb thermochemistry dataset took 13.872485160827637s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 6.961822509765625e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.783989429473877s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 1.0622313022613525s
Interlinking | skos check for chemdb thermochemistry dataset took 2.018254041671753s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5059816837310791s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 1.094756841659546s
Currency | Creation date check for chemdb thermochemistry dataset took 1.2857556343078613s
Currency | Modification date check for chemdb thermochemistry dataset took 0.9982495307922363s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.41467022895813s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.49774789810180664s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.7376611232757568s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.7468643188476562s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 3.1579298973083496s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.03037714958190918s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.032659053802490234s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.8068637847900391s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.197685956954956s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.5773916244506836s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 3.8761420249938965s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.2664175033569336s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 1.9658317565917969s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.03290271759033203s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.49890732765197754s
Security | Sign check for chemdb thermochemistry dataset took 1.9638266563415527s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2536.659403324127s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 1.5822100639343262s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.842613220214844e-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 7.867813110351562e-06s
INFO | --- Analysis for chemdb-thermochemistry took 4554.282293558121s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.363059997558594e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.24178433418273926s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.02081465721130371s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.5762786865234375e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.1920928955078125e-05s
INFO | --- Analysis for chempedia-rdf took 11.004791259765625s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.291534423828125e-05s
Availability | VoID file availability check for Chiman Maru took 0.0003256797790527344s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.2500467300415039s
Reputation | Calculation of the PageRank for Chiman Maru took 0.021534204483032227s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.000904083251953125s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.647804260253906e-05s
Believability | Calculation of trust value for Chiman Maru took 7.62939453125e-06s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 2.2349257469177246s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 393.0207543373108s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.7733702659606934s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.021179676055908203s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0008165836334228516s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.62396240234375e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 8.344650268554688e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 799.0457980632782s
Availability | SPARQL endpoint availability check for Chronicling America took 5.340576171875e-05s
Availability | VoID file availability check for Chronicling America took 0.0008020401000976562s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.2473602294921875s
Reputation | Calculation of the PageRank for Chronicling America took 0.020832300186157227s
Interlinking | Calculation of Degree of Connection for Chronicling America took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.0001316070556640625s
Believability | Calculation of trust value for Chronicling America took 5.7220458984375e-06s
INFO | --- Analysis for chronicling-america took 8.827162742614746s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.6748521327972412s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0007541179656982422s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 77.92043852806091s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.398956537246704s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.6323604583740234s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.0288941860198975s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.5682549476623535s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.5903716087341309s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.28169894218444824s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.2936110496520996s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 8.479830741882324s
License | MR license check for Cultural Heritage Thesaurus took 0.27750682830810547s
License | HR license check for Cultural Heritage Thesaurus took 0.3427267074584961s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.2771759033203125s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.3313915729522705s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.578845739364624s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.29524779319763184s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.30596137046813965s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.27623581886291504s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.085073947906494s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 9.059906005859375e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.2948746681213379s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.27968430519104004s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.27049922943115234s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.298250675201416s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.2841989994049072s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.5930831432342529s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.5814423561096191s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 31.372304439544678s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 0.9144418239593506s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.28678011894226074s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.29767489433288574s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.26085519790649414s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 7.4622111320495605s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.2207624912261963s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.27622365951538086s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.0019800662994385s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.29424333572387695s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.672509670257568s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.057427167892456s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00015354156494140625s
Security | Sign check for Cultural Heritage Thesaurus took 0.29586124420166016s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 309.2855815887451s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.8454225063323975s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00010204315185546875s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.6175158023834229s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for cht took 496.475209236145s
Availability | SPARQL endpoint availability check for ciard-ring took 5.0067901611328125e-05s
Availability | VoID file availability check for ciard-ring took 0.00030994415283203125s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.275726318359375s
Reputation | Calculation of the PageRank for ciard-ring took 0.02031397819519043s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.6253204345703125e-05s
Believability | Calculation of trust value for ciard-ring took 5.9604644775390625e-06s
INFO | --- Analysis for ciard-ring took 5.1064653396606445s
Availability | SPARQL endpoint availability check for Cine Figure took 4.3392181396484375e-05s
Availability | VoID file availability check for Cine Figure took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.2501044273376465s
Reputation | Calculation of the PageRank for Cine Figure took 0.020309925079345703s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.315376281738281e-05s
Believability | Calculation of trust value for Cine Figure took 6.67572021484375e-06s
INFO | --- Analysis for Cine_Figure took 2.3369076251983643s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 1.3484811782836914s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.2617838382720947s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.0203397274017334s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.482269287109375e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 5.358299732208252s
Availability | SPARQL endpoint availability check for CIPFA took 4.3392181396484375e-05s
Availability | VoID file availability check for CIPFA took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for CIPFA took 0.24811768531799316s
Reputation | Calculation of the PageRank for CIPFA took 0.020307064056396484s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for CIPFA took 4.506111145019531e-05s
Believability | Calculation of trust value for CIPFA took 5.245208740234375e-06s
INFO | --- Analysis for cipfa took 2.5606749057769775s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.056302070617676s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0007283687591552734s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.6876273155212402s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0004088878631591797s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 7.3909759521484375e-06s
INFO | --- Analysis for ckan took 263.0221297740936s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.6199266910552979s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.2697784900665283s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020414352416992188s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.00543212890625e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for CLaSSES took 4.194768667221069s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.172325134277344e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.2558629512786865s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.314018249511719e-05s
Believability | Calculation of trust value for Temples of the Classical World took 5.9604644775390625e-06s
INFO | --- Analysis for classical_temples took 3.669175624847412s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 2.1278653144836426s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.2776527404785156s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 9.393692016601562e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 8.344650268554688e-06s
INFO | --- Analysis for clean-energy-data-reegle took 13.36225438117981s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.291534423828125e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0004241466522216797s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.2506721019744873s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020693302154541016s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 8.463859558105469e-05s
Believability | Calculation of trust value for CLLD-afbo took 5.9604644775390625e-06s
INFO | --- Analysis for clld-afbo took 3.4462759494781494s
Availability | SPARQL endpoint availability check for CLLD-APICS took 7.62939453125e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.279205322265625s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.724761962890625e-05s
Believability | Calculation of trust value for CLLD-APICS took 6.67572021484375e-06s
INFO | --- Analysis for clld-apics took 4.183315277099609s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.100799560546875e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.26349425315856934s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.02037215232849121s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 4.2438507080078125e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 5.9604644775390625e-06s
INFO | --- Analysis for clld-ewave took 3.4441757202148438s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.220008850097656e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.26034116744995117s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010895729064941406s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 6.198883056640625e-06s
INFO | --- Analysis for clld-glottolog took 3.4362008571624756s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.38690185546875e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.27832579612731934s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.225440979003906e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 9.5367431640625e-06s
INFO | --- Analysis for clld-phoible took 3.4207587242126465s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.792213439941406e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.2439732551574707s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.0207977294921875s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 8.106231689453125e-05s
Believability | Calculation of trust value for CLLD-SAILS took 6.4373016357421875e-06s
INFO | --- Analysis for clld-sails took 3.599534273147583s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.863739013671875e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.26564860343933105s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020618438720703125s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.821487426757812e-05s
Believability | Calculation of trust value for CLLD-WALS took 5.7220458984375e-06s
INFO | --- Analysis for clld-wals took 4.7889885902404785s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 5.53131103515625e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.26664257049560547s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020714998245239258s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.000823974609375s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 9.226799011230469e-05s
Believability | Calculation of trust value for CLLD-WOLD took 1.1682510375976562e-05s
INFO | --- Analysis for clld-wold took 3.485464334487915s
Availability | SPARQL endpoint availability check for COD inventory took 4.2438507080078125e-05s
Availability | VoID file availability check for COD inventory took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for COD inventory took 0.2663578987121582s
Reputation | Calculation of the PageRank for COD inventory took 0.02069687843322754s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.2901763916015625e-05s
Believability | Calculation of trust value for COD inventory took 6.198883056640625e-06s
INFO | --- Analysis for cod-inventory took 2.8424291610717773s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.24045944213867188s
Availability | VoID file availability check for Cooperation Databank took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.25732946395874023s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.020732402801513672s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 4.3392181396484375e-05s
Believability | Calculation of trust value for Cooperation Databank took 7.152557373046875e-06s
INFO | --- Analysis for CoDa took 2.6185905933380127s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.0531158447265625e-05s
Availability | VoID file availability check for CODE Endpoint took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.27807092666625977s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.020506620407104492s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.314018249511719e-05s
Believability | Calculation of trust value for CODE Endpoint took 6.67572021484375e-06s
INFO | --- Analysis for code-endpoint took 2.864797592163086s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.6573467254638672s
Availability | VoID file availability check for OpenUpLabs COINS took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.2679626941680908s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.020447731018066406s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.409385681152344e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 4.5299530029296875e-06s
INFO | --- Analysis for coins-openuplabs took 3.1290786266326904s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.378943920135498s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.26802730560302734s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.797645568847656e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 5.9604644775390625e-06s
INFO | --- Analysis for CoLChina_sp2000 took 7.2064385414123535s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.0639350414276123s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.29236721992492676s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.3392181396484375e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for colinda took 2.418893337249756s
Availability | SPARQL endpoint availability check for CN  2012 took 25.692636966705322s
Availability | VoID file availability check for CN  2012 took 0.0009169578552246094s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.42682790756225586s
Reputation | Calculation of the PageRank for CN  2012 took 0.0208895206451416s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 4.696846008300781e-05s
Believability | Calculation of trust value for CN  2012 took 5.0067901611328125e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 124.94348907470703s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 3.9577484130859375e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.24764633178710938s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.020705461502075195s
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.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.3855438232421875e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 7.152557373046875e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 3.019314765930176s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 4.553794860839844e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.2952759265899658s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.020672321319580078s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 3.147125244140625e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 6.4373016357421875e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 2.9407312870025635s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.1484832763671875e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.2720000743865967s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.02042865753173828s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.266334533691406e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 8.344650268554688e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 2.903597593307495s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.2438507080078125e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.25047731399536133s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.02046656608581543s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 3.218650817871094e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 6.9141387939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.8329508304595947s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 4.1961669921875e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.27249884605407715s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.123283386230469e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 1.2636184692382812e-05s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.8367886543273926s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.5033864974975586s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0007486343383789062s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.2762315273284912s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.020313739776611328s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.719329833984375e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for CompHistSem took 3.893557071685791s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 2.579225540161133s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.2803306579589844s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 4.172325134277344e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 6.4373016357421875e-06s
INFO | --- Analysis for comsode-d3-2 took 7.743456840515137s
Availability | SPARQL endpoint availability check for ConceptNet took 4.076957702636719e-05s
Availability | VoID file availability check for ConceptNet took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.26785755157470703s
Reputation | Calculation of the PageRank for ConceptNet took 0.020952701568603516s
Interlinking | Calculation of Degree of Connection for ConceptNet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ConceptNet took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 3.528594970703125e-05s
Believability | Calculation of trust value for ConceptNet took 7.3909759521484375e-06s
INFO | --- Analysis for conceptnet took 2.913872718811035s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.315376281738281e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.25633692741394043s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020647525787353516s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.58306884765625e-05s
Believability | Calculation of trust value for 2011 US Congress People took 5.245208740234375e-06s
INFO | --- Analysis for congresspeople took 2.932166337966919s
Availability | SPARQL endpoint availability check for MIMO took 0.404339075088501s
Availability | VoID file availability check for MIMO took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for MIMO took 0.24957704544067383s
Reputation | Calculation of the PageRank for MIMO took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for MIMO took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.2159347534179688e-05s
Believability | Calculation of trust value for MIMO took 6.4373016357421875e-06s
INFO | --- Analysis for CONNECTED took 3.655641555786133s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 4.124641418457031e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.2762284278869629s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 7.867813110351562e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.803391933441162s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.029273986816406e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0003139972686767578s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.2533884048461914s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.020202159881591797s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.220008850097656e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 2.8371810913085938e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 7.3909759521484375e-06s
INFO | --- Analysis for copac-library-catalogue took 2.81900691986084s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.1961669921875e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.2338407039642334s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.0201413631439209s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.7894973754882812e-05s
Believability | Calculation of trust value for Copyright Free Music took 5.9604644775390625e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.4171762466430664s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.220008850097656e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.2696390151977539s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020648717880249023s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.343292236328125e-05s
Believability | Calculation of trust value for CopyrightTermBank took 6.4373016357421875e-06s
INFO | --- Analysis for copyrighttermbank took 33.99243378639221s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.2197794914245605s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.24935650825500488s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020554780960083008s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 4.172325134277344e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 7.152557373046875e-06s
INFO | --- Analysis for core took 6.820689678192139s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.9613800048828125s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.2557673454284668s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.020650625228881836s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.24249267578125e-05s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for Corine_linked_dataset took 3.9409537315368652s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.076957702636719e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.272876501083374s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.123283386230469e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 6.67572021484375e-06s
INFO | --- Analysis for corn took 2.8798046112060547s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 5.245208740234375e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.27435874938964844s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020402908325195312s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.170967102050781e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 7.3909759521484375e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 2.8346917629241943s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 5.626678466796875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.2635483741760254s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.020344018936157227s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.218650817871094e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 6.9141387939453125e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 2.8824880123138428s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.2438507080078125e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.27927303314208984s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020234107971191406s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.602836608886719e-05s
Believability | Calculation of trust value for Cornetto1.2 took 5.7220458984375e-06s
INFO | --- Analysis for cornetto took 13.092167377471924s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.3119802474975586s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0006334781646728516s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 198.13832020759583s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.5621767044067383s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 114.4014778137207s
Interoperability | New terms check for Corporate Body Named Authority List  took 82.77209067344666s
Versatility | Languages check for Corporate Body Named Authority List  took 300.1319479942322s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 16.247283458709717s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.30777955055236816s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.4781758785247803s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 3.684532880783081s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.32747411727905273s
License | MR license check for Corporate Body Named Authority List  took 0.399259090423584s
License | HR license check for Corporate Body Named Authority List  took 300.08548307418823s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.15673613548278809s
Understandability | Number of label check for Corporate Body Named Authority List  took 2.565397024154663s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.3507857322692871s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.13010954856872559s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.23183727264404297s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.20788812637329102s
Performance | Throughput check for Corporate Body Named Authority List  took 10.78244137763977s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 7.2479248046875e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.18320250511169434s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 7.217386484146118s
Interlinking | skos check for Corporate Body Named Authority List  took 0.37563014030456543s
Interlinking | skos check for Corporate Body Named Authority List  took 0.3298156261444092s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.23099923133850098s
Currency | Creation date check for Corporate Body Named Authority List  took 0.4463949203491211s
Currency | Modification date check for Corporate Body Named Authority List  took 0.11914396286010742s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 479.7168073654175s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.16263723373413086s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.17353224754333496s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.1616358757019043s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 40.33621644973755s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.1769211292266846s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.7383430004119873s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.17673826217651367s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.3727135658264s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.514383316040039s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 36.34084749221802s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.743257999420166s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.4531693458557s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.027825355529785s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.37148499488830566s
Security | Sign check for Corporate Body Named Authority List  took 0.10712194442749023s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 17.298805236816406s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 1.1920394897460938s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.021200895309448242s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007021427154541016s
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 6.9141387939453125e-06s
INFO | --- Analysis for corporate-body took 15144.612211227417s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.609081506729126s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.24583792686462402s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020611286163330078s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.719329833984375e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for CorpusFibonacci took 5.04942774772644s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.1484832763671875e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.25771284103393555s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 2.8371810913085938e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 6.67572021484375e-06s
INFO | --- Analysis for corscheck took 2.8282968997955322s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.10065174102783203s
Availability | VoID file availability check for Country Name Authority List took 0.0006737709045410156s
Extra | Recovery of all triples for Country Name Authority List took 220.82434463500977s
Performance | Total latancy measurement for Country Name Authority List took 0.6025772094726562s
Amount of data | Number of triples check for Country Name Authority List took 131.52048516273499s
Interoperability | New terms check for Country Name Authority List took 79.21353507041931s
Versatility | Languages check for Country Name Authority List took 300.9626009464264s
Interpretability | Number of blank nodes check for Country Name Authority List took 68.50771427154541s
Security | Check HTTPS for Country Name Authority List took 0.3909742832183838s
Interpretability | RDF structures check for Country Name Authority List took 0.6409735679626465s
Versatility | Serialization formats check for Country Name Authority List took 3.4676051139831543s
Availability | RDF dump link check for Country Name Authority List took 0.21024107933044434s
License | MR license check for Country Name Authority List took 0.45908427238464355s
License | HR license check for Country Name Authority List took 300.11844182014465s
Amount of data | Number of property check for Country Name Authority List took 0.15735793113708496s
Understandability | Number of label check for Country Name Authority List took 1.6266236305236816s
Understandability | URI regex check for Country Name Authority List took 0.44447875022888184s
Understandability | Vocabs check for Country Name Authority List took 0.12121105194091797s
Verifiability | Authors check for Country Name Authority List took 0.27572083473205566s
Verifiability | Publishers check for Country Name Authority List took 0.15082597732543945s
Performance | Throughput check for Country Name Authority List took 10.457619190216064s
Amount of data | Check the number of entities for Country Name Authority List took 0.00013780593872070312s
Verifiability | Contribs. check for Country Name Authority List took 0.22850561141967773s
Interlinking | sameAs chians check for Country Name Authority List took 7.3928375244140625s
Interlinking | skos check for Country Name Authority List took 0.14916181564331055s
Interlinking | skos check for Country Name Authority List took 0.2990226745605469s
Timeliness | dataset update frequency check for Country Name Authority List took 0.26141905784606934s
Currency | Creation date check for Country Name Authority List took 0.44628238677978516s
Currency | Modification date check for Country Name Authority List took 0.17682743072509766s
Rep.Conc. | URIs length for Country Name Authority List took 479.42832946777344s
Interoperability | New vocabularies check for Country Name Authority List took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.1429743766784668s
Accuracy | Check Functional Property for Country Name Authority List took 0.18440866470336914s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.17565107345581055s
Accuracy | Check Empty annotation labels for Country Name Authority List took 39.12403988838196s
Accuracy | Check White space in annotation for Country Name Authority List took 3.0495553016662598s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.7154064178466797s
Consistency | Disjoint class check for Country Name Authority List took 0.20880913734436035s
Consistency | Check Misplaced properties for Country Name Authority List took 300.32557106018066s
Consistency | Misplaced classes for Country Name Authority List took 8.538468360900879s
Consistency | Check Ontology hijacking for Country Name Authority List took 37.63240075111389s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.7299723625183105s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.431423664093s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.0104758739471436s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.42704033851623535s
Security | Sign check for Country Name Authority List took 0.44820213317871094s
Availability | Check URIs Dereferenciability for Country Name Authority List took 17.151960849761963s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.7756779193878174s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.02116227149963379s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.9073486328125e-06s
Believability | Calculation of trust value for Country Name Authority List took 7.62939453125e-06s
INFO | --- Analysis for country-authority-list took 15480.544106960297s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.07266879081726074s
Availability | VoID file availability check for Courts thesaurus took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.2804577350616455s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020529508590698242s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.842613220214844e-05s
Believability | Calculation of trust value for Courts thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for courts-thesaurus took 2.5029349327087402s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.3924884796142578s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0006542205810546875s
Extra | Recovery of all triples for Covid-on-the-Web Dataset took 2.2578113079071045s
Performance | Total latancy measurement for Covid-on-the-Web Dataset took 0.5443012714385986s
Amount of data | Number of triples check for Covid-on-the-Web Dataset took 62.5971462726593s
Interoperability | New terms check for Covid-on-the-Web Dataset took 2.1377570629119873s
Versatility | Languages check for Covid-on-the-Web Dataset took 300.0940742492676s
Interpretability | Number of blank nodes check for Covid-on-the-Web Dataset took 300.154256105423s
Interpretability | RDF structures check for Covid-on-the-Web Dataset took 0.16342568397521973s
Versatility | Serialization formats check for Covid-on-the-Web Dataset took 0.19609975814819336s
Availability | RDF dump link check for Covid-on-the-Web Dataset took 8.0532808303833s
License | MR license check for Covid-on-the-Web Dataset took 0.4821741580963135s
License | HR license check for Covid-on-the-Web Dataset took 300.10755944252014s
Amount of data | Number of property check for Covid-on-the-Web Dataset took 0.177534818649292s
Understandability | Number of label check for Covid-on-the-Web Dataset took 2.1681549549102783s
Understandability | URI regex check for Covid-on-the-Web Dataset took 0.3573496341705322s
Understandability | Vocabs check for Covid-on-the-Web Dataset took 0.11887931823730469s
Verifiability | Authors check for Covid-on-the-Web Dataset took 0.12055397033691406s
Verifiability | Publishers check for Covid-on-the-Web Dataset took 0.13373208045959473s
Performance | Throughput check for Covid-on-the-Web Dataset took 10.65056848526001s
Amount of data | Check the number of entities for Covid-on-the-Web Dataset took 0.09961414337158203s
Verifiability | Contribs. check for Covid-on-the-Web Dataset took 0.12461280822753906s
Interlinking | sameAs chians check for Covid-on-the-Web Dataset took 0.13182711601257324s
Interlinking | skos check for Covid-on-the-Web Dataset took 0.1209709644317627s
Interlinking | skos check for Covid-on-the-Web Dataset took 0.10977387428283691s
Timeliness | dataset update frequency check for Covid-on-the-Web Dataset took 0.3041725158691406s
Currency | Creation date check for Covid-on-the-Web Dataset took 0.25254082679748535s
Currency | Modification date check for Covid-on-the-Web Dataset took 0.27130699157714844s
Rep.Conc. | URIs length for Covid-on-the-Web Dataset took 42.2082040309906s
Interoperability | New vocabularies check for Covid-on-the-Web Dataset took 18.266749620437622s
Consistency | Deprecated classes/propertiers check for Covid-on-the-Web Dataset took 0.11988019943237305s
Accuracy | Check Functional Property for Covid-on-the-Web Dataset took 0.25660181045532227s
Accuracy | Check Inverse Functional Property for Covid-on-the-Web Dataset took 0.24238896369934082s
Accuracy | Check Empty annotation labels for Covid-on-the-Web Dataset took 1.0190532207489014s
Accuracy | Check White space in annotation for Covid-on-the-Web Dataset took 0.08419561386108398s
Accuracy | Check Datatype consistency for Covid-on-the-Web Dataset took 0.08135366439819336s
Consistency | Disjoint class check for Covid-on-the-Web Dataset took 0.12521982192993164s
Consistency | Check Misplaced properties for Covid-on-the-Web Dataset took 49.7477822303772s
Consistency | Misplaced classes for Covid-on-the-Web Dataset took 1.059852123260498s
Consistency | Check Ontology hijacking for Covid-on-the-Web Dataset took 2.990809917449951s
Consistency | Check Invalid usage of undefined classes for Covid-on-the-Web Dataset took 1.254575490951538s
Consistency | Check Invalid usage of undefined properties for Covid-on-the-Web Dataset took 32.50331091880798s
Conciseness | Check Extensional conciseness for Covid-on-the-Web Dataset took 0.08481836318969727s
Conciseness | Check Intensional conciseness for Covid-on-the-Web Dataset took 1.3198373317718506s
Security | Sign check for Covid-on-the-Web Dataset took 0.38176488876342773s
Availability | Check URIs Dereferenciability for Covid-on-the-Web Dataset took 1974.7866775989532s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 1.1270577907562256s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020751953125s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 8.821487426757812e-05s
Interoperability | Check the re-using of existing vocabs for Covid-on-the-Web Dataset took 11.514270544052124s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for Covid-on-the-Web took 10633.350758552551s
Availability | SPARQL endpoint availability check for CPA 2008 took 26.203941345214844s
Availability | VoID file availability check for CPA 2008 took 0.0008540153503417969s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.27469491958618164s
Reputation | Calculation of the PageRank for CPA 2008 took 0.021136999130249023s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 6.222724914550781e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.553794860839844e-05s
Believability | Calculation of trust value for CPA 2008 took 5.4836273193359375e-06s
INFO | --- Analysis for cpa-2008 took 127.06837892532349s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.4945085048675537s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0005965232849121094s
Extra | Recovery of all triples for Cooperative Patent Classification took 21.517303228378296s
Performance | Total latancy measurement for Cooperative Patent Classification took 0.9506685733795166s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.16724705696106s
Versatility | Languages check for Cooperative Patent Classification took 120.13044714927673s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.35555291175842s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.2677574157714844s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.280991792678833s
Availability | RDF dump link check for Cooperative Patent Classification took 0.2260587215423584s
License | MR license check for Cooperative Patent Classification took 0.22286486625671387s
License | HR license check for Cooperative Patent Classification took 90.53428769111633s
Amount of data | Number of property check for Cooperative Patent Classification took 0.21786904335021973s
Understandability | Number of label check for Cooperative Patent Classification took 90.27202558517456s
Understandability | URI regex check for Cooperative Patent Classification took 0.5697228908538818s
Understandability | Vocabs check for Cooperative Patent Classification took 0.22633123397827148s
Verifiability | Authors check for Cooperative Patent Classification took 0.23748302459716797s
Verifiability | Publishers check for Cooperative Patent Classification took 0.2391371726989746s
Performance | Throughput check for Cooperative Patent Classification took 10.854056119918823s
Amount of data | Check the number of entities for Cooperative Patent Classification took 6.937980651855469e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.22540688514709473s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.22060894966125488s
Interlinking | skos check for Cooperative Patent Classification took 0.20551061630249023s
Interlinking | skos check for Cooperative Patent Classification took 0.24257850646972656s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.3323390483856201s
Currency | Creation date check for Cooperative Patent Classification took 0.37969207763671875s
Currency | Modification date check for Cooperative Patent Classification took 0.48844432830810547s
Rep.Conc. | URIs length for Cooperative Patent Classification took 149.79992079734802s
Interoperability | New vocabularies check for Cooperative Patent Classification took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.34960269927978516s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 15.26163363456726s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.97894549369812s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.940094709396362s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.24259686470031738s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.49170160293579s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 18.15628671646118s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.5910980701446533s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.59039402008057s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.861621379852295s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.4541308879852295s
Security | Sign check for Cooperative Patent Classification took 0.23639178276062012s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.8703479766845703s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.9684164524078369s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.020704984664916992s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 4.38690185546875e-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 7.867813110351562e-06s
INFO | --- Analysis for CPC took 1279.7989087104797s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.458898305892944s
Availability | VoID file availability check for CPC 2008 took 0.0008533000946044922s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.2875347137451172s
Reputation | Calculation of the PageRank for CPC 2008 took 0.0205535888671875s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.8160552978515625e-05s
Believability | Calculation of trust value for CPC 2008 took 4.76837158203125e-06s
INFO | --- Analysis for cpc-2008 took 125.160325050354s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.99160385131836s
Availability | VoID file availability check for CPV  2003 took 0.0009100437164306641s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.32470178604125977s
Reputation | Calculation of the PageRank for CPV  2003 took 0.02037978172302246s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.886222839355469e-05s
Believability | Calculation of trust value for CPV  2003 took 5.245208740234375e-06s
INFO | --- Analysis for cpv-2003 took 114.95263361930847s
Availability | SPARQL endpoint availability check for CPV 2008 took 25.937699556350708s
Availability | VoID file availability check for CPV 2008 took 0.0008916854858398438s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.2619619369506836s
Reputation | Calculation of the PageRank for CPV 2008 took 0.020325899124145508s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.76837158203125e-05s
Believability | Calculation of trust value for CPV 2008 took 5.0067901611328125e-06s
INFO | --- Analysis for cpv-2008 took 124.91688060760498s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 261.34512543678284s
Availability | VoID file availability check for crowdsourcing-fb took 0.0003299713134765625s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 1.1952612400054932s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.021546125411987305s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0008232593536376953s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.935264587402344e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 7.867813110351562e-06s
INFO | --- Analysis for crowdsourcing-fb took 536.2834033966064s
Availability | SPARQL endpoint availability check for CRTM took 4.982948303222656e-05s
Availability | VoID file availability check for CRTM took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for CRTM took 0.2723813056945801s
Reputation | Calculation of the PageRank for CRTM took 0.02032756805419922s
Interlinking | Calculation of Degree of Connection for CRTM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CRTM took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for CRTM took 2.9325485229492188e-05s
Believability | Calculation of trust value for CRTM took 6.9141387939453125e-06s
INFO | --- Analysis for crtm took 3.7938408851623535s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 4.172325134277344e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.23215222358703613s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.02010035514831543s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 3.147125244140625e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 6.4373016357421875e-06s
INFO | --- Analysis for crystal-eye took 2.8654236793518066s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.67882513999939s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.28846096992492676s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020285606384277344s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 5.4836273193359375e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 5.0067901611328125e-06s
INFO | --- Analysis for ctic-public-dataset took 43.82712268829346s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 4.172325134277344e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.6902334690093994s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.02026534080505371s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 2.8371810913085938e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 7.152557373046875e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 3.666912794113159s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 2.84049391746521s
Availability | VoID file availability check for CulturaLinkedData took 0.0005016326904296875s
Extra | Recovery of all triples for CulturaLinkedData took 146.25731992721558s
Performance | Total latancy measurement for CulturaLinkedData took 2.782292366027832s
Amount of data | Number of triples check for CulturaLinkedData took 4.8446433544158936s
Interoperability | New terms check for CulturaLinkedData took 2.18398380279541s
Versatility | Languages check for CulturaLinkedData took 61.46046590805054s
Interpretability | Number of blank nodes check for CulturaLinkedData took 2.0275893211364746s
Interpretability | RDF structures check for CulturaLinkedData took 2.186138391494751s
Versatility | Serialization formats check for CulturaLinkedData took 0.3825185298919678s
Availability | RDF dump link check for CulturaLinkedData took 2.077035665512085s
License | MR license check for CulturaLinkedData took 0.5132458209991455s
License | HR license check for CulturaLinkedData took 60.51138472557068s
Amount of data | Number of property check for CulturaLinkedData took 2.066894054412842s
Understandability | Number of label check for CulturaLinkedData took 0.9917426109313965s
Understandability | URI regex check for CulturaLinkedData took 0.5417895317077637s
Understandability | Vocabs check for CulturaLinkedData took 0.24554133415222168s
Verifiability | Authors check for CulturaLinkedData took 0.2888619899749756s
Verifiability | Publishers check for CulturaLinkedData took 2.0732944011688232s
Performance | Throughput check for CulturaLinkedData took 22.488725423812866s
Amount of data | Check the number of entities for CulturaLinkedData took 7.462501525878906e-05s
Verifiability | Contribs. check for CulturaLinkedData took 2.0953476428985596s
Interlinking | sameAs chians check for CulturaLinkedData took 0.3727543354034424s
Interlinking | skos check for CulturaLinkedData took 0.4952976703643799s
Interlinking | skos check for CulturaLinkedData took 0.18228888511657715s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.352313756942749s
Currency | Creation date check for CulturaLinkedData took 0.47208237648010254s
Currency | Modification date check for CulturaLinkedData took 4.004714012145996s
Rep.Conc. | URIs length for CulturaLinkedData took 63.66774868965149s
Interoperability | New vocabularies check for CulturaLinkedData took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 1.914581298828125s
Accuracy | Check Functional Property for CulturaLinkedData took 2.011188268661499s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.19933724403381348s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 44.07683062553406s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6103229522705078s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.2816367149353027s
Consistency | Disjoint class check for CulturaLinkedData took 0.21585774421691895s
Consistency | Check Misplaced properties for CulturaLinkedData took 12.477089166641235s
Consistency | Misplaced classes for CulturaLinkedData took 5.980729818344116s
Consistency | Check Ontology hijacking for CulturaLinkedData took 43.371957778930664s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.3770167827606201s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 11.95661187171936s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3932392597198486s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.18120360374450684s
Security | Sign check for CulturaLinkedData took 2.7409825325012207s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 17.196385622024536s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.7868213653564453s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.021419763565063477s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 4.363059997558594e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 1.9073486328125e-06s
Believability | Calculation of trust value for CulturaLinkedData took 8.344650268554688e-06s
INFO | --- Analysis for culturalinkeddata took 678.911661863327s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.4698777198791504s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2698793411254883s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020405054092407227s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.981590270996094e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-ares-or took 4.050283193588257s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11563849449157715s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.25557661056518555s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.02069830894470215s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.743171691894531e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 5.245208740234375e-06s
INFO | --- Analysis for cz-ares-rzp took 3.2639591693878174s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11682963371276855s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.26473331451416016s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.6716461181640625e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 4.76837158203125e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 3.3320205211639404s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.10075116157531738s
Availability | VoID file availability check for Integrated pollution registry took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.2940332889556885s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.933906555175781e-05s
Believability | Calculation of trust value for Integrated pollution registry took 5.245208740234375e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.8375158309936523s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.11098647117614746s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.26733827590942383s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.020833492279052734s
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.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 4.1484832763671875e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 5.9604644775390625e-06s
INFO | --- Analysis for cz-contracts took 3.1409482955932617s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 4.100799560546875e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.2796344757080078s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.020476102828979492s
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.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 3.0279159545898438e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 6.198883056640625e-06s
INFO | --- Analysis for cz-courts took 2.862308979034424s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.10487866401672363s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0008714199066162109s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.28046631813049316s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 5.245208740234375e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 4.76837158203125e-06s
INFO | --- Analysis for cz-ctia-bans took 14.153211116790771s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.11368250846862793s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0007786750793457031s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.25522875785827637s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.6716461181640625e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 5.7220458984375e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.7006990909576416s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.10950827598571777s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.24883675575256348s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.02082657814025879s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.6716461181640625e-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.7500152587890625s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.1136167049407959s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.25261545181274414s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020903348922729492s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.38690185546875e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.7596418857574463s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.1127462387084961s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.23873066902160645s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.528594970703125e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 5.245208740234375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 6.456995487213135s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.20489120483398438s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.2702443599700928s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.02069687843322754s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.00543212890625e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 5.245208740234375e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 2.8850221633911133s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.11317610740661621s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0008828639984130859s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.266970157623291s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.02086806297302246s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.528594970703125e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 5.4836273193359375e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 2.7584457397460938s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.6168885231018066s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.2612740993499756s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020910978317260742s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.0531158447265625e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.4715497493743896s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.3543710708618164s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.25910091400146484s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.02092599868774414s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.696846008300781e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.1902425289154053s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.3583984375s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.327744722366333s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.124641418457031e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.9604644775390625e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.319324016571045s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.3380298614501953s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.27964186668395996s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.021126270294189453s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.673004150390625e-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.1665422916412354s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.3722376823425293s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.27002453804016113s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.076957702636719e-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.2063448429107666s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.35798215866088867s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2593042850494385s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.695487976074219e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 5.7220458984375e-06s
INFO | --- Analysis for cz-czso-regions took 2.9550344944000244s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3265562057495117s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.2561194896697998s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.933906555175781e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.2306199073791504s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.340975284576416s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2646825313568115s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020505666732788086s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.649162292480469e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.1339428424835205s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.34360384941101074s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.24418425559997559s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.886222839355469e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.1832656860351562s
Availability | SPARQL endpoint availability check for ATC groups took 0.10895538330078125s
Availability | VoID file availability check for ATC groups took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for ATC groups took 0.2623131275177002s
Reputation | Calculation of the PageRank for ATC groups took 0.02068805694580078s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.319450378417969e-05s
Believability | Calculation of trust value for ATC groups took 7.62939453125e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.6921961307525635s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.11017608642578125s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.2553751468658447s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 6.556510925292969e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 4.76837158203125e-06s
INFO | --- Analysis for cz-fulfillments took 2.749971866607666s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.05401611328125s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.251018762588501s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 5.1021575927734375e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ic took 3.08247709274292s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.1357564926147461s
Availability | VoID file availability check for List of Czech data boxes took 0.0003521442413330078s
Extra | Recovery of all triples for List of Czech data boxes took 143.51283168792725s
Performance | Total latancy measurement for List of Czech data boxes took 0.5876913070678711s
Amount of data | Number of triples check for List of Czech data boxes took 10.195922136306763s
Interoperability | New terms check for List of Czech data boxes took 11.922770261764526s
Versatility | Languages check for List of Czech data boxes took 300.0963888168335s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.209291696548462s
Interpretability | RDF structures check for List of Czech data boxes took 0.14480948448181152s
Versatility | Serialization formats check for List of Czech data boxes took 0.17656993865966797s
Availability | RDF dump link check for List of Czech data boxes took 14.576162815093994s
License | MR license check for List of Czech data boxes took 1.024144172668457s
License | HR license check for List of Czech data boxes took 56.771939277648926s
Amount of data | Number of property check for List of Czech data boxes took 0.1427454948425293s
Understandability | Number of label check for List of Czech data boxes took 1.6947927474975586s
Understandability | URI regex check for List of Czech data boxes took 0.9743609428405762s
Understandability | Vocabs check for List of Czech data boxes took 0.10902857780456543s
Verifiability | Authors check for List of Czech data boxes took 0.1343393325805664s
Verifiability | Publishers check for List of Czech data boxes took 0.12133979797363281s
Performance | Throughput check for List of Czech data boxes took 10.889684677124023s
Amount of data | Check the number of entities for List of Czech data boxes took 3.109866142272949s
Verifiability | Contribs. check for List of Czech data boxes took 0.12690234184265137s
Interlinking | sameAs chians check for List of Czech data boxes took 0.5765604972839355s
Interlinking | skos check for List of Czech data boxes took 0.2655980587005615s
Interlinking | skos check for List of Czech data boxes took 0.1137537956237793s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.34509754180908203s
Currency | Creation date check for List of Czech data boxes took 0.23355650901794434s
Currency | Modification date check for List of Czech data boxes took 0.12926554679870605s
Rep.Conc. | URIs length for List of Czech data boxes took 112.13655185699463s
Interoperability | New vocabularies check for List of Czech data boxes took 10.727748155593872s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.3711991310119629s
Accuracy | Check Functional Property for List of Czech data boxes took 0.3839566707611084s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.40375638008117676s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 30.896865606307983s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.022083282470703s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.5267248153686523s
Consistency | Disjoint class check for List of Czech data boxes took 0.11473298072814941s
Consistency | Check Misplaced properties for List of Czech data boxes took 71.71747660636902s
Consistency | Misplaced classes for List of Czech data boxes took 7.458845376968384s
Consistency | Check Ontology hijacking for List of Czech data boxes took 33.34056234359741s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.4105315208435059s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 63.46728730201721s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.670974016189575s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.4149601459503174s
Security | Sign check for List of Czech data boxes took 0.14909052848815918s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 353.29246950149536s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.7908775806427002s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.02097177505493164s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 9.96215534210205s
Believability | Calculation of trust value for List of Czech data boxes took 5.4836273193359375e-06s
INFO | --- Analysis for cz-list-of-databoxes took 1606.6477100849152s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10953783988952637s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0005822181701660156s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 146.00652647018433s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5727274417877197s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.43789553642273s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.952861309051514s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.14539217948914s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3679704666137695s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17566132545471191s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.20723724365234375s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 14.669384241104126s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10596466064453125s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 56.172301054000854s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13202500343322754s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.477072238922119s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.237717866897583s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13234925270080566s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13083219528198242s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1053459644317627s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.677579402923584s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.304964303970337s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12440347671508789s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6574156284332275s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1298673152923584s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12900090217590332s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12553071975708008s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.26965975761413574s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12836384773254395s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 113.48679184913635s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 16.379218339920044s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.39885926246643066s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3679182529449463s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4174351692199707s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 35.232337474823s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0220837593078613s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.5847690105438232s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11847138404846191s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 70.05903697013855s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.4304258823394775s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 34.202715158462524s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3592779636383057s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 62.7598078250885s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.7107818126678467s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4071686267852783s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.19423961639404297s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 355.9066014289856s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4132106304168701s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.021042346954345703s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.814697265625e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.18895673751831s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 6.67572021484375e-06s
INFO | --- Analysis for cz-nace took 1614.9804091453552s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3258512020111084s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0006308555603027344s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 394.12686133384705s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8198835849761963s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.8129372596740723s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.7526206970214844s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 300.1242833137512s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.5395824909210205s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.42849063873291016s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 6.051527500152588s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3901510238647461s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8407578468322754s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.3409535884857178s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16936111450195312s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5916004180908203s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5081536769866943s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.24003124237060547s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4139280319213867s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3011012077331543s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.711763620376587s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.009506225585938e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.23260855674743652s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2075817584991455s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.47395849227905273s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15834546089172363s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.8409957885742188s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5613532066345215s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4261455535888672s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 97.90199303627014s
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.16814589500427246s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3972902297973633s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.37369847297668457s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 79.0328540802002s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.3765764236450195s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.7635397911071777s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.22441482543945312s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 6.779075622558594s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.149503707885742s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 78.21806597709656s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.8113508224487305s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.451088905334473s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.1973490715026855s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.25254058837890625s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.306121826171875s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 932.6154642105103s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.7172510623931885s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.021605730056762695s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007979869842529297s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.863739013671875e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.9073486328125e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 5.9604644775390625e-06s
INFO | --- Analysis for cz-nkod took 30845.186942338943s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.22608637809753418s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.2681403160095215s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020461320877075195s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.504753112792969e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 5.245208740234375e-06s
INFO | --- Analysis for cz-orders took 2.840501308441162s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.19822287559509277s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0006358623504638672s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 142.775484085083s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.5974249839782715s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 9.509173393249512s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 10.946887493133545s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.13362431526184s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.3405890464782715s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.12856578826904297s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.1961655616760254s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 14.698698997497559s
License | MR license check for Institutions of public power of the Czech Republic took 0.49582982063293457s
License | HR license check for Institutions of public power of the Czech Republic took 55.79728126525879s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.12624788284301758s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.9095432758331299s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.7091913223266602s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.11617898941040039s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.13191628456115723s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.12705135345458984s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.5957612991333s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.3140463829040527s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.14839696884155273s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.457674503326416s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.20073986053466797s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.11364960670471191s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.2613840103149414s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.26468944549560547s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.13324451446533203s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 113.18942975997925s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 9.94750452041626s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.35079169273376465s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.2026820182800293s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.17228412628173828s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 33.066526889801025s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.0311381816864014s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.5990450382232666s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.13166046142578125s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 74.68614912033081s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.46851921081543s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 34.06608247756958s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.437675952911377s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 67.39366626739502s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.618687868118286s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.42172765731811523s
Security | Sign check for Institutions of public power of the Czech Republic took 0.2150423526763916s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 350.830956697464s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.9145584106445312s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.021188735961914062s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 9.860704898834229s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-ovm took 1612.5305964946747s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.10857605934143066s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.24771428108215332s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.02071404457092285s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.4332275390625e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ovm-agendas took 2.6945998668670654s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.09946894645690918s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007162094116210938s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 59.81553912162781s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.558415412902832s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 21.18956971168518s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 36.5947847366333s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.1633677482605s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.15155315399169922s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6859736442565918s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10663008689880371s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7610552310943604s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12697339057922363s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11192536354064941s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1230926513671875s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.9786620140075684s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.22046613693237305s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12336206436157227s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.17630624771118164s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12131118774414062s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.691844940185547s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.62939453125e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12486147880554199s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12430024147033691s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12929987907409668s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10146737098693848s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11630606651306152s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.22339820861816406s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11165261268615723s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 242.3599853515625s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.20242547988891602s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12759804725646973s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1140592098236084s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 13.459269046783447s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.186384439468384s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.6039342880249023s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12349653244018555s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 185.2096884250641s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.248687982559204s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 18.000543117523193s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.3840453624725342s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 186.61870980262756s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.925414562225342s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.27175331115722656s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10776948928833008s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 25.00978374481201s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.9849340915679932s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.021058320999145508s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.367134094238281e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.6689300537109375e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.198883056640625e-06s
INFO | --- Analysis for cz-ruian took 1542.6512756347656s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.6900815963745117s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.28090882301330566s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.224082946777344e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 1.4066696166992188e-05s
INFO | --- Analysis for cz-sao-audited-subjects took 4.084779739379883s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.4610762596130371s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.2841787338256836s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020307540893554688s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.790855407714844e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 4.0531158447265625e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.962787389755249s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.4783787727355957s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.26766085624694824s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020312070846557617s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.0517578125e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 4.0531158447265625e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 3.5048577785491943s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10890793800354004s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.2632927894592285s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020336389541625977s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.743171691894531e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 2.7579312324523926s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.11205267906188965s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007126331329345703s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.258685827255249s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.02019333839416504s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.147125244140625e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.7509429454803467s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.1170806884765625s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.2646903991699219s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.02019214630126953s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.600120544433594e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 7.152557373046875e-06s
INFO | --- Analysis for cz-sidc-drugs took 2.814053535461426s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.19978880882263184s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0005831718444824219s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 146.69221591949463s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5903422832489014s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 9.693176031112671s
Interoperability | New terms check for Summary types of Czech institutions of public power took 11.445053577423096s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.1267440319061s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.5523242950439453s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.15249204635620117s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.21721529960632324s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 14.349840641021729s
License | MR license check for Summary types of Czech institutions of public power took 0.13194799423217773s
License | HR license check for Summary types of Czech institutions of public power took 54.779540061950684s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.13850069046020508s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.7058818340301514s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.6721763610839844s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.12806320190429688s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.14185380935668945s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.12634778022766113s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.619970798492432s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.11436128616333s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.12699604034423828s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.5162498950958252s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.25694990158081055s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.13066601753234863s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.34268951416015625s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.2551994323730469s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.13251852989196777s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 113.82925486564636s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 10.995721578598022s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.409437894821167s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.315887451171875s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.12134766578674316s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 32.8943247795105s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.0568220615386963s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.668274164199829s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.11985206604003906s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 69.67763113975525s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.53789210319519s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 31.801201820373535s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.3896043300628662s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 61.941766023635864s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.6360459327697754s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.40141725540161133s
Security | Sign check for Summary types of Czech institutions of public power took 0.11677765846252441s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 359.5657835006714s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 1.0795974731445312s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.021441936492919922s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.8160552978515625e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 9.37800908088684s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 5.245208740234375e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 1610.024246931076s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.11643767356872559s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0010898113250732422s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.26747560501098633s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.552436828613281e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 3.2270712852478027s
Availability | SPARQL endpoint availability check for State funding providers took 0.10856986045837402s
Availability | VoID file availability check for State funding providers took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for State funding providers took 0.6937747001647949s
Reputation | Calculation of the PageRank for State funding providers took 0.0203397274017334s
Interlinking | Calculation of Degree of Connection for State funding providers took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for State funding providers took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.838539123535156e-05s
Believability | Calculation of trust value for State funding providers took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 3.2083189487457275s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.11636185646057129s
Availability | VoID file availability check for Organizations active in R&D took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.26450276374816895s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.220008850097656e-05s
Believability | Calculation of trust value for Organizations active in R&D took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-organizations took 2.894191265106201s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.11242413520812988s
Availability | VoID file availability check for R&D Programmes took 0.000911712646484375s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.2649965286254883s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020241260528564453s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.001026153564453125s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.982948303222656e-05s
Believability | Calculation of trust value for R&D Programmes took 5.9604644775390625e-06s
INFO | --- Analysis for cz-vavai-programmes took 2.75864577293396s
Availability | SPARQL endpoint availability check for R&D Projects took 0.10160017013549805s
Availability | VoID file availability check for R&D Projects took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.2636101245880127s
Reputation | Calculation of the PageRank for R&D Projects took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.100799560546875e-05s
Believability | Calculation of trust value for R&D Projects took 4.0531158447265625e-06s
INFO | --- Analysis for cz-vavai-projects took 2.7276315689086914s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.10934305191040039s
Availability | VoID file availability check for Institutional research plans took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.23413419723510742s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020208120346069336s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.00543212890625e-05s
Believability | Calculation of trust value for Institutional research plans took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.721146821975708s
Availability | SPARQL endpoint availability check for Results of R&D took 0.09976410865783691s
Availability | VoID file availability check for Results of R&D took 0.0008325576782226562s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.25391364097595215s
Reputation | Calculation of the PageRank for Results of R&D took 0.020325422286987305s
Interlinking | Calculation of Degree of Connection for Results of R&D took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.100799560546875e-05s
Believability | Calculation of trust value for Results of R&D took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-results took 2.716984987258911s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.11669015884399414s
Availability | VoID file availability check for Tenders in R&D took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.2833240032196045s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.020386695861816406s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007305145263671875s
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 4.5299530029296875e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.7771096229553223s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.5299530029296875e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.26091980934143066s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020518064498901367s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.4332275390625e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 6.67572021484375e-06s
INFO | --- Analysis for czech_addresses took 4.103089094161987s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.7097256183624268s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.2578880786895752s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020314455032348633s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for DanteLatinLoanwords took 4.254415035247803s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.3762631416320801s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.000637054443359375s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 143.17792868614197s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 0.9771947860717773s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 9.96019196510315s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.365326642990112s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.26193284988403s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.21202731132507324s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.10943460464477539s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 1.076704502105713s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.4050025939941406s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.3904304504394531s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 1.8464884757995605s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 74.68579244613647s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.2115170955657959s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 3.820410966873169s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.5829794406890869s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.20136213302612305s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.3938181400299072s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.20737576484680176s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.362720251083374s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 8.177757263183594e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.18380284309387207s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.418642520904541s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.0798630714416504s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.939333438873291s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.20197653770446777s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 1.1923511028289795s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 0.8550281524658203s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 83.59817671775818s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.1825542449951172s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.24401140213012695s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.235093355178833s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 38.11352777481079s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.1896066665649414s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.5359139442443848s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.22186803817749023s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 21.93773341178894s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.452540874481201s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 46.452070236206055s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.4705836772918701s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 23.124971866607666s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.8432819843292236s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.21886754035949707s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.5239081382751465s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 13.5192551612854s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 1.4820992946624756s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.02087998390197754s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014925003051757812s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 2.1457672119140625e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 6.67572021484375e-06s
INFO | --- Analysis for data-bnf-fr took 786.439346075058s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.09050893783569336s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005507469177246094s
Extra | Recovery of all triples for Open Data from the Italian National Research Council took 0.7591631412506104s
Performance | Total latancy measurement for Open Data from the Italian National Research Council took 0.2696070671081543s
Amount of data | Number of triples check for Open Data from the Italian National Research Council took 5.410184144973755s
Interoperability | New terms check for Open Data from the Italian National Research Council took 2.3282365798950195s
Versatility | Languages check for Open Data from the Italian National Research Council took 0.05514383316040039s
Interpretability | Number of blank nodes check for Open Data from the Italian National Research Council took 0.5605678558349609s
Security | Check HTTPS for Open Data from the Italian National Research Council took 0.03793692588806152s
Interpretability | RDF structures check for Open Data from the Italian National Research Council took 0.0710752010345459s
Versatility | Serialization formats check for Open Data from the Italian National Research Council took 0.06350445747375488s
Availability | RDF dump link check for Open Data from the Italian National Research Council took 0.05349326133728027s
License | MR license check for Open Data from the Italian National Research Council took 0.06134653091430664s
License | HR license check for Open Data from the Italian National Research Council took 12.186761140823364s
Amount of data | Number of property check for Open Data from the Italian National Research Council took 0.0639498233795166s
Understandability | Number of label check for Open Data from the Italian National Research Council took 3.7841544151306152s
Understandability | URI regex check for Open Data from the Italian National Research Council took 0.11754345893859863s
Understandability | Vocabs check for Open Data from the Italian National Research Council took 0.06140470504760742s
Verifiability | Authors check for Open Data from the Italian National Research Council took 0.0604400634765625s
Verifiability | Publishers check for Open Data from the Italian National Research Council took 0.059472084045410156s
Performance | Throughput check for Open Data from the Italian National Research Council took 11.919811010360718s
Amount of data | Check the number of entities for Open Data from the Italian National Research Council took 7.510185241699219e-05s
Verifiability | Contribs. check for Open Data from the Italian National Research Council took 0.05985665321350098s
Interlinking | sameAs chians check for Open Data from the Italian National Research Council took 0.06160283088684082s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.0592503547668457s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.056307315826416016s
Timeliness | dataset update frequency check for Open Data from the Italian National Research Council took 0.06071734428405762s
Currency | Creation date check for Open Data from the Italian National Research Council took 0.12334728240966797s
Currency | Modification date check for Open Data from the Italian National Research Council took 0.1328575611114502s
Rep.Conc. | URIs length for Open Data from the Italian National Research Council took 11.57327675819397s
Interoperability | New vocabularies check for Open Data from the Italian National Research Council took 1.8619201183319092s
Consistency | Deprecated classes/propertiers check for Open Data from the Italian National Research Council took 0.05774664878845215s
Accuracy | Check Functional Property for Open Data from the Italian National Research Council took 0.05708956718444824s
Accuracy | Check Inverse Functional Property for Open Data from the Italian National Research Council took 0.054296016693115234s
Accuracy | Check Empty annotation labels for Open Data from the Italian National Research Council took 0.3102602958679199s
Accuracy | Check White space in annotation for Open Data from the Italian National Research Council took 0.03189682960510254s
Accuracy | Check Datatype consistency for Open Data from the Italian National Research Council took 0.0286099910736084s
Consistency | Disjoint class check for Open Data from the Italian National Research Council took 0.053412675857543945s
Consistency | Check Misplaced properties for Open Data from the Italian National Research Council took 10.012844800949097s
Consistency | Misplaced classes for Open Data from the Italian National Research Council took 0.15330100059509277s
Consistency | Check Ontology hijacking for Open Data from the Italian National Research Council took 1.6343491077423096s
Consistency | Check Invalid usage of undefined classes for Open Data from the Italian National Research Council took 1.4120032787322998s
Consistency | Check Invalid usage of undefined properties for Open Data from the Italian National Research Council took 12.056687831878662s
Conciseness | Check Extensional conciseness for Open Data from the Italian National Research Council took 0.03392505645751953s
Conciseness | Check Intensional conciseness for Open Data from the Italian National Research Council took 0.07786846160888672s
Security | Sign check for Open Data from the Italian National Research Council took 0.05335593223571777s
Availability | Check URIs Dereferenciability for Open Data from the Italian National Research Council took 488.6378855705261s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.8273847103118896s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.021353960037231445s
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 8.20159912109375e-05s
Interoperability | Check the re-using of existing vocabs for Open Data from the Italian National Research Council took 1.534238338470459s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 5.4836273193359375e-06s
INFO | --- Analysis for data-cnr-it took 595.2992422580719s
Availability | SPARQL endpoint availability check for Data.gov took 1.2225372791290283s
Availability | VoID file availability check for Data.gov took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Data.gov took 0.25330257415771484s
Reputation | Calculation of the PageRank for Data.gov took 0.02072763442993164s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.218650817871094e-05s
Believability | Calculation of trust value for Data.gov took 5.9604644775390625e-06s
INFO | --- Analysis for data-gov took 18.767468452453613s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.16635966300964355s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.25917911529541016s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.02075505256652832s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.914138793945312e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 4.5299530029296875e-06s
INFO | --- Analysis for data-gov-ie took 3.121619939804077s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.315376281738281e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.2633943557739258s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.2479248046875e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 5.7220458984375e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.453536033630371s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 22.158900022506714s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.7037920951843262s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02113652229309082s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.818771362304688e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 8.58306884765625e-06s
INFO | --- Analysis for data-hnm-hu took 165.88885164260864s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.1518867015838623s
Availability | VoID file availability check for Climb Dataincubator took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.254941463470459s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020459413528442383s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.390975952148438e-05s
Believability | Calculation of trust value for Climb Dataincubator took 7.62939453125e-06s
INFO | --- Analysis for data-incubator-climb took 2.5048863887786865s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.482269287109375e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0007462501525878906s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.7290120124816895s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020359516143798828s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.465217590332031e-05s
Believability | Calculation of trust value for Discogs in RDF took 6.67572021484375e-06s
INFO | --- Analysis for data-incubator-discogs took 7.3250346183776855s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.05340719223022461s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0007982254028320312s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.26895809173583984s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 6.270408630371094e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 5.0067901611328125e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.374464750289917s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.055917978286743164s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0009195804595947266s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.2650482654571533s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020916223526000977s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 9.202957153320312e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 6.198883056640625e-06s
INFO | --- Analysis for data-incubator-moseley took 8.573585748672485s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.04829120635986328s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.25429606437683105s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.630752563476562e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.4075512886047363s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 4.457050085067749s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0007762908935546875s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.25815534591674805s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.02051997184753418s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0008139610290527344s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 9.441375732421875e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 4.76837158203125e-06s
INFO | --- Analysis for data-incubator-nasa took 11.913435220718384s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.06644582748413086s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.24768424034118652s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.021016359329223633s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.677078247070312e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 7.62939453125e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.517666816711426s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.07425141334533691s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.27985477447509766s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.020564794540405273s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.465217590332031e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 8.58306884765625e-06s
INFO | --- Analysis for data-incubator-pokedex took 4.111116170883179s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.06538033485412598s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.27071690559387207s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.02068948745727539s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 9.107589721679688e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 7.62939453125e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.472262382507324s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.44704723358154297s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.24385380744934082s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.020306825637817383s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.890296936035156e-05s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 6.9141387939453125e-06s
INFO | --- Analysis for data-open-ac-uk took 3.875415086746216s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.8951809406280518s
Availability | VoID file availability check for Persée in RDF took 0.0006899833679199219s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.25533199310302734s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020746469497680664s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00010752677917480469s
Believability | Calculation of trust value for Persée in RDF took 7.62939453125e-06s
INFO | --- Analysis for data-persee-fr took 6.875957250595093s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 4.220008850097656e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.24715971946716309s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.020671844482421875s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.0279159545898438e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 7.3909759521484375e-06s
INFO | --- Analysis for data-southampton-ac-uk took 2.8294901847839355s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.1670970916748047s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.250213623046875s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.00087738037109375s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011658668518066406s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 7.867813110351562e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 9.11970329284668s
Availability | SPARQL endpoint availability check for Open Data Web took 0.9588820934295654s
Availability | VoID file availability check for Open Data Web took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.25336217880249023s
Reputation | Calculation of the PageRank for Open Data Web took 0.020259857177734375s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.218650817871094e-05s
Believability | Calculation of trust value for Open Data Web took 7.3909759521484375e-06s
INFO | --- Analysis for data.odw.tw took 3.344118356704712s
Availability | SPARQL endpoint availability check for DataFAQs took 4.076957702636719e-05s
Availability | VoID file availability check for DataFAQs took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.268817663192749s
Reputation | Calculation of the PageRank for DataFAQs took 0.020258188247680664s
Interlinking | Calculation of Degree of Connection for DataFAQs took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 2.956390380859375e-05s
Believability | Calculation of trust value for DataFAQs took 7.867813110351562e-06s
INFO | --- Analysis for datafaqs took 2.8778438568115234s
Availability | SPARQL endpoint availability check for datahub took 4.267692565917969e-05s
Availability | VoID file availability check for datahub took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for datahub took 0.2747979164123535s
Reputation | Calculation of the PageRank for datahub took 0.02066183090209961s
Interlinking | Calculation of Degree of Connection for datahub took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for datahub took 4.696846008300781e-05s
Believability | Calculation of trust value for datahub took 6.4373016357421875e-06s
INFO | --- Analysis for datahub took 5.519665002822876s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 6.1696717739105225s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.25410938262939453s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.1948089599609375e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 8.106231689453125e-06s
INFO | --- Analysis for datahub-kr-datamap took 16.421648740768433s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.4528806209564209s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.24817538261413574s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0203249454498291s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 6.937980651855469e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 6.67572021484375e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 4.910144805908203s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.241732358932495s
Availability | VoID file availability check for datos-artium-org took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.26660895347595215s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011539459228515625s
Believability | Calculation of trust value for datos-artium-org took 7.152557373046875e-06s
INFO | --- Analysis for datos-artium-org took 164.6858069896698s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.9054334163665771s
Availability | VoID file availability check for Datos.bcn.cl took 0.0006387233734130859s
Extra | Recovery of all triples for Datos.bcn.cl took 32.75723624229431s
Performance | Total latancy measurement for Datos.bcn.cl took 5.939276933670044s
Amount of data | Number of triples check for Datos.bcn.cl took 14.689788341522217s
Interoperability | New terms check for Datos.bcn.cl took 4.331732988357544s
Versatility | Languages check for Datos.bcn.cl took 300.96358346939087s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.215484619140625s
Security | Check HTTPS for Datos.bcn.cl took 0.7207238674163818s
Interpretability | RDF structures check for Datos.bcn.cl took 1.2580435276031494s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2122445106506348s
Availability | RDF dump link check for Datos.bcn.cl took 1.2025279998779297s
License | MR license check for Datos.bcn.cl took 1.2196695804595947s
License | HR license check for Datos.bcn.cl took 56.26139211654663s
Amount of data | Number of property check for Datos.bcn.cl took 1.2727205753326416s
Understandability | Number of label check for Datos.bcn.cl took 2.005335569381714s
Understandability | URI regex check for Datos.bcn.cl took 2.4029767513275146s
Understandability | Vocabs check for Datos.bcn.cl took 1.2160258293151855s
Verifiability | Authors check for Datos.bcn.cl took 1.2228608131408691s
Verifiability | Publishers check for Datos.bcn.cl took 1.1928048133850098s
Performance | Throughput check for Datos.bcn.cl took 12.10507345199585s
Amount of data | Check the number of entities for Datos.bcn.cl took 7.319450378417969e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.2294514179229736s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.1985900402069092s
Interlinking | skos check for Datos.bcn.cl took 1.2187864780426025s
Interlinking | skos check for Datos.bcn.cl took 1.2123873233795166s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.218315839767456s
Currency | Creation date check for Datos.bcn.cl took 2.467050552368164s
Currency | Modification date check for Datos.bcn.cl took 1.2178490161895752s
Rep.Conc. | URIs length for Datos.bcn.cl took 37.26570415496826s
Interoperability | New vocabularies check for Datos.bcn.cl took 3.62396240234375e-05s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.2209289073944092s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.2311975955963135s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.209632396697998s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 8.775074243545532s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.2359769344329834s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.2603416442871094s
Consistency | Disjoint class check for Datos.bcn.cl took 1.2088556289672852s
Consistency | Check Misplaced properties for Datos.bcn.cl took 17.120885372161865s
Consistency | Misplaced classes for Datos.bcn.cl took 2.066108465194702s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 14.746622323989868s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.3098487854003906s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 17.162171840667725s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.30060863494873047s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.482346773147583s
Security | Sign check for Datos.bcn.cl took 1.2035398483276367s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 16.33444309234619s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.0001404285430908s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.02097010612487793s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 9.465217590332031e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.1920928955078125e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 6.4373016357421875e-06s
INFO | --- Analysis for datos-bcn-cl took 1323.3589158058167s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.27979183197021484s
Availability | VoID file availability check for datos.bne.es took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.2672743797302246s
Reputation | Calculation of the PageRank for datos.bne.es took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00013494491577148438s
Believability | Calculation of trust value for datos.bne.es took 8.106231689453125e-06s
INFO | --- Analysis for datos-bne-es took 4.4750752449035645s
Availability | SPARQL endpoint availability check for dbacademic took 0.16527438163757324s
Availability | VoID file availability check for dbacademic took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for dbacademic took 0.2500131130218506s
Reputation | Calculation of the PageRank for dbacademic took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for dbacademic took 2.9087066650390625e-05s
Believability | Calculation of trust value for dbacademic took 6.67572021484375e-06s
INFO | --- Analysis for dbacademic took 2.98872447013855s
Availability | SPARQL endpoint availability check for DBkWik took 3.843160390853882s
Availability | VoID file availability check for DBkWik took 0.0006015300750732422s
Extra | Recovery of all triples for DBkWik took 1.3739149570465088s
Performance | Total latancy measurement for DBkWik took 4.056602954864502s
Amount of data | Number of triples check for DBkWik took 6.679689645767212s
Interoperability | New terms check for DBkWik took 2.337040424346924s
Versatility | Languages check for DBkWik took 61.53485560417175s
Interpretability | Number of blank nodes check for DBkWik took 10.005170583724976s
Interpretability | RDF structures check for DBkWik took 10.08758807182312s
Versatility | Serialization formats check for DBkWik took 10.102530002593994s
Availability | RDF dump link check for DBkWik took 10.002969980239868s
License | MR license check for DBkWik took 10.09548807144165s
License | HR license check for DBkWik took 9.999889135360718s
Amount of data | Number of property check for DBkWik took 10.008061408996582s
Understandability | Number of label check for DBkWik took 10.263788223266602s
Understandability | URI regex check for DBkWik took 3.127479314804077s
Understandability | Vocabs check for DBkWik took 0.12389564514160156s
Verifiability | Authors check for DBkWik took 0.09272170066833496s
Verifiability | Publishers check for DBkWik took 0.09899330139160156s
Performance | Throughput check for DBkWik took 11.129111289978027s
Amount of data | Check the number of entities for DBkWik took 7.224082946777344e-05s
Verifiability | Contribs. check for DBkWik took 0.08775615692138672s
Interlinking | sameAs chians check for DBkWik took 0.4033374786376953s
Interlinking | skos check for DBkWik took 0.38854479789733887s
Interlinking | skos check for DBkWik took 0.09244298934936523s
Timeliness | dataset update frequency check for DBkWik took 0.1989288330078125s
Currency | Creation date check for DBkWik took 0.44425010681152344s
Currency | Modification date check for DBkWik took 2.960820198059082s
Rep.Conc. | URIs length for DBkWik took 11.303766965866089s
Interoperability | New vocabularies check for DBkWik took 2.6112093925476074s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.08971428871154785s
Accuracy | Check Functional Property for DBkWik took 0.2471935749053955s
Accuracy | Check Inverse Functional Property for DBkWik took 0.3148767948150635s
Accuracy | Check Empty annotation labels for DBkWik took 1.136047601699829s
Accuracy | Check White space in annotation for DBkWik took 0.023003578186035156s
Accuracy | Check Datatype consistency for DBkWik took 0.03808450698852539s
Consistency | Disjoint class check for DBkWik took 0.1450178623199463s
Consistency | Check Misplaced properties for DBkWik took 11.780057191848755s
Consistency | Misplaced classes for DBkWik took 7.54511833190918s
Consistency | Check Ontology hijacking for DBkWik took 4.691622734069824s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.2486944198608398s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.784195184707642s
Conciseness | Check Extensional conciseness for DBkWik took 0.035859107971191406s
Conciseness | Check Intensional conciseness for DBkWik took 0.6628291606903076s
Security | Sign check for DBkWik took 0.30039358139038086s
Availability | Check URIs Dereferenciability for DBkWik took 14.925133466720581s
Completeness | Calculation of interlinking completeness for DBkWik took 0.5304403305053711s
Reputation | Calculation of the PageRank for DBkWik took 0.02091836929321289s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for DBkWik took 8.153915405273438e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 2.4716992378234863s
Believability | Calculation of trust value for DBkWik took 7.152557373046875e-06s
INFO | --- Analysis for dbkwik took 1560.2517416477203s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 4.38690185546875e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.25611257553100586s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.020347118377685547s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00011157989501953125s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 7.0797789096832275s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.3530442714691162s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0005934238433837891s
Extra | Recovery of all triples for dblp Knowledge Graph took 8.1434485912323s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.7511265277862549s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.14860320091247559s
Interoperability | New terms check for dblp Knowledge Graph took 1.6863822937011719s
Versatility | Languages check for dblp Knowledge Graph took 6.956806182861328s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 2.2771060466766357s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.14995718002319336s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.14728450775146484s
Availability | RDF dump link check for dblp Knowledge Graph took 0.15996980667114258s
License | MR license check for dblp Knowledge Graph took 0.16855144500732422s
License | HR license check for dblp Knowledge Graph took 30.168586492538452s
Amount of data | Number of property check for dblp Knowledge Graph took 0.1533372402191162s
Understandability | Number of label check for dblp Knowledge Graph took 0.33530545234680176s
Understandability | URI regex check for dblp Knowledge Graph took 0.2776472568511963s
Understandability | Vocabs check for dblp Knowledge Graph took 0.15203022956848145s
Verifiability | Authors check for dblp Knowledge Graph took 0.15659546852111816s
Verifiability | Publishers check for dblp Knowledge Graph took 0.1265242099761963s
Performance | Throughput check for dblp Knowledge Graph took 10.886467218399048s
Amount of data | Check the number of entities for dblp Knowledge Graph took 7.319450378417969e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.1704561710357666s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.2276782989501953s
Interlinking | skos check for dblp Knowledge Graph took 0.1701509952545166s
Interlinking | skos check for dblp Knowledge Graph took 0.14731645584106445s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.1498093605041504s
Currency | Creation date check for dblp Knowledge Graph took 0.2816019058227539s
Currency | Modification date check for dblp Knowledge Graph took 0.2616705894470215s
Rep.Conc. | URIs length for dblp Knowledge Graph took 14.412447452545166s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.14800548553466797s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.14763474464416504s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.14752650260925293s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 6.977126121520996s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.0451512336730957s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.2102203369140625s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.1688404083251953s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.280012845993042s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 5.489163398742676s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 18782.63834452629s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 3.1685211658477783s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.718926191329956s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.18111276626586914s
Security | Sign check for dblp Knowledge Graph took 0.15047287940979004s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 2870.611212015152s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 1.6733932495117188s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.024073362350463867s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.52587890625e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 1.6689300537109375e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 6.9141387939453125e-06s
INFO | --- Analysis for dblp-kg took 21785.937162399292s
Availability | SPARQL endpoint availability check for dbnary took 0.2813277244567871s
Availability | VoID file availability check for dbnary took 0.0005018711090087891s
Extra | Recovery of all triples for dbnary took 1.0560939311981201s
Performance | Total latancy measurement for dbnary took 0.3312413692474365s
Amount of data | Number of triples check for dbnary took 1.1300008296966553s
Interoperability | New terms check for dbnary took 3.607470750808716s
Versatility | Languages check for dbnary took 61.18150353431702s
Interpretability | Number of blank nodes check for dbnary took 1.8480730056762695s
Security | Check HTTPS for dbnary took 0.15651345252990723s
Interpretability | RDF structures check for dbnary took 0.11414098739624023s
Versatility | Serialization formats check for dbnary took 0.23870301246643066s
Availability | RDF dump link check for dbnary took 0.06028938293457031s
License | MR license check for dbnary took 0.2712135314941406s
License | HR license check for dbnary took 58.00817251205444s
Amount of data | Number of property check for dbnary took 0.07660531997680664s
Understandability | Number of label check for dbnary took 0.782254695892334s
Understandability | URI regex check for dbnary took 0.14171552658081055s
Understandability | Vocabs check for dbnary took 0.2030470371246338s
Verifiability | Authors check for dbnary took 0.305065393447876s
Verifiability | Publishers check for dbnary took 0.14601516723632812s
Performance | Throughput check for dbnary took 10.28329610824585s
Amount of data | Check the number of entities for dbnary took 7.462501525878906e-05s
Verifiability | Contribs. check for dbnary took 0.19910287857055664s
Interlinking | sameAs chians check for dbnary took 0.07222795486450195s
Interlinking | skos check for dbnary took 0.25032663345336914s
Interlinking | skos check for dbnary took 0.11415481567382812s
Timeliness | dataset update frequency check for dbnary took 0.14448308944702148s
Currency | Creation date check for dbnary took 0.24788260459899902s
Currency | Modification date check for dbnary took 0.222883939743042s
Rep.Conc. | URIs length for dbnary took 11.130650758743286s
Interoperability | New vocabularies check for dbnary took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.06763553619384766s
Accuracy | Check Functional Property for dbnary took 0.13109254837036133s
Accuracy | Check Inverse Functional Property for dbnary took 0.1450340747833252s
Accuracy | Check Empty annotation labels for dbnary took 0.5152847766876221s
Accuracy | Check White space in annotation for dbnary took 0.02479863166809082s
Accuracy | Check Datatype consistency for dbnary took 0.027254581451416016s
Consistency | Disjoint class check for dbnary took 0.08155465126037598s
Consistency | Check Misplaced properties for dbnary took 8.746843576431274s
Consistency | Misplaced classes for dbnary took 0.19789886474609375s
Consistency | Check Ontology hijacking for dbnary took 1.722097635269165s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.401015043258667s
Consistency | Check Invalid usage of undefined properties for dbnary took 9.964469194412231s
Conciseness | Check Extensional conciseness for dbnary took 0.03267955780029297s
Conciseness | Check Intensional conciseness for dbnary took 0.13677549362182617s
Security | Sign check for dbnary took 0.07002496719360352s
Availability | Check URIs Dereferenciability for dbnary took 16.282257795333862s
Completeness | Calculation of interlinking completeness for dbnary took 0.2699248790740967s
Reputation | Calculation of the PageRank for dbnary took 0.02092266082763672s
Interlinking | Calculation of Degree of Connection for dbnary took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for dbnary took 6.103515625e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.430511474609375e-06s
Believability | Calculation of trust value for dbnary took 7.62939453125e-06s
INFO | --- Analysis for dbnary took 293.78872418403625s
Availability | SPARQL endpoint availability check for DBpedia took 2.4977710247039795s
Availability | VoID file availability check for DBpedia took 0.0007052421569824219s
Extra | Recovery of all triples for DBpedia took 4.989507436752319s
Performance | Total latancy measurement for DBpedia took 2.859438896179199s
Amount of data | Number of triples check for DBpedia took 1.7158873081207275s
Interoperability | New terms check for DBpedia took 5.02953839302063s
Versatility | Languages check for DBpedia took 32.45950722694397s
Interpretability | Number of blank nodes check for DBpedia took 0.5754518508911133s
Security | Check HTTPS for DBpedia took 0.3267087936401367s
Interpretability | RDF structures check for DBpedia took 1.0164482593536377s
Versatility | Serialization formats check for DBpedia took 0.9337222576141357s
Availability | RDF dump link check for DBpedia took 0.7484939098358154s
License | MR license check for DBpedia took 0.8109269142150879s
License | HR license check for DBpedia took 31.46322512626648s
Amount of data | Number of property check for DBpedia took 0.6230635643005371s
Understandability | Number of label check for DBpedia took 6.907392740249634s
Understandability | URI regex check for DBpedia took 1.1816558837890625s
Understandability | Vocabs check for DBpedia took 0.6318140029907227s
Verifiability | Authors check for DBpedia took 0.8839976787567139s
Verifiability | Publishers check for DBpedia took 0.5536797046661377s
Performance | Throughput check for DBpedia took 11.806390762329102s
Amount of data | Check the number of entities for DBpedia took 7.271766662597656e-05s
Verifiability | Contribs. check for DBpedia took 0.5947067737579346s
Interlinking | sameAs chians check for DBpedia took 3.3295042514801025s
Interlinking | skos check for DBpedia took 1.2268497943878174s
Interlinking | skos check for DBpedia took 0.5527389049530029s
Timeliness | dataset update frequency check for DBpedia took 0.5845754146575928s
Currency | Creation date check for DBpedia took 1.2731170654296875s
Currency | Modification date check for DBpedia took 1.1773333549499512s
Rep.Conc. | URIs length for DBpedia took 40.50744986534119s
Interoperability | New vocabularies check for DBpedia took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.6014225482940674s
Accuracy | Check Functional Property for DBpedia took 0.6348495483398438s
Accuracy | Check Inverse Functional Property for DBpedia took 0.6261007785797119s
Accuracy | Check Empty annotation labels for DBpedia took 2.188702344894409s
Accuracy | Check White space in annotation for DBpedia took 0.028885841369628906s
Accuracy | Check Datatype consistency for DBpedia took 0.027032136917114258s
Consistency | Disjoint class check for DBpedia took 0.6104862689971924s
Consistency | Check Misplaced properties for DBpedia took 34.14601016044617s
Consistency | Misplaced classes for DBpedia took 2.6841988563537598s
Consistency | Check Ontology hijacking for DBpedia took 2.928253173828125s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.2397792339324951s
Consistency | Check Invalid usage of undefined properties for DBpedia took 2.217548131942749s
Conciseness | Check Extensional conciseness for DBpedia took 0.033399105072021484s
Conciseness | Check Intensional conciseness for DBpedia took 3.6844980716705322s
Security | Sign check for DBpedia took 2.054940700531006s
Availability | Check URIs Dereferenciability for DBpedia took 1735.927033662796s
Completeness | Calculation of interlinking completeness for DBpedia took 1.0033841133117676s
Reputation | Calculation of the PageRank for DBpedia took 0.02092123031616211s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008938312530517578s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia took 2226.1000139713287s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.38690185546875e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.26977038383483887s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020821571350097656s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.67572021484375e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-abstract-corpus took 8.630465269088745s
Availability | SPARQL endpoint availability check for DBpedia Commons took 4.619809627532959s
Availability | VoID file availability check for DBpedia Commons took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.2635214328765869s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.818771362304688e-05s
Believability | Calculation of trust value for DBpedia Commons took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-commons took 14.859062910079956s
Availability | SPARQL endpoint availability check for DBpedia in German took 6.079673767089844e-05s
Availability | VoID file availability check for DBpedia in German took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.25151538848876953s
Reputation | Calculation of the PageRank for DBpedia in German took 0.02083563804626465s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.866455078125e-05s
Believability | Calculation of trust value for DBpedia in German took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia-de took 2.8848085403442383s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 0.8662559986114502s
Availability | VoID file availability check for DBpedia in Greek took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.2692403793334961s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.02110910415649414s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0008270740509033203s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.0002048015594482422s
Believability | Calculation of trust value for DBpedia in Greek took 4.76837158203125e-06s
INFO | --- Analysis for dbpedia-el took 6.939850568771362s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 1.2214348316192627s
Availability | VoID file availability check for DBpedia in Spanish took 0.00036144256591796875s
Extra | Recovery of all triples for DBpedia in Spanish took 3.0288126468658447s
Performance | Total latancy measurement for DBpedia in Spanish took 1.1714286804199219s
Amount of data | Number of triples check for DBpedia in Spanish took 0.9892661571502686s
Interoperability | New terms check for DBpedia in Spanish took 2.8049397468566895s
Versatility | Languages check for DBpedia in Spanish took 61.79155445098877s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.3466651439666748s
Security | Check HTTPS for DBpedia in Spanish took 0.12635278701782227s
Interpretability | RDF structures check for DBpedia in Spanish took 1.501539707183838s
Versatility | Serialization formats check for DBpedia in Spanish took 0.7492897510528564s
Availability | RDF dump link check for DBpedia in Spanish took 0.3873171806335449s
License | MR license check for DBpedia in Spanish took 1.1096923351287842s
License | HR license check for DBpedia in Spanish took 61.737592935562134s
Amount of data | Number of property check for DBpedia in Spanish took 0.32105517387390137s
Understandability | Number of label check for DBpedia in Spanish took 1.5857045650482178s
Understandability | URI regex check for DBpedia in Spanish took 0.7665648460388184s
Understandability | Vocabs check for DBpedia in Spanish took 0.3640477657318115s
Verifiability | Authors check for DBpedia in Spanish took 0.3091707229614258s
Verifiability | Publishers check for DBpedia in Spanish took 0.2654566764831543s
Performance | Throughput check for DBpedia in Spanish took 11.362584590911865s
Amount of data | Check the number of entities for DBpedia in Spanish took 0.00011897087097167969s
Verifiability | Contribs. check for DBpedia in Spanish took 0.2629363536834717s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.48633408546447754s
Interlinking | skos check for DBpedia in Spanish took 0.8387024402618408s
Interlinking | skos check for DBpedia in Spanish took 0.21428823471069336s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.5021553039550781s
Currency | Creation date check for DBpedia in Spanish took 0.575671911239624s
Currency | Modification date check for DBpedia in Spanish took 0.5554168224334717s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.522719621658325s
Interoperability | New vocabularies check for DBpedia in Spanish took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.2756922245025635s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.458817720413208s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.4334995746612549s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.1405749320983887s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.030256271362304688s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.028386592864990234s
Consistency | Disjoint class check for DBpedia in Spanish took 0.2843163013458252s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.044641017913818s
Consistency | Misplaced classes for DBpedia in Spanish took 1.071190357208252s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.172088384628296s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.3072421550750732s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 6.94045877456665s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03758072853088379s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.328075885772705s
Security | Sign check for DBpedia in Spanish took 0.7779202461242676s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 15.239343166351318s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.2940540313720703s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.020572185516357422s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00011324882507324219s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 5.245208740234375e-06s
INFO | --- Analysis for dbpedia-es took 1235.3894629478455s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 30.48741102218628s
Availability | VoID file availability check for DBpedia in Basque took 0.0007195472717285156s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.28397560119628906s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.933906555175781e-05s
Believability | Calculation of trust value for DBpedia in Basque took 5.245208740234375e-06s
INFO | --- Analysis for dbpedia-eu took 93.11305904388428s
Availability | SPARQL endpoint availability check for DBpedia in French took 1.1093573570251465s
Availability | VoID file availability check for DBpedia in French took 0.0004999637603759766s
Extra | Recovery of all triples for DBpedia in French took 156.97779989242554s
Performance | Total latancy measurement for DBpedia in French took 94.18839430809021s
Amount of data | Number of triples check for DBpedia in French took 8.187770366668701s
Interoperability | New terms check for DBpedia in French took 5.0850913524627686s
Versatility | Languages check for DBpedia in French took 300.09686255455017s
Interpretability | Number of blank nodes check for DBpedia in French took 77.44954633712769s
Interpretability | RDF structures check for DBpedia in French took 9.998894691467285s
Versatility | Serialization formats check for DBpedia in French took 10.006678342819214s
Availability | RDF dump link check for DBpedia in French took 3003.607979297638s
License | MR license check for DBpedia in French took 2.566944122314453s
License | HR license check for DBpedia in French took 300.10515332221985s
Amount of data | Number of property check for DBpedia in French took 6.669688940048218s
Understandability | Number of label check for DBpedia in French took 6.712843894958496s
Understandability | URI regex check for DBpedia in French took 1.4174573421478271s
Understandability | Vocabs check for DBpedia in French took 1.0815963745117188s
Verifiability | Authors check for DBpedia in French took 1.7196054458618164s
Verifiability | Publishers check for DBpedia in French took 0.6398329734802246s
Performance | Throughput check for DBpedia in French took 27.762954473495483s
Amount of data | Check the number of entities for DBpedia in French took 2.233325242996216s
Verifiability | Contribs. check for DBpedia in French took 2.220674514770508s
Interlinking | sameAs chians check for DBpedia in French took 2.139759063720703s
Interlinking | skos check for DBpedia in French took 3.9661221504211426s
Interlinking | skos check for DBpedia in French took 1.6046361923217773s
Timeliness | dataset update frequency check for DBpedia in French took 0.8886110782623291s
Currency | Creation date check for DBpedia in French took 0.6428837776184082s
Currency | Modification date check for DBpedia in French took 2.602276086807251s
Rep.Conc. | URIs length for DBpedia in French took 63.19096899032593s
Interoperability | New vocabularies check for DBpedia in French took 7.510171890258789s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 8.118268251419067s
Accuracy | Check Functional Property for DBpedia in French took 1.2704546451568604s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.45818042755126953s
Accuracy | Check Empty annotation labels for DBpedia in French took 30.67949676513672s
Accuracy | Check White space in annotation for DBpedia in French took 3.0447170734405518s
Accuracy | Check Datatype consistency for DBpedia in French took 2.7024199962615967s
Consistency | Disjoint class check for DBpedia in French took 11.903988122940063s
Consistency | Check Misplaced properties for DBpedia in French took 42.48594641685486s
Consistency | Misplaced classes for DBpedia in French took 37.28822326660156s
Consistency | Check Ontology hijacking for DBpedia in French took 43.607951402664185s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.3359813690185547s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 13.393160104751587s
Conciseness | Check Extensional conciseness for DBpedia in French took 2.9607489109039307s
Conciseness | Check Intensional conciseness for DBpedia in French took 7.223031520843506s
Security | Sign check for DBpedia in French took 3.8241398334503174s
Availability | Check URIs Dereferenciability for DBpedia in French took 4292.621506929398s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.7449929714202881s
Reputation | Calculation of the PageRank for DBpedia in French took 0.02338695526123047s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 8.344650268554688e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.0001590251922607422s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 7.422083616256714s
Believability | Calculation of trust value for DBpedia in French took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia-fr took 9068.040075302124s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.9291255474090576s
Availability | VoID file availability check for DBpedia in Japanese took 4.10681414604187s
Extra | Recovery of all triples for DBpedia in Japanese took 5.563844203948975s
Performance | Total latancy measurement for DBpedia in Japanese took 6.640988111495972s
Amount of data | Number of triples check for DBpedia in Japanese took 29.89776921272278s
Interoperability | New terms check for DBpedia in Japanese took 18.411302089691162s
Versatility | Languages check for DBpedia in Japanese took 1.3243215084075928s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.35707688331604s
Security | Check HTTPS for DBpedia in Japanese took 0.7944669723510742s
Interpretability | RDF structures check for DBpedia in Japanese took 1.3641574382781982s
Versatility | Serialization formats check for DBpedia in Japanese took 1.354548454284668s
Availability | RDF dump link check for DBpedia in Japanese took 1.3225996494293213s
License | MR license check for DBpedia in Japanese took 1.3570454120635986s
License | HR license check for DBpedia in Japanese took 61.319785833358765s
Amount of data | Number of property check for DBpedia in Japanese took 1.3270061016082764s
Understandability | Number of label check for DBpedia in Japanese took 1.3262858390808105s
Understandability | URI regex check for DBpedia in Japanese took 2.654071569442749s
Understandability | Vocabs check for DBpedia in Japanese took 1.3249664306640625s
Verifiability | Authors check for DBpedia in Japanese took 1.339463472366333s
Verifiability | Publishers check for DBpedia in Japanese took 1.3254475593566895s
Performance | Throughput check for DBpedia in Japanese took 13.291222333908081s
Amount of data | Check the number of entities for DBpedia in Japanese took 0.00015807151794433594s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3238458633422852s
Interlinking | sameAs chians check for DBpedia in Japanese took 2.9246175289154053s
Interlinking | skos check for DBpedia in Japanese took 1.3441672325134277s
Interlinking | skos check for DBpedia in Japanese took 1.334604024887085s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.3374085426330566s
Currency | Creation date check for DBpedia in Japanese took 2.674136161804199s
Currency | Modification date check for DBpedia in Japanese took 2.673395872116089s
Rep.Conc. | URIs length for DBpedia in Japanese took 110.74920511245728s
Interoperability | New vocabularies check for DBpedia in Japanese took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3246328830718994s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.337646245956421s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.3417949676513672s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 3.0110301971435547s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.025463581085205078s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.027250051498413086s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4715023040771484s
Consistency | Check Misplaced properties for DBpedia in Japanese took 94.11896896362305s
Consistency | Misplaced classes for DBpedia in Japanese took 2.9873414039611816s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.208202123641968s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.3345086574554443s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 94.17909026145935s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.03262925148010254s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 4.354935646057129s
Security | Sign check for DBpedia in Japanese took 1.3654215335845947s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 13.346097230911255s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.9048054218292236s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.0210721492767334s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010132789611816406s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 7.152557373046875e-07s
Believability | Calculation of trust value for DBpedia in Japanese took 5.245208740234375e-06s
INFO | --- Analysis for dbpedia-ja took 792.9623744487762s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.9591064453125e-05s
Availability | VoID file availability check for dbpedia lite took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.7142982482910156s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020792007446289062s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00010991096496582031s
Believability | Calculation of trust value for dbpedia lite took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-lite took 23.335732221603394s
Availability | SPARQL endpoint availability check for DBpedia-Live took 7.796287536621094e-05s
Availability | VoID file availability check for DBpedia-Live took 0.000274658203125s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.2629964351654053s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020543336868286133s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.361701965332031e-05s
Believability | Calculation of trust value for DBpedia-Live took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-live took 3.3548743724823s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.25238776206970215s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.2786898612976074s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.02030634880065918s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00016498565673828125s
Believability | Calculation of trust value for DBpedia in Dutch took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-nl took 3.218695640563965s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 23.62453532218933s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0007898807525634766s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.26628637313842773s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.02060079574584961s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 9.036064147949219e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-pt took 54.13701367378235s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 4.172325134277344e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.27787089347839355s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.020365476608276367s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.170967102050781e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-spotlight took 3.417633533477783s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.4345855712890625e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.27589869499206543s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.818771362304688e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 14.125568628311157s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 5.3882598876953125e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.2666177749633789s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.02063298225402832s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 3.123283386230469e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 6.198883056640625e-06s
INFO | --- Analysis for dbpedia-wikidata took 2.811739921569824s
Availability | SPARQL endpoint availability check for DBpedia took 4.1484832763671875e-05s
Availability | VoID file availability check for DBpedia took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for DBpedia took 0.276064395904541s
Reputation | Calculation of the PageRank for DBpedia took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for DBpedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for DBpedia took 3.0040740966796875e-05s
Believability | Calculation of trust value for DBpedia took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia_ took 3.280937910079956s
Availability | SPARQL endpoint availability check for DBTropes took 4.315376281738281e-05s
Availability | VoID file availability check for DBTropes took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for DBTropes took 0.26407837867736816s
Reputation | Calculation of the PageRank for DBTropes took 0.020793914794921875s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.72747802734375e-05s
Believability | Calculation of trust value for DBTropes took 7.3909759521484375e-06s
INFO | --- Analysis for dbtropes took 3.523284435272217s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.267692565917969e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.25845766067504883s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.838539123535156e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 6.67572021484375e-06s
INFO | --- Analysis for dbtune took 2.84617018699646s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 5.626678466796875e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.2592794895172119s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.626678466796875e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 6.4373016357421875e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 6.0529491901397705s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 6.198883056640625e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.28479743003845215s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020898103713989258s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007417201995849609s
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 5.9604644775390625e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 5.95234227180481s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.87613582611084s
Availability | VoID file availability check for DBTune.org/classical took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.24655818939208984s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020829439163208008s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.915496826171875e-05s
Believability | Calculation of trust value for DBTune.org/classical took 6.9141387939453125e-06s
INFO | --- Analysis for dbtune-classical took 22.429221391677856s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.319326400756836s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0007517337799072266s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.2530989646911621s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 7.104873657226562e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 6.67572021484375e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 27.58289337158203s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.346648216247559s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0008640289306640625s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.24450922012329102s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.02077317237854004s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.937980651855469e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-magnatune took 23.877039194107056s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.197647094726562s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0007600784301757812s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.2699093818664551s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.0206146240234375s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00010991096496582031s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-musicbrainz took 23.86855435371399s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.29033374786377s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0003142356872558594s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.2828223705291748s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020937204360961914s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.9604644775390625e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-myspace took 17.85977029800415s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.458427429199219e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.0003314018249511719s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.2622194290161133s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.023637771606445312s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.00121307373046875s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 4.410743713378906e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 7.152557373046875e-06s
INFO | --- Analysis for dclg-openuplabs took 2.877033233642578s
Availability | SPARQL endpoint availability check for data.dcs took 4.458427429199219e-05s
Availability | VoID file availability check for data.dcs took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for data.dcs took 0.2929568290710449s
Reputation | Calculation of the PageRank for data.dcs took 0.02085280418395996s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0010030269622802734s
Interlinking | Calculation of Clustering coefficient for data.dcs took 8.0108642578125e-05s
Believability | Calculation of trust value for data.dcs took 7.3909759521484375e-06s
INFO | --- Analysis for dcs-sheffield took 2.5049233436584473s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.100799560546875e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.26159238815307617s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 3.147125244140625e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 1.239776611328125e-05s
INFO | --- Analysis for de-budget took 2.8861114978790283s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 6.747245788574219e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.24613475799560547s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.021739959716796875s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 4.38690185546875e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 8.58306884765625e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.411916971206665s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.363059997558594e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.24666547775268555s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020236730575561523s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.38690185546875e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 7.62939453125e-06s
INFO | --- Analysis for debian-package-tracking-system took 4.495560169219971s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 4.57763671875e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.2619786262512207s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 2.956390380859375e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 7.152557373046875e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.8259949684143066s
Availability | SPARQL endpoint availability check for Demografie took 7.05718994140625e-05s
Availability | VoID file availability check for Demografie took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Demografie took 0.24989843368530273s
Reputation | Calculation of the PageRank for Demografie took 0.020580291748046875s
Interlinking | Calculation of Degree of Connection for Demografie took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0009679794311523438s
Interlinking | Calculation of Clustering coefficient for Demografie took 3.695487976074219e-05s
Believability | Calculation of trust value for Demografie took 7.62939453125e-06s
INFO | --- Analysis for demografie took 2.7967050075531006s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.38690185546875e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0006461143493652344s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.257631778717041s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.021275997161865234s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0010268688201904297s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 4.76837158203125e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 7.62939453125e-06s
INFO | --- Analysis for desaparecidos took 3.0754482746124268s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.792213439941406e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.2711453437805176s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.02037811279296875s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.822845458984375e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 6.67572021484375e-06s
INFO | --- Analysis for deustoentrepreneurship took 5.985289573669434s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 5.6743621826171875e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0007646083831787109s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.25235986709594727s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00010895729064941406s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 7.3909759521484375e-06s
INFO | --- Analysis for deustotech took 6.20058536529541s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.3671486377716064s
Availability | VoID file availability check for Deutsche Biographie took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.2560403347015381s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.02022242546081543s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.743171691894531e-05s
Believability | Calculation of trust value for Deutsche Biographie took 7.3909759521484375e-06s
INFO | --- Analysis for deutsche-biographie took 4.099905490875244s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 7.796287536621094e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0011751651763916016s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2540125846862793s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.8650970458984375e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 7.152557373046875e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.291282892227173s
Availability | SPARQL endpoint availability check for dev8d took 4.315376281738281e-05s
Availability | VoID file availability check for dev8d took 0.0007290840148925781s
Completeness | Calculation of interlinking completeness for dev8d took 0.2825021743774414s
Reputation | Calculation of the PageRank for dev8d took 0.020590543746948242s
Interlinking | Calculation of Degree of Connection for dev8d took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for dev8d took 7.104873657226562e-05s
Believability | Calculation of trust value for dev8d took 7.3909759521484375e-06s
INFO | --- Analysis for dev8d took 2.4428114891052246s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.182064294815063s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.2695012092590332s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020294189453125s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.1975250244140625e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 5.7220458984375e-06s
INFO | --- Analysis for dewey_decimal_classification took 92.61657977104187s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.363059997558594e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.29042482376098633s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.020793914794921875s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.361701965332031e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 6.9141387939453125e-06s
INFO | --- Analysis for DHSVM took 208.16419124603271s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.1484832763671875e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.2438044548034668s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.020459651947021484s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 3.0279159545898438e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 6.9141387939453125e-06s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 3.315467357635498s
Availability | SPARQL endpoint availability check for Diavgeia took 4.2438507080078125e-05s
Availability | VoID file availability check for Diavgeia took 0.0007190704345703125s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.2853829860687256s
Reputation | Calculation of the PageRank for Diavgeia took 0.020456314086914062s
Interlinking | Calculation of Degree of Connection for Diavgeia took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.106231689453125e-05s
Believability | Calculation of trust value for Diavgeia took 4.76837158203125e-06s
INFO | --- Analysis for diavgeia took 5.493464231491089s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.315376281738281e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.26027417182922363s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02077937126159668s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007066726684570312s
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 16.940918445587158s
Availability | SPARQL endpoint availability check for diigo.feed took 4.1961669921875e-05s
Availability | VoID file availability check for diigo.feed took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.2798023223876953s
Reputation | Calculation of the PageRank for diigo.feed took 0.02035236358642578s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 3.0517578125e-05s
Believability | Calculation of trust value for diigo.feed took 7.152557373046875e-06s
INFO | --- Analysis for diigo-feed took 2.943112373352051s
Availability | SPARQL endpoint availability check for DisGeNET took 3.3760740756988525s
Availability | VoID file availability check for DisGeNET took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.24648070335388184s
Reputation | Calculation of the PageRank for DisGeNET took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015115737915039062s
Believability | Calculation of trust value for DisGeNET took 7.3909759521484375e-06s
INFO | --- Analysis for disgenet took 9.147481918334961s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.0531158447265625e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.2661101818084717s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.020273447036743164s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 2.8848648071289062e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 6.4373016357421875e-06s
INFO | --- Analysis for disk took 2.8671531677246094s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.076957702636719e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.25180697441101074s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.020161867141723633s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 3.0040740966796875e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 6.9141387939453125e-06s
INFO | --- Analysis for distritos-zaragoza took 2.875673770904541s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.1961669921875e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2622208595275879s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.218650817871094e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 7.867813110351562e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 5.414664030075073s
Availability | SPARQL endpoint availability check for DM2E took 7.748603820800781e-05s
Availability | VoID file availability check for DM2E took 0.0003247261047363281s
Completeness | Calculation of interlinking completeness for DM2E took 0.2340245246887207s
Reputation | Calculation of the PageRank for DM2E took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for DM2E took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DM2E took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00010848045349121094s
Believability | Calculation of trust value for DM2E took 6.9141387939453125e-06s
INFO | --- Analysis for dm2e took 3.1352009773254395s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.124641418457031e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.26137709617614746s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.02015542984008789s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 2.8848648071289062e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 6.198883056640625e-06s
INFO | --- Analysis for dmoz_rdf_dump took 2.905092477798462s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 4.482269287109375e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0012476444244384766s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.3132145404815674s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.02047562599182129s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00015354156494140625s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 5.9604644775390625e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 7.5373921394348145s
Availability | SPARQL endpoint availability check for DOAP Store took 4.0531158447265625e-05s
Availability | VoID file availability check for DOAP Store took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.27477455139160156s
Reputation | Calculation of the PageRank for DOAP Store took 0.02021312713623047s
Interlinking | Calculation of Degree of Connection for DOAP Store took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 2.8848648071289062e-05s
Believability | Calculation of trust value for DOAP Store took 7.3909759521484375e-06s
INFO | --- Analysis for doap_store took 2.8730053901672363s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.291534423828125e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.24732279777526855s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020843505859375s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.699562072753906e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 5.0067901611328125e-06s
INFO | --- Analysis for doi took 7.799917221069336s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.8160552978515625e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.2819983959197998s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.02024531364440918s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.6716461181640625e-05s
Believability | Calculation of trust value for Driggu Florentino took 6.4373016357421875e-06s
INFO | --- Analysis for Driggu took 3.240938425064087s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 7.0575270652771s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0013577938079833984s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.2713751792907715s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.02038741111755371s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.600120544433594e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 7.62939453125e-06s
INFO | --- Analysis for drug-data-hifm took 36.953808307647705s
Availability | SPARQL endpoint availability check for dspace took 4.4345855712890625e-05s
Availability | VoID file availability check for dspace took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for dspace took 0.28215456008911133s
Reputation | Calculation of the PageRank for dspace took 0.020321130752563477s
Interlinking | Calculation of Degree of Connection for dspace took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for dspace took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for dspace took 3.0279159545898438e-05s
Believability | Calculation of trust value for dspace took 6.9141387939453125e-06s
INFO | --- Analysis for dspace took 2.915266513824463s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 4.2438507080078125e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.24842095375061035s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.020216703414916992s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 2.8133392333984375e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 6.198883056640625e-06s
INFO | --- Analysis for duraark-linked-building-data took 2.898513078689575s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 270.7881455421448s
Availability | VoID file availability check for MetaLex Document Server took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.2755579948425293s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.02125239372253418s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 4.2438507080078125e-05s
Believability | Calculation of trust value for MetaLex Document Server took 7.3909759521484375e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 554.1280207633972s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.473500967025757s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.26302361488342285s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020823240280151367s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.00543212890625e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 8.821487426757812e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 15.056511402130127s
Availability | SPARQL endpoint availability check for DWS-Group took 5.53131103515625e-05s
Availability | VoID file availability check for DWS-Group took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.2794332504272461s
Reputation | Calculation of the PageRank for DWS-Group took 0.02045750617980957s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010657310485839844s
Believability | Calculation of trust value for DWS-Group took 6.9141387939453125e-06s
INFO | --- Analysis for dws-group took 3.122182607650757s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.3392181396484375e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.2589893341064453s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.3855438232421875e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 7.867813110351562e-06s
INFO | --- Analysis for E1 took 4.062311410903931s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.07539916038513184s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0003705024719238281s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.24913239479064941s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.02069377899169922s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00013256072998046875s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-alaska took 3.0069260597229004s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.057086944580078125s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.00037384033203125s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.2681581974029541s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.793571472167969e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-cau took 2.4721553325653076s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.06374311447143555s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.00035452842712402344s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.2567098140716553s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.02082681655883789s
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.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.890296936035156e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.42844557762146s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.03806734085083008s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.25276851654052734s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.894371032714844e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.394469738006592s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.03946685791015625s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.26566624641418457s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.020630836486816406s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.0001347064971923828s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.8806145191192627s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.05784773826599121s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.26618528366088867s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02078080177307129s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.559226989746094e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.0251998901367188e-05s
INFO | --- Analysis for eagle-i-famu took 2.490992784500122s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.058588504791259766s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.2661721706390381s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00012826919555664062s
Believability | Calculation of trust value for eagle-i @ Harvard University took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-harvard took 2.4721579551696777s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.04865002632141113s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.24302124977111816s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020253419876098633s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012826919555664062s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.466458797454834s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.03975629806518555s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.2500298023223877s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020284175872802734s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.651878356933594e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-howard took 2.459768295288086s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.03478431701660156s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.27834153175354004s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020597457885742188s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.890296936035156e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 5.9604644775390625e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.481926679611206s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.0384366512298584s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.00041365623474121094s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.25405240058898926s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.021392345428466797s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011968612670898438s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-jsu took 2.4717395305633545s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.04472947120666504s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.269237756729126s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.02027606964111328s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0023322105407714844s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 4.839897155761719e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-meharry took 2.447251319885254s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.04320836067199707s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2599828243255615s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.02119898796081543s
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.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.0001049041748046875s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-montana took 2.4287703037261963s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.030008792877197266s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.25481724739074707s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0008311271667480469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 0.00010275840759277344s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-msm took 2.3380744457244873s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.047453880310058594s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2745800018310547s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.021655797958374023s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.00119781494140625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00017786026000976562s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.479471445083618s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.049579620361328125s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.26192593574523926s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.914138793945312e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-psm took 2.430927038192749s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.04146099090576172s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.25668835639953613s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020505189895629883s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.604194641113281e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 5.4836273193359375e-06s
INFO | --- Analysis for eagle-i-tsu took 2.403536081314087s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.04062986373901367s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2598862648010254s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020910978317260742s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 7.557868957519531e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.4555163383483887s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.05973243713378906s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.276475191116333s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.020607948303222656s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00010037422180175781s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 5.7220458984375e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.463303565979004s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.04618501663208008s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.2726726531982422s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00013327598571777344s
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.48933482170105s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.04448437690734863s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.2662997245788574s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020554542541503906s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.4849853515625e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 9.298324584960938e-06s
INFO | --- Analysis for eagle-i-utep took 2.4875290393829346s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.04009509086608887s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.28056931495666504s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.510185241699219e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-utsa took 2.4235522747039795s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.17887449264526367s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.24747180938720703s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.02067708969116211s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.226799011230469e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.6220791339874268s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.03945159912109375s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.25684452056884766s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.867813110351562e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 5.9604644775390625e-06s
INFO | --- Analysis for eagle-i-xula took 2.41398286819458s
Availability | SPARQL endpoint availability check for Emergency situation took 0.5590615272521973s
Availability | VoID file availability check for Emergency situation took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.26450252532958984s
Reputation | Calculation of the PageRank for Emergency situation took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 5.054473876953125e-05s
Believability | Calculation of trust value for Emergency situation took 8.821487426757812e-06s
INFO | --- Analysis for Earthquake took 3.6429080963134766s
Availability | SPARQL endpoint availability check for ESO took 0.7194883823394775s
Availability | VoID file availability check for ESO took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for ESO took 0.2588655948638916s
Reputation | Calculation of the PageRank for ESO took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for ESO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for ESO took 8.487701416015625e-05s
Believability | Calculation of trust value for ESO took 8.106231689453125e-06s
INFO | --- Analysis for Earthquake_case took 4.044170141220093s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.6192631721496582s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.26852893829345703s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020367145538330078s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010228157043457031s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 4.5299530029296875e-06s
INFO | --- Analysis for ecb-linked-data took 3.0706419944763184s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 6.493727922439575s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.2719910144805908s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020597219467163086s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 4.57763671875e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 5.4836273193359375e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 15.411657333374023s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 4.597669839859009s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.269650936126709s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020275354385375977s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.890296936035156e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 10.35696291923523s
Availability | SPARQL endpoint availability check for ECLAP took 20.723742485046387s
Availability | VoID file availability check for ECLAP took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for ECLAP took 0.2529783248901367s
Reputation | Calculation of the PageRank for ECLAP took 0.020334720611572266s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.910064697265625e-05s
Believability | Calculation of trust value for ECLAP took 7.152557373046875e-06s
INFO | --- Analysis for eclap took 53.159796714782715s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 4.267692565917969e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.29014134407043457s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.020229816436767578s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.1444091796875e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 7.62939453125e-06s
INFO | --- Analysis for ECNU-GISer took 3.926412582397461s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.3392181396484375e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2693603038787842s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.6743621826171875e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 6.9141387939453125e-06s
INFO | --- Analysis for ecs took 2.518442153930664s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.291534423828125e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.00030732154846191406s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.265366792678833s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.0215609073638916s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.218650817871094e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 8.58306884765625e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.8364150524139404s
Availability | SPARQL endpoint availability check for Edublogs took 4.458427429199219e-05s
Availability | VoID file availability check for Edublogs took 0.00033783912658691406s
Completeness | Calculation of interlinking completeness for Edublogs took 0.27643680572509766s
Reputation | Calculation of the PageRank for Edublogs took 0.02147078514099121s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.989738464355469e-05s
Believability | Calculation of trust value for Edublogs took 7.867813110351562e-06s
INFO | --- Analysis for edublogs took 3.338550090789795s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.5272464752197266s
Availability | VoID file availability check for education.data.gov.uk took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.2542417049407959s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020707130432128906s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.226799011230469e-05s
Believability | Calculation of trust value for education.data.gov.uk took 4.0531158447265625e-06s
INFO | --- Analysis for education-data-gov-uk took 4.5215840339660645s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 8.058547973632812e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.2570173740386963s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.020325183868408203s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.24249267578125e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 7.152557373046875e-06s
INFO | --- Analysis for education-openuplabs took 2.855358600616455s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.87727999687195s
Availability | VoID file availability check for Educational programs - SISVU took 0.0011527538299560547s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.41176486015319824s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.021106243133544922s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 3.0279159545898438e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.888938903808594e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 7.867813110351562e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1323.1986463069916s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 0.7588202953338623s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.676616907119751s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.9577484130859375e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 9.059906005859375e-06s
INFO | --- Analysis for eea took 6.972069501876831s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.48188281059265137s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.2900962829589844s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.555152893066406e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 5.7220458984375e-06s
INFO | --- Analysis for eea-rod took 5.212714433670044s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.1716475486755371s
Availability | VoID file availability check for EEA Vocabularies took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.24823212623596191s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.225440979003906e-05s
Believability | Calculation of trust value for EEA Vocabularies took 5.9604644775390625e-06s
INFO | --- Analysis for eea-vocabularies took 4.995579481124878s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.7569694519042969s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007607936859130859s
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 7.62939453125e-06s
INFO | --- Analysis for ege-university-linked-open-data took 3.4710655212402344s
Availability | SPARQL endpoint availability check for E-Government Ontology took 0.4183952808380127s
Availability | VoID file availability check for E-Government Ontology took 0.001041412353515625s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.2669856548309326s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.020528554916381836s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.337860107421875e-05s
Believability | Calculation of trust value for E-Government Ontology took 7.867813110351562e-06s
INFO | --- Analysis for EGovOntology took 3.2589504718780518s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7268557548522949s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0006976127624511719s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 2.8128135204315186s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3314228057861328s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7067115306854248s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9366340637207031s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.35209059715271s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.63671875s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.639779806137085s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8311886787414551s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.26539087295532227s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5232028961181641s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 6.62695050239563s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2745184898376465s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4193854331970215s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6645100116729736s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3164980411529541s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.34897565841674805s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2931239604949951s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 10.872442722320557s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 7.033348083496094e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.35187649726867676s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.29798316955566406s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4210991859436035s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.28032636642456055s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0477378368377686s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.464440107345581s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5398774147033691s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.6273980140686035s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.26235055923461914s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3364143371582031s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3428061008453369s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.099017858505249s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.030146121978759766s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.027798891067504883s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23478007316589355s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.294898509979248s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.48389554023742676s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.4201736450195312s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2470548152923584s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.145493507385254s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03400874137878418s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4278528690338135s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4720442295074463s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 2971.3630759716034s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1808664798736572s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.53131103515625e-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 6.9141387939453125e-06s
INFO | --- Analysis for ei2a took 14849.315997123718s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.291534423828125e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.27013301849365234s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.020095109939575195s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010585784912109375s
Believability | Calculation of trust value for EIONET RDF Data took 4.76837158203125e-06s
INFO | --- Analysis for eionet-rdf took 3.947455883026123s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.3392181396484375e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.2735111713409424s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.020219087600708008s
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.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.0040740966796875e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 6.9141387939453125e-06s
INFO | --- Analysis for ElgooG_ took 2.7887513637542725s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 4.124641418457031e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.2643599510192871s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.02025604248046875s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 2.8848648071289062e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 7.3909759521484375e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 2.8715007305145264s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 6.177347421646118s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.2550191879272461s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.557868957519531e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 6.9141387939453125e-06s
INFO | --- Analysis for elviajero took 24.725677967071533s
Availability | SPARQL endpoint availability check for EMN took 4.38690185546875e-05s
Availability | VoID file availability check for EMN took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for EMN took 0.26171326637268066s
Reputation | Calculation of the PageRank for EMN took 0.020413637161254883s
Interlinking | Calculation of Degree of Connection for EMN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for EMN took 4.172325134277344e-05s
Believability | Calculation of trust value for EMN took 7.152557373046875e-06s
INFO | --- Analysis for emn took 2.7015788555145264s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.315376281738281e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.24385809898376465s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.221366882324219e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 4.76837158203125e-06s
INFO | --- Analysis for enakting-co2emission took 2.368669271469116s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.25176572799682617s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.020550012588500977s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 5.1021575927734375e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 4.5299530029296875e-06s
INFO | --- Analysis for enakting-crime took 2.3467912673950195s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.291534423828125e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.2640380859375s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.02303791046142578s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0009603500366210938s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 5.1021575927734375e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 5.4836273193359375e-06s
INFO | --- Analysis for enakting-energy took 2.4016425609588623s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 0.00013756752014160156s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.27263975143432617s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.02100682258605957s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.393692016601562e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 4.76837158203125e-06s
INFO | --- Analysis for enakting-mortality took 2.425395965576172s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.267692565917969e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.2484123706817627s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 4.506111145019531e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 4.76837158203125e-06s
INFO | --- Analysis for enakting-nhs took 2.3712055683135986s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.291534423828125e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.2686748504638672s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.02090167999267578s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 6.270408630371094e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 4.76837158203125e-06s
INFO | --- Analysis for enakting-population took 2.431617498397827s
Availability | SPARQL endpoint availability check for Enel Shops took 4.38690185546875e-05s
Availability | VoID file availability check for Enel Shops took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.26862025260925293s
Reputation | Calculation of the PageRank for Enel Shops took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 2.956390380859375e-05s
Believability | Calculation of trust value for Enel Shops took 1.1920928955078125e-05s
INFO | --- Analysis for enel-shops took 2.908348321914673s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 6.532669067382812e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.2686190605163574s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.020500659942626953s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 3.0279159545898438e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 7.152557373046875e-06s
INFO | --- Analysis for energy-efficiency took 2.943892478942871s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 4.1484832763671875e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.24507808685302734s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.020252704620361328s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.0279159545898438e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 2.8464853763580322s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 4.315376281738281e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.25025224685668945s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.020203351974487305s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 2.956390380859375e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 2.8509998321533203s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.26635098457336426s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.020465373992919922s
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.00072479248046875s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 2.8560895919799805s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 4.4345855712890625e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.2621474266052246s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.020528554916381836s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.8966758251190186s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.00030541419982910156s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.2657806873321533s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.02083134651184082s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 3.4809112548828125e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 2.8790664672851562s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 4.029273986816406e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.00039887428283691406s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.26806068420410156s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.02044057846069336s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 3.1948089599609375e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.9028983116149902s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.25258350372314453s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.020539045333862305s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 3.1948089599609375e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 2.8481481075286865s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.6162822246551514s
Availability | VoID file availability check for English Heritage Periods List took 0.0007073879241943359s
Extra | Recovery of all triples for English Heritage Periods List took 0.37654805183410645s
Performance | Total latancy measurement for English Heritage Periods List took 1.70204496383667s
Amount of data | Number of triples check for English Heritage Periods List took 0.6861064434051514s
Versatility | Languages check for English Heritage Periods List took 0.2945282459259033s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.644695520401001s
Security | Check HTTPS for English Heritage Periods List took 0.22259974479675293s
Interpretability | RDF structures check for English Heritage Periods List took 0.2904224395751953s
Versatility | Serialization formats check for English Heritage Periods List took 0.49219608306884766s
Availability | RDF dump link check for English Heritage Periods List took 0.30762600898742676s
License | MR license check for English Heritage Periods List took 0.5043725967407227s
License | HR license check for English Heritage Periods List took 0.36200618743896484s
Amount of data | Number of property check for English Heritage Periods List took 0.38636231422424316s
Understandability | Number of label check for English Heritage Periods List took 0.43705034255981445s
Understandability | URI regex check for English Heritage Periods List took 0.6606919765472412s
Understandability | Vocabs check for English Heritage Periods List took 0.4686601161956787s
Verifiability | Authors check for English Heritage Periods List took 0.4684939384460449s
Verifiability | Publishers check for English Heritage Periods List took 0.3785879611968994s
Performance | Throughput check for English Heritage Periods List took 12.384464740753174s
Amount of data | Check the number of entities for English Heritage Periods List took 6.937980651855469e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.4585139751434326s
Interlinking | sameAs chians check for English Heritage Periods List took 0.3436896800994873s
Interlinking | skos check for English Heritage Periods List took 0.3747117519378662s
Interlinking | skos check for English Heritage Periods List took 0.35152387619018555s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.489088773727417s
Currency | Creation date check for English Heritage Periods List took 0.6687867641448975s
Currency | Modification date check for English Heritage Periods List took 0.7112655639648438s
Rep.Conc. | URIs length for English Heritage Periods List took 0.6379678249359131s
Interoperability | New vocabularies check for English Heritage Periods List took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.33037900924682617s
Accuracy | Check Functional Property for English Heritage Periods List took 0.3314857482910156s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.3244442939758301s
Consistency | Disjoint class check for English Heritage Periods List took 0.3088207244873047s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.3275890350341797s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.6444642543792725s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00016188621520996094s
Security | Sign check for English Heritage Periods List took 0.4077754020690918s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.2688596248626709s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020758390426635742s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.814697265625e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Periods List took 7.867813110351562e-06s
INFO | --- Analysis for english-heritage-periods-list took 55.344284534454346s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.5369722843170166s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0007555484771728516s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 1.1793434619903564s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 1.3335630893707275s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.30727219581604004s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.6221096515655518s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.6705968379974365s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 30.241541147232056s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.10602045059204102s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.31636714935302734s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.1406855583190918s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 57.334646701812744s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.3415718078613281s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.233160734176636s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.14741873741149902s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.3284621238708496s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.3487429618835449s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.1305694580078125s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.1943225860595703s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.537677526473999s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 11.394808530807495s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 3.218650817871094e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.1954345703125s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.31725049018859863s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.3594849109649658s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.6056778430938721s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.2090296745300293s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.48697543144226074s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.4891471862792969s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 1.415100336074829s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.2175905704498291s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.14400625228881836s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.14786529541015625s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.488600492477417s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 1.1957330703735352s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 1.1413624286651611s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.6520915031433105s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.0001399517059326172s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.5434257984161377s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.2208995819091797s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.3348500728607178s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02039361000061035s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 4.029273986816406e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 1.5497207641601562e-05s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 286.2673077583313s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.16760039329528809s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.00048232078552246094s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 1.8686037063598633s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.9932682514190674s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.20679235458374023s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.5142743587493896s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.5767204761505127s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 30.191034078598022s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.21834540367126465s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.16740918159484863s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.14203858375549316s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 58.12065625190735s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.15635466575622559s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.183395862579346s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.1486225128173828s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.127244234085083s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.35051679611206055s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.12992382049560547s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.14709973335266113s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.15974712371826172s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 11.750283241271973s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 7.009506225585938e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.21062850952148438s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.1348130702972412s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.13195276260375977s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.15854930877685547s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.20972323417663574s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.3384270668029785s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.20880937576293945s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.2815749645233154s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.15057897567749023s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.1354081630706787s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.12587499618530273s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.19038796424865723s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.4068183898925781s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 1.1195123195648193s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.5081071853637695s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.00017690658569335938s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.23345398902893066s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.20571351051330566s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.26807260513305664s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 4.076957702636719e-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 5.245208740234375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 275.95487236976624s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 6.556510925292969e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.27349305152893066s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.02063775062561035s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 3.218650817871094e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 6.67572021484375e-06s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 3.8040528297424316s
Availability | SPARQL endpoint availability check for English WordNet took 6.890296936035156e-05s
Availability | VoID file availability check for English WordNet took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for English WordNet took 0.2749335765838623s
Reputation | Calculation of the PageRank for English WordNet took 0.0209348201751709s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.6716461181640625e-05s
Believability | Calculation of trust value for English WordNet took 1.8596649169921875e-05s
INFO | --- Analysis for english-wordnet took 3.0561585426330566s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.1484832763671875e-05s
Availability | VoID file availability check for English Heritage Places took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.26535606384277344s
Reputation | Calculation of the PageRank for English Heritage Places took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 3.170967102050781e-05s
Believability | Calculation of trust value for English Heritage Places took 7.152557373046875e-06s
INFO | --- Analysis for englishheritage_places took 4.304290771484375s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.20016837120056152s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.25105810165405273s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.02017378807067871s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 9.179115295410156e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 7.152557373046875e-06s
INFO | --- Analysis for enipedia took 2.514693260192871s
Availability | SPARQL endpoint availability check for Enslaved.org took 4.267692565917969e-05s
Availability | VoID file availability check for Enslaved.org took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.26054954528808594s
Reputation | Calculation of the PageRank for Enslaved.org took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0008184909820556641s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.4332275390625e-05s
Believability | Calculation of trust value for Enslaved.org took 7.3909759521484375e-06s
INFO | --- Analysis for enslaved.org took 4.698108196258545s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.5425527095794678s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.2732813358306885s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.340576171875e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 8.106231689453125e-06s
INFO | --- Analysis for entice-graph took 2.9538328647613525s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.363059997558594e-05s
Availability | VoID file availability check for Entrez Gene took 0.0007517337799072266s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.26635313034057617s
Reputation | Calculation of the PageRank for Entrez Gene took 0.02017831802368164s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.457069396972656e-05s
Believability | Calculation of trust value for Entrez Gene took 1.1444091796875e-05s
INFO | --- Analysis for entrez_gene took 27.21348762512207s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.1961669921875e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.24985408782958984s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.075599670410156e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 7.152557373046875e-06s
INFO | --- Analysis for entrez_gene_extract took 2.815669298171997s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.0667057037353516s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.2662699222564697s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0008394718170166016s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.054473876953125e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 5.4836273193359375e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 11.53260350227356s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.3222236633300781s
Availability | VoID file availability check for environment.data.gov.uk took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.2789320945739746s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020346641540527344s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.410743713378906e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for environment-data-gov-uk took 9.542809247970581s
Availability | SPARQL endpoint availability check for EARTh took 271.9426894187927s
Availability | VoID file availability check for EARTh took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for EARTh took 0.29653334617614746s
Reputation | Calculation of the PageRank for EARTh took 0.020417213439941406s
Interlinking | Calculation of Degree of Connection for EARTh took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EARTh took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00010800361633300781s
Believability | Calculation of trust value for EARTh took 5.7220458984375e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 563.3820209503174s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.998037576675415s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.6997256278991699s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.020680665969848633s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 3.528594970703125e-05s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for EO_metadata took 5.248008489608765s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.267692565917969e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.2732863426208496s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.218650817871094e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 8.344650268554688e-06s
INFO | --- Analysis for EOKP-Datasets took 3.233407497406006s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.315376281738281e-05s
Availability | VoID file availability check for EPA-CDR took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.2630431652069092s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02024221420288086s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.528594970703125e-05s
Believability | Calculation of trust value for EPA-CDR took 4.5299530029296875e-06s
INFO | --- Analysis for epa-cdr took 7.329546689987183s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.291534423828125e-05s
Availability | VoID file availability check for EPA-FRS took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.2527749538421631s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020186185836791992s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.2479248046875e-05s
Believability | Calculation of trust value for EPA-FRS took 4.76837158203125e-06s
INFO | --- Analysis for epa-frs took 5.790678024291992s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.267692565917969e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.23876118659973145s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 4.029273986816406e-05s
Believability | Calculation of trust value for EPA-RCRA took 4.5299530029296875e-06s
INFO | --- Analysis for epa-rcra took 5.808686256408691s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.1484832763671875e-05s
Availability | VoID file availability check for EPA-SRS took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.27469587326049805s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020450592041015625s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.271766662597656e-05s
Believability | Calculation of trust value for EPA-SRS took 9.5367431640625e-06s
INFO | --- Analysis for epa-srs took 5.874670028686523s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.315376281738281e-05s
Availability | VoID file availability check for EPA-TRI took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.2714877128601074s
Reputation | Calculation of the PageRank for EPA-TRI took 0.02031087875366211s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0008299350738525391s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.7670135498046875e-05s
Believability | Calculation of trust value for EPA-TRI took 4.76837158203125e-06s
INFO | --- Analysis for epa-tri took 6.3355138301849365s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 5.316734313964844e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.26999568939208984s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.02055501937866211s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.271766662597656e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 7.152557373046875e-06s
INFO | --- Analysis for epo took 7.921228408813477s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.05207991600036621s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.28943562507629395s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020343303680419922s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.0001385211944580078s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.5332000255584717s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.5455162525177002s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.2680933475494385s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.023528575897216797s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 9.107589721679688e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 7.3909759521484375e-06s
INFO | --- Analysis for eprtr took 3.6580214500427246s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.8189122676849365s
Availability | VoID file availability check for Railway Infrastructure KG took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.28101134300231934s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 3.075599670410156e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 7.152557373046875e-06s
INFO | --- Analysis for ERAKG took 3.2244791984558105s
Availability | SPARQL endpoint availability check for reg took 4.172325134277344e-05s
Availability | VoID file availability check for reg took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for reg took 0.2524435520172119s
Reputation | Calculation of the PageRank for reg took 0.020817041397094727s
Interlinking | Calculation of Degree of Connection for reg took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for reg took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for reg took 1.2636184692382812e-05s
Believability | Calculation of trust value for reg took 5.7220458984375e-06s
INFO | --- Analysis for erg took 2.379772186279297s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.5300400257110596s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007779598236083984s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.2734973430633545s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 2.9325485229492188e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 5.0067901611328125e-06s
INFO | --- Analysis for es-msssi-drug-prices took 3.156632423400879s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 4.3392181396484375e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.2774806022644043s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.020438432693481445s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 9.226799011230469e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 4.76837158203125e-06s
INFO | --- Analysis for esd-standards took 3.8831489086151123s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.291534423828125e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.26794910430908203s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.295608520507812e-05s
Believability | Calculation of trust value for ESD-Toolkit took 5.245208740234375e-06s
INFO | --- Analysis for esd-toolkit took 3.117591381072998s
Availability | SPARQL endpoint availability check for Dataset Esis took 5.555152893066406e-05s
Availability | VoID file availability check for Dataset Esis took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.2647395133972168s
Reputation | Calculation of the PageRank for Dataset Esis took 0.0204007625579834s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.3855438232421875e-05s
Believability | Calculation of trust value for Dataset Esis took 7.62939453125e-06s
INFO | --- Analysis for esislearning took 2.756105899810791s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 4.2438507080078125e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0014276504516601562s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.2609996795654297s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.02009272575378418s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.0040740966796875e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 6.67572021484375e-06s
INFO | --- Analysis for ESV took 4.555920839309692s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.6734826564788818s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.26545238494873047s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.020223140716552734s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.424553632736206s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 18.61673617362976s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.2831606864929199s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020496845245361328s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.390975952148438e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 6.9141387939453125e-06s
INFO | --- Analysis for eu-agencies-bodies took 49.11389183998108s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 4.220008850097656e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.25020432472229004s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.218650817871094e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 7.3909759521484375e-06s
INFO | --- Analysis for eu-dgt-tm took 3.181596279144287s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 8.893013000488281e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.285907506942749s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020431041717529297s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007073879241943359s
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 5.0067901611328125e-06s
INFO | --- Analysis for eu-institutions took 12.111587762832642s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 3.092937469482422s
Availability | VoID file availability check for EU Parliament Media Library took 0.0003974437713623047s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.24442601203918457s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.020565271377563477s
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.0007574558258056641s
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 5.4836273193359375e-06s
INFO | --- Analysis for eu-parliament-media took 19.864513397216797s
Availability | SPARQL endpoint availability check for EU Who Is Who took 1.5392649173736572s
Availability | VoID file availability check for EU Who Is Who took 0.0007309913635253906s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2642245292663574s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.62396240234375e-05s
Believability | Calculation of trust value for EU Who Is Who took 9.059906005859375e-06s
INFO | --- Analysis for eu-who-is-who took 19.57569718360901s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 2.300912618637085s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.2428910732269287s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020215988159179688s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 3.743171691894531e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 4.5299530029296875e-06s
INFO | --- Analysis for eumida-linked-data took 16.951765060424805s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.2959616184234619s
Availability | VoID file availability check for European Nature Information System took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.25356101989746094s
Reputation | Calculation of the PageRank for European Nature Information System took 0.020298004150390625s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010466575622558594s
Believability | Calculation of trust value for European Nature Information System took 6.4373016357421875e-06s
INFO | --- Analysis for eunis took 4.076790809631348s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 9.443028211593628s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.25258731842041016s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.510185241699219e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for eur-lex-rdf took 23.755651712417603s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 1.6862678527832031s
Availability | VoID file availability check for Standard Eurobarometer took 0.0003795623779296875s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.2588307857513428s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020232439041137695s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.172325134277344e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 4.76837158203125e-06s
INFO | --- Analysis for eurobarometer-standard took 12.923592805862427s
Availability | SPARQL endpoint availability check for European Election Results took 1.8795080184936523s
Availability | VoID file availability check for European Election Results took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for European Election Results took 0.2560412883758545s
Reputation | Calculation of the PageRank for European Election Results took 0.020624876022338867s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0008664131164550781s
Interlinking | Calculation of Clustering coefficient for European Election Results took 4.100799560546875e-05s
Believability | Calculation of trust value for European Election Results took 5.245208740234375e-06s
INFO | --- Analysis for european-election-results took 15.958837032318115s
Availability | SPARQL endpoint availability check for EPO patents took 0.5342352390289307s
Availability | VoID file availability check for EPO patents took 0.0006766319274902344s
Extra | Recovery of all triples for EPO patents took 21.78606128692627s
Performance | Total latancy measurement for EPO patents took 1.1570088863372803s
Amount of data | Number of triples check for EPO patents took 90.24048781394958s
Versatility | Languages check for EPO patents took 120.09233450889587s
Interpretability | Number of blank nodes check for EPO patents took 90.27838516235352s
Interpretability | RDF structures check for EPO patents took 0.21730661392211914s
Versatility | Serialization formats check for EPO patents took 0.24501371383666992s
Availability | RDF dump link check for EPO patents took 0.21770167350769043s
License | MR license check for EPO patents took 0.22399210929870605s
License | HR license check for EPO patents took 90.21704149246216s
Amount of data | Number of property check for EPO patents took 0.21713876724243164s
Understandability | Number of label check for EPO patents took 90.21503400802612s
Understandability | URI regex check for EPO patents took 0.48436403274536133s
Understandability | Vocabs check for EPO patents took 0.24649977684020996s
Verifiability | Authors check for EPO patents took 0.25159358978271484s
Verifiability | Publishers check for EPO patents took 0.25316810607910156s
Performance | Throughput check for EPO patents took 12.002212762832642s
Amount of data | Check the number of entities for EPO patents took 7.200241088867188e-05s
Verifiability | Contribs. check for EPO patents took 0.1652088165283203s
Interlinking | sameAs chians check for EPO patents took 0.1840677261352539s
Interlinking | skos check for EPO patents took 0.2728869915008545s
Interlinking | skos check for EPO patents took 0.17702531814575195s
Timeliness | dataset update frequency check for EPO patents took 0.199202299118042s
Currency | Creation date check for EPO patents took 0.41864657402038574s
Currency | Modification date check for EPO patents took 0.40633296966552734s
Rep.Conc. | URIs length for EPO patents took 150.30606079101562s
Interoperability | New vocabularies check for EPO patents took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.23873400688171387s
Accuracy | Check Empty annotation labels for EPO patents took 14.643623352050781s
Accuracy | Check White space in annotation for EPO patents took 2.9385721683502197s
Accuracy | Check Datatype consistency for EPO patents took 4.8656089305877686s
Consistency | Disjoint class check for EPO patents took 0.2861933708190918s
Consistency | Check Misplaced properties for EPO patents took 120.34448742866516s
Consistency | Check Ontology hijacking for EPO patents took 18.05792474746704s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.647864818572998s
Consistency | Check Invalid usage of undefined properties for EPO patents took 121.60846543312073s
Conciseness | Check Extensional conciseness for EPO patents took 2.906114101409912s
Conciseness | Check Intensional conciseness for EPO patents took 0.3605670928955078s
Security | Sign check for EPO patents took 0.3288898468017578s
Availability | Check URIs Dereferenciability for EPO patents took 2.019528388977051s
Completeness | Calculation of interlinking completeness for EPO patents took 1.0903511047363281s
Reputation | Calculation of the PageRank for EPO patents took 0.02115464210510254s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for EPO patents took 5.030632019042969e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 1.9073486328125e-06s
Believability | Calculation of trust value for EPO patents took 7.152557373046875e-06s
INFO | --- Analysis for European_Patent_Information took 1280.1899654865265s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 4.363059997558594e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.6764693260192871s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.020978450775146484s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.361701965332031e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for europeana-lod took 4.249587059020996s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 5.340576171875e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.32564425468444824s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.020253419876098633s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.584426879882812e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 6.9141387939453125e-06s
INFO | --- Analysis for europeana-lod-v1 took 7.269680500030518s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.03184103965759277s
Availability | VoID file availability check for Europeana SPARQL took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.27040886878967285s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.0203402042388916s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.269050598144531e-05s
Believability | Calculation of trust value for Europeana SPARQL took 8.58306884765625e-06s
INFO | --- Analysis for europeana-sparql took 3.204998016357422s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.07323217391967773s
Availability | VoID file availability check for EuroSentiment took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.3013286590576172s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02084827423095703s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 4.38690185546875e-05s
Believability | Calculation of trust value for EuroSentiment took 8.58306884765625e-06s
INFO | --- Analysis for eurosentiment took 3.186964511871338s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 4.3392181396484375e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.2821061611175537s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0008363723754882812s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 8.916854858398438e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 4.5299530029296875e-06s
INFO | --- Analysis for eurostat-rdf took 11.133829355239868s
Availability | SPARQL endpoint availability check for EuroVoc took 0.3126256465911865s
Availability | VoID file availability check for EuroVoc took 0.0006108283996582031s
Extra | Recovery of all triples for EuroVoc took 180.63690829277039s
Performance | Total latancy measurement for EuroVoc took 0.6130778789520264s
Amount of data | Number of triples check for EuroVoc took 284.93616914749146s
Interoperability | New terms check for EuroVoc took 82.21320796012878s
Versatility | Languages check for EuroVoc took 300.11498284339905s
Interpretability | Number of blank nodes check for EuroVoc took 16.787988901138306s
Security | Check HTTPS for EuroVoc took 0.3308279514312744s
Interpretability | RDF structures check for EuroVoc took 0.4391481876373291s
Versatility | Serialization formats check for EuroVoc took 4.4459288120269775s
Availability | RDF dump link check for EuroVoc took 0.302654504776001s
License | MR license check for EuroVoc took 0.44982361793518066s
License | HR license check for EuroVoc took 300.02508020401s
Amount of data | Number of property check for EuroVoc took 0.12894845008850098s
Understandability | Number of label check for EuroVoc took 6.446826934814453s
Understandability | URI regex check for EuroVoc took 0.47142481803894043s
Understandability | Vocabs check for EuroVoc took 0.1072998046875s
Verifiability | Authors check for EuroVoc took 0.2579991817474365s
Verifiability | Publishers check for EuroVoc took 0.2085278034210205s
Performance | Throughput check for EuroVoc took 10.597694396972656s
Amount of data | Check the number of entities for EuroVoc took 6.961822509765625e-05s
Verifiability | Contribs. check for EuroVoc took 0.20607805252075195s
Interlinking | sameAs chians check for EuroVoc took 7.824752330780029s
Interlinking | skos check for EuroVoc took 0.4034383296966553s
Interlinking | skos check for EuroVoc took 0.6594421863555908s
Timeliness | dataset update frequency check for EuroVoc took 0.2932579517364502s
Currency | Creation date check for EuroVoc took 0.5659828186035156s
Currency | Modification date check for EuroVoc took 0.1937248706817627s
Rep.Conc. | URIs length for EuroVoc took 465.8161861896515s
Interoperability | New vocabularies check for EuroVoc took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.1598343849182129s
Accuracy | Check Functional Property for EuroVoc took 0.17049431800842285s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.17990827560424805s
Accuracy | Check Empty annotation labels for EuroVoc took 39.33698582649231s
Accuracy | Check White space in annotation for EuroVoc took 3.1688332557678223s
Accuracy | Check Datatype consistency for EuroVoc took 2.5587921142578125s
Consistency | Disjoint class check for EuroVoc took 0.17773938179016113s
Consistency | Check Misplaced properties for EuroVoc took 300.43696689605713s
Consistency | Misplaced classes for EuroVoc took 8.469373941421509s
Consistency | Check Ontology hijacking for EuroVoc took 35.21108436584473s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.5326921939849854s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.49422121047974s
Conciseness | Check Extensional conciseness for EuroVoc took 3.01070499420166s
Conciseness | Check Intensional conciseness for EuroVoc took 0.35176920890808105s
Security | Sign check for EuroVoc took 0.3894920349121094s
Availability | Check URIs Dereferenciability for EuroVoc took 16.367086172103882s
Completeness | Calculation of interlinking completeness for EuroVoc took 1.240095853805542s
Reputation | Calculation of the PageRank for EuroVoc took 0.020998716354370117s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 0.0001385211944580078s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 2.6226043701171875e-06s
Believability | Calculation of trust value for EuroVoc took 8.106231689453125e-06s
INFO | --- Analysis for eurovoc took 15335.441356182098s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 4.935264587402344e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.2651658058166504s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.0205991268157959s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 3.933906555175781e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 6.67572021484375e-06s
INFO | --- Analysis for eurovoc-in-skos took 3.7748405933380127s
Availability | SPARQL endpoint availability check for European Television Heritage took 4.5299530029296875e-05s
Availability | VoID file availability check for European Television Heritage took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.27330756187438965s
Reputation | Calculation of the PageRank for European Television Heritage took 0.020159244537353516s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 3.0994415283203125e-05s
Believability | Calculation of trust value for European Television Heritage took 6.9141387939453125e-06s
INFO | --- Analysis for euscreen took 3.352252960205078s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.315376281738281e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.2463836669921875s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.76837158203125e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 4.76837158203125e-06s
INFO | --- Analysis for euskadi-farmacias took 5.1796488761901855s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.7984528541564941s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.26267004013061523s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020276546478271484s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.170967102050781e-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.49983286857605s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.2986438274383545s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0008580684661865234s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.2684905529022217s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020321369171142578s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 6.866455078125e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 7.62939453125e-06s
INFO | --- Analysis for eutc-productions took 6.815789222717285s
Availability | SPARQL endpoint availability check for EventMedia took 0.3399670124053955s
Availability | VoID file availability check for EventMedia took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for EventMedia took 0.277355432510376s
Reputation | Calculation of the PageRank for EventMedia took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010776519775390625s
Believability | Calculation of trust value for EventMedia took 7.62939453125e-06s
INFO | --- Analysis for event-media took 8.742855310440063s
Availability | SPARQL endpoint availability check for EventKG took 4.2438507080078125e-05s
Availability | VoID file availability check for EventKG took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for EventKG took 0.25960373878479004s
Reputation | Calculation of the PageRank for EventKG took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for EventKG took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EventKG took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.296966552734375e-05s
Believability | Calculation of trust value for EventKG took 6.67572021484375e-06s
INFO | --- Analysis for eventkg took 5.112729549407959s
Availability | SPARQL endpoint availability check for Eventseer took 3.823634147644043s
Availability | VoID file availability check for Eventseer took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Eventseer took 0.25666308403015137s
Reputation | Calculation of the PageRank for Eventseer took 0.020070552825927734s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Eventseer took 5.817413330078125e-05s
Believability | Calculation of trust value for Eventseer took 7.152557373046875e-06s
INFO | --- Analysis for eventseer took 6.164781093597412s
Availability | SPARQL endpoint availability check for Face Link took 5.650520324707031e-05s
Availability | VoID file availability check for Face Link took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Face Link took 0.26944684982299805s
Reputation | Calculation of the PageRank for Face Link took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for Face Link took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Face Link took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.218650817871094e-05s
Believability | Calculation of trust value for Face Link took 7.3909759521484375e-06s
INFO | --- Analysis for Face_Link took 2.3222758769989014s
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.00025391578674316406s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.2789919376373291s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 2.956390380859375e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 8.58306884765625e-06s
INFO | --- Analysis for facebook-lids took 2.8924546241760254s
Availability | SPARQL endpoint availability check for Fact Forge took 4.220008850097656e-05s
Availability | VoID file availability check for Fact Forge took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.25510597229003906s
Reputation | Calculation of the PageRank for Fact Forge took 0.020442485809326172s
Interlinking | Calculation of Degree of Connection for Fact Forge took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 3.147125244140625e-05s
Believability | Calculation of trust value for Fact Forge took 7.152557373046875e-06s
INFO | --- Analysis for fact-forge took 2.842029333114624s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3546867370605469s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2500309944152832s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.719329833984375e-05s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 6.9141387939453125e-06s
INFO | --- Analysis for FADN_(2019) took 4.324879884719849s
Availability | SPARQL endpoint availability check for FAMEData took 4.220008850097656e-05s
Availability | VoID file availability check for FAMEData took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for FAMEData took 0.25209712982177734s
Reputation | Calculation of the PageRank for FAMEData took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.0279159545898438e-05s
Believability | Calculation of trust value for FAMEData took 6.9141387939453125e-06s
INFO | --- Analysis for famedata took 4.534435033798218s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.8160552978515625e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.25620269775390625s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.020699739456176758s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.751319885253906e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 4.76837158203125e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 10.327565431594849s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.1312243938446045s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.26792073249816895s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020195722579956055s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.918212890625e-05s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for fao-linked-data took 2.571174383163452s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 0.00011301040649414062s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.2752389907836914s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.02034449577331543s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.3855438232421875e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for FAO_species took 2.3158133029937744s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.587625980377197s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.00039458274841308594s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.2642176151275635s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.02041769027709961s
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.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.363059997558594e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 6.67572021484375e-06s
INFO | --- Analysis for farmbio-chembl took 66.16805028915405s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 4.124641418457031e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.2783932685852051s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.020314931869506836s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 3.0517578125e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 7.3909759521484375e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 2.862807512283325s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.26295948028564453s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020577430725097656s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 2.956390380859375e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 7.62939453125e-06s
INFO | --- Analysis for farolapp-dataset took 2.8772666454315186s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.172325134277344e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.00031185150146484375s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.24320363998413086s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.02024984359741211s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 3.0279159545898438e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 7.62939453125e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 2.8401541709899902s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.792213439941406e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0003333091735839844s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.25841569900512695s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 2.9802322387695312e-05s
Believability | Calculation of trust value for I4.0-Onto took 6.9141387939453125e-06s
INFO | --- Analysis for fatimazahra took 2.338062286376953s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 4.267692565917969e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.260897159576416s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 3.0517578125e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 7.3909759521484375e-06s
INFO | --- Analysis for federal-economic-rdf took 2.8635447025299072s
Availability | SPARQL endpoint availability check for Feed Wrapper took 6.580352783203125e-05s
Availability | VoID file availability check for Feed Wrapper took 0.0003857612609863281s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.26958274841308594s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.021208524703979492s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 3.218650817871094e-05s
Believability | Calculation of trust value for Feed Wrapper took 7.3909759521484375e-06s
INFO | --- Analysis for feedwrapper-lids took 2.875839948654175s
Availability | SPARQL endpoint availability check for FHIR STU3 took 5.841255187988281e-05s
Availability | VoID file availability check for FHIR STU3 took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.2573087215423584s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020541906356811523s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 3.0994415283203125e-05s
Believability | Calculation of trust value for FHIR STU3 took 6.9141387939453125e-06s
INFO | --- Analysis for FHIR_STU3 took 2.661940097808838s
Availability | SPARQL endpoint availability check for FiESTA took 4.363059997558594e-05s
Availability | VoID file availability check for FiESTA took 0.0007276535034179688s
Completeness | Calculation of interlinking completeness for FiESTA took 0.27057957649230957s
Reputation | Calculation of the PageRank for FiESTA took 0.021340370178222656s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.9577484130859375e-05s
Believability | Calculation of trust value for FiESTA took 6.9141387939453125e-06s
INFO | --- Analysis for fiesta took 12.585023164749146s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.38690185546875e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.2708139419555664s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02098870277404785s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.9802322387695312e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 7.3909759521484375e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.410761594772339s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 7.939338684082031e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.262542724609375s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.319450378417969e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 5.4836273193359375e-06s
INFO | --- Analysis for finnish-municipalities took 5.368670225143433s
Availability | SPARQL endpoint availability check for firmao took 4.1484832763671875e-05s
Availability | VoID file availability check for firmao took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for firmao took 0.27426719665527344s
Reputation | Calculation of the PageRank for firmao took 0.020970821380615234s
Interlinking | Calculation of Degree of Connection for firmao took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for firmao took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for firmao took 3.218650817871094e-05s
Believability | Calculation of trust value for firmao took 8.344650268554688e-06s
INFO | --- Analysis for firmao took 2.874398946762085s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.9114227294921875e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.2648191452026367s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 3.170967102050781e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.9810211658477783s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.5693254470825195s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0002963542938232422s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.27490806579589844s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.020576000213623047s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 3.218650817871094e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for Fishery_Stock_Dataset took 3.5613350868225098s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.267692565917969e-05s
Availability | VoID file availability check for Fishes of Texas took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.2639951705932617s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.678436279296875e-05s
Believability | Calculation of trust value for Fishes of Texas took 6.4373016357421875e-06s
INFO | --- Analysis for fishes-of-texas took 2.8781166076660156s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.291534423828125e-05s
Availability | VoID file availability check for flickr? wrappr took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.254380464553833s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020740985870361328s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.5367431640625e-05s
Believability | Calculation of trust value for flickr? wrappr took 8.58306884765625e-06s
INFO | --- Analysis for flickr-wrappr took 3.3793365955352783s
Availability | SPARQL endpoint availability check for flickr.person took 4.076957702636719e-05s
Availability | VoID file availability check for flickr.person took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for flickr.person took 0.27662181854248047s
Reputation | Calculation of the PageRank for flickr.person took 0.020650625228881836s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for flickr.person took 3.0517578125e-05s
Believability | Calculation of trust value for flickr.person took 6.4373016357421875e-06s
INFO | --- Analysis for flickr_person took 2.939636468887329s
Availability | SPARQL endpoint availability check for flickr.videoobject took 4.601478576660156e-05s
Availability | VoID file availability check for flickr.videoobject took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.276885986328125s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.022238731384277344s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 2.9802322387695312e-05s
Believability | Calculation of trust value for flickr.videoobject took 6.67572021484375e-06s
INFO | --- Analysis for flickr_videoobject took 2.8822884559631348s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.410743713378906e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0007216930389404297s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.261519193649292s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.02041149139404297s
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.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.0517578125e-05s
Believability | Calculation of trust value for Future land use simulation model took 7.62939453125e-06s
INFO | --- Analysis for FLUS took 7.021995782852173s
Availability | SPARQL endpoint availability check for Fly-TED took 4.1484832763671875e-05s
Availability | VoID file availability check for Fly-TED took 0.0010404586791992188s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.2718088626861572s
Reputation | Calculation of the PageRank for Fly-TED took 0.020244598388671875s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 2.8848648071289062e-05s
Believability | Calculation of trust value for Fly-TED took 7.62939453125e-06s
INFO | --- Analysis for fly-ted took 2.9481940269470215s
Availability | SPARQL endpoint availability check for FlyAtlas took 4.172325134277344e-05s
Availability | VoID file availability check for FlyAtlas took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.2598421573638916s
Reputation | Calculation of the PageRank for FlyAtlas took 0.0203402042388916s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 2.8848648071289062e-05s
Believability | Calculation of trust value for FlyAtlas took 6.9141387939453125e-06s
INFO | --- Analysis for flyatlas took 2.885479211807251s
Availability | SPARQL endpoint availability check for Flybase took 1.123875379562378s
Availability | VoID file availability check for Flybase took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Flybase took 0.2589397430419922s
Reputation | Calculation of the PageRank for Flybase took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for Flybase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.600120544433594e-05s
Believability | Calculation of trust value for Flybase took 7.3909759521484375e-06s
INFO | --- Analysis for flybase took 5.149953126907349s
Availability | SPARQL endpoint availability check for Flyted took 0.7548637390136719s
Availability | VoID file availability check for Flyted took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Flyted took 0.24576807022094727s
Reputation | Calculation of the PageRank for Flyted took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for Flyted took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.123283386230469e-05s
Believability | Calculation of trust value for Flyted took 1.1920928955078125e-05s
INFO | --- Analysis for flyted took 5.22787070274353s
Availability | SPARQL endpoint availability check for Foodista took 1.5385208129882812s
Availability | VoID file availability check for Foodista took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for Foodista took 0.24843740463256836s
Reputation | Calculation of the PageRank for Foodista took 0.020513057708740234s
Interlinking | Calculation of Degree of Connection for Foodista took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0009136199951171875s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.4809112548828125e-05s
Believability | Calculation of trust value for Foodista took 7.3909759521484375e-06s
INFO | --- Analysis for foodista took 10.744245290756226s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.17902731895446777s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.24910330772399902s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0008902549743652344s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.963180541992188e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 8.58306884765625e-06s
INFO | --- Analysis for foodpedia took 2.511665105819702s
Availability | SPARQL endpoint availability check for FORGE Course information took 4.076957702636719e-05s
Availability | VoID file availability check for FORGE Course information took 0.0003361701965332031s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.26880693435668945s
Reputation | Calculation of the PageRank for FORGE Course information took 0.02032017707824707s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 2.765655517578125e-05s
Believability | Calculation of trust value for FORGE Course information took 7.867813110351562e-06s
INFO | --- Analysis for forge-course-information took 2.913869619369507s
Availability | SPARQL endpoint availability check for FrameBase schema took 4.2438507080078125e-05s
Availability | VoID file availability check for FrameBase schema took 0.00033926963806152344s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.26189184188842773s
Reputation | Calculation of the PageRank for FrameBase schema took 0.020452260971069336s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.5299530029296875e-05s
Believability | Calculation of trust value for FrameBase schema took 7.62939453125e-06s
INFO | --- Analysis for framebase-schema took 2.9466726779937744s
Availability | SPARQL endpoint availability check for FrameNet took 4.0531158447265625e-05s
Availability | VoID file availability check for FrameNet took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for FrameNet took 0.2703561782836914s
Reputation | Calculation of the PageRank for FrameNet took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for FrameNet took 2.9802322387695312e-05s
Believability | Calculation of trust value for FrameNet took 6.9141387939453125e-06s
INFO | --- Analysis for framenet took 2.798400640487671s
Availability | SPARQL endpoint availability check for Framester took 4.363059997558594e-05s
Availability | VoID file availability check for Framester took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Framester took 0.2792186737060547s
Reputation | Calculation of the PageRank for Framester took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Framester took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Framester took 7.653236389160156e-05s
Believability | Calculation of trust value for Framester took 1.049041748046875e-05s
INFO | --- Analysis for framester took 3.4149744510650635s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.06018710136413574s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.26432228088378906s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.02042102813720703s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 9.1552734375e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for frb-linked-data took 2.4601216316223145s
Availability | SPARQL endpoint availability check for Freebase took 4.4345855712890625e-05s
Availability | VoID file availability check for Freebase took 0.0007607936859130859s
Completeness | Calculation of interlinking completeness for Freebase took 0.24004316329956055s
Reputation | Calculation of the PageRank for Freebase took 0.020504236221313477s
Interlinking | Calculation of Degree of Connection for Freebase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.0002758502960205078s
Believability | Calculation of trust value for Freebase took 7.3909759521484375e-06s
INFO | --- Analysis for freebase took 4.5741071701049805s
Availability | SPARQL endpoint availability check for Freeyork took 6.723403930664062e-05s
Availability | VoID file availability check for Freeyork took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for Freeyork took 0.2787511348724365s
Reputation | Calculation of the PageRank for Freeyork took 0.023365259170532227s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0008113384246826172s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.0001251697540283203s
Believability | Calculation of trust value for Freeyork took 8.58306884765625e-06s
INFO | --- Analysis for freeyork-org took 3.1029109954833984s
Availability | SPARQL endpoint availability check for French School Program took 4.5299530029296875e-05s
Availability | VoID file availability check for French School Program took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for French School Program took 0.2684767246246338s
Reputation | Calculation of the PageRank for French School Program took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for French School Program took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0008962154388427734s
Interlinking | Calculation of Clustering coefficient for French School Program took 3.457069396972656e-05s
Believability | Calculation of trust value for French School Program took 8.106231689453125e-06s
INFO | --- Analysis for french-school-program took 2.836756467819214s
Availability | SPARQL endpoint availability check for French School System took 4.601478576660156e-05s
Availability | VoID file availability check for French School System took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for French School System took 0.2583465576171875s
Reputation | Calculation of the PageRank for French School System took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for French School System took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for French School System took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for French School System took 3.457069396972656e-05s
Believability | Calculation of trust value for French School System took 7.3909759521484375e-06s
INFO | --- Analysis for french-school-system took 2.891035795211792s
Availability | SPARQL endpoint availability check for French TimeBank took 4.1961669921875e-05s
Availability | VoID file availability check for French TimeBank took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.24976730346679688s
Reputation | Calculation of the PageRank for French TimeBank took 0.020215988159179688s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 2.9802322387695312e-05s
Believability | Calculation of trust value for French TimeBank took 7.3909759521484375e-06s
INFO | --- Analysis for french-timebank took 2.8364460468292236s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.6665773391723633s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.27768445014953613s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.020873308181762695s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.748603820800781e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 5.4836273193359375e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.266608476638794s
Availability | SPARQL endpoint availability check for DailyMed took 0.6559112071990967s
Availability | VoID file availability check for DailyMed took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for DailyMed took 0.2577831745147705s
Reputation | Calculation of the PageRank for DailyMed took 0.021734952926635742s
Interlinking | Calculation of Degree of Connection for DailyMed took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.001032114028930664s
Interlinking | Calculation of Clustering coefficient for DailyMed took 0.00011563301086425781s
Believability | Calculation of trust value for DailyMed took 8.58306884765625e-06s
INFO | --- Analysis for fu-berlin-dailymed took 5.4814136028289795s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.6674633026123047s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.2763655185699463s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.02080082893371582s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 9.083747863769531e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 8.344650268554688e-06s
INFO | --- Analysis for fu-berlin-dblp took 4.2403724193573s
Availability | SPARQL endpoint availability check for Diseasome took 0.6445400714874268s
Availability | VoID file availability check for Diseasome took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Diseasome took 0.2684755325317383s
Reputation | Calculation of the PageRank for Diseasome took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00011229515075683594s
Believability | Calculation of trust value for Diseasome took 8.106231689453125e-06s
INFO | --- Analysis for fu-berlin-diseasome took 5.671175718307495s
Availability | SPARQL endpoint availability check for DrugBank took 0.6321501731872559s
Availability | VoID file availability check for DrugBank took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2836918830871582s
Reputation | Calculation of the PageRank for DrugBank took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011992454528808594s
Believability | Calculation of trust value for DrugBank took 9.5367431640625e-06s
INFO | --- Analysis for fu-berlin-drugbank took 5.462214946746826s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.6515977382659912s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.24909424781799316s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.02056097984313965s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.4332275390625e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 4.2862043380737305s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.6678228378295898s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.2599046230316162s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.43865966796875e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 5.7220458984375e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.234610557556152s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.676668643951416s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.28180837631225586s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.020201683044433594s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.271766662597656e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 5.4836273193359375e-06s
INFO | --- Analysis for fu-berlin-eures took 4.369878768920898s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.6765172481536865s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2630188465118408s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020267486572265625s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 0.00010013580322265625s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 4.5299530029296875e-06s
INFO | --- Analysis for fu-berlin-eurostat took 4.824478387832642s
Availability | SPARQL endpoint availability check for MediCare took 0.6428606510162354s
Availability | VoID file availability check for MediCare took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for MediCare took 0.2601189613342285s
Reputation | Calculation of the PageRank for MediCare took 0.020394563674926758s
Interlinking | Calculation of Degree of Connection for MediCare took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.1484832763671875e-05s
Believability | Calculation of trust value for MediCare took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-medicare took 4.792926788330078s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.6882083415985107s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.24964618682861328s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020243406295776367s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.867813110351562e-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.20953106880188s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.6682677268981934s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.2696096897125244s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.250640869140625e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 8.106231689453125e-06s
INFO | --- Analysis for fu-berlin-sider took 4.851181268692017s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.6352231502532959s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.27214527130126953s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020647525787353516s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.963180541992188e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-stitch took 4.230123281478882s
Availability | SPARQL endpoint availability check for fvdb took 4.2438507080078125e-05s
Availability | VoID file availability check for fvdb took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for fvdb took 0.2777283191680908s
Reputation | Calculation of the PageRank for fvdb took 0.020474910736083984s
Interlinking | Calculation of Degree of Connection for fvdb took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for fvdb took 2.9325485229492188e-05s
Believability | Calculation of trust value for fvdb took 7.62939453125e-06s
INFO | --- Analysis for fv took 12.352899074554443s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 4.315376281738281e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.2483198642730713s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.02067422866821289s
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.0008358955383300781s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.337860107421875e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 6.9141387939453125e-06s
INFO | --- Analysis for GACS took 2.9803524017333984s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 4.291534423828125e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.2910196781158447s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 2.9087066650390625e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 6.9141387939453125e-06s
INFO | --- Analysis for galen_from_co-odeorg took 2.988814115524292s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.220008850097656e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.2501871585845947s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 7.152557373046875e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 4.9065001010894775s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 4.744529724121094e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.260805606842041s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.02025318145751953s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 9.632110595703125e-05s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.0967254638671875e-05s
INFO | --- Analysis for garnicaplywood took 3.8178725242614746s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 5.5789947509765625e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.24723386764526367s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.226799011230469e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 7.152557373046875e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.717140197753906s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.34137940406799316s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0010671615600585938s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.2663290500640869s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0009589195251464844s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 0.000102996826171875s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for gemet took 4.8502655029296875s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.38690185546875e-05s
Availability | VoID file availability check for gemet-annotated took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.2758948802947998s
Reputation | Calculation of the PageRank for gemet-annotated took 0.02090287208557129s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.4809112548828125e-05s
Believability | Calculation of trust value for gemet-annotated took 7.3909759521484375e-06s
INFO | --- Analysis for gemet-annotated took 3.1157963275909424s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.9005653858184814s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.23244690895080566s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020723342895507812s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 4.100799560546875e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 7.3909759521484375e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.149362087249756s
Availability | SPARQL endpoint availability check for Super Ontology took 1.4985132217407227s
Availability | VoID file availability check for Super Ontology took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.2775382995605469s
Reputation | Calculation of the PageRank for Super Ontology took 0.02044534683227539s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 2.8848648071289062e-05s
Believability | Calculation of trust value for Super Ontology took 1.239776611328125e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 4.932912111282349s
Availability | SPARQL endpoint availability check for geo.place took 4.1484832763671875e-05s
Availability | VoID file availability check for geo.place took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for geo.place took 0.23970699310302734s
Reputation | Calculation of the PageRank for geo.place took 0.02042675018310547s
Interlinking | Calculation of Degree of Connection for geo.place took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for geo.place took 3.123283386230469e-05s
Believability | Calculation of trust value for geo.place took 7.152557373046875e-06s
INFO | --- Analysis for geo_place took 2.780808925628662s
Availability | SPARQL endpoint availability check for Geographic detector model took 4.2438507080078125e-05s
Availability | VoID file availability check for Geographic detector model took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.29685282707214355s
Reputation | Calculation of the PageRank for Geographic detector model took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 2.86102294921875e-05s
Believability | Calculation of trust value for Geographic detector model took 7.152557373046875e-06s
INFO | --- Analysis for GeoDetector took 21.230308771133423s
Availability | SPARQL endpoint availability check for geodomainwn took 5.6743621826171875e-05s
Availability | VoID file availability check for geodomainwn took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.26967644691467285s
Reputation | Calculation of the PageRank for geodomainwn took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 5.435943603515625e-05s
Believability | Calculation of trust value for geodomainwn took 7.867813110351562e-06s
INFO | --- Analysis for geodomainwn took 3.7172605991363525s
Availability | SPARQL endpoint availability check for GeoEcuador took 8.320808410644531e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.2517271041870117s
Reputation | Calculation of the PageRank for GeoEcuador took 0.02071404457092285s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.818771362304688e-05s
Believability | Calculation of trust value for GeoEcuador took 7.152557373046875e-06s
INFO | --- Analysis for geoecuador took 13.465182542800903s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.2685623168945312s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.27717161178588867s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.020653963088989258s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 7.104873657226562e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 8.821487426757812e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 47.60759997367859s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 5.650520324707031e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.266176700592041s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 7.3909759521484375e-06s
INFO | --- Analysis for geographic-openuplabs took 2.9171464443206787s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.428877592086792s
Availability | VoID file availability check for GeoLinkedData took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.25372910499572754s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.020267963409423828s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.749961853027344e-05s
Believability | Calculation of trust value for GeoLinkedData took 4.76837158203125e-06s
INFO | --- Analysis for geolinkeddata took 3.8339009284973145s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.24501419067382812s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0006585121154785156s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 8.626787424087524s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.34799814224243164s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.1185915470123291s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.4221696853637695s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.15935492515563965s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.13910818099975586s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.18527531623840332s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.06096482276916504s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.07585382461547852s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.06688570976257324s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.07460999488830566s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.7490589618682861s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.06145763397216797s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.0818486213684082s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.15117549896240234s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.06807732582092285s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.06086897850036621s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.06714272499084473s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.31346082687378s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 7.414817810058594e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.06802129745483398s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.07057857513427734s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.06786847114562988s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.06749272346496582s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.07505369186401367s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.16147994995117188s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.14272522926330566s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.2148067951202393s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 0.6435489654541016s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.06039023399353027s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06710338592529297s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.0740656852722168s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.26287055015563965s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007279634475708008s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.22807621955871582s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.0671701431274414s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.21942830085754395s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5232229232788086s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 2.897935390472412s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.4247725009918213s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.5690326690673828s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.1743936538696289s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.07508730888366699s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.0450255870819092s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.3071601390838623s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020457029342651367s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.273124694824219e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 0.4732027053833008s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 50.96691012382507s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 5.364418029785156e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.2712376117706299s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.019911766052246094s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0006802082061767578s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.00047016143798828125s
Believability | Calculation of trust value for GeoNames Semantic Web took 7.3909759521484375e-06s
INFO | --- Analysis for geonames-semantic-web took 4.811812162399292s
Availability | SPARQL endpoint availability check for Geospatial World  took 4.2438507080078125e-05s
Availability | VoID file availability check for Geospatial World  took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.2705874443054199s
Reputation | Calculation of the PageRank for Geospatial World  took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0009477138519287109s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00012254714965820312s
Believability | Calculation of trust value for Geospatial World  took 8.344650268554688e-06s
INFO | --- Analysis for geospatialworld-net took 2.8925018310546875s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 1.3739933967590332s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0003228187561035156s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.2511563301086426s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020328998565673828s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00013446807861328125s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 7.152557373046875e-06s
INFO | --- Analysis for geospecies took 6.5000340938568115s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.1484832763671875e-05s
Availability | VoID file availability check for GeoWordNet took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.25714564323425293s
Reputation | Calculation of the PageRank for GeoWordNet took 0.020189762115478516s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 4.887580871582031e-05s
Believability | Calculation of trust value for GeoWordNet took 6.4373016357421875e-06s
INFO | --- Analysis for geowordnet took 7.398706436157227s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.08283209800720215s
Availability | VoID file availability check for German labor law thesaurus took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.26455116271972656s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.020099639892578125s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 7.62939453125e-05s
Believability | Calculation of trust value for German labor law thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.5321667194366455s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.26538777351379395s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.020967721939086914s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.649162292480469e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.9311904907226562e-05s
INFO | --- Analysis for germlex took 2.9064583778381348s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.7931938171386719s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.212493896484375s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.28861117362976074s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.441375732421875e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 5.7220458984375e-06s
INFO | --- Analysis for gesis-thesoz took 7.324180603027344s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.9607532024383545s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.2656290531158447s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 8.320808410644531e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for getty-aat took 16.233675003051758s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.340406894683838s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.3007655143737793s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.3882598876953125e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 7.3909759521484375e-06s
INFO | --- Analysis for getty-tgn took 13.425154685974121s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 0.2214663028717041s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.2694869041442871s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.020316600799560547s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 2.8848648071289062e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 5.0067901611328125e-06s
INFO | --- Analysis for gipuzkoademografia took 3.0550246238708496s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.100799560546875e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.24868249893188477s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02031087875366211s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 2.9087066650390625e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 6.9141387939453125e-06s
INFO | --- Analysis for glastonbury-2011 took 5.487424373626709s
Availability | SPARQL endpoint availability check for Global Change Information System took 5.316734313964844e-05s
Availability | VoID file availability check for Global Change Information System took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.2655375003814697s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020259618759155273s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 3.0040740966796875e-05s
Believability | Calculation of trust value for Global Change Information System took 7.3909759521484375e-06s
INFO | --- Analysis for global-change-information-system took 2.9002480506896973s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.935264587402344e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.25514817237854004s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.021005630493164062s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.601478576660156e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 6.4373016357421875e-06s
INFO | --- Analysis for global-hunger-index-2011 took 3.1886565685272217s
Availability | SPARQL endpoint availability check for Glottolog took 4.1961669921875e-05s
Availability | VoID file availability check for Glottolog took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2622652053833008s
Reputation | Calculation of the PageRank for Glottolog took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for Glottolog took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Glottolog took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.125999450683594e-05s
Believability | Calculation of trust value for Glottolog took 1.1920928955078125e-05s
INFO | --- Analysis for glottolog took 6.251350164413452s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.5299530029296875e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0003304481506347656s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.2931828498840332s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020427703857421875s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010085105895996094s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.1444091796875e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 12.470971822738647s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.1484832763671875e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.24073314666748047s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 2.956390380859375e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 6.67572021484375e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.7771284580230713s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 5.14984130859375e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.2666759490966797s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.02088618278503418s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.266334533691406e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 7.3909759521484375e-06s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 2.9254372119903564s
Availability | SPARQL endpoint availability check for 1121 took 4.291534423828125e-05s
Availability | VoID file availability check for 1121 took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for 1121 took 0.2534763813018799s
Reputation | Calculation of the PageRank for 1121 took 0.020473003387451172s
Interlinking | Calculation of Degree of Connection for 1121 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.0279159545898438e-05s
Believability | Calculation of trust value for 1121 took 7.152557373046875e-06s
INFO | --- Analysis for God_ took 2.8891594409942627s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.267692565917969e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.25168704986572266s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.3882598876953125e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 5.9604644775390625e-06s
INFO | --- Analysis for gold took 4.059371471405029s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.124641418457031e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0012545585632324219s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.2590939998626709s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020321369171142578s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 7.224082946777344e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 7.152557373046875e-06s
INFO | --- Analysis for googleart-wrapper took 2.6413707733154297s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.0992887020111084s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.2519099712371826s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.02030038833618164s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.552436828613281e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.7642974853515625e-05s
INFO | --- Analysis for govagribus-denmark took 34.72058629989624s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.3588178157806396s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.2667074203491211s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.821487426757812e-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.865363121032715s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.7246837615966797s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.26647257804870605s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.797645568847656e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 4.76837158203125e-06s
INFO | --- Analysis for govtrack took 4.449153900146484s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.100799560546875e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.25859832763671875s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.02030038833618164s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 5.745887756347656e-05s
Believability | Calculation of trust value for greek-administrative-geography took 6.4373016357421875e-06s
INFO | --- Analysis for greek-administrative-geography took 2.459944725036621s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.4845161437988281s
Availability | VoID file availability check for Greek Wordnet took 0.0003695487976074219s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.24881792068481445s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020186424255371094s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007948875427246094s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 5.221366882324219e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.0728836059570312e-05s
INFO | --- Analysis for greek-wordnet took 2.8706188201904297s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 2.8197479248046875s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.26328539848327637s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.52587890625e-05s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 8.106231689453125e-06s
INFO | --- Analysis for greek_prisons_releases took 20.820401906967163s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.7595088481903076s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.27006030082702637s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.106231689453125e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 7.152557373046875e-06s
INFO | --- Analysis for greekchildrensartmuseum took 4.394197225570679s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.3392181396484375e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0007462501525878906s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.2950925827026367s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00010132789611816406s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 8.106231689453125e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 9.085002660751343s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.7112951278686523s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.28130483627319336s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.02101588249206543s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0009541511535644531s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 6.222724914550781e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 7.867813110351562e-06s
INFO | --- Analysis for grrp took 4.2151405811309814s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.0223486423492432s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.00030350685119628906s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.27118420600891113s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.699562072753906e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 5.9604644775390625e-06s
INFO | --- Analysis for grrt took 3.404327392578125s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.553431510925293s
Availability | VoID file availability check for Geological Timescale took 0.0006670951843261719s
Extra | Recovery of all triples for Geological Timescale took 2.4954922199249268s
Performance | Total latancy measurement for Geological Timescale took 2.7380101680755615s
Amount of data | Number of triples check for Geological Timescale took 1.0526702404022217s
Interoperability | New terms check for Geological Timescale took 1.7992722988128662s
Versatility | Languages check for Geological Timescale took 0.5296456813812256s
Interpretability | Number of blank nodes check for Geological Timescale took 0.47988104820251465s
Security | Check HTTPS for Geological Timescale took 0.980191707611084s
Interpretability | RDF structures check for Geological Timescale took 0.4411928653717041s
Versatility | Serialization formats check for Geological Timescale took 1.0476782321929932s
Availability | RDF dump link check for Geological Timescale took 1.1427664756774902s
License | MR license check for Geological Timescale took 0.42009758949279785s
License | HR license check for Geological Timescale took 0.49741649627685547s
Amount of data | Number of property check for Geological Timescale took 1.003591537475586s
Understandability | Number of label check for Geological Timescale took 1.216209888458252s
Understandability | URI regex check for Geological Timescale took 2.037498950958252s
Understandability | Vocabs check for Geological Timescale took 1.0474836826324463s
Verifiability | Authors check for Geological Timescale took 0.46041202545166016s
Verifiability | Publishers check for Geological Timescale took 0.43359851837158203s
Performance | Throughput check for Geological Timescale took 14.666773796081543s
Amount of data | Check the number of entities for Geological Timescale took 0.022356271743774414s
Verifiability | Contribs. check for Geological Timescale took 1.0482537746429443s
Interlinking | sameAs chians check for Geological Timescale took 0.4282858371734619s
Interlinking | skos check for Geological Timescale took 0.41337060928344727s
Interlinking | skos check for Geological Timescale took 0.4206702709197998s
Timeliness | dataset update frequency check for Geological Timescale took 0.42720794677734375s
Currency | Creation date check for Geological Timescale took 1.9890713691711426s
Currency | Modification date check for Geological Timescale took 0.4472959041595459s
Rep.Conc. | URIs length for Geological Timescale took 2.2396693229675293s
Interoperability | New vocabularies check for Geological Timescale took 1.3639013767242432s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.4188723564147949s
Accuracy | Check Functional Property for Geological Timescale took 0.41858482360839844s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.3959658145904541s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.353774070739746s
Accuracy | Check White space in annotation for Geological Timescale took 0.015404939651489258s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07396864891052246s
Consistency | Disjoint class check for Geological Timescale took 0.4044961929321289s
Consistency | Check Misplaced properties for Geological Timescale took 2.330695629119873s
Consistency | Misplaced classes for Geological Timescale took 1.1911053657531738s
Consistency | Check Ontology hijacking for Geological Timescale took 2.409677267074585s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.2910418510437012s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 1.7575511932373047s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.05437731742858887s
Conciseness | Check Intensional conciseness for Geological Timescale took 1.0160279273986816s
Security | Sign check for Geological Timescale took 0.465221643447876s
Availability | Check URIs Dereferenciability for Geological Timescale took 3.625159502029419s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.2640814781188965s
Reputation | Calculation of the PageRank for Geological Timescale took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 7.390975952148438e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 1.4492831230163574s
Believability | Calculation of trust value for Geological Timescale took 6.4373016357421875e-06s
INFO | --- Analysis for GTS took 108.5687255859375s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.2674863338470459s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.020250320434570312s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.457069396972656e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 6.67572021484375e-06s
INFO | --- Analysis for GTS-ont took 2.7441108226776123s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.172325134277344e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.236328125s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.021505355834960938s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.3855438232421875e-05s
Believability | Calculation of trust value for GUTSTOK  took 1.1682510375976562e-05s
INFO | --- Analysis for Guillaume_Forget took 2.3354108333587646s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.172325134277344e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.251509428024292s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.02049708366394043s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 7.62939453125e-05s
Believability | Calculation of trust value for Project Gutenberg took 6.67572021484375e-06s
INFO | --- Analysis for gutenberg took 18.457181930541992s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.291534423828125e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007936954498291016s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.38066840171813965s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.020686626434326172s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.552436828613281e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 6.4373016357421875e-06s
INFO | --- Analysis for gwa-ili took 5.731801271438599s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 6.771087646484375e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.2636902332305908s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.02021622657775879s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.0040740966796875e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 7.62939453125e-06s
INFO | --- Analysis for GWR took 18.186166048049927s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 5.1975250244140625e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.2658200263977051s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.0040740966796875e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 5.9604644775390625e-06s
INFO | --- Analysis for HASM took 25.49267601966858s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 3.981590270996094e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.258608341217041s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.020840883255004883s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0008611679077148438s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.504753112792969e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 7.62939453125e-06s
INFO | --- Analysis for hcls-knowledge-base took 2.9573919773101807s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 0.5441665649414062s
Availability | VoID file availability check for HealthCare Ontology took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.25793886184692383s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.695487976074219e-05s
Believability | Calculation of trust value for HealthCare Ontology took 6.67572021484375e-06s
INFO | --- Analysis for HealthCare_Ontology took 3.5468013286590576s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.363059997558594e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.27648234367370605s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.020190954208374023s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.127357482910156e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 7.3909759521484375e-06s
INFO | --- Analysis for heartfailure took 3.039039373397827s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.80839967727661s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.26259803771972656s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 4.601478576660156e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 6.9141387939453125e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 120.17005395889282s
Availability | SPARQL endpoint availability check for Hedatuz took 30.21583104133606s
Availability | VoID file availability check for Hedatuz took 0.0007555484771728516s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.2596139907836914s
Reputation | Calculation of the PageRank for Hedatuz took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 4.601478576660156e-05s
Believability | Calculation of trust value for Hedatuz took 7.62939453125e-06s
INFO | --- Analysis for hedatuz took 92.73525905609131s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.12175703048706055s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004029273986816406s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.25234460830688477s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.0001556873321533203s
Believability | Calculation of trust value for Hellenic Fire Brigade took 5.245208740234375e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.5100483894348145s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.025925397872924805s
Availability | VoID file availability check for Hellenic Police took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.2855091094970703s
Reputation | Calculation of the PageRank for Hellenic Police took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.0001304149627685547s
Believability | Calculation of trust value for Hellenic Police took 4.76837158203125e-06s
INFO | --- Analysis for hellenic-police took 2.4430041313171387s
Availability | SPARQL endpoint availability check for Hermos took 4.363059997558594e-05s
Availability | VoID file availability check for Hermos took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Hermos took 0.25988268852233887s
Reputation | Calculation of the PageRank for Hermos took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for Hermos took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Hermos took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Hermos took 3.0994415283203125e-05s
Believability | Calculation of trust value for Hermos took 7.62939453125e-06s
INFO | --- Analysis for Hermos took 2.756903886795044s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.363059997558594e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.2781538963317871s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 3.838539123535156e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 7.152557373046875e-06s
INFO | --- Analysis for Himanshu_Mahawar took 2.379032850265503s
Availability | SPARQL endpoint availability check for HITO took 0.45339226722717285s
Availability | VoID file availability check for HITO took 0.0006077289581298828s
Extra | Recovery of all triples for HITO took 1.8032660484313965s
Performance | Total latancy measurement for HITO took 0.9843106269836426s
Amount of data | Number of triples check for HITO took 0.2161262035369873s
Interoperability | New terms check for HITO took 1.532658338546753s
Versatility | Languages check for HITO took 0.2341451644897461s
Interpretability | Number of blank nodes check for HITO took 0.22181129455566406s
Interpretability | RDF structures check for HITO took 0.4608168601989746s
Versatility | Serialization formats check for HITO took 0.8060240745544434s
Availability | RDF dump link check for HITO took 0.22672176361083984s
License | MR license check for HITO took 0.20180010795593262s
License | HR license check for HITO took 0.23259210586547852s
Amount of data | Number of property check for HITO took 0.20961451530456543s
Understandability | Number of label check for HITO took 0.2571883201599121s
Understandability | URI regex check for HITO took 0.4164597988128662s
Understandability | Vocabs check for HITO took 0.21690034866333008s
Verifiability | Authors check for HITO took 0.21332049369812012s
Verifiability | Publishers check for HITO took 0.21254253387451172s
Performance | Throughput check for HITO took 11.737304210662842s
Amount of data | Check the number of entities for HITO took 0.00010967254638671875s
Verifiability | Contribs. check for HITO took 0.19561243057250977s
Interlinking | sameAs chians check for HITO took 0.19433832168579102s
Interlinking | skos check for HITO took 0.2307755947113037s
Interlinking | skos check for HITO took 0.19996237754821777s
Timeliness | dataset update frequency check for HITO took 0.19732284545898438s
Currency | Creation date check for HITO took 0.40665435791015625s
Currency | Modification date check for HITO took 0.43125009536743164s
Rep.Conc. | URIs length for HITO took 1.1047227382659912s
Interoperability | New vocabularies check for HITO took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.19026756286621094s
Accuracy | Check Functional Property for HITO took 0.21376442909240723s
Accuracy | Check Inverse Functional Property for HITO took 0.21679234504699707s
Accuracy | Check Empty annotation labels for HITO took 0.6021270751953125s
Accuracy | Check White space in annotation for HITO took 0.019205808639526367s
Accuracy | Check Datatype consistency for HITO took 0.07588958740234375s
Consistency | Disjoint class check for HITO took 0.1974201202392578s
Consistency | Check Misplaced properties for HITO took 0.5632369518280029s
Consistency | Misplaced classes for HITO took 0.37898874282836914s
Consistency | Check Ontology hijacking for HITO took 1.7949306964874268s
Consistency | Check Invalid usage of undefined classes for HITO took 1.2859892845153809s
Consistency | Check Invalid usage of undefined properties for HITO took 1.568659782409668s
Conciseness | Check Extensional conciseness for HITO took 0.06497764587402344s
Conciseness | Check Intensional conciseness for HITO took 0.1995842456817627s
Security | Sign check for HITO took 0.21119308471679688s
Availability | Check URIs Dereferenciability for HITO took 1979.8978168964386s
Completeness | Calculation of interlinking completeness for HITO took 1.4937644004821777s
Reputation | Calculation of the PageRank for HITO took 0.02212357521057129s
Interlinking | Calculation of Degree of Connection for HITO took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for HITO took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for HITO took 7.486343383789062e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.6689300537109375e-06s
Believability | Calculation of trust value for HITO took 7.867813110351562e-06s
INFO | --- Analysis for hito took 2039.0987119674683s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 5.538839340209961s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.724174976348877s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 3.695487976074219e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 6.4373016357421875e-06s
INFO | --- Analysis for Hoa_Thinh_Phat took 14.392825841903687s
Availability | SPARQL endpoint availability check for Homologene took 4.100799560546875e-05s
Availability | VoID file availability check for Homologene took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Homologene took 0.286043643951416s
Reputation | Calculation of the PageRank for Homologene took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for Homologene took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Homologene took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Homologene took 3.24249267578125e-05s
Believability | Calculation of trust value for Homologene took 8.58306884765625e-06s
INFO | --- Analysis for homologene took 2.973762035369873s
Availability | SPARQL endpoint availability check for gseg took 4.2438507080078125e-05s
Availability | VoID file availability check for gseg took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for gseg took 0.25577831268310547s
Reputation | Calculation of the PageRank for gseg took 0.020145416259765625s
Interlinking | Calculation of Degree of Connection for gseg took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for gseg took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for gseg took 2.956390380859375e-05s
Believability | Calculation of trust value for gseg took 6.67572021484375e-06s
INFO | --- Analysis for hongse took 2.8722612857818604s
Availability | SPARQL endpoint availability check for Noticias Universia took 5.316734313964844e-05s
Availability | VoID file availability check for Noticias Universia took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.27602267265319824s
Reputation | Calculation of the PageRank for Noticias Universia took 0.02052450180053711s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 3.147125244140625e-05s
Believability | Calculation of trust value for Noticias Universia took 8.344650268554688e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 2.859436511993408s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.2438507080078125e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.2572176456451416s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 3.361701965332031e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 6.9141387939453125e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 2.891411304473877s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.5992355346679688s
Availability | VoID file availability check for COURAGE Dataset took 0.0007717609405517578s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.24538445472717285s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.24249267578125e-05s
Believability | Calculation of trust value for COURAGE Dataset took 7.62939453125e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 5.1507720947265625s
Availability | SPARQL endpoint availability check for RoadTrb took 4.38690185546875e-05s
Availability | VoID file availability check for RoadTrb took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.2569129467010498s
Reputation | Calculation of the PageRank for RoadTrb took 0.022588014602661133s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.1948089599609375e-05s
Believability | Calculation of trust value for RoadTrb took 6.9141387939453125e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.3665847778320312s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0007381439208984375s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.2778024673461914s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.02086329460144043s
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.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.152557373046875e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 25.251510620117188s
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.00026988983154296875s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.2682054042816162s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.02068805694580078s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 3.337860107421875e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 7.152557373046875e-06s
INFO | --- Analysis for http:pakistan.com took 2.341743230819702s
Availability | SPARQL endpoint availability check for CEDICT took 4.506111145019531e-05s
Availability | VoID file availability check for CEDICT took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for CEDICT took 0.27536916732788086s
Reputation | Calculation of the PageRank for CEDICT took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.910064697265625e-05s
Believability | Calculation of trust value for CEDICT took 8.106231689453125e-06s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.009405851364136s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.5592820644378662s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2550771236419678s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.937980651855469e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.58306884765625e-06s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 4.459334850311279s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.172325134277344e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.27086663246154785s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.02083563804626465s
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.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.147125244140625e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 6.9141387939453125e-06s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 2.8820576667785645s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.4345855712890625e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0003459453582763672s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.2515711784362793s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.218650817871094e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.384868621826172s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.291534423828125e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.25119519233703613s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.022159814834594727s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.552436828613281e-05s
Believability | Calculation of trust value for Soccer Dataset took 6.67572021484375e-06s
INFO | --- Analysis for http:www.msm.com took 2.412438154220581s
Availability | SPARQL endpoint availability check for Game Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Game Ontology took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.27115583419799805s
Reputation | Calculation of the PageRank for Game Ontology took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for Game Ontology took 6.198883056640625e-06s
INFO | --- Analysis for http:www.RAG.comgameonto# took 2.891908884048462s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.982948303222656e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007607936859130859s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.2673187255859375s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0009987354278564453s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.124641418457031e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.58306884765625e-06s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.0897624492645264s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.458427429199219e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.256209135055542s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020338773727416992s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.075599670410156e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 6.9141387939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.3731417655944824s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.7206878662109375e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0003600120544433594s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.23939895629882812s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.075599670410156e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.62939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.3111772537231445s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.1961669921875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.26888346672058105s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020154714584350586s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0994415283203125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.62939453125e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.343475580215454s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.38690185546875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.29056525230407715s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020279645919799805s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.123283386230469e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.67572021484375e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.3803372383117676s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.696846008300781e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2654135227203369s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.0201263427734375s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0994415283203125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.3909759521484375e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 3.805774450302124s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.458427429199219e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.279238224029541s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021027088165283203s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0011925697326660156s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 4.410743713378906e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.62939453125e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.338550329208374s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.792213439941406e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.26718902587890625s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020389080047607422s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.552436828613281e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 7.3909759521484375e-06s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 4.906435966491699s
Availability | SPARQL endpoint availability check for Bookkeeping took 0.9914710521697998s
Availability | VoID file availability check for Bookkeeping took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.2899179458618164s
Reputation | Calculation of the PageRank for Bookkeeping took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bookkeeping took 8.344650268554688e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 3.9686121940612793s
Availability | SPARQL endpoint availability check for Legal Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Legal Ontology took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.2770841121673584s
Reputation | Calculation of the PageRank for Legal Ontology took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.4332275390625e-05s
Believability | Calculation of trust value for Legal Ontology took 1.049041748046875e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 2.8617944717407227s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 5.888938903808594e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.25978684425354004s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020603179931640625s
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.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.82012939453125e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 7.3909759521484375e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.6444921493530273s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.601478576660156e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.26659584045410156s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.020589828491210938s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 3.24249267578125e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 6.4373016357421875e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.6199564933776855s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 4.7206878662109375e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.27634406089782715s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 3.170967102050781e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 7.152557373046875e-06s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 2.8886232376098633s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 5.364418029785156e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2580273151397705s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.02136826515197754s
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.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 4.0531158447265625e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 7.867813110351562e-06s
INFO | --- Analysis for hud-library-usagedata took 2.933997869491577s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.4385707378387451s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.25359463691711426s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020478487014770508s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010919570922851562s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 7.152557373046875e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 4.100795745849609s
Availability | SPARQL endpoint availability check for IATE RDF took 4.172325134277344e-05s
Availability | VoID file availability check for IATE RDF took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.2700929641723633s
Reputation | Calculation of the PageRank for IATE RDF took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.719329833984375e-05s
Believability | Calculation of trust value for IATE RDF took 6.67572021484375e-06s
INFO | --- Analysis for iate-rdf took 2.630080223083496s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.075457334518433s
Availability | VoID file availability check for IATI as Linked Data took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.27950501441955566s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.02046370506286621s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 9.1552734375e-05s
Believability | Calculation of trust value for IATI as Linked Data took 6.4373016357421875e-06s
INFO | --- Analysis for iati-as-linked-data took 12.78819227218628s
Availability | SPARQL endpoint availability check for ICANE took 0.41464900970458984s
Availability | VoID file availability check for ICANE took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for ICANE took 0.2580530643463135s
Reputation | Calculation of the PageRank for ICANE took 0.02036881446838379s
Interlinking | Calculation of Degree of Connection for ICANE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.654594421386719e-05s
Believability | Calculation of trust value for ICANE took 4.291534423828125e-06s
INFO | --- Analysis for icane took 3.4737303256988525s
Availability | SPARQL endpoint availability check for ichoose took 0.1511530876159668s
Availability | VoID file availability check for ichoose took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for ichoose took 0.24855422973632812s
Reputation | Calculation of the PageRank for ichoose took 0.02063608169555664s
Interlinking | Calculation of Degree of Connection for ichoose took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ichoose took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.866455078125e-05s
Believability | Calculation of trust value for ichoose took 6.198883056640625e-06s
INFO | --- Analysis for ichoose took 54.29956555366516s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 1.0153543949127197s
Availability | VoID file availability check for The Iconology Dataset took 0.0006425380706787109s
Extra | Recovery of all triples for The Iconology Dataset took 3.6047844886779785s
Performance | Total latancy measurement for The Iconology Dataset took 0.5394637584686279s
Amount of data | Number of triples check for The Iconology Dataset took 0.21984434127807617s
Interoperability | New terms check for The Iconology Dataset took 1.4601941108703613s
Versatility | Languages check for The Iconology Dataset took 0.8122355937957764s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.20784401893615723s
Interpretability | RDF structures check for The Iconology Dataset took 0.1499941349029541s
Versatility | Serialization formats check for The Iconology Dataset took 0.11168861389160156s
Availability | RDF dump link check for The Iconology Dataset took 0.09871172904968262s
License | MR license check for The Iconology Dataset took 0.12465500831604004s
License | HR license check for The Iconology Dataset took 0.5820918083190918s
Amount of data | Number of property check for The Iconology Dataset took 0.11203598976135254s
Understandability | Number of label check for The Iconology Dataset took 0.17136216163635254s
Understandability | URI regex check for The Iconology Dataset took 0.17666959762573242s
Understandability | Vocabs check for The Iconology Dataset took 0.09493136405944824s
Verifiability | Authors check for The Iconology Dataset took 0.10743904113769531s
Verifiability | Publishers check for The Iconology Dataset took 0.09597969055175781s
Performance | Throughput check for The Iconology Dataset took 10.375701904296875s
Amount of data | Check the number of entities for The Iconology Dataset took 0.00011706352233886719s
Verifiability | Contribs. check for The Iconology Dataset took 0.08938932418823242s
Interlinking | sameAs chians check for The Iconology Dataset took 0.09570741653442383s
Interlinking | skos check for The Iconology Dataset took 0.09674572944641113s
Interlinking | skos check for The Iconology Dataset took 0.0940561294555664s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.09281182289123535s
Currency | Creation date check for The Iconology Dataset took 0.1899259090423584s
Currency | Modification date check for The Iconology Dataset took 0.1999671459197998s
Rep.Conc. | URIs length for The Iconology Dataset took 1.199704885482788s
Interoperability | New vocabularies check for The Iconology Dataset took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08183956146240234s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.2838742733001709s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.016335010528564453s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.44042181968688965s
Consistency | Disjoint class check for The Iconology Dataset took 0.08430004119873047s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.15399932861328125s
Consistency | Misplaced classes for The Iconology Dataset took 0.875190019607544s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.5837528705596924s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.2744271755218506s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.3501033782958984s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.29197216033935547s
Security | Sign check for The Iconology Dataset took 0.08554577827453613s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2550.928211450577s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 0.6401371955871582s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.2874603271484375e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The Iconology Dataset took 8.58306884765625e-06s
INFO | --- Analysis for iconology-dataset took 2616.6690781116486s
Availability | SPARQL endpoint availability check for Identifiers.org took 4.458427429199219e-05s
Availability | VoID file availability check for Identifiers.org took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.2592926025390625s
Reputation | Calculation of the PageRank for Identifiers.org took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 3.695487976074219e-05s
Believability | Calculation of trust value for Identifiers.org took 7.152557373046875e-06s
INFO | --- Analysis for identifiers-org took 3.336643695831299s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.2438507080078125e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.276475191116333s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02025294303894043s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.43865966796875e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 6.67572021484375e-06s
INFO | --- Analysis for idreffr took 4.352930545806885s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 1.3373844623565674s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.27156877517700195s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020515918731689453s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 5.14984130859375e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 7.3909759521484375e-06s
INFO | --- Analysis for ids took 4.152373552322388s
Availability | SPARQL endpoint availability check for ietflang took 4.267692565917969e-05s
Availability | VoID file availability check for ietflang took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for ietflang took 0.2506570816040039s
Reputation | Calculation of the PageRank for ietflang took 0.020117521286010742s
Interlinking | Calculation of Degree of Connection for ietflang took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ietflang took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.410743713378906e-05s
Believability | Calculation of trust value for ietflang took 4.601478576660156e-05s
INFO | --- Analysis for ietflang took 12.598618507385254s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.6144154071807861s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.26680803298950195s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02038264274597168s
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.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.647804260253906e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for IGVLL took 3.995420217514038s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.5640943050384521s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0005314350128173828s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.356309175491333s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 1.4541771411895752s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.20343875885009766s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.5003430843353271s
Versatility | Languages check for 3LGM² IHE Ontology took 0.2259986400604248s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.21753668785095215s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.2558591365814209s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.20852160453796387s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.1978447437286377s
License | MR license check for 3LGM² IHE Ontology took 0.21042490005493164s
License | HR license check for 3LGM² IHE Ontology took 0.21486544609069824s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.19687914848327637s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.22419142723083496s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.40521907806396484s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.20825958251953125s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.22066998481750488s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.19954419136047363s
Performance | Throughput check for 3LGM² IHE Ontology took 11.35624647140503s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 7.62939453125e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.20620203018188477s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.20197129249572754s
Interlinking | skos check for 3LGM² IHE Ontology took 0.1955568790435791s
Interlinking | skos check for 3LGM² IHE Ontology took 0.20471429824829102s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.21512532234191895s
Currency | Creation date check for 3LGM² IHE Ontology took 0.40950942039489746s
Currency | Modification date check for 3LGM² IHE Ontology took 0.41191864013671875s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8077170848846436s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.21269750595092773s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.19854450225830078s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.2104952335357666s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.3489222526550293s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.0028231143951416016s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.0494081974029541s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.1908414363861084s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.4749939441680908s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.29881906509399414s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.6048929691314697s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.268580436706543s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.5265226364135742s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.031131267547607422s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.19001555442810059s
Security | Sign check for 3LGM² IHE Ontology took 0.20043253898620605s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 520.6706216335297s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.33582592010498047s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.021064043045043945s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.9073486328125e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for IHE took 568.4169111251831s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.11054444313049316s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.24467182159423828s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.020841121673583984s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.24249267578125e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 8.106231689453125e-06s
INFO | --- Analysis for iislod-test took 2.8671741485595703s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.887580871582031e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.2650609016418457s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.0207061767578125s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.838539123535156e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 6.4373016357421875e-06s
INFO | --- Analysis for ILUSOC took 14.475353956222534s
Availability | SPARQL endpoint availability check for im@sparql took 7.58381199836731s
Availability | VoID file availability check for im@sparql took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for im@sparql took 0.29692769050598145s
Reputation | Calculation of the PageRank for im@sparql took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.218650817871094e-05s
Believability | Calculation of trust value for im@sparql took 1.1682510375976562e-05s
INFO | --- Analysis for im@sparql took 14.339109897613525s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.363059997558594e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.28221797943115234s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.020700693130493164s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.24249267578125e-05s
Believability | Calculation of trust value for imagery bailingniao took 7.62939453125e-06s
INFO | --- Analysis for imagery_bailingniao took 3.5592494010925293s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.0804698467254639s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0007545948028564453s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 19.904453992843628s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.3378446102142334s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 10.322942733764648s
Interoperability | New terms check for Imagesnippets Image Descriptions took 2.1808922290802s
Versatility | Languages check for Imagesnippets Image Descriptions took 20.715736865997314s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.554933309555054s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.68711256980896s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7127704620361328s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.679295539855957s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.6487469673156738s
License | MR license check for Imagesnippets Image Descriptions took 0.6617758274078369s
License | HR license check for Imagesnippets Image Descriptions took 30.687976360321045s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.6815130710601807s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.5868234634399414s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.343421459197998s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.6985042095184326s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.671750545501709s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.6685318946838379s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.644989252090454s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 6.151199340820312e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.6691460609436035s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.6511561870574951s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7023675441741943s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7090129852294922s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.6599183082580566s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.404858112335205s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.3501274585723877s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 33.83693075180054s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.6448431015014648s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.6617674827575684s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.6526329517364502s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 11.08718991279602s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.2340641021728516s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.281084060668945s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.69716477394104s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 8.097989559173584s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 4.948087453842163s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.381340742111206s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.78665566444397s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 2.8494973182678223s
Security | Sign check for Imagesnippets Image Descriptions took 0.6506612300872803s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 14.183569431304932s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.5482869148254395s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.020305871963500977s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.179115295410156e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.9073486328125e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 7.867813110351562e-06s
INFO | --- Analysis for imagesnippets took 307.0287570953369s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.18696355819702148s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.2530374526977539s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.020301342010498047s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.893013000488281e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 7.62939453125e-06s
INFO | --- Analysis for imf-linked-data took 2.6015572547912598s
Availability | SPARQL endpoint availability check for IMGpedia took 5.125999450683594e-05s
Availability | VoID file availability check for IMGpedia took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.2388901710510254s
Reputation | Calculation of the PageRank for IMGpedia took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for IMGpedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.075599670410156e-05s
Believability | Calculation of trust value for IMGpedia took 7.62939453125e-06s
INFO | --- Analysis for imgpedia took 2.8741681575775146s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 4.076957702636719e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.2561988830566406s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.02030181884765625s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 2.8848648071289062e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 6.198883056640625e-06s
INFO | --- Analysis for import-status-of-gmo-crops took 2.881291389465332s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.315376281738281e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.26523423194885254s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.020519256591796875s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.1682510375976562e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 6.9141387939453125e-06s
INFO | --- Analysis for Imtiaz took 2.417576551437378s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.363059997558594e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.2647280693054199s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.020258665084838867s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 3.0994415283203125e-05s
Believability | Calculation of trust value for Royalty Free Music took 6.67572021484375e-06s
INFO | --- Analysis for inaudio.org took 3.7965304851531982s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.1484832763671875e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.2547123432159424s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 3.0517578125e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 6.9141387939453125e-06s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 2.8306329250335693s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 4.172325134277344e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.25926923751831055s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.020459413528442383s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 3.0517578125e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 6.9141387939453125e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 2.8972246646881104s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.4890775680541992s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.26607179641723633s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.02038288116455078s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 4.57763671875e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 6.4373016357421875e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 3.995728015899658s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.601478576660156e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.2647209167480469s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.020351409912109375s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.075599670410156e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 6.9141387939453125e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 2.922900676727295s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.220008850097656e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0007686614990234375s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.2589871883392334s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.02065443992614746s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.0001347064971923828s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 7.3909759521484375e-06s
INFO | --- Analysis for ineverycrea took 19.203408002853394s
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.00044417381286621094s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.24324703216552734s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020648479461669922s
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.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.799003601074219e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.1682510375976562e-05s
INFO | --- Analysis for ineverycrea-argentina took 10.180506467819214s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 271.6721222400665s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.26104187965393066s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02184748649597168s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 8.916854858398438e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 8.344650268554688e-06s
INFO | --- Analysis for influence-tracker-dataset took 565.2047395706177s
Availability | SPARQL endpoint availability check for INSEMTIVES took 7.104873657226562e-05s
Availability | VoID file availability check for INSEMTIVES took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.2577359676361084s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020722389221191406s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 3.147125244140625e-05s
Believability | Calculation of trust value for INSEMTIVES took 8.58306884765625e-06s
INFO | --- Analysis for insemtives took 4.442819356918335s
Availability | SPARQL endpoint availability check for instagram.person took 4.172325134277344e-05s
Availability | VoID file availability check for instagram.person took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for instagram.person took 0.2739865779876709s
Reputation | Calculation of the PageRank for instagram.person took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for instagram.person took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for instagram.person took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for instagram.person took 3.24249267578125e-05s
Believability | Calculation of trust value for instagram.person took 6.9141387939453125e-06s
INFO | --- Analysis for instagram_person took 3.4096901416778564s
Availability | SPARQL endpoint availability check for instagram.videoobject took 4.172325134277344e-05s
Availability | VoID file availability check for instagram.videoobject took 0.0003139972686767578s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.2710397243499756s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.021261215209960938s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 3.62396240234375e-05s
Believability | Calculation of trust value for instagram.videoobject took 7.152557373046875e-06s
INFO | --- Analysis for instagram_videoobject took 2.858081340789795s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.1484832763671875e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.23314428329467773s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 2.9325485229492188e-05s
Believability | Calculation of trust value for Instance Hub Countries took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-countries took 2.7774996757507324s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 5.459785461425781e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.2816786766052246s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 2.956390380859375e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.2889177799224854s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.076957702636719e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.25583887100219727s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.020192623138427734s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-organizations took 2.8568062782287598s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.2438507080078125e-05s
Availability | VoID file availability check for Instance Hub People took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.27976107597351074s
Reputation | Calculation of the PageRank for Instance Hub People took 0.020352840423583984s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 3.24249267578125e-05s
Believability | Calculation of trust value for Instance Hub People took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-people took 2.9318978786468506s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 4.1484832763671875e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.25573277473449707s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.020966529846191406s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 3.147125244140625e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 6.198883056640625e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 2.930084228515625s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.2974698543548584s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.020632028579711914s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.123283386230469e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 6.4373016357421875e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.927672863006592s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.2728264331817627s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 3.075599670410156e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 6.67572021484375e-06s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.8873372077941895s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.2643404006958008s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.02048349380493164s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.0279159545898438e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 1.2636184692382812e-05s
INFO | --- Analysis for instance-hub-us-crops took 2.9085896015167236s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.2527742385864258s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.02057027816772461s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 3.075599670410156e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 6.4373016357421875e-06s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.8843376636505127s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 4.649162292480469e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.0003581047058105469s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.2672102451324463s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.147125244140625e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 2.898536443710327s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 3.981590270996094e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.2566030025482178s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.02051091194152832s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 3.218650817871094e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 1.1682510375976562e-05s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 2.9630138874053955s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 4.1961669921875e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0003085136413574219s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.25487208366394043s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.020283222198486328s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 4.9591064453125e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 7.62939453125e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 2.874264717102051s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.3392181396484375e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0003376007080078125s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.27383947372436523s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.02048182487487793s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.846687316894531e-05s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 6.67572021484375e-06s
INFO | --- Analysis for interactivemaps-gnoss took 11.869836568832397s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.172325134277344e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.2641615867614746s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.027137041091918945s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 2.574920654296875e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0019919872283935547s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 4.935264587402344e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 1.0967254638671875e-05s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 2.9464352130889893s
Availability | SPARQL endpoint availability check for intervalue took 0.1490917205810547s
Availability | VoID file availability check for intervalue took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for intervalue took 0.25503110885620117s
Reputation | Calculation of the PageRank for intervalue took 0.020392894744873047s
Interlinking | Calculation of Degree of Connection for intervalue took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.818771362304688e-05s
Believability | Calculation of trust value for intervalue took 7.152557373046875e-06s
INFO | --- Analysis for intervalue took 2.4846320152282715s
Availability | SPARQL endpoint availability check for Inztrow took 4.291534423828125e-05s
Availability | VoID file availability check for Inztrow took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for Inztrow took 0.27199602127075195s
Reputation | Calculation of the PageRank for Inztrow took 0.020528316497802734s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.24249267578125e-05s
Believability | Calculation of trust value for Inztrow took 6.9141387939453125e-06s
INFO | --- Analysis for Inztrow took 3.5153744220733643s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.28055238723754883s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.0202023983001709s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 6.67572021484375e-06s
INFO | --- Analysis for ipbes took 3.7202444076538086s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.291534423828125e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.2817249298095703s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007984638214111328s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 5.054473876953125e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 6.67572021484375e-06s
INFO | --- Analysis for iptc-newscodes took 3.5684425830841064s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.1961669921875e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.2912752628326416s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020257949829101562s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.0040740966796875e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 6.9141387939453125e-06s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 2.877896547317505s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 1.904050350189209s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.28164029121398926s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.02028656005859375s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.989738464355469e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 6.67572021484375e-06s
INFO | --- Analysis for iserve took 6.628681898117065s
Availability | SPARQL endpoint availability check for ISIC V4 took 20.91726040840149s
Availability | VoID file availability check for ISIC V4 took 0.0008392333984375s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.2804429531097412s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020513057708740234s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 4.267692565917969e-05s
Believability | Calculation of trust value for ISIC V4 took 5.245208740234375e-06s
INFO | --- Analysis for isic-v4 took 115.14241123199463s
Availability | SPARQL endpoint availability check for Isidore took 4.1961669921875e-05s
Availability | VoID file availability check for Isidore took 0.00029659271240234375s
Completeness | Calculation of interlinking completeness for Isidore took 0.24220943450927734s
Reputation | Calculation of the PageRank for Isidore took 0.020604848861694336s
Interlinking | Calculation of Degree of Connection for Isidore took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Isidore took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Isidore took 3.361701965332031e-05s
Believability | Calculation of trust value for Isidore took 7.152557373046875e-06s
INFO | --- Analysis for isidore took 2.830657720565796s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.2438507080078125e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.3696868419647217s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020520448684692383s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.033348083496094e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 5.0067901611328125e-06s
INFO | --- Analysis for isil-dbpedia took 4.322514772415161s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 8.654594421386719e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.26047587394714355s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.020654916763305664s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 3.409385681152344e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 7.3909759521484375e-06s
INFO | --- Analysis for iso-3166-2-data took 2.9017999172210693s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.38690185546875e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.25245213508605957s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.8623809814453125e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 7.867813110351562e-06s
INFO | --- Analysis for iso-639-oasis took 3.2830634117126465s
Availability | SPARQL endpoint availability check for ISOcat took 4.267692565917969e-05s
Availability | VoID file availability check for ISOcat took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for ISOcat took 0.3159158229827881s
Reputation | Calculation of the PageRank for ISOcat took 0.020613431930541992s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.985664367675781e-05s
Believability | Calculation of trust value for ISOcat took 9.775161743164062e-06s
INFO | --- Analysis for isocat took 33.8891658782959s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 5.8650970458984375e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.29341793060302734s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.719329833984375e-05s
Believability | Calculation of trust value for ISOcat-metadata took 6.9141387939453125e-06s
INFO | --- Analysis for isocat-metadata took 4.82358193397522s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.0531158447265625e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.27437853813171387s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.020282745361328125s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 3.0279159545898438e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 7.3909759521484375e-06s
INFO | --- Analysis for ispra-lod-ihi took 2.8649909496307373s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09928178787231445s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0005724430084228516s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.318673133850098s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.24864768981933594s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.11958098411560059s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.9178316593170166s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.06702256202698s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.05334758758544922s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.03135204315185547s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08270955085754395s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.06763100624084473s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.056577205657958984s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.11065983772277832s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.44016361236572s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.05456733703613281s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2050468921661377s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2109389305114746s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08793902397155762s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0935826301574707s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.05110597610473633s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.170659065246582s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.557868957519531e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.08665275573730469s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14828777313232422s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.34218692779541016s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.34020447731018066s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.09710240364074707s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10238194465637207s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.04980802536010742s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 13.475007772445679s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.04811882972717285s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.05313277244567871s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.06271886825561523s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.6407201290130615s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.31165170669555664s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2627427577972412s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.050829410552978516s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.474185228347778s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.8604309558868408s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.7487430572509766s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.268420934677124s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.75028371810913s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.28839659690856934s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.06904029846191406s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.07877874374389648s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 13.393094062805176s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.34289073944091797s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.020788908004760742s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00010013580322265625s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.430511474609375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.344650268554688e-06s
INFO | --- Analysis for ispra-lod-place took 449.93810749053955s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.2438507080078125e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.6948413848876953s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.147125244140625e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 7.3909759521484375e-06s
INFO | --- Analysis for ispra-lod-rmn took 4.214282989501953s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.05037832260131836s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0003261566162109375s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 5.391316890716553s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.23993563652038574s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.1185147762298584s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.993018388748169s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 90.08006811141968s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.06386446952819824s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.035471439361572266s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.08653688430786133s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.06777143478393555s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.05715823173522949s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.11855053901672363s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 90.87321329116821s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.05292820930480957s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.2109065055847168s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.21282672882080078s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.08769011497497559s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.09226679801940918s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.051598310470581055s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.14008355140686s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 8.630752563476562e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.08900976181030273s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.15076422691345215s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.35398387908935547s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.35070013999938965s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.09172415733337402s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.10446429252624512s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.05286860466003418s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 13.453340768814087s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.0506899356842041s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.05921030044555664s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.05377912521362305s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 2.6740224361419678s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.3043215274810791s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.27500224113464355s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.057587623596191406s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.520414113998413s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.8796899318695068s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 2.7789063453674316s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.2815465927124023s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.821147918701172s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.2935945987701416s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.0610044002532959s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.07575583457946777s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 12.11247444152832s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.36222386360168457s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.02095627784729004s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.220008850097656e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 1.2636184692382812e-05s
INFO | --- Analysis for ispra-lod-ron took 441.9697184562683s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 4.291534423828125e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.267864465713501s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 3.361701965332031e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 7.867813110351562e-06s
INFO | --- Analysis for ispra-lod-sc took 3.495388984680176s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.6938209533691406s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.2717111110687256s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 0.000102996826171875s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 5.7220458984375e-06s
INFO | --- Analysis for issa-agritrop took 4.932842254638672s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.38690185546875e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2576889991760254s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020459651947021484s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.1948089599609375e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 7.3909759521484375e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.354034662246704s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 5.555152893066406e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.26575469970703125s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.147125244140625e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 6.9141387939453125e-06s
INFO | --- Analysis for ISSN:_0080-3626 took 2.7901198863983154s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.482269287109375e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.25348997116088867s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.020679712295532227s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.409385681152344e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 8.344650268554688e-06s
INFO | --- Analysis for ISSN:_0080-3626. took 2.6056902408599854s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.203965425491333s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.2596566677093506s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020226716995239258s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.702278137207031e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 4.76837158203125e-06s
INFO | --- Analysis for istat-immigration took 3.537716865539551s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 4.1961669921875e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.25971221923828125s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.021137714385986328s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0010037422180175781s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 4.458427429199219e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 8.58306884765625e-06s
INFO | --- Analysis for istat-immigrazione took 2.861100435256958s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.40430331230163574s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0011675357818603516s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.24079656600952148s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 3.123283386230469e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 4.5299530029296875e-06s
INFO | --- Analysis for it-aifa-drug-prices took 3.0396199226379395s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.1609444618225098s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.2573413848876953s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020215749740600586s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.557868957519531e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 7.62939453125e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 3.5135343074798584s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.220008850097656e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.2587010860443115s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 3.2901763916015625e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 7.3909759521484375e-06s
INFO | --- Analysis for iucr-acta-cryst-e took 2.843485116958618s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.172325134277344e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.25983691215515137s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 3.314018249511719e-05s
Believability | Calculation of trust value for IWMI Research Reports took 6.67572021484375e-06s
INFO | --- Analysis for iwmi-research-reports took 2.7686691284179688s
Availability | SPARQL endpoint availability check for IWN took 4.363059997558594e-05s
Availability | VoID file availability check for IWN took 0.0003833770751953125s
Completeness | Calculation of interlinking completeness for IWN took 0.24528050422668457s
Reputation | Calculation of the PageRank for IWN took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for IWN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IWN took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for IWN took 3.814697265625e-05s
Believability | Calculation of trust value for IWN took 7.3909759521484375e-06s
INFO | --- Analysis for iwn took 2.7273993492126465s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 4.267692565917969e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.25382351875305176s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.020519733428955078s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 3.123283386230469e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 7.152557373046875e-06s
INFO | --- Analysis for j-global-knowledge took 2.8235888481140137s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 4.3392181396484375e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.2665262222290039s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.020137786865234375s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 2.9802322387695312e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 6.67572021484375e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 2.8942439556121826s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 9.295165061950684s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0007526874542236328s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.24705910682678223s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.270408630371094e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 7.152557373046875e-06s
INFO | --- Analysis for jamendo-dbtune took 25.452926635742188s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 5.53131103515625e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.2692570686340332s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020212411880493164s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.553794860839844e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.387504577636719s
Availability | SPARQL endpoint availability check for JEL Classification took 4.506111145019531e-05s
Availability | VoID file availability check for JEL Classification took 0.0003650188446044922s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.27138447761535645s
Reputation | Calculation of the PageRank for JEL Classification took 0.02068305015563965s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.4809112548828125e-05s
Believability | Calculation of trust value for JEL Classification took 6.198883056640625e-06s
INFO | --- Analysis for jel-classification took 4.905210494995117s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.1979291439056396s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.26799774169921875s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020794391632080078s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.337860107421875e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 8.106231689453125e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 7.080051422119141s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.35949897766113s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.2844510078430176s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.02076578140258789s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.462501525878906e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 6.9141387939453125e-06s
INFO | --- Analysis for jita took 540.1839125156403s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 7.605552673339844e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.25455355644226074s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.021356821060180664s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0009777545928955078s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 3.647804260253906e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 7.62939453125e-06s
INFO | --- Analysis for jmdict took 3.298499584197998s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.056875944137573s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.26065683364868164s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.022480010986328125s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 0.00010347366333007812s
Believability | Calculation of trust value for John Goodwin's Family Tree took 7.867813110351562e-06s
INFO | --- Analysis for john-goodwins-family-tree took 63.0495069026947s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.291534423828125e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.2824857234954834s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 4.076957702636719e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 7.152557373046875e-06s
INFO | --- Analysis for jp-cos took 4.393779516220093s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.2438507080078125e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0007612705230712891s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.2770974636077881s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.020694255828857422s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 4.100799560546875e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 7.867813110351562e-06s
INFO | --- Analysis for jp-textbook took 4.345847129821777s
Availability | SPARQL endpoint availability check for JRC-Names took 4.38690185546875e-05s
Availability | VoID file availability check for JRC-Names took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.25191664695739746s
Reputation | Calculation of the PageRank for JRC-Names took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.981590270996094e-05s
Believability | Calculation of trust value for JRC-Names took 7.3909759521484375e-06s
INFO | --- Analysis for jrc-names-ec took 5.169707775115967s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.0975580215454102s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.2577192783355713s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.021047353744506836s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 7.224082946777344e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 7.62939453125e-06s
INFO | --- Analysis for jrc-names-mlode took 3.588974952697754s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.38690185546875e-05s
Availability | VoID file availability check for JudaicaLink took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.27338552474975586s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00010323524475097656s
Believability | Calculation of trust value for JudaicaLink took 8.58306884765625e-06s
INFO | --- Analysis for judaicalink took 22.522752285003662s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 4.1484832763671875e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.24611949920654297s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.020794391632080078s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 3.337860107421875e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 1.2159347534179688e-05s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.8082070350646973s
Availability | SPARQL endpoint availability check for KAKEN took 4.601478576660156e-05s
Availability | VoID file availability check for KAKEN took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for KAKEN took 0.26446008682250977s
Reputation | Calculation of the PageRank for KAKEN took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for KAKEN took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for KAKEN took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for KAKEN took 3.170967102050781e-05s
Believability | Calculation of trust value for KAKEN took 8.106231689453125e-06s
INFO | --- Analysis for kaken took 2.854569673538208s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.06822800636291504s
Availability | VoID file availability check for Kallikratis municipalities took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.25430870056152344s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.021071434020996094s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.560585021972656e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 5.4836273193359375e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.4261434078216553s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.0531158447265625e-05s
Availability | VoID file availability check for Openflights Routes took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.2654542922973633s
Reputation | Calculation of the PageRank for Openflights Routes took 0.02068805694580078s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.266334533691406e-05s
Believability | Calculation of trust value for Openflights Routes took 7.867813110351562e-06s
INFO | --- Analysis for kasabi-openflights-routes took 2.9124042987823486s
Availability | SPARQL endpoint availability check for EU Soccer League took 4.6253204345703125e-05s
Availability | VoID file availability check for EU Soccer League took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.2811729907989502s
Reputation | Calculation of the PageRank for EU Soccer League took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.1948089599609375e-05s
Believability | Calculation of trust value for EU Soccer League took 6.9141387939453125e-06s
INFO | --- Analysis for KG:Course_Submission took 5.584635257720947s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 4.1484832763671875e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.24524998664855957s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.33514404296875e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 5.0067901611328125e-06s
INFO | --- Analysis for KING took 2.6263952255249023s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.696846008300781e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.2766139507293701s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.021167516708374023s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 7.128715515136719e-05s
Believability | Calculation of trust value for Klappstuhlclub took 5.245208740234375e-06s
INFO | --- Analysis for klappstuhlclub took 12.538032531738281s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.845457792282104s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.279407262802124s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.020564794540405273s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 7.033348083496094e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 8.821487426757812e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.301677703857422s
Availability | SPARQL endpoint availability check for Knowledge Forest took 5.8650970458984375e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2734215259552002s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020672321319580078s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.266334533691406e-05s
Believability | Calculation of trust value for Knowledge Forest took 6.67572021484375e-06s
INFO | --- Analysis for knowledge-map took 2.892733335494995s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.410743713378906e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2432551383972168s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02024102210998535s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.1948089599609375e-05s
Believability | Calculation of trust value for Knowledge Forest took 6.9141387939453125e-06s
INFO | --- Analysis for KnowledgeFusion took 2.3694074153900146s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.482269287109375e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.2712366580963135s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 7.295608520507812e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 1.3828277587890625e-05s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.250362873077393s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 4.410743713378906e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.25692224502563477s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.02077031135559082s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 3.504753112792969e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 7.62939453125e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 2.9398155212402344s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.76837158203125e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.25014328956604004s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.600120544433594e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0728836059570312e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.3438773155212402s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 5.435943603515625e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.2639198303222656s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 3.504753112792969e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 8.344650268554688e-06s
INFO | --- Analysis for ktr took 2.9063756465911865s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.4345855712890625e-05s
Availability | VoID file availability check for Informatics Studies took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.25725793838500977s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020633220672607422s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 3.337860107421875e-05s
Believability | Calculation of trust value for Informatics Studies took 7.3909759521484375e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 2.987379789352417s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.07464981079101562s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.27227020263671875s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 4.1961669921875e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 7.3909759521484375e-06s
INFO | --- Analysis for kupkb took 9.864481210708618s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 4.1961669921875e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.2664353847503662s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 3.910064697265625e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 6.198883056640625e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.8417580127716064s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 10.131664752960205s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006051063537597656s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.3661484718322754s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.02060079574584961s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.224082946777344e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 6.67572021484375e-06s
INFO | --- Analysis for l3s-dblp took 48.91838502883911s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 24.26149344444275s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.2852027416229248s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.02104496955871582s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 7.295608520507812e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 8.106231689453125e-06s
INFO | --- Analysis for lak-dataset took 67.34702157974243s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.24333810806274414s
Availability | VoID file availability check for  Language Name Authority List  took 0.0007231235504150391s
Extra | Recovery of all triples for  Language Name Authority List  took 167.91440749168396s
Performance | Total latancy measurement for  Language Name Authority List  took 0.6022031307220459s
Amount of data | Number of triples check for  Language Name Authority List  took 246.13628315925598s
Interoperability | New terms check for  Language Name Authority List  took 81.75070834159851s
Versatility | Languages check for  Language Name Authority List  took 300.085488319397s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 15.24907374382019s
Security | Check HTTPS for  Language Name Authority List  took 0.37601375579833984s
Interpretability | RDF structures check for  Language Name Authority List  took 0.5470991134643555s
Versatility | Serialization formats check for  Language Name Authority List  took 3.9188880920410156s
Availability | RDF dump link check for  Language Name Authority List  took 0.2882697582244873s
License | MR license check for  Language Name Authority List  took 0.4298701286315918s
License | HR license check for  Language Name Authority List  took 300.05151557922363s
Amount of data | Number of property check for  Language Name Authority List  took 0.16300630569458008s
Understandability | Number of label check for  Language Name Authority List  took 1.6441140174865723s
Understandability | URI regex check for  Language Name Authority List  took 0.38117170333862305s
Understandability | Vocabs check for  Language Name Authority List  took 0.12179207801818848s
Verifiability | Authors check for  Language Name Authority List  took 0.23753738403320312s
Verifiability | Publishers check for  Language Name Authority List  took 0.22458600997924805s
Performance | Throughput check for  Language Name Authority List  took 10.668444156646729s
Amount of data | Check the number of entities for  Language Name Authority List  took 0.0001087188720703125s
Verifiability | Contribs. check for  Language Name Authority List  took 0.19579577445983887s
Interlinking | sameAs chians check for  Language Name Authority List  took 7.378003120422363s
Interlinking | skos check for  Language Name Authority List  took 0.3221406936645508s
Interlinking | skos check for  Language Name Authority List  took 0.38953590393066406s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.28524231910705566s
Currency | Creation date check for  Language Name Authority List  took 0.4025747776031494s
Currency | Modification date check for  Language Name Authority List  took 0.12789607048034668s
Rep.Conc. | URIs length for  Language Name Authority List  took 425.4855070114136s
Interoperability | New vocabularies check for  Language Name Authority List  took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.14858007431030273s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.14827919006347656s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.16058087348937988s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 39.09284424781799s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.1890244483947754s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.8095948696136475s
Consistency | Disjoint class check for  Language Name Authority List  took 0.1230928897857666s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.47072744369507s
Consistency | Misplaced classes for  Language Name Authority List  took 8.955646514892578s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 37.33719301223755s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.6730802059173584s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.54188418388367s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 3.0844902992248535s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.5057852268218994s
Security | Sign check for  Language Name Authority List  took 0.10660743713378906s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 16.727502822875977s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 1.2053651809692383s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.021448612213134766s
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.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.489059448242188e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 2.384185791015625e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 7.62939453125e-06s
INFO | --- Analysis for language-authority-list took 15319.504811525345s
Availability | SPARQL endpoint availability check for Lark took 385.75378465652466s
Availability | VoID file availability check for Lark took 0.0008530616760253906s
Completeness | Calculation of interlinking completeness for Lark took 0.5314385890960693s
Reputation | Calculation of the PageRank for Lark took 0.020978450775146484s
Interlinking | Calculation of Degree of Connection for Lark took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Lark took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Lark took 9.274482727050781e-05s
Believability | Calculation of trust value for Lark took 8.106231689453125e-06s
INFO | --- Analysis for LARK took 1682.2073678970337s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.6236085891723633s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0007228851318359375s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.2655370235443115s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020960569381713867s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 4.1484832763671875e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 9.059906005859375e-06s
INFO | --- Analysis for LASLA took 5.411550998687744s
Availability | SPARQL endpoint availability check for LATC Linksets took 4.315376281738281e-05s
Availability | VoID file availability check for LATC Linksets took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.29059481620788574s
Reputation | Calculation of the PageRank for LATC Linksets took 0.021516799926757812s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0010170936584472656s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 4.5299530029296875e-05s
Believability | Calculation of trust value for LATC Linksets took 7.62939453125e-06s
INFO | --- Analysis for latc-linksets took 2.9618237018585205s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.5039918422698975s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.25249719619750977s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.031505584716796875s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0013537406921386719s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 5.745887756347656e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 9.059906005859375e-06s
INFO | --- Analysis for Latin_Vallex2.0 took 3.937499761581421s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.5205733776092529s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0009553432464599609s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.2618279457092285s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 4.172325134277344e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 7.62939453125e-06s
INFO | --- Analysis for LatinAffectus took 3.8221466541290283s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.476895809173584s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.26523375511169434s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.020815610885620117s
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.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.792213439941406e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 8.344650268554688e-06s
INFO | --- Analysis for LatinWordnetLiLa took 4.3612329959869385s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.220008850097656e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.27950191497802734s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.020870447158813477s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 3.457069396972656e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 7.62939453125e-06s
INFO | --- Analysis for lcc took 2.8602466583251953s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 5.2928924560546875e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.2420196533203125s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00012803077697753906s
Believability | Calculation of trust value for Library of Congress Subject Headings took 6.9141387939453125e-06s
INFO | --- Analysis for lcsh took 6.391722679138184s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.3392181396484375e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.2472829818725586s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.02079606056213379s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 9.202957153320312e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 7.152557373046875e-06s
INFO | --- Analysis for lcsubjects took 2.58748197555542s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 5.4836273193359375e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.25730156898498535s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.02073192596435547s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 3.337860107421875e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 6.4373016357421875e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 2.7685794830322266s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 9.202871084213257s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0007615089416503906s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.26412010192871094s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 5.221366882324219e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 8.106231689453125e-06s
INFO | --- Analysis for ldt@library took 36.05036425590515s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 5.745887756347656e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.25867724418640137s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.020800352096557617s
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.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 3.0517578125e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 1.3589859008789062e-05s
INFO | --- Analysis for learned-genre-ontology-eng took 2.843393564224243s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 4.38690185546875e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.2485945224761963s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.020662784576416016s
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.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 3.1948089599609375e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 6.67572021484375e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 2.895749807357788s
Availability | SPARQL endpoint availability check for U ime Legije took 4.696846008300781e-05s
Availability | VoID file availability check for U ime Legije took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.25553178787231445s
Reputation | Calculation of the PageRank for U ime Legije took 0.020873069763183594s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.170967102050781e-05s
Believability | Calculation of trust value for U ime Legije took 6.9141387939453125e-06s
INFO | --- Analysis for LEGIJA_STRANACA took 2.2818565368652344s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 4.315376281738281e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.26924991607666016s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 3.2901763916015625e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 7.152557373046875e-06s
INFO | --- Analysis for legislation-openuplabs took 2.749506711959839s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.5267884731292725s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.2781355381011963s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.653236389160156e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.1444091796875e-05s
INFO | --- Analysis for LemmaBank took 4.514360189437866s
Availability | SPARQL endpoint availability check for lemonUby took 4.410743713378906e-05s
Availability | VoID file availability check for lemonUby took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for lemonUby took 0.26613926887512207s
Reputation | Calculation of the PageRank for lemonUby took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.818771362304688e-05s
Believability | Calculation of trust value for lemonUby took 7.62939453125e-06s
INFO | --- Analysis for lemonuby took 3.2962937355041504s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.458427429199219e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.27793359756469727s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.02076101303100586s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.933906555175781e-05s
Believability | Calculation of trust value for LemonWiktionary took 7.3909759521484375e-06s
INFO | --- Analysis for lemonwiktionary took 4.2075464725494385s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.47787976264953613s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0006899833679199219s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.26792192459106445s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.020781755447387695s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0008263587951660156s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 4.410743713378906e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for LewisShort took 3.9025352001190186s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.4891409873962402s
Availability | VoID file availability check for LEXIN-RDF took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.26934242248535156s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.02071356773376465s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.24249267578125e-05s
Believability | Calculation of trust value for LEXIN-RDF took 8.821487426757812e-06s
INFO | --- Analysis for lexin-rdf took 6.0527074337005615s
Availability | SPARQL endpoint availability check for lexinfo took 7.843971252441406e-05s
Availability | VoID file availability check for lexinfo took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for lexinfo took 0.2624187469482422s
Reputation | Calculation of the PageRank for lexinfo took 0.020601987838745117s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.96453857421875e-05s
Believability | Calculation of trust value for lexinfo took 8.106231689453125e-06s
INFO | --- Analysis for lexinfo took 4.351367950439453s
Availability | SPARQL endpoint availability check for Lexvo took 4.2438507080078125e-05s
Availability | VoID file availability check for Lexvo took 0.0010516643524169922s
Completeness | Calculation of interlinking completeness for Lexvo took 0.2587904930114746s
Reputation | Calculation of the PageRank for Lexvo took 0.020686864852905273s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.0001785755157470703s
Believability | Calculation of trust value for Lexvo took 7.152557373046875e-06s
INFO | --- Analysis for lexvo took 2.8719875812530518s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.482269287109375e-05s
Availability | VoID file availability check for Lexvo.org took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.2478175163269043s
Reputation | Calculation of the PageRank for Lexvo.org took 0.020490169525146484s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.486343383789062e-05s
Believability | Calculation of trust value for Lexvo.org took 8.344650268554688e-06s
INFO | --- Analysis for lexvo-org took 2.4309301376342773s
Availability | SPARQL endpoint availability check for LIBRIS took 0.39269375801086426s
Availability | VoID file availability check for LIBRIS took 0.0003879070281982422s
Extra | Recovery of all triples for LIBRIS took 6.204704523086548s
Performance | Total latancy measurement for LIBRIS took 0.730396032333374s
Amount of data | Number of triples check for LIBRIS took 20.675487756729126s
Interoperability | New terms check for LIBRIS took 15.231269359588623s
Versatility | Languages check for LIBRIS took 0.17197394371032715s
Interpretability | Number of blank nodes check for LIBRIS took 300.07284212112427s
Security | Check HTTPS for LIBRIS took 0.3568134307861328s
Interpretability | RDF structures check for LIBRIS took 0.16765236854553223s
Versatility | Serialization formats check for LIBRIS took 0.20415496826171875s
Availability | RDF dump link check for LIBRIS took 0.1353893280029297s
License | MR license check for LIBRIS took 0.24549341201782227s
License | HR license check for LIBRIS took 0.2683720588684082s
Amount of data | Number of property check for LIBRIS took 0.1744096279144287s
Understandability | Number of label check for LIBRIS took 0.5343801975250244s
Understandability | URI regex check for LIBRIS took 0.3831777572631836s
Understandability | Vocabs check for LIBRIS took 0.15118193626403809s
Verifiability | Authors check for LIBRIS took 0.17146730422973633s
Verifiability | Publishers check for LIBRIS took 0.16856980323791504s
Performance | Throughput check for LIBRIS took 11.22201943397522s
Amount of data | Check the number of entities for LIBRIS took 0.00011157989501953125s
Verifiability | Contribs. check for LIBRIS took 0.1836855411529541s
Interlinking | sameAs chians check for LIBRIS took 0.19422507286071777s
Interlinking | skos check for LIBRIS took 0.3757765293121338s
Interlinking | skos check for LIBRIS took 0.14596343040466309s
Timeliness | dataset update frequency check for LIBRIS took 0.14847302436828613s
Currency | Creation date check for LIBRIS took 0.37360119819641113s
Currency | Modification date check for LIBRIS took 0.6183147430419922s
Rep.Conc. | URIs length for LIBRIS took 81.02798628807068s
Interoperability | New vocabularies check for LIBRIS took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.1566770076751709s
Accuracy | Check Functional Property for LIBRIS took 0.2162928581237793s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.18452024459838867s
Accuracy | Check Datatype consistency for LIBRIS took 0.2797966003417969s
Consistency | Disjoint class check for LIBRIS took 0.21116995811462402s
Consistency | Check Misplaced properties for LIBRIS took 61.96723985671997s
Consistency | Misplaced classes for LIBRIS took 1.104701042175293s
Consistency | Check Ontology hijacking for LIBRIS took 3.1950721740722656s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.312434196472168s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 63.00207781791687s
Conciseness | Check Extensional conciseness for LIBRIS took 0.28986573219299316s
Conciseness | Check Intensional conciseness for LIBRIS took 0.40551018714904785s
Security | Sign check for LIBRIS took 0.2982289791107178s
Availability | Check URIs Dereferenciability for LIBRIS took 14.85472846031189s
Completeness | Calculation of interlinking completeness for LIBRIS took 1.257840633392334s
Reputation | Calculation of the PageRank for LIBRIS took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 0.00010275840759277344s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.9073486328125e-06s
Believability | Calculation of trust value for LIBRIS took 1.2159347534179688e-05s
INFO | --- Analysis for libris took 1072.2623682022095s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.07033467292785645s
Availability | VoID file availability check for Public Library of Veroia took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.28261709213256836s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.02106451988220215s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.939338684082031e-05s
Believability | Calculation of trust value for Public Library of Veroia took 6.67572021484375e-06s
INFO | --- Analysis for libver took 4.1026997566223145s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.15639567375183105s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.24706339836120605s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.020888090133666992s
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.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.440017700195312e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 5.4836273193359375e-06s
INFO | --- Analysis for lichfield-spending took 2.5285110473632812s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.220008850097656e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0007348060607910156s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.2579526901245117s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.02093815803527832s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.695487976074219e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 7.3909759521484375e-06s
INFO | --- Analysis for lime took 6.443398475646973s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 7.486343383789062e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.481001615524292s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.26348876953125s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010728836059570312s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 6.67572021484375e-06s
INFO | --- Analysis for lingvoj took 10.245088815689087s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.363059997558594e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.2901935577392578s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.021048307418823242s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.726119995117188e-05s
Believability | Calculation of trust value for Linked Crunchbase took 8.106231689453125e-06s
INFO | --- Analysis for linked-crunchbase took 14.931698083877563s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.075144052505493s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0008151531219482422s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.2539191246032715s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.021025896072387695s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 8.940696716308594e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.2159347534179688e-05s
INFO | --- Analysis for linked-drugs took 22.102717876434326s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.57763671875e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.25266051292419434s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 0.00010418891906738281s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 5.7220458984375e-06s
INFO | --- Analysis for linked-edgar took 4.061367034912109s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.506111145019531e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.25362586975097656s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.021116971969604492s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 0.00010251998901367188s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 7.62939453125e-06s
INFO | --- Analysis for linked-eurostat took 5.224725723266602s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.410743713378906e-05s
Availability | VoID file availability check for linked hypernyms took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.2559788227081299s
Reputation | Calculation of the PageRank for linked hypernyms took 0.021300315856933594s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 8.106231689453125e-05s
Believability | Calculation of trust value for linked hypernyms took 8.58306884765625e-06s
INFO | --- Analysis for linked-hypernyms took 3.2805211544036865s
Availability | SPARQL endpoint availability check for Linked Life Data took 239.39357948303223s
Availability | VoID file availability check for Linked Life Data took 0.0009617805480957031s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.8812158107757568s
Reputation | Calculation of the PageRank for Linked Life Data took 0.021045446395874023s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 5.3882598876953125e-05s
Believability | Calculation of trust value for Linked Life Data took 7.62939453125e-06s
INFO | --- Analysis for linked-life-data took 723.1921730041504s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.24630999565124512s
Availability | VoID file availability check for Linked Logainm took 0.0005955696105957031s
Extra | Recovery of all triples for Linked Logainm took 1.7681105136871338s
Performance | Total latancy measurement for Linked Logainm took 0.5403997898101807s
Amount of data | Number of triples check for Linked Logainm took 0.12526416778564453s
Interoperability | New terms check for Linked Logainm took 1.5088703632354736s
Versatility | Languages check for Linked Logainm took 1.541701078414917s
Interpretability | Number of blank nodes check for Linked Logainm took 0.1190345287322998s
Security | Check HTTPS for Linked Logainm took 0.27068471908569336s
Interpretability | RDF structures check for Linked Logainm took 0.20623087882995605s
Versatility | Serialization formats check for Linked Logainm took 0.12524056434631348s
Availability | RDF dump link check for Linked Logainm took 0.11439132690429688s
License | MR license check for Linked Logainm took 0.13397789001464844s
License | HR license check for Linked Logainm took 0.11232924461364746s
Amount of data | Number of property check for Linked Logainm took 0.12591767311096191s
Understandability | Number of label check for Linked Logainm took 0.1670830249786377s
Understandability | URI regex check for Linked Logainm took 0.2441263198852539s
Understandability | Vocabs check for Linked Logainm took 0.11336779594421387s
Verifiability | Authors check for Linked Logainm took 0.1154634952545166s
Verifiability | Publishers check for Linked Logainm took 0.12273573875427246s
Performance | Throughput check for Linked Logainm took 10.703478574752808s
Amount of data | Check the number of entities for Linked Logainm took 0.00010752677917480469s
Verifiability | Contribs. check for Linked Logainm took 0.10750412940979004s
Interlinking | sameAs chians check for Linked Logainm took 0.12303805351257324s
Interlinking | skos check for Linked Logainm took 0.12298059463500977s
Interlinking | skos check for Linked Logainm took 0.1105644702911377s
Timeliness | dataset update frequency check for Linked Logainm took 0.11745095252990723s
Currency | Creation date check for Linked Logainm took 0.2332744598388672s
Currency | Modification date check for Linked Logainm took 0.21990418434143066s
Rep.Conc. | URIs length for Linked Logainm took 0.849435567855835s
Interoperability | New vocabularies check for Linked Logainm took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Linked Logainm took 0.10293745994567871s
Accuracy | Check Functional Property for Linked Logainm took 0.18419337272644043s
Accuracy | Check Inverse Functional Property for Linked Logainm took 0.17779970169067383s
Accuracy | Check Empty annotation labels for Linked Logainm took 0.5016961097717285s
Accuracy | Check White space in annotation for Linked Logainm took 0.024148225784301758s
Accuracy | Check Datatype consistency for Linked Logainm took 0.031230926513671875s
Consistency | Disjoint class check for Linked Logainm took 0.17657256126403809s
Consistency | Check Misplaced properties for Linked Logainm took 0.30980920791625977s
Consistency | Misplaced classes for Linked Logainm took 0.2512204647064209s
Consistency | Check Ontology hijacking for Linked Logainm took 1.8288404941558838s
Consistency | Check Invalid usage of undefined classes for Linked Logainm took 1.3462605476379395s
Consistency | Check Invalid usage of undefined properties for Linked Logainm took 1.5721218585968018s
Conciseness | Check Extensional conciseness for Linked Logainm took 0.03567242622375488s
Conciseness | Check Intensional conciseness for Linked Logainm took 0.1607365608215332s
Security | Sign check for Linked Logainm took 0.12547016143798828s
Availability | Check URIs Dereferenciability for Linked Logainm took 903.087488412857s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.45130133628845215s
Reputation | Calculation of the PageRank for Linked Logainm took 0.021264076232910156s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 8.416175842285156e-05s
Interoperability | Check the re-using of existing vocabs for Linked Logainm took 1.9073486328125e-06s
Believability | Calculation of trust value for Linked Logainm took 9.059906005859375e-06s
INFO | --- Analysis for linked-logainm took 959.6227948665619s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.863739013671875e-05s
Availability | VoID file availability check for Linked NUTS took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.28209686279296875s
Reputation | Calculation of the PageRank for Linked NUTS took 0.020868539810180664s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.817413330078125e-05s
Believability | Calculation of trust value for Linked NUTS took 6.198883056640625e-06s
INFO | --- Analysis for linked-nuts took 2.4857802391052246s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 5.841255187988281e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.2558884620666504s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.02088785171508789s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 3.4332275390625e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 9.298324584960938e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 2.8455772399902344s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.2896082401275635s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.25347447395324707s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.695487976074219e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 5.0067901611328125e-06s
INFO | --- Analysis for linked-open-camera took 3.842231035232544s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.364291429519653s
Availability | VoID file availability check for Linked Open Commerce took 0.000698089599609375s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.2539660930633545s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.020636796951293945s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.457069396972656e-05s
Believability | Calculation of trust value for Linked Open Commerce took 8.58306884765625e-06s
INFO | --- Analysis for linked-open-commerce took 14.901701927185059s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.2205498218536377s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.2641918659210205s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.020987987518310547s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010514259338378906s
Believability | Calculation of trust value for Linked Open Data of Ecology took 6.9141387939453125e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 3.6412153244018555s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.4345855712890625e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.23894357681274414s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020712852478027344s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 9.441375732421875e-05s
Believability | Calculation of trust value for Linked Open Numbers took 9.059906005859375e-06s
INFO | --- Analysis for linked-open-numbers took 2.6048669815063477s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 4.4345855712890625e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0007309913635253906s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.2699885368347168s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 4.100799560546875e-05s
Believability | Calculation of trust value for Linked Open Piracy took 6.198883056640625e-06s
INFO | --- Analysis for linked-open-piracy took 7.097766876220703s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 4.696846008300781e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.25680088996887207s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 3.552436828613281e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 8.58306884765625e-06s
INFO | --- Analysis for linked-open-senate took 2.826319932937622s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 2.163567066192627s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.00067138671875s
Extra | Recovery of all triples for Linked Open Vocabularies (LOV) took 49.54961609840393s
Performance | Total latancy measurement for Linked Open Vocabularies (LOV) took 1.3173174858093262s
Amount of data | Number of triples check for Linked Open Vocabularies (LOV) took 1.7073063850402832s
Interoperability | New terms check for Linked Open Vocabularies (LOV) took 2.4634294509887695s
Versatility | Languages check for Linked Open Vocabularies (LOV) took 12.46215271949768s
Interpretability | Number of blank nodes check for Linked Open Vocabularies (LOV) took 1.7419044971466064s
Interpretability | RDF structures check for Linked Open Vocabularies (LOV) took 0.38890862464904785s
Versatility | Serialization formats check for Linked Open Vocabularies (LOV) took 0.21436405181884766s
Availability | RDF dump link check for Linked Open Vocabularies (LOV) took 9.959660530090332s
License | MR license check for Linked Open Vocabularies (LOV) took 0.5991909503936768s
License | HR license check for Linked Open Vocabularies (LOV) took 43.79823136329651s
Amount of data | Number of property check for Linked Open Vocabularies (LOV) took 0.18934035301208496s
Understandability | Number of label check for Linked Open Vocabularies (LOV) took 0.7907876968383789s
Understandability | URI regex check for Linked Open Vocabularies (LOV) took 0.4150869846343994s
Understandability | Vocabs check for Linked Open Vocabularies (LOV) took 0.20796442031860352s
Verifiability | Authors check for Linked Open Vocabularies (LOV) took 0.21956825256347656s
Verifiability | Publishers check for Linked Open Vocabularies (LOV) took 0.4950394630432129s
Performance | Throughput check for Linked Open Vocabularies (LOV) took 11.687896013259888s
Amount of data | Check the number of entities for Linked Open Vocabularies (LOV) took 1.0371098518371582s
Verifiability | Contribs. check for Linked Open Vocabularies (LOV) took 0.3280456066131592s
Interlinking | sameAs chians check for Linked Open Vocabularies (LOV) took 0.22703218460083008s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.2600405216217041s
Interlinking | skos check for Linked Open Vocabularies (LOV) took 0.18931007385253906s
Timeliness | dataset update frequency check for Linked Open Vocabularies (LOV) took 0.40496087074279785s
Currency | Creation date check for Linked Open Vocabularies (LOV) took 1.2727100849151611s
Currency | Modification date check for Linked Open Vocabularies (LOV) took 0.497039794921875s
Rep.Conc. | URIs length for Linked Open Vocabularies (LOV) took 23.19737696647644s
Interoperability | New vocabularies check for Linked Open Vocabularies (LOV) took 17.19419813156128s
Consistency | Deprecated classes/propertiers check for Linked Open Vocabularies (LOV) took 0.30832767486572266s
Accuracy | Check Functional Property for Linked Open Vocabularies (LOV) took 0.19990754127502441s
Accuracy | Check Inverse Functional Property for Linked Open Vocabularies (LOV) took 0.24516797065734863s
Accuracy | Check Empty annotation labels for Linked Open Vocabularies (LOV) took 6.555256605148315s
Accuracy | Check White space in annotation for Linked Open Vocabularies (LOV) took 0.6973719596862793s
Accuracy | Check Datatype consistency for Linked Open Vocabularies (LOV) took 5.026168346405029s
Consistency | Disjoint class check for Linked Open Vocabularies (LOV) took 0.34335994720458984s
Consistency | Check Misplaced properties for Linked Open Vocabularies (LOV) took 6.705794095993042s
Consistency | Misplaced classes for Linked Open Vocabularies (LOV) took 0.23245859146118164s
Consistency | Check Ontology hijacking for Linked Open Vocabularies (LOV) took 6.532135725021362s
Consistency | Check Invalid usage of undefined classes for Linked Open Vocabularies (LOV) took 1.469843864440918s
Conciseness | Check Extensional conciseness for Linked Open Vocabularies (LOV) took 2.908529043197632s
Conciseness | Check Intensional conciseness for Linked Open Vocabularies (LOV) took 1.7295031547546387s
Security | Sign check for Linked Open Vocabularies (LOV) took 0.30263495445251465s
Availability | Check URIs Dereferenciability for Linked Open Vocabularies (LOV) took 5768.597427606583s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 1.5232832431793213s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.021841764450073242s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 6.437301635742188e-05s
Interoperability | Check the re-using of existing vocabs for Linked Open Vocabularies (LOV) took 16.53275775909424s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 8.58306884765625e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 6812.686210155487s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.506111145019531e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.25105762481689453s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.02153468132019043s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 4.2438507080078125e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 5.4836273193359375e-06s
INFO | --- Analysis for linked-periodicals took 4.460910320281982s
Availability | SPARQL endpoint availability check for Linked Index took 4.38690185546875e-05s
Availability | VoID file availability check for Linked Index took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Linked Index took 0.2586534023284912s
Reputation | Calculation of the PageRank for Linked Index took 0.02098393440246582s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.702278137207031e-05s
Believability | Calculation of trust value for Linked Index took 7.3909759521484375e-06s
INFO | --- Analysis for linked-stockindex took 2.9690003395080566s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.700807809829712s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.2662849426269531s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.021282672882080078s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 4.0531158447265625e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 7.62939453125e-06s
INFO | --- Analysis for linked-structured-product-labels took 19.696030855178833s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.9555525779724121s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0007503032684326172s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.25499391555786133s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.031906843185424805s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0015211105346679688s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 5.173683166503906e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 9.5367431640625e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 4.241800546646118s
Availability | SPARQL endpoint availability check for Linked TCGA took 21.941081762313843s
Availability | VoID file availability check for Linked TCGA took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.24931597709655762s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02115607261657715s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 9.560585021972656e-05s
Believability | Calculation of trust value for Linked TCGA took 1.2159347534179688e-05s
INFO | --- Analysis for linked-tcga took 64.49423265457153s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.09759759902954102s
Availability | VoID file availability check for Linked User Feedback took 0.0003814697265625s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.27165865898132324s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.021167278289794922s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 4.3392181396484375e-05s
Believability | Calculation of trust value for Linked User Feedback took 7.62939453125e-06s
INFO | --- Analysis for linked-user-feedback took 2.5164084434509277s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.267692565917969e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.27628636360168457s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.0210726261138916s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 9.250640869140625e-05s
Believability | Calculation of trust value for USPTO Patent data took 1.0013580322265625e-05s
INFO | --- Analysis for linked-uspto-patent-data took 53.32902526855469s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 4.172325134277344e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.25888919830322266s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.02083587646484375s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 3.266334533691406e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 1.0251998901367188e-05s
INFO | --- Analysis for linked-web-apis took 2.916067600250244s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 4.220008850097656e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.2791562080383301s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.021985292434692383s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0009922981262207031s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 4.220008850097656e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 8.821487426757812e-06s
INFO | --- Analysis for linkedarc took 2.953404188156128s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.07793140411376953s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.27138495445251465s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.021147966384887695s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 4.2438507080078125e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 8.106231689453125e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 2.8030848503112793s
Availability | SPARQL endpoint availability check for LinkedCT took 1.4499635696411133s
Availability | VoID file availability check for LinkedCT took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.27239251136779785s
Reputation | Calculation of the PageRank for LinkedCT took 0.020873546600341797s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.00010538101196289062s
Believability | Calculation of trust value for LinkedCT took 8.106231689453125e-06s
INFO | --- Analysis for linkedct took 5.202147960662842s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.13840818405151367s
Availability | VoID file availability check for LinkedGeoData took 0.0005822181701660156s
Extra | Recovery of all triples for LinkedGeoData took 7.278616189956665s
Performance | Total latancy measurement for LinkedGeoData took 0.6871130466461182s
Amount of data | Number of triples check for LinkedGeoData took 51.56532430648804s
Interoperability | New terms check for LinkedGeoData took 90.96040678024292s
Versatility | Languages check for LinkedGeoData took 181.75693893432617s
Interpretability | Number of blank nodes check for LinkedGeoData took 1.2463526725769043s
Security | Check HTTPS for LinkedGeoData took 0.3357255458831787s
Interpretability | RDF structures check for LinkedGeoData took 0.2240753173828125s
Versatility | Serialization formats check for LinkedGeoData took 0.24193334579467773s
Availability | RDF dump link check for LinkedGeoData took 0.13866519927978516s
License | MR license check for LinkedGeoData took 0.14070820808410645s
License | HR license check for LinkedGeoData took 114.4502067565918s
Amount of data | Number of property check for LinkedGeoData took 0.1360034942626953s
Understandability | Number of label check for LinkedGeoData took 0.9548921585083008s
Understandability | URI regex check for LinkedGeoData took 0.2698185443878174s
Understandability | Vocabs check for LinkedGeoData took 0.13317060470581055s
Verifiability | Authors check for LinkedGeoData took 0.15201878547668457s
Verifiability | Publishers check for LinkedGeoData took 0.13380742073059082s
Performance | Throughput check for LinkedGeoData took 10.772255420684814s
Amount of data | Check the number of entities for LinkedGeoData took 0.07954120635986328s
Verifiability | Contribs. check for LinkedGeoData took 0.13784337043762207s
Interlinking | sameAs chians check for LinkedGeoData took 0.1685199737548828s
Interlinking | skos check for LinkedGeoData took 0.13925838470458984s
Interlinking | skos check for LinkedGeoData took 0.12445449829101562s
Timeliness | dataset update frequency check for LinkedGeoData took 0.13941359519958496s
Currency | Creation date check for LinkedGeoData took 0.26334095001220703s
Currency | Modification date check for LinkedGeoData took 0.2741832733154297s
Rep.Conc. | URIs length for LinkedGeoData took 272.0622718334198s
Interoperability | New vocabularies check for LinkedGeoData took 13.07918906211853s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.14551663398742676s
Accuracy | Check Functional Property for LinkedGeoData took 0.12401032447814941s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.1326158046722412s
Accuracy | Check Empty annotation labels for LinkedGeoData took 1.96051025390625s
Accuracy | Check White space in annotation for LinkedGeoData took 0.1557002067565918s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.1466379165649414s
Consistency | Disjoint class check for LinkedGeoData took 0.13747119903564453s
Consistency | Check Misplaced properties for LinkedGeoData took 180.6791787147522s
Consistency | Misplaced classes for LinkedGeoData took 0.7512576580047607s
Consistency | Check Ontology hijacking for LinkedGeoData took 3.719545602798462s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.3629474639892578s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 182.91646456718445s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.15262079238891602s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.23423194885253906s
Security | Sign check for LinkedGeoData took 0.12546038627624512s
Availability | Check URIs Dereferenciability for LinkedGeoData took 17.626211166381836s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.9559435844421387s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.021123409271240234s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00014853477478027344s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 13.449110746383667s
Believability | Calculation of trust value for LinkedGeoData took 7.867813110351562e-06s
INFO | --- Analysis for linkedgeodata took 2200.8518171310425s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 4.315376281738281e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.24920034408569336s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.021335840225219727s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.457069396972656e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 8.344650268554688e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 5.556653022766113s
Availability | SPARQL endpoint availability check for LinkedLCCN took 1.0764870643615723s
Availability | VoID file availability check for LinkedLCCN took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.2692384719848633s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.0207061767578125s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.0001068115234375s
Believability | Calculation of trust value for LinkedLCCN took 7.62939453125e-06s
INFO | --- Analysis for linkedlccn took 21.687283992767334s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.220008850097656e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.24781179428100586s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.020766019821166992s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.62396240234375e-05s
Believability | Calculation of trust value for LinkedMarkMail took 8.344650268554688e-06s
INFO | --- Analysis for linkedmarkmail took 2.4775490760803223s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.599575996398926s
Availability | VoID file availability check for Linked Movie DataBase took 0.0007004737854003906s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.27556848526000977s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.021162986755371094s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0008456707000732422s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.0001575946807861328s
Believability | Calculation of trust value for Linked Movie DataBase took 7.152557373046875e-06s
INFO | --- Analysis for linkedmdb took 133.31988501548767s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.47335147857666016s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.2616250514984131s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.02151012420654297s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 0.00010037422180175781s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 8.106231689453125e-06s
INFO | --- Analysis for linkedspending took 4.035467147827148s
Availability | SPARQL endpoint availability check for LinkedStats took 4.1484832763671875e-05s
Availability | VoID file availability check for LinkedStats took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.2506594657897949s
Reputation | Calculation of the PageRank for LinkedStats took 0.021261930465698242s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0012023448944091797s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 5.030632019042969e-05s
Believability | Calculation of trust value for LinkedStats took 7.3909759521484375e-06s
INFO | --- Analysis for linkedstats took 3.347977638244629s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.38690185546875e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.0003097057342529297s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.24541282653808594s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.020767688751220703s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 3.361701965332031e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 1.33514404296875e-05s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 2.8914926052093506s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 4.5299530029296875e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.27486348152160645s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 3.266334533691406e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 7.867813110351562e-06s
INFO | --- Analysis for linking-open-drug-data took 2.90509033203125s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 18.681721687316895s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.00029397010803222656s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.25513410568237305s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.02083277702331543s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00012636184692382812s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 8.106231689453125e-06s
INFO | --- Analysis for linklion took 186.60660123825073s
Availability | SPARQL endpoint availability check for Lion's Den took 4.7206878662109375e-05s
Availability | VoID file availability check for Lion's Den took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.3294029235839844s
Reputation | Calculation of the PageRank for Lion's Den took 0.02109551429748535s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0008575916290283203s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 3.814697265625e-05s
Believability | Calculation of trust value for Lion's Den took 8.58306884765625e-06s
INFO | --- Analysis for lionsden took 3.1417949199676514s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 24.193822860717773s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0003871917724609375s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.23865342140197754s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.02083611488342285s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0008172988891601562s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.888938903808594e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 30.029480934143066s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 6.556510925292969e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.27611875534057617s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.02115464210510254s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 3.62396240234375e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 7.152557373046875e-06s
INFO | --- Analysis for livtdm took 2.8303990364074707s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 4.1961669921875e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.27219510078430176s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.020664691925048828s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0008633136749267578s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 3.647804260253906e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 7.152557373046875e-06s
INFO | --- Analysis for livtdm2017 took 2.8891632556915283s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.29034924507141113s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.020920515060424805s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.000812530517578125s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 3.457069396972656e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 7.867813110351562e-06s
INFO | --- Analysis for lobi took 2.9048540592193604s
Availability | SPARQL endpoint availability check for lobid-organisations took 0.860741138458252s
Availability | VoID file availability check for lobid-organisations took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.24623632431030273s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0008101463317871094s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 0.00010824203491210938s
Believability | Calculation of trust value for lobid-organisations took 7.62939453125e-06s
INFO | --- Analysis for lobid-organisations took 4.87041449546814s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.6510465145111084s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.2549593448638916s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020981788635253906s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00011277198791503906s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 7.62939453125e-06s
INFO | --- Analysis for lobid-resources took 7.05316424369812s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.3392181396484375e-05s
Availability | VoID file availability check for Linked Open Colors took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.23600006103515625s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020884037017822266s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0008552074432373047s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 8.606910705566406e-05s
Believability | Calculation of trust value for Linked Open Colors took 6.9141387939453125e-06s
INFO | --- Analysis for loc took 6.9213714599609375s
Availability | SPARQL endpoint availability check for Location Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Location Ontology took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.26863861083984375s
Reputation | Calculation of the PageRank for Location Ontology took 0.020938634872436523s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.4809112548828125e-05s
Believability | Calculation of trust value for Location Ontology took 8.344650268554688e-06s
INFO | --- Analysis for Location_Ontology took 4.676592826843262s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.744529724121094e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.38131117820739746s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020837783813476562s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0009188652038574219s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.695487976074219e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 8.106231689453125e-06s
INFO | --- Analysis for locv took 43.06251263618469s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7309486865997314s
Availability | VoID file availability check for LOD-a-lot took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.2530076503753662s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.0213625431060791s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.000843048095703125s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.6716461181640625e-05s
Believability | Calculation of trust value for LOD-a-lot took 6.9141387939453125e-06s
INFO | --- Analysis for lod-a-lot took 13.834803104400635s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.2438507080078125e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.0002884864807128906s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.2802150249481201s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 3.218650817871094e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 8.106231689453125e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 2.976491689682007s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.291534423828125e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.2992405891418457s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 3.218650817871094e-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.974170684814453s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 8.273124694824219e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.24292945861816406s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.02208566665649414s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0009975433349609375s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 0.00010848045349121094s
Believability | Calculation of trust value for LOD2 Project Wiki took 7.867813110351562e-06s
INFO | --- Analysis for lod2-project-wiki took 3.5054168701171875s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.833805561065674s
Availability | VoID file availability check for LODAC BDLS took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.25731348991394043s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.510185241699219e-05s
Believability | Calculation of trust value for LODAC BDLS took 8.821487426757812e-06s
INFO | --- Analysis for lodac-bdls took 13.886933088302612s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.363059997558594e-05s
Availability | VoID file availability check for LODRussia Math took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.26409220695495605s
Reputation | Calculation of the PageRank for LODRussia Math took 0.021153688430786133s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 3.504753112792969e-05s
Believability | Calculation of trust value for LODRussia Math took 1.2159347534179688e-05s
INFO | --- Analysis for lodrussia-math took 2.9392638206481934s
Availability | SPARQL endpoint availability check for LODRussia Nano took 5.507469177246094e-05s
Availability | VoID file availability check for LODRussia Nano took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.2577090263366699s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.021207571029663086s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 3.552436828613281e-05s
Believability | Calculation of trust value for LODRussia Nano took 7.867813110351562e-06s
INFO | --- Analysis for lodrussia-nano took 2.909968137741089s
Availability | SPARQL endpoint availability check for LODStats took 4.315376281738281e-05s
Availability | VoID file availability check for LODStats took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for LODStats took 0.256467342376709s
Reputation | Calculation of the PageRank for LODStats took 0.0210573673248291s
Interlinking | Calculation of Degree of Connection for LODStats took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LODStats took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for LODStats took 3.457069396972656e-05s
Believability | Calculation of trust value for LODStats took 8.344650268554688e-06s
INFO | --- Analysis for lodstats took 2.9131767749786377s
Availability | SPARQL endpoint availability check for LODUM took 4.1484832763671875e-05s
Availability | VoID file availability check for LODUM took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for LODUM took 0.2673783302307129s
Reputation | Calculation of the PageRank for LODUM took 0.02093029022216797s
Interlinking | Calculation of Degree of Connection for LODUM took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LODUM took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for LODUM took 3.266334533691406e-05s
Believability | Calculation of trust value for LODUM took 8.344650268554688e-06s
INFO | --- Analysis for lodum took 2.9171037673950195s
Availability | SPARQL endpoint availability check for lofd took 0.1277320384979248s
Availability | VoID file availability check for lofd took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for lofd took 0.2542088031768799s
Reputation | Calculation of the PageRank for lofd took 0.0213320255279541s
Interlinking | Calculation of Degree of Connection for lofd took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for lofd took 3.504753112792969e-05s
Believability | Calculation of trust value for lofd took 7.152557373046875e-06s
INFO | --- Analysis for lofd took 2.5010826587677s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 271.3378953933716s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0011026859283447266s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.31621670722961426s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.021047115325927734s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.793571472167969e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 6.198883056640625e-06s
INFO | --- Analysis for loius took 585.3594009876251s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.410743713378906e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.712214469909668s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.0212252140045166s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 3.3855438232421875e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 8.821487426757812e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 3.898437261581421s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.6906719207763672s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.2815062999725342s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.020852327346801758s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0008075237274169922s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.650520324707031e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 6.198883056640625e-06s
INFO | --- Analysis for london-gazette took 4.464678764343262s
Availability | SPARQL endpoint availability check for Weather Stations took 6.747245788574219e-05s
Availability | VoID file availability check for Weather Stations took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.2685821056365967s
Reputation | Calculation of the PageRank for Weather Stations took 0.021060705184936523s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.535385131835938e-05s
Believability | Calculation of trust value for Weather Stations took 1.239776611328125e-05s
INFO | --- Analysis for los_metar took 14.121524572372437s
Availability | SPARQL endpoint availability check for Lotico took 0.8857448101043701s
Availability | VoID file availability check for Lotico took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for Lotico took 0.25351786613464355s
Reputation | Calculation of the PageRank for Lotico took 0.020698070526123047s
Interlinking | Calculation of Degree of Connection for Lotico took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Lotico took 9.274482727050781e-05s
Believability | Calculation of trust value for Lotico took 8.58306884765625e-06s
INFO | --- Analysis for lotico took 6.705856084823608s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.2841629981994629s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0005967617034912109s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 1.0769004821777344s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 0.8812246322631836s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.19983983039855957s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.622152328491211s
Versatility | Languages check for Lower Layer Super Output Areas took 0.381406307220459s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 30.182422161102295s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.11426806449890137s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.1412661075592041s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.14365696907043457s
Availability | RDF dump link check for Lower Layer Super Output Areas took 51.23230743408203s
License | MR license check for Lower Layer Super Output Areas took 0.1530594825744629s
License | HR license check for Lower Layer Super Output Areas took 30.220839500427246s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.14766955375671387s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.12892699241638184s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.2697865962982178s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.5961201190948486s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.13399696350097656s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.14660954475402832s
Performance | Throughput check for Lower Layer Super Output Areas took 11.527738809585571s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 5.173683166503906e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.1399085521697998s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.20397114753723145s
Interlinking | skos check for Lower Layer Super Output Areas took 0.14011120796203613s
Interlinking | skos check for Lower Layer Super Output Areas took 0.1552436351776123s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.214247465133667s
Currency | Creation date check for Lower Layer Super Output Areas took 0.5569489002227783s
Currency | Modification date check for Lower Layer Super Output Areas took 0.21355342864990234s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 2.892371892929077s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.1874384880065918s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.13592123985290527s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.22454142570495605s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.15896224975585938s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 1.4226140975952148s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 1.668771505355835s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.915201187133789s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.00020313262939453125s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.45162296295166016s
Security | Sign check for Lower Layer Super Output Areas took 0.1604626178741455s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.7542109489440918s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.02077031135559082s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 5.936622619628906e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 4.0531158447265625e-06s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 8.344650268554688e-06s
INFO | --- Analysis for lower-layer-super-output-areas took 274.98531675338745s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.628342866897583s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0002932548522949219s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 119.2715756893158s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9829421043395996s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 29.986660718917847s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.797060251235962s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.1421639919281s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.5094919204711914s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4993886947631836s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.587927341461182s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.250622034072876s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.4488048553466797s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.16286063194275s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21358561515808105s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.741917371749878s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5688695907592773s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2590198516845703s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.37970972061157227s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5960092544555664s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.574303388595581s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.081031799316406e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.25093984603881836s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.23595070838928223s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3808481693267822s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4098947048187256s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.101851224899292s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.182213544845581s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4648299217224121s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 171.53712368011475s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20190095901489258s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.23429012298583984s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.23716115951538086s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 42.65098214149475s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6650731563568115s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6338820457458496s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3383219242095947s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 86.89864587783813s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.580896615982056s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 36.962385177612305s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.4863722324371338s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 87.30839586257935s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.746100425720215s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6815185546875s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3723335266113281s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.353883743286133s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.0526759624481201s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.020997285842895508s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.220008850097656e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.58306884765625e-06s
INFO | --- Analysis for LPIS_(Poland) took 2429.4916501045227s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.208251953125s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0006735324859619141s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 124.70815706253052s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.9612722396850586s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.86020016670227s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 14.358570098876953s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.23710465431213s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.110769271850586s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21681809425354004s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 10.036602020263672s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.24268269538879395s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19760394096374512s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.2182083129883s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20023107528686523s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.937898874282837s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.7267749309539795s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.38048648834228516s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19785070419311523s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.23413443565368652s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.402713537216187s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.891654968261719e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21182608604431152s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21254491806030273s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4268918037414551s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.41885995864868164s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.820775747299194s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.4556155204772949s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21408724784851074s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 154.60796546936035s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19349145889282227s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3051309585571289s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3288240432739258s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 42.259408950805664s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.670130491256714s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.6614654064178467s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.17824435234069824s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 86.59576964378357s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.372806787490845s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 36.281553983688354s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.4702279567718506s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 87.61685705184937s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.8595340251922607s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5428204536437988s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.7252902984619141s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 13.488055944442749s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.581242322921753s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.021521568298339844s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.106231689453125e-06s
INFO | --- Analysis for LPIS_Czech_Republic took 2383.828679084778s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 6.341934204101562e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.29132986068725586s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.02131175994873047s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.528594970703125e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 8.58306884765625e-06s
INFO | --- Analysis for lremap-auth took 4.802791118621826s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.8160552978515625e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.24015307426452637s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.021363258361816406s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.8623809814453125e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 9.298324584960938e-06s
INFO | --- Analysis for lremap-conf took 3.068693161010742s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.982948303222656e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.2624015808105469s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.021367549896240234s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.6716461181640625e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 8.344650268554688e-06s
INFO | --- Analysis for lremap-ri took 2.5903890132904053s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.601478576660156e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.24127960205078125s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.020769834518432617s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.5762786865234375e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 8.58306884765625e-06s
INFO | --- Analysis for lremap-sub took 2.656630754470825s
Availability | SPARQL endpoint availability check for LSQ took 4.458427429199219e-05s
Availability | VoID file availability check for LSQ took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for LSQ took 0.23968839645385742s
Reputation | Calculation of the PageRank for LSQ took 0.020925283432006836s
Interlinking | Calculation of Degree of Connection for LSQ took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.4809112548828125e-05s
Believability | Calculation of trust value for LSQ took 1.3589859008789062e-05s
INFO | --- Analysis for lsq took 3.488046884536743s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.6780686378479004s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0007684230804443359s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.2505786418914795s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.021420001983642578s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 4.4345855712890625e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 8.821487426757812e-06s
INFO | --- Analysis for LucaniPharsalia took 4.151793956756592s
Availability | SPARQL endpoint availability check for Linked rules took 4.506111145019531e-05s
Availability | VoID file availability check for Linked rules took 0.000362396240234375s
Completeness | Calculation of interlinking completeness for Linked rules took 0.24290227890014648s
Reputation | Calculation of the PageRank for Linked rules took 0.022185087203979492s
Interlinking | Calculation of Degree of Connection for Linked rules took 3.4809112548828125e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0009715557098388672s
Interlinking | Calculation of Clustering coefficient for Linked rules took 4.3392181396484375e-05s
Believability | Calculation of trust value for Linked rules took 8.821487426757812e-06s
INFO | --- Analysis for Luminaires_senlis took 2.3573391437530518s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.458427429199219e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.0003070831298828125s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.2572662830352783s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.021433115005493164s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 3.719329833984375e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 8.106231689453125e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 2.921560764312744s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.17890238761902s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0007426738739013672s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.2800145149230957s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020871639251708984s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 3.24249267578125e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 8.344650268554688e-06s
INFO | --- Analysis for makg took 63.50583291053772s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.38690185546875e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.25795722007751465s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.02102947235107422s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0010929107666015625s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 4.553794860839844e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 7.62939453125e-06s
INFO | --- Analysis for manchester-university-reading-lists took 3.7510759830474854s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.363059997558594e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.000362396240234375s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.26347923278808594s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.021399497985839844s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 4.0531158447265625e-05s
Believability | Calculation of trust value for engineering equipment ontology took 6.67572021484375e-06s
INFO | --- Analysis for manish took 2.38515043258667s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 4.3392181396484375e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.2858774662017822s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.02092123031616211s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 3.4332275390625e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 7.62939453125e-06s
INFO | --- Analysis for mapa-referencia-bogota took 2.9365148544311523s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 7.224082946777344e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.2666442394256592s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 3.075599670410156e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 8.106231689453125e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 2.8866569995880127s
Availability | SPARQL endpoint availability check for MARC Codes List took 8.153915405273438e-05s
Availability | VoID file availability check for MARC Codes List took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.26987791061401367s
Reputation | Calculation of the PageRank for MARC Codes List took 0.021197080612182617s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.0001304149627685547s
Believability | Calculation of trust value for MARC Codes List took 8.58306884765625e-06s
INFO | --- Analysis for marc-codes took 13.408302545547485s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.458427429199219e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.00041985511779785156s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.26935863494873047s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.220008850097656e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 6.67572021484375e-06s
INFO | --- Analysis for masc took 5.869476079940796s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 5.221366882324219e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.26863741874694824s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.020741939544677734s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 4.1961669921875e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 7.152557373046875e-06s
INFO | --- Analysis for masc-bn-nif took 2.4600071907043457s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.083233118057251s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.2644083499908447s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.020864248275756836s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 4.00543212890625e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 6.198883056640625e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 3.5658047199249268s
Availability | SPARQL endpoint availability check for medline took 4.267692565917969e-05s
Availability | VoID file availability check for medline took 0.0004162788391113281s
Completeness | Calculation of interlinking completeness for medline took 0.26538586616516113s
Reputation | Calculation of the PageRank for medline took 0.021297693252563477s
Interlinking | Calculation of Degree of Connection for medline took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for medline took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for medline took 4.482269287109375e-05s
Believability | Calculation of trust value for medline took 6.198883056640625e-06s
INFO | --- Analysis for medline took 6.9962241649627686s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.4085886478424072s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0007951259613037109s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.29052186012268066s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 7.700920104980469e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 8.344650268554688e-06s
INFO | --- Analysis for meducator took 10.35175347328186s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 4.2438507080078125e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.24830389022827148s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.020919322967529297s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 3.2901763916015625e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 8.344650268554688e-06s
INFO | --- Analysis for mesh-finnish took 2.8748667240142822s
Availability | SPARQL endpoint availability check for MeSH headings took 4.57763671875e-05s
Availability | VoID file availability check for MeSH headings took 0.0003254413604736328s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.25232768058776855s
Reputation | Calculation of the PageRank for MeSH headings took 0.022552490234375s
Interlinking | Calculation of Degree of Connection for MeSH headings took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 3.409385681152344e-05s
Believability | Calculation of trust value for MeSH headings took 9.059906005859375e-06s
INFO | --- Analysis for mesh_headings took 2.860243797302246s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 4.220008850097656e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.2615194320678711s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.021044254302978516s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 3.337860107421875e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 7.62939453125e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.855548620223999s
Availability | SPARQL endpoint availability check for MeSH pairs took 4.3392181396484375e-05s
Availability | VoID file availability check for MeSH pairs took 0.0003409385681152344s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.24640774726867676s
Reputation | Calculation of the PageRank for MeSH pairs took 0.02043008804321289s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 3.4332275390625e-05s
Believability | Calculation of trust value for MeSH pairs took 7.62939453125e-06s
INFO | --- Analysis for mesh_pairs took 2.854912519454956s
Availability | SPARQL endpoint availability check for MeSH titles took 4.267692565917969e-05s
Availability | VoID file availability check for MeSH titles took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.2658810615539551s
Reputation | Calculation of the PageRank for MeSH titles took 0.021337509155273438s
Interlinking | Calculation of Degree of Connection for MeSH titles took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MeSH titles took 0.0008141994476318359s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 3.314018249511719e-05s
Believability | Calculation of trust value for MeSH titles took 7.62939453125e-06s
INFO | --- Analysis for mesh_titles took 2.880068302154541s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 4.410743713378906e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.2733330726623535s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.021926164627075195s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0011057853698730469s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 4.0531158447265625e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 8.106231689453125e-06s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.9413723945617676s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 4.458427429199219e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.29487013816833496s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.023335695266723633s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.000820159912109375s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 3.695487976074219e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 7.3909759521484375e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 3.032136917114258s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.38690185546875e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.26854491233825684s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.0206143856048584s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.677078247070312e-05s
Believability | Calculation of trust value for MetaShare metadata model took 7.62939453125e-06s
INFO | --- Analysis for metashare took 2.4780054092407227s
Availability | SPARQL endpoint availability check for MExiCo took 4.3392181396484375e-05s
Availability | VoID file availability check for MExiCo took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for MExiCo took 0.28115081787109375s
Reputation | Calculation of the PageRank for MExiCo took 0.02068305015563965s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for MExiCo took 5.221366882324219e-05s
Believability | Calculation of trust value for MExiCo took 7.867813110351562e-06s
INFO | --- Analysis for mexico took 22.521408319473267s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.0060784816741943s
Availability | VoID file availability check for Coronavirus dataset took 0.00026988983154296875s
Extra | Recovery of all triples for Coronavirus dataset took 5.911452293395996s
Performance | Total latancy measurement for Coronavirus dataset took 2.460907459259033s
Amount of data | Number of triples check for Coronavirus dataset took 1.1602482795715332s
Interoperability | New terms check for Coronavirus dataset took 2.6129908561706543s
Versatility | Languages check for Coronavirus dataset took 60.481627225875854s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.8349111080169678s
Interpretability | RDF structures check for Coronavirus dataset took 0.586782693862915s
Versatility | Serialization formats check for Coronavirus dataset took 0.5327610969543457s
Availability | RDF dump link check for Coronavirus dataset took 0.49765563011169434s
License | MR license check for Coronavirus dataset took 0.5445001125335693s
License | HR license check for Coronavirus dataset took 42.44704627990723s
Amount of data | Number of property check for Coronavirus dataset took 0.527472972869873s
Understandability | Number of label check for Coronavirus dataset took 1.6646766662597656s
Understandability | URI regex check for Coronavirus dataset took 1.0248165130615234s
Understandability | Vocabs check for Coronavirus dataset took 0.51131272315979s
Verifiability | Authors check for Coronavirus dataset took 0.6022365093231201s
Verifiability | Publishers check for Coronavirus dataset took 0.5067288875579834s
Performance | Throughput check for Coronavirus dataset took 14.785200595855713s
Amount of data | Check the number of entities for Coronavirus dataset took 7.462501525878906e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.5032694339752197s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5134496688842773s
Interlinking | skos check for Coronavirus dataset took 0.5343635082244873s
Interlinking | skos check for Coronavirus dataset took 0.5030293464660645s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.5089066028594971s
Currency | Creation date check for Coronavirus dataset took 1.0133390426635742s
Currency | Modification date check for Coronavirus dataset took 1.0117888450622559s
Rep.Conc. | URIs length for Coronavirus dataset took 8.617563486099243s
Interoperability | New vocabularies check for Coronavirus dataset took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.501032829284668s
Accuracy | Check Functional Property for Coronavirus dataset took 0.7743415832519531s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.5549654960632324s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.202766180038452s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.02208232879638672s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.029479503631591797s
Consistency | Disjoint class check for Coronavirus dataset took 1.126718282699585s
Consistency | Check Misplaced properties for Coronavirus dataset took 7.531343698501587s
Consistency | Misplaced classes for Coronavirus dataset took 0.6037650108337402s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.4256832599639893s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.3511550426483154s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.7209312915802s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.034628868103027344s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.4966592788696289s
Security | Sign check for Coronavirus dataset took 0.527930498123169s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 2976.9590413570404s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 1.6358411312103271s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021355628967285156s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 8.797645568847656e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Coronavirus dataset took 7.152557373046875e-06s
INFO | --- Analysis for micro-coronavirus took 3217.594126701355s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 5.0067901611328125e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007131099700927734s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.26651811599731445s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.02025890350341797s
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.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0001087188720703125s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 8.106231689453125e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 7.202718734741211s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 7.05718994140625e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.26485419273376465s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020776748657226562s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00011372566223144531s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 8.344650268554688e-06s
INFO | --- Analysis for mismuseos-gnoss took 6.0958850383758545s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.12310671806335449s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.2566516399383545s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.021231651306152344s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 5.316734313964844e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 8.58306884765625e-06s
INFO | --- Analysis for mlsa took 2.9518380165100098s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 4.410743713378906e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.2835195064544678s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.021019458770751953s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.2901763916015625e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 6.67572021484375e-06s
INFO | --- Analysis for model took 35.35864233970642s
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.0007565021514892578s
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.2745237350463867s
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.020902156829833984s
Interlinking | Calculation of Degree of Connection for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007214546203613281s
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.3855438232421875e-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 6.4373016357421875e-06s
INFO | --- Analysis for model1 took 17.534725666046143s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 4.124641418457031e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.27500128746032715s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 3.4809112548828125e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 1.239776611328125e-05s
INFO | --- Analysis for mond took 2.979931592941284s
Availability | SPARQL endpoint availability check for MONDIS took 4.291534423828125e-05s
Availability | VoID file availability check for MONDIS took 0.00038552284240722656s
Completeness | Calculation of interlinking completeness for MONDIS took 0.2571444511413574s
Reputation | Calculation of the PageRank for MONDIS took 0.02199578285217285s
Interlinking | Calculation of Degree of Connection for MONDIS took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for MONDIS took 0.0008723735809326172s
Interlinking | Calculation of Clustering coefficient for MONDIS took 4.267692565917969e-05s
Believability | Calculation of trust value for MONDIS took 9.775161743164062e-06s
INFO | --- Analysis for mondis took 2.8327929973602295s
Availability | SPARQL endpoint availability check for Monumentos took 4.363059997558594e-05s
Availability | VoID file availability check for Monumentos took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Monumentos took 0.26555919647216797s
Reputation | Calculation of the PageRank for Monumentos took 0.0208590030670166s
Interlinking | Calculation of Degree of Connection for Monumentos took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Monumentos took 3.4332275390625e-05s
Believability | Calculation of trust value for Monumentos took 7.3909759521484375e-06s
INFO | --- Analysis for monumentos-zaragoza took 2.930443525314331s
Availability | SPARQL endpoint availability check for MORElab took 31.66544771194458s
Availability | VoID file availability check for MORElab took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for MORElab took 0.25846123695373535s
Reputation | Calculation of the PageRank for MORElab took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for MORElab took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0008137226104736328s
Interlinking | Calculation of Clustering coefficient for MORElab took 9.703636169433594e-05s
Believability | Calculation of trust value for MORElab took 7.867813110351562e-06s
INFO | --- Analysis for morelab took 84.48250079154968s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 1.7692787647247314s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0003612041473388672s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.26831698417663574s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.02080845832824707s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 9.655952453613281e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 8.821487426757812e-06s
INFO | --- Analysis for msc took 5.958847284317017s
Availability | SPARQL endpoint availability check for Multext-East took 4.482269287109375e-05s
Availability | VoID file availability check for Multext-East took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Multext-East took 0.2554283142089844s
Reputation | Calculation of the PageRank for Multext-East took 0.020690441131591797s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for Multext-East took 4.100799560546875e-05s
Believability | Calculation of trust value for Multext-East took 8.344650268554688e-06s
INFO | --- Analysis for multext-east took 2.3291943073272705s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.291534423828125e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.00029850006103515625s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.2640714645385742s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.021170377731323242s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 3.266334533691406e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 8.344650268554688e-06s
INFO | --- Analysis for multilingualeulaw took 2.8600382804870605s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.6253204345703125e-05s
Availability | VoID file availability check for Multimedia Lab took 0.00029397010803222656s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.25696468353271484s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0008187294006347656s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 4.076957702636719e-05s
Believability | Calculation of trust value for Multimedia Lab took 8.106231689453125e-06s
INFO | --- Analysis for multimedia-lab took 2.287834644317627s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.982948303222656e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.0003082752227783203s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.2660670280456543s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.020955562591552734s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 4.100799560546875e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 8.821487426757812e-06s
INFO | --- Analysis for munich-offener-haushalt took 2.8894805908203125s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.5678634643554688s
Availability | VoID file availability check for Muninn World War I took 0.0007767677307128906s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.25841212272644043s
Reputation | Calculation of the PageRank for Muninn World War I took 0.020763635635375977s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.58306884765625e-05s
Believability | Calculation of trust value for Muninn World War I took 7.867813110351562e-06s
INFO | --- Analysis for muninn-world-war-i took 10.597583532333374s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.124641418457031e-05s
Availability | VoID file availability check for Musei Italiani took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.2577061653137207s
Reputation | Calculation of the PageRank for Musei Italiani took 0.021030902862548828s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 3.600120544433594e-05s
Believability | Calculation of trust value for Musei Italiani took 7.867813110351562e-06s
INFO | --- Analysis for musei-italiani took 2.8762919902801514s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 4.5299530029296875e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.2744467258453369s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.021292924880981445s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00011515617370605469s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for museosespania-gnoss took 40.371745347976685s
Availability | SPARQL endpoint availability check for Italian Museums took 1.6732921600341797s
Availability | VoID file availability check for Italian Museums took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.29344654083251953s
Reputation | Calculation of the PageRank for Italian Museums took 0.02091693878173828s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.749961853027344e-05s
Believability | Calculation of trust value for Italian Museums took 7.3909759521484375e-06s
INFO | --- Analysis for museums-in-italy took 4.208741664886475s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.172325134277344e-05s
Availability | VoID file availability check for MusicBrainz took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.27198004722595215s
Reputation | Calculation of the PageRank for MusicBrainz took 0.020932435989379883s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 3.0517578125e-05s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0008392333984375s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 3.743171691894531e-05s
Believability | Calculation of trust value for MusicBrainz took 8.58306884765625e-06s
INFO | --- Analysis for musicbrainz_ took 2.9531939029693604s
Availability | SPARQL endpoint availability check for MusicNet Codex took 6.747245788574219e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0003311634063720703s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.24167752265930176s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.020600080490112305s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 3.170967102050781e-05s
Believability | Calculation of trust value for MusicNet Codex took 7.62939453125e-06s
INFO | --- Analysis for musicnet_codex took 2.9020113945007324s
Availability | SPARQL endpoint availability check for Muziekweb took 0.798863410949707s
Availability | VoID file availability check for Muziekweb took 0.0005185604095458984s
Extra | Recovery of all triples for Muziekweb took 0.9350271224975586s
Performance | Total latancy measurement for Muziekweb took 1.565122365951538s
Amount of data | Number of triples check for Muziekweb took 0.2928006649017334s
Interoperability | New terms check for Muziekweb took 1.7339622974395752s
Versatility | Languages check for Muziekweb took 0.3240938186645508s
Interpretability | Number of blank nodes check for Muziekweb took 0.31078028678894043s
Interpretability | RDF structures check for Muziekweb took 0.332653284072876s
Versatility | Serialization formats check for Muziekweb took 0.29979944229125977s
Availability | RDF dump link check for Muziekweb took 0.28745317459106445s
License | MR license check for Muziekweb took 0.30521631240844727s
License | HR license check for Muziekweb took 0.3168153762817383s
Amount of data | Number of property check for Muziekweb took 0.2877318859100342s
Understandability | Number of label check for Muziekweb took 0.3047301769256592s
Understandability | URI regex check for Muziekweb took 0.594038724899292s
Understandability | Vocabs check for Muziekweb took 0.2744719982147217s
Verifiability | Authors check for Muziekweb took 0.27703094482421875s
Verifiability | Publishers check for Muziekweb took 0.29450368881225586s
Performance | Throughput check for Muziekweb took 12.068869352340698s
Amount of data | Check the number of entities for Muziekweb took 7.43865966796875e-05s
Verifiability | Contribs. check for Muziekweb took 0.3010826110839844s
Interlinking | sameAs chians check for Muziekweb took 0.3120543956756592s
Interlinking | skos check for Muziekweb took 0.3084084987640381s
Interlinking | skos check for Muziekweb took 0.30405592918395996s
Timeliness | dataset update frequency check for Muziekweb took 0.2987234592437744s
Currency | Creation date check for Muziekweb took 0.5860841274261475s
Currency | Modification date check for Muziekweb took 0.6294002532958984s
Rep.Conc. | URIs length for Muziekweb took 0.9572262763977051s
Interoperability | New vocabularies check for Muziekweb took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.29213953018188477s
Accuracy | Check Functional Property for Muziekweb took 0.3213462829589844s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.2874934673309326s
Accuracy | Check Empty annotation labels for Muziekweb took 0.601510763168335s
Accuracy | Check White space in annotation for Muziekweb took 0.03380227088928223s
Accuracy | Check Datatype consistency for Muziekweb took 0.030190229415893555s
Consistency | Disjoint class check for Muziekweb took 0.30426526069641113s
Consistency | Check Misplaced properties for Muziekweb took 0.5975279808044434s
Consistency | Check Ontology hijacking for Muziekweb took 1.9401626586914062s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.3783104419708252s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.6911187171936035s
Conciseness | Check Extensional conciseness for Muziekweb took 0.0367894172668457s
Conciseness | Check Intensional conciseness for Muziekweb took 0.2854304313659668s
Security | Sign check for Muziekweb took 0.2826712131500244s
Availability | Check URIs Dereferenciability for Muziekweb took 1875.8159425258636s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.977813720703125s
Reputation | Calculation of the PageRank for Muziekweb took 0.020895957946777344s
Interlinking | Calculation of Degree of Connection for Muziekweb took 2.7418136596679688e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 6.389617919921875e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.6689300537109375e-06s
Believability | Calculation of trust value for Muziekweb took 9.059906005859375e-06s
INFO | --- Analysis for muziekweb took 1935.1510879993439s
Availability | SPARQL endpoint availability check for myExperiment took 0.45545315742492676s
Availability | VoID file availability check for myExperiment took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for myExperiment took 0.27335500717163086s
Reputation | Calculation of the PageRank for myExperiment took 0.021000146865844727s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00010204315185546875s
Believability | Calculation of trust value for myExperiment took 6.9141387939453125e-06s
INFO | --- Analysis for my-experiment took 4.729267835617065s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.06699609756469727s
Availability | VoID file availability check for My Family Lineage took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.2772634029388428s
Reputation | Calculation of the PageRank for My Family Lineage took 0.022960901260375977s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0010912418365478516s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 0.00011444091796875s
Believability | Calculation of trust value for My Family Lineage took 7.867813110351562e-06s
INFO | --- Analysis for my-family-lineage took 14.506325244903564s
Availability | SPARQL endpoint availability check for My ontology test took 0.47297048568725586s
Availability | VoID file availability check for My ontology test took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for My ontology test took 0.2514975070953369s
Reputation | Calculation of the PageRank for My ontology test took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.147125244140625e-05s
Believability | Calculation of trust value for My ontology test took 9.775161743164062e-06s
INFO | --- Analysis for myontologytest took 3.814026117324829s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 4.315376281738281e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0007617473602294922s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.2659444808959961s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.02089691162109375s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.00011610984802246094s
Believability | Calculation of trust value for myopenlink dataspaces took 8.58306884765625e-06s
INFO | --- Analysis for myopenlink-dataspaces took 3.6404595375061035s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 7.106317758560181s
Availability | VoID file availability check for N-Lex as Linked Data took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.2633838653564453s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.020509004592895508s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 7.271766662597656e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for n-lex-as-linked-data took 16.9451162815094s
Availability | SPARQL endpoint availability check for NAICS 2007 took 26.086926221847534s
Availability | VoID file availability check for NAICS 2007 took 0.0009191036224365234s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.26644158363342285s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.021757125854492188s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.6253204345703125e-05s
Believability | Calculation of trust value for NAICS 2007 took 6.198883056640625e-06s
INFO | --- Analysis for naics-2007 took 124.78589820861816s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.8373441696167s
Availability | VoID file availability check for NAICS 2012 took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.28034496307373047s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.021436214447021484s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 6.008148193359375e-05s
Believability | Calculation of trust value for NAICS 2012 took 5.0067901611328125e-06s
INFO | --- Analysis for naics-2012 took 123.715012550354s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.28426694869995117s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.02076101303100586s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0008447170257568359s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 5.650520324707031e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for nalt took 3.1317458152770996s
Availability | SPARQL endpoint availability check for Usernames  took 4.553794860839844e-05s
Availability | VoID file availability check for Usernames  took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Usernames  took 0.2672133445739746s
Reputation | Calculation of the PageRank for Usernames  took 0.020806074142456055s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0008358955383300781s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.600120544433594e-05s
Believability | Calculation of trust value for Usernames  took 1.1444091796875e-05s
INFO | --- Analysis for Names took 2.742661714553833s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.2621769905090332s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0006451606750488281s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 0.9990522861480713s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 1.9784603118896484s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.154243230819702s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 15.045663118362427s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.80592942237854s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.474101543426514s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.38068199157714844s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.859471321105957s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.414351224899292s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.40070271492004395s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.3670053482055664s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.81278538703918s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.8892593383789062s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 6.244246006011963s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 1.2481577396392822s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.4077475070953369s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.3605968952178955s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.4084789752960205s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.908601760864258s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 0.00011992454528808594s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.4145228862762451s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.4749183654785156s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.508070707321167s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.096787929534912s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.4146432876586914s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.1454484462738037s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.7243835926055908s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.0131869316101074s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.372589111328125s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3486173152923584s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.39589738845825195s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.4070546627044678s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007669925689697266s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0010280609130859375s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.35575389862060547s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.698277473449707s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.40413665771484375s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.7838261127471924s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.3642148971557617s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.7524216175079346s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0006914138793945312s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.41187453269958496s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 4.012487173080444s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.26907944679260254s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.413459777832031e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 2.1457672119140625e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 5.245208740234375e-06s
INFO | --- Analysis for national-diet-library-authorities took 231.4023141860962s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.38716864585876465s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0006530284881591797s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 0.9545261859893799s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 1.9343364238739014s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.692553520202637s
Interoperability | New terms check for National Diet Library of Japan subject headings took 15.876447439193726s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.7745394706726074s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.620450496673584s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.3767726421356201s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.8473391532897949s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.40744829177856445s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.3913416862487793s
License | MR license check for National Diet Library of Japan subject headings took 0.33373165130615234s
License | HR license check for National Diet Library of Japan subject headings took 91.7610604763031s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8487968444824219s
Understandability | Number of label check for National Diet Library of Japan subject headings took 4.897839307785034s
Understandability | URI regex check for National Diet Library of Japan subject headings took 1.2711617946624756s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.36326003074645996s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.3665163516998291s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.3347294330596924s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.703627347946167s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.58306884765625e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.37914204597473145s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.47948217391967773s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.3837506771087646s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.3044757843017578s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.8546087741851807s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.0995101928710938s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.7639012336730957s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.987060546875s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.336104154586792s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.37189769744873047s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.38622593879699707s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.3581247329711914s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0005369186401367188s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0007395744323730469s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.37067222595214844s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.7816030979156494s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.3588254451751709s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.7420876026153564s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.3460183143615723s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.7602496147155762s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0007684230804443359s
Security | Sign check for National Diet Library of Japan subject headings took 0.34276866912841797s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 3.934574604034424s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.36475086212158203s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02176380157470703s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 6.341934204101562e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.9073486328125e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 7.867813110351562e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 227.37732362747192s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.132551670074463s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.24466943740844727s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.863739013671875e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 7.3909759521484375e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 6.250529766082764s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.839897155761719e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2572441101074219s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.104873657226562e-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 3.3670434951782227s
Availability | SPARQL endpoint availability check for Naturopathy took 4.100799560546875e-05s
Availability | VoID file availability check for Naturopathy took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.25211572647094727s
Reputation | Calculation of the PageRank for Naturopathy took 0.020929813385009766s
Interlinking | Calculation of Degree of Connection for Naturopathy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 3.3855438232421875e-05s
Believability | Calculation of trust value for Naturopathy took 1.0013580322265625e-05s
INFO | --- Analysis for naturopathy2 took 3.4001827239990234s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 5.602836608886719e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.26764678955078125s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02088642120361328s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.504753112792969e-05s
Believability | Calculation of trust value for NCI Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for nci-thesaurus took 2.931478977203369s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.3659567832946777s
Availability | VoID file availability check for COVID-19 Data took 0.0003905296325683594s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.269428014755249s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.021876811981201172s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0010445117950439453s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 4.8160552978515625e-05s
Believability | Calculation of trust value for COVID-19 Data took 7.62939453125e-06s
INFO | --- Analysis for NCMI-COVID-19 took 7.16079306602478s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.406212091445923s
Availability | VoID file availability check for NCMI-COVID-19 took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.24741339683532715s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.021164894104003906s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.3828277587890625e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 8.344650268554688e-06s
INFO | --- Analysis for NCMICOVID-19 took 6.205773115158081s
Availability | SPARQL endpoint availability check for NDF-RT took 7.390975952148438e-05s
Availability | VoID file availability check for NDF-RT took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.24937915802001953s
Reputation | Calculation of the PageRank for NDF-RT took 0.0206911563873291s
Interlinking | Calculation of Degree of Connection for NDF-RT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 3.457069396972656e-05s
Believability | Calculation of trust value for NDF-RT took 9.5367431640625e-06s
INFO | --- Analysis for ndf-rt took 2.8644700050354004s
Availability | SPARQL endpoint availability check for Near took 4.38690185546875e-05s
Availability | VoID file availability check for Near took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Near took 0.2797379493713379s
Reputation | Calculation of the PageRank for Near took 0.02072930335998535s
Interlinking | Calculation of Degree of Connection for Near took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Near took 0.0008130073547363281s
Interlinking | Calculation of Clustering coefficient for Near took 0.00010418891906738281s
Believability | Calculation of trust value for Near took 6.9141387939453125e-06s
INFO | --- Analysis for near took 8.995090246200562s
Availability | SPARQL endpoint availability check for Neel took 5.650520324707031e-05s
Availability | VoID file availability check for Neel took 0.00030732154846191406s
Completeness | Calculation of interlinking completeness for Neel took 0.2577705383300781s
Reputation | Calculation of the PageRank for Neel took 0.021088838577270508s
Interlinking | Calculation of Degree of Connection for Neel took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Neel took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Neel took 3.504753112792969e-05s
Believability | Calculation of trust value for Neel took 8.106231689453125e-06s
INFO | --- Analysis for neel took 2.884129285812378s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 4.1961669921875e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.26479601860046387s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 3.647804260253906e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 7.3909759521484375e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.858809232711792s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.363059997558594e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.2511405944824219s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020775318145751953s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.457069396972656e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 7.3909759521484375e-06s
INFO | --- Analysis for neurolex-wiki took 2.3001880645751953s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 8.535385131835938e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.2844383716583252s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.020867586135864258s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 5.14984130859375e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 7.3909759521484375e-06s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 3.5485079288482666s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 9.107589721679688e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.25156712532043457s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020868301391601562s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 7.414817810058594e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 7.867813110351562e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 3.9345703125s
Availability | SPARQL endpoint availability check for Newsweek took 4.1961669921875e-05s
Availability | VoID file availability check for Newsweek took 0.0003292560577392578s
Completeness | Calculation of interlinking completeness for Newsweek took 0.26847004890441895s
Reputation | Calculation of the PageRank for Newsweek took 0.021614551544189453s
Interlinking | Calculation of Degree of Connection for Newsweek took 2.574920654296875e-05s
Interlinking | Calculation of Centrality for Newsweek took 0.0010428428649902344s
Interlinking | Calculation of Clustering coefficient for Newsweek took 4.124641418457031e-05s
Believability | Calculation of trust value for Newsweek took 7.867813110351562e-06s
INFO | --- Analysis for newsweek took 2.923245429992676s
Availability | SPARQL endpoint availability check for neXtProt took 1.5431723594665527s
Availability | VoID file availability check for neXtProt took 0.0003337860107421875s
Completeness | Calculation of interlinking completeness for neXtProt took 0.2681593894958496s
Reputation | Calculation of the PageRank for neXtProt took 0.021534442901611328s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for neXtProt took 4.4345855712890625e-05s
Believability | Calculation of trust value for neXtProt took 8.58306884765625e-06s
INFO | --- Analysis for nextprot took 4.551618576049805s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.3392181396484375e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.2677178382873535s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.020999670028686523s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0001327991485595703s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for nextweb-gnoss took 10.400121927261353s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.410743713378906e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.24190521240234375s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.606910705566406e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 6.4373016357421875e-06s
INFO | --- Analysis for nhs-jargon took 2.9515221118927s
Availability | SPARQL endpoint availability check for NIT Patna took 4.410743713378906e-05s
Availability | VoID file availability check for NIT Patna took 0.0007841587066650391s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.2768263816833496s
Reputation | Calculation of the PageRank for NIT Patna took 0.020956754684448242s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 7.915496826171875e-05s
Believability | Calculation of trust value for NIT Patna took 9.059906005859375e-06s
INFO | --- Analysis for NITP took 3.193385601043701s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 4.410743713378906e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.26536989212036133s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.02095770835876465s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.814697265625e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 8.106231689453125e-06s
INFO | --- Analysis for nlm_2007_mesh took 2.892505407333374s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 5.8650970458984375e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.26666736602783203s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.02108168601989746s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.457069396972656e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 7.867813110351562e-06s
INFO | --- Analysis for nlr-dataset-mod took 3.9516241550445557s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.6327376365661621s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0006425380706787109s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.2596273422241211s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.021297216415405273s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0008804798126220703s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 4.5299530029296875e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 1.2874603271484375e-05s
INFO | --- Analysis for NLW took 4.230659008026123s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.103806257247925s
Availability | VoID file availability check for Nobel Prizes took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.2376546859741211s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02151775360107422s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0009338855743408203s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 0.00011730194091796875s
Believability | Calculation of trust value for Nobel Prizes took 9.059906005859375e-06s
INFO | --- Analysis for nobelprizes took 8.549947738647461s
Availability | SPARQL endpoint availability check for NoiPA took 0.47635769844055176s
Availability | VoID file availability check for NoiPA took 0.0002949237823486328s
Extra | Recovery of all triples for NoiPA took 1.7497260570526123s
Performance | Total latancy measurement for NoiPA took 1.3190176486968994s
Amount of data | Number of triples check for NoiPA took 1.6031954288482666s
Interoperability | New terms check for NoiPA took 3.1867682933807373s
Versatility | Languages check for NoiPA took 60.22661566734314s
Interpretability | Number of blank nodes check for NoiPA took 0.3871619701385498s
Interpretability | RDF structures check for NoiPA took 0.2896873950958252s
Versatility | Serialization formats check for NoiPA took 0.24623799324035645s
Availability | RDF dump link check for NoiPA took 0.3053104877471924s
License | MR license check for NoiPA took 0.46050143241882324s
License | HR license check for NoiPA took 60.39809608459473s
Amount of data | Number of property check for NoiPA took 0.39487481117248535s
Understandability | Number of label check for NoiPA took 0.5962398052215576s
Understandability | URI regex check for NoiPA took 0.5287046432495117s
Understandability | Vocabs check for NoiPA took 0.27324676513671875s
Verifiability | Authors check for NoiPA took 0.18969440460205078s
Verifiability | Publishers check for NoiPA took 0.19713926315307617s
Performance | Throughput check for NoiPA took 10.689234018325806s
Amount of data | Check the number of entities for NoiPA took 0.00011110305786132812s
Verifiability | Contribs. check for NoiPA took 0.2542259693145752s
Interlinking | sameAs chians check for NoiPA took 0.18373489379882812s
Interlinking | skos check for NoiPA took 0.3968031406402588s
Interlinking | skos check for NoiPA took 0.1977853775024414s
Timeliness | dataset update frequency check for NoiPA took 0.20307660102844238s
Currency | Creation date check for NoiPA took 0.36336588859558105s
Currency | Modification date check for NoiPA took 0.20577502250671387s
Rep.Conc. | URIs length for NoiPA took 20.458949327468872s
Interoperability | New vocabularies check for NoiPA took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.2700462341308594s
Accuracy | Check Functional Property for NoiPA took 0.18979573249816895s
Accuracy | Check Inverse Functional Property for NoiPA took 0.25614261627197266s
Accuracy | Check Empty annotation labels for NoiPA took 0.674762487411499s
Accuracy | Check White space in annotation for NoiPA took 0.029913663864135742s
Accuracy | Check Datatype consistency for NoiPA took 0.02920222282409668s
Consistency | Disjoint class check for NoiPA took 0.1977529525756836s
Consistency | Check Misplaced properties for NoiPA took 18.37886905670166s
Consistency | Misplaced classes for NoiPA took 0.438671350479126s
Consistency | Check Ontology hijacking for NoiPA took 2.046323776245117s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.3482742309570312s
Consistency | Check Invalid usage of undefined properties for NoiPA took 19.54517412185669s
Conciseness | Check Extensional conciseness for NoiPA took 0.03791308403015137s
Conciseness | Check Intensional conciseness for NoiPA took 0.37127065658569336s
Security | Sign check for NoiPA took 0.23395705223083496s
Availability | Check URIs Dereferenciability for NoiPA took 15.47135853767395s
Completeness | Calculation of interlinking completeness for NoiPA took 0.3327193260192871s
Reputation | Calculation of the PageRank for NoiPA took 0.020864009857177734s
Interlinking | Calculation of Degree of Connection for NoiPA took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for NoiPA took 3.719329833984375e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.9073486328125e-06s
Believability | Calculation of trust value for NoiPA took 7.3909759521484375e-06s
INFO | --- Analysis for NoiPA took 418.197954416275s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 5.551563262939453s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.27364277839660645s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.020809412002563477s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.512901306152344e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.3589859008789062e-05s
INFO | --- Analysis for nom took 19.42970299720764s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 25.727863550186157s
Availability | VoID file availability check for Nomenclator Asturias took 0.0009553432464599609s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.8392062187194824s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.020955324172973633s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.606910705566406e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 5.7220458984375e-06s
INFO | --- Analysis for nomenclator-asturias took 138.17404985427856s
Availability | SPARQL endpoint availability check for nomisma took 4.3392181396484375e-05s
Availability | VoID file availability check for nomisma took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for nomisma took 0.2504241466522217s
Reputation | Calculation of the PageRank for nomisma took 0.021936893463134766s
Interlinking | Calculation of Degree of Connection for nomisma took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for nomisma took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for nomisma took 3.409385681152344e-05s
Believability | Calculation of trust value for nomisma took 7.152557373046875e-06s
INFO | --- Analysis for nomisma took 3.257222890853882s
Availability | SPARQL endpoint availability check for Nomisma.org  took 1.3527107238769531s
Availability | VoID file availability check for Nomisma.org  took 0.0006201267242431641s
Extra | Recovery of all triples for Nomisma.org  took 300.00595116615295s
Performance | Total latancy measurement for Nomisma.org  took 1.999314785003662s
Amount of data | Number of triples check for Nomisma.org  took 35.2278037071228s
Interoperability | New terms check for Nomisma.org  took 9.374436140060425s
Versatility | Languages check for Nomisma.org  took 92.33290147781372s
Interpretability | Number of blank nodes check for Nomisma.org  took 31.525891065597534s
Security | Check HTTPS for Nomisma.org  took 1.061779260635376s
Interpretability | RDF structures check for Nomisma.org  took 0.40987586975097656s
Versatility | Serialization formats check for Nomisma.org  took 0.4235720634460449s
Availability | RDF dump link check for Nomisma.org  took 929.9178023338318s
License | MR license check for Nomisma.org  took 0.4218573570251465s
License | HR license check for Nomisma.org  took 57.29674744606018s
Amount of data | Number of property check for Nomisma.org  took 0.5089800357818604s
Understandability | Number of label check for Nomisma.org  took 6.826342821121216s
Understandability | URI regex check for Nomisma.org  took 1.143667221069336s
Understandability | Vocabs check for Nomisma.org  took 0.6262218952178955s
Verifiability | Authors check for Nomisma.org  took 0.42552638053894043s
Verifiability | Publishers check for Nomisma.org  took 0.42642974853515625s
Performance | Throughput check for Nomisma.org  took 12.460901021957397s
Amount of data | Check the number of entities for Nomisma.org  took 0.0004649162292480469s
Verifiability | Contribs. check for Nomisma.org  took 0.4094204902648926s
Interlinking | sameAs chians check for Nomisma.org  took 0.4078676700592041s
Interlinking | skos check for Nomisma.org  took 1.1234381198883057s
Interlinking | skos check for Nomisma.org  took 0.5683913230895996s
Timeliness | dataset update frequency check for Nomisma.org  took 0.3932979106903076s
Currency | Creation date check for Nomisma.org  took 0.8761165142059326s
Currency | Modification date check for Nomisma.org  took 0.7904491424560547s
Rep.Conc. | URIs length for Nomisma.org  took 326.6821630001068s
Interoperability | New vocabularies check for Nomisma.org  took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.5890884399414062s
Accuracy | Check Functional Property for Nomisma.org  took 0.4981091022491455s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.4480288028717041s
Accuracy | Check Empty annotation labels for Nomisma.org  took 544.747635602951s
Accuracy | Check White space in annotation for Nomisma.org  took 2.7252449989318848s
Consistency | Disjoint class check for Nomisma.org  took 0.4355185031890869s
Consistency | Check Misplaced properties for Nomisma.org  took 25.818827390670776s
Consistency | Check Ontology hijacking for Nomisma.org  took 538.2587389945984s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 27.062784433364868s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.00018143653869628906s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.45000743865966797s
Security | Sign check for Nomisma.org  took 0.4763374328613281s
Availability | Check URIs Dereferenciability for Nomisma.org  took 2072.353710412979s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 1.5952069759368896s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.0214385986328125s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 3.528594970703125e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 5.173683166503906e-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 7.62939453125e-06s
INFO | --- Analysis for nomisma_org took 8421.562410831451s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 4.601478576660156e-05s
Availability | VoID file availability check for Curriculum Vitae took 0.0003399848937988281s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.7304325103759766s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 3.170967102050781e-05s
Believability | Calculation of trust value for Curriculum Vitae took 7.62939453125e-06s
INFO | --- Analysis for Nordine_Bittich took 4.602015733718872s
Availability | SPARQL endpoint availability check for NorPark took 4.267692565917969e-05s
Availability | VoID file availability check for NorPark took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for NorPark took 0.26509642601013184s
Reputation | Calculation of the PageRank for NorPark took 0.021170377731323242s
Interlinking | Calculation of Degree of Connection for NorPark took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.9114227294921875e-05s
Believability | Calculation of trust value for NorPark took 8.106231689453125e-06s
INFO | --- Analysis for norpark took 3.336784601211548s
Availability | SPARQL endpoint availability check for Parking Dataset took 7.271766662597656e-05s
Availability | VoID file availability check for Parking Dataset took 0.000293731689453125s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.2517867088317871s
Reputation | Calculation of the PageRank for Parking Dataset took 0.021011829376220703s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.7206878662109375e-05s
Believability | Calculation of trust value for Parking Dataset took 8.344650268554688e-06s
INFO | --- Analysis for norpark2 took 2.858647108078003s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 4.172325134277344e-05s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0003714561462402344s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.23959946632385254s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.021347522735595703s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 3.4809112548828125e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset took 8.821487426757812e-06s
INFO | --- Analysis for Norway_Fishery_ took 2.8637752532958984s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 4.3392181396484375e-05s
Availability | VoID file availability check for Norwegian geo-divisions took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.26087284088134766s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.021034955978393555s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 5.1975250244140625e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 7.62939453125e-06s
INFO | --- Analysis for norwegian-geo-divisions took 2.8573570251464844s
Availability | SPARQL endpoint availability check for NorwegianSoE took 4.4345855712890625e-05s
Availability | VoID file availability check for NorwegianSoE took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.250795841217041s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.02087259292602539s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 3.361701965332031e-05s
Believability | Calculation of trust value for NorwegianSoE took 8.344650268554688e-06s
INFO | --- Analysis for norwegiansoe took 2.8297438621520996s
Availability | SPARQL endpoint availability check for NITP took 4.267692565917969e-05s
Availability | VoID file availability check for NITP took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for NITP took 0.2520430088043213s
Reputation | Calculation of the PageRank for NITP took 0.0212554931640625s
Interlinking | Calculation of Degree of Connection for NITP took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for NITP took 7.486343383789062e-05s
Believability | Calculation of trust value for NITP took 1.049041748046875e-05s
INFO | --- Analysis for notIdentifier took 2.9002716541290283s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.3392181396484375e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.2836575508117676s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02095794677734375s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 4.029273986816406e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 9.059906005859375e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.915600061416626s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 4.291534423828125e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.00031495094299316406s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.2467207908630371s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 3.2901763916015625e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 7.867813110351562e-06s
INFO | --- Analysis for npg took 2.8298192024230957s
Availability | SPARQL endpoint availability check for NPM took 4.2438507080078125e-05s
Availability | VoID file availability check for NPM took 0.00035643577575683594s
Completeness | Calculation of interlinking completeness for NPM took 0.2823941707611084s
Reputation | Calculation of the PageRank for NPM took 0.0209500789642334s
Interlinking | Calculation of Degree of Connection for NPM took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for NPM took 4.458427429199219e-05s
Believability | Calculation of trust value for NPM took 9.059906005859375e-06s
INFO | --- Analysis for npm took 2.952113151550293s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.044158935546875s
Availability | VoID file availability check for NTNU special collections took 0.0003223419189453125s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.26080942153930664s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020937681198120117s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 6.079673767089844e-05s
Believability | Calculation of trust value for NTNU special collections took 1.239776611328125e-05s
INFO | --- Analysis for ntnusc took 2.9065542221069336s
Availability | SPARQL endpoint availability check for links took 4.172325134277344e-05s
Availability | VoID file availability check for links took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for links took 0.277911901473999s
Reputation | Calculation of the PageRank for links took 0.021134138107299805s
Interlinking | Calculation of Degree of Connection for links took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for links took 0.0009813308715820312s
Interlinking | Calculation of Clustering coefficient for links took 1.621246337890625e-05s
Believability | Calculation of trust value for links took 8.344650268554688e-06s
INFO | --- Analysis for nugmyanmar took 2.923595905303955s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.267692565917969e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.25447678565979004s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.020794391632080078s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 0.00010323524475097656s
Believability | Calculation of trust value for NUTS (GeoVocab) took 8.106231689453125e-06s
INFO | --- Analysis for nuts-geovocab took 2.8620917797088623s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 4.2438507080078125e-05s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.26194262504577637s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.021303892135620117s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 7.295608520507812e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 1.430511474609375e-05s
INFO | --- Analysis for nvd took 3.0021533966064453s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 4.291534423828125e-05s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.2636411190032959s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.02219533920288086s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 9.274482727050781e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.2159347534179688e-05s
INFO | --- Analysis for nvs took 2.863415002822876s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.291534423828125e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0003266334533691406s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.26349377632141113s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.020832061767578125s
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.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00019502639770507812s
Believability | Calculation of trust value for New York Times - Linked Open Data took 8.58306884765625e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.8799571990966797s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 5.507469177246094e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.00029397010803222656s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.2490847110748291s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.02136397361755371s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0009737014770507812s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 5.173683166503906e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 8.821487426757812e-06s
INFO | --- Analysis for o-anc took 2.800708055496216s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.410743713378906e-05s
Availability | VoID file availability check for OANetzwerk took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.2431631088256836s
Reputation | Calculation of the PageRank for OANetzwerk took 0.02102065086364746s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 3.361701965332031e-05s
Believability | Calculation of trust value for OANetzwerk took 9.059906005859375e-06s
INFO | --- Analysis for oanetzwerk took 2.8153765201568604s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 4.363059997558594e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.2881157398223877s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.02197408676147461s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0010662078857421875s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 4.00543212890625e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 8.821487426757812e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.899890899658203s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 4.935264587402344e-05s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0003077983856201172s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.23960590362548828s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.021350383758544922s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00010180473327636719s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 8.58306884765625e-06s
INFO | --- Analysis for ocd took 2.782081365585327s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 4.3392181396484375e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.26126790046691895s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.02100229263305664s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 4.291534423828125e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 8.821487426757812e-06s
INFO | --- Analysis for oceandrilling-borehole took 2.849623203277588s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 4.2438507080078125e-05s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.25528478622436523s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020979642868041992s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 0.00010013580322265625s
Believability | Calculation of trust value for Ocean Drilling - Codices took 9.5367431640625e-06s
INFO | --- Analysis for oceandrilling-codices took 2.914682149887085s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 4.124641418457031e-05s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.2766554355621338s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.02089405059814453s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.552436828613281e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.4781951904296875e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 2.9070522785186768s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 4.267692565917969e-05s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.27080392837524414s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.02099466323852539s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.790855407714844e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 9.298324584960938e-06s
INFO | --- Analysis for oceandrilling-forams took 2.888824701309204s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 4.100799560546875e-05s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.24717068672180176s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.0208590030670166s
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.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.647804260253906e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.239776611328125e-05s
INFO | --- Analysis for oceandrilling-janus took 2.8838300704956055s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 4.2438507080078125e-05s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.26094770431518555s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.62396240234375e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 8.344650268554688e-06s
INFO | --- Analysis for oceandrilling-janusamp took 2.8373866081237793s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 4.172325134277344e-05s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.2652878761291504s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.02082538604736328s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.24249267578125e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 8.344650268554688e-06s
INFO | --- Analysis for oceandrilling-ldeo took 2.862672805786133s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 5.0067901611328125e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.2554941177368164s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.02077174186706543s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 6.031990051269531e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 7.867813110351562e-06s
INFO | --- Analysis for oclc-fast took 2.870460033416748s
Availability | SPARQL endpoint availability check for Open Data Communities took 4.506111145019531e-05s
Availability | VoID file availability check for Open Data Communities took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.2580451965332031s
Reputation | Calculation of the PageRank for Open Data Communities took 0.020879745483398438s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 3.266334533691406e-05s
Believability | Calculation of trust value for Open Data Communities took 8.106231689453125e-06s
INFO | --- Analysis for odc took 2.8188533782958984s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.291534423828125e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.24585247039794922s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.021266460418701172s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 5.53131103515625e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 7.62939453125e-06s
INFO | --- Analysis for odc-imd-environment-score took 2.7298340797424316s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 5.269050598144531e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.2568390369415283s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.020911693572998047s
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.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 3.266334533691406e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 8.106231689453125e-06s
INFO | --- Analysis for odc-imd-rank-2007 took 2.890820026397705s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 8.416175842285156e-05s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.2717866897583008s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.02097606658935547s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 4.220008850097656e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 7.152557373046875e-06s
INFO | --- Analysis for odc-lsoa took 2.826155424118042s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 4.1961669921875e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.2541041374206543s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.020676374435424805s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 3.266334533691406e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 8.106231689453125e-06s
INFO | --- Analysis for odc-population-2005 took 2.812469005584717s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.57763671875e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.26125240325927734s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.0209197998046875s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 9.059906005859375e-06s
INFO | --- Analysis for ods took 2.840768575668335s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 4.315376281738281e-05s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.2658350467681885s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.02123856544494629s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.00012373924255371094s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.1444091796875e-05s
INFO | --- Analysis for oecd-linked-data took 2.899369478225708s
Availability | SPARQL endpoint availability check for Offener Haushalt took 5.078315734863281e-05s
Availability | VoID file availability check for Offener Haushalt took 0.0004012584686279297s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.25900721549987793s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.021506786346435547s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0008394718170166016s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 3.790855407714844e-05s
Believability | Calculation of trust value for Offener Haushalt took 8.106231689453125e-06s
INFO | --- Analysis for offener-haushalt took 2.8775432109832764s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 4.291534423828125e-05s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0003345012664794922s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.2554287910461426s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.021517276763916016s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.7206878662109375e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 8.821487426757812e-06s
INFO | --- Analysis for ogolod took 2.959453582763672s
Availability | SPARQL endpoint availability check for OLAC Metadata took 4.4345855712890625e-05s
Availability | VoID file availability check for OLAC Metadata took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.27079248428344727s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.02133655548095703s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 4.744529724121094e-05s
Believability | Calculation of trust value for OLAC Metadata took 7.62939453125e-06s
INFO | --- Analysis for olac took 2.8084216117858887s
Availability | SPARQL endpoint availability check for OLiA took 4.863739013671875e-05s
Availability | VoID file availability check for OLiA took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for OLiA took 0.2648026943206787s
Reputation | Calculation of the PageRank for OLiA took 0.020646333694458008s
Interlinking | Calculation of Degree of Connection for OLiA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.0001289844512939453s
Believability | Calculation of trust value for OLiA took 7.867813110351562e-06s
INFO | --- Analysis for olia took 2.7976572513580322s
Availability | SPARQL endpoint availability check for OLiA Discourse took 7.486343383789062e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.24945783615112305s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020955324172973633s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.38690185546875e-05s
Believability | Calculation of trust value for OLiA Discourse took 8.821487426757812e-06s
INFO | --- Analysis for olia-discourse took 2.891976833343506s
Availability | SPARQL endpoint availability check for Open Land Use took 4.172325134277344e-05s
Availability | VoID file availability check for Open Land Use took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.2783956527709961s
Reputation | Calculation of the PageRank for Open Land Use took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 3.314018249511719e-05s
Believability | Calculation of trust value for Open Land Use took 1.1920928955078125e-05s
INFO | --- Analysis for OLU took 2.890413761138916s
Availability | SPARQL endpoint availability check for OmegaWiki took 6.0558319091796875e-05s
Availability | VoID file availability check for OmegaWiki took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.28250718116760254s
Reputation | Calculation of the PageRank for OmegaWiki took 0.020981788635253906s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 3.266334533691406e-05s
Believability | Calculation of trust value for OmegaWiki took 7.867813110351562e-06s
INFO | --- Analysis for omegawiki took 2.8703906536102295s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.26047825813293457s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.02087879180908203s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 4.124641418457031e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-als took 2.863262414932251s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 4.267692565917969e-05s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.48714637756347656s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.021068572998046875s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0008146762847900391s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 4.506111145019531e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-arb took 4.3093345165252686s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 8.869171142578125e-05s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.43656468391418457s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.02133965492248535s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0008823871612548828s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 4.649162292480469e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-bul took 4.357275724411011s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 4.3392181396484375e-05s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.24145817756652832s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.02079939842224121s
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.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 5.125999450683594e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-cow took 2.8901917934417725s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 4.267692565917969e-05s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.25156664848327637s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020885467529296875s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0008141994476318359s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 4.38690185546875e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-cwn took 3.1281604766845703s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 8.749961853027344e-05s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.2708241939544678s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.021251201629638672s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 1.9073486328125e-05s
INFO | --- Analysis for omwn-dan took 3.1257073879241943s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 4.4345855712890625e-05s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.2912564277648926s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0008442401885986328s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 4.744529724121094e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-ell took 3.0449109077453613s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 4.1961669921875e-05s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2491471767425537s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.02091693878173828s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 4.124641418457031e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
INFO | --- Analysis for omwn-eng took 2.923557996749878s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 8.058547973632812e-05s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.24958300590515137s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.020837783813476562s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 4.220008850097656e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-fas took 2.8257930278778076s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.291534423828125e-05s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2461073398590088s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.02087092399597168s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.3392181396484375e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
INFO | --- Analysis for omwn-fin took 2.8816540241241455s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 4.220008850097656e-05s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0003330707550048828s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.26467442512512207s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.021018505096435547s
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.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 4.410743713378906e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-06s
INFO | --- Analysis for omwn-fra took 2.8626668453216553s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 4.3392181396484375e-05s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.24013185501098633s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.02085256576538086s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-heb took 2.84745192527771s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 4.1484832763671875e-05s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.27433133125305176s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.020926713943481445s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 4.124641418457031e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-hrv took 2.8394317626953125s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 4.291534423828125e-05s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.24498701095581055s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.02077317237854004s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-isl took 2.7460432052612305s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 4.1484832763671875e-05s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.25679755210876465s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.021623611450195312s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 4.6253204345703125e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-ita took 2.8411178588867188s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 4.267692565917969e-05s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.2662220001220703s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.02121734619140625s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 4.458427429199219e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-iwn took 2.8908982276916504s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 5.1021575927734375e-05s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.27005982398986816s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.021204233169555664s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0010571479797363281s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 5.5789947509765625e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-jpn took 2.837768316268921s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 4.506111145019531e-05s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.27554917335510254s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.021078824996948242s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 4.649162292480469e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
INFO | --- Analysis for omwn-mcr took 2.9532864093780518s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 4.363059997558594e-05s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2509644031524658s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.02112126350402832s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 4.315376281738281e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-06s
INFO | --- Analysis for omwn-msa took 2.8547089099884033s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 4.291534423828125e-05s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.23787665367126465s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.022883892059326172s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 4.863739013671875e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-nld took 2.830047607421875s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.2615041732788086s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.02124476432800293s
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.0009305477142333984s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 4.649162292480469e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-nor took 2.846853017807007s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 4.267692565917969e-05s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.25198912620544434s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 4.0531158447265625e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
INFO | --- Analysis for omwn-pol took 2.898491859436035s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 4.291534423828125e-05s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2671854496002197s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.02100992202758789s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 4.4345855712890625e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-por took 2.830167055130005s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2906489372253418s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.02067279815673828s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 4.3392181396484375e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
INFO | --- Analysis for omwn-ron took 2.8767507076263428s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 6.794929504394531e-05s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.26486802101135254s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.021085023880004883s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 4.1484832763671875e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-slk took 2.8382480144500732s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 5.698204040527344e-05s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.25766587257385254s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020774126052856445s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 4.220008850097656e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-slv took 2.930309772491455s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 4.220008850097656e-05s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2477266788482666s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.021126747131347656s
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.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
INFO | --- Analysis for omwn-swe took 2.813856840133667s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 4.3392181396484375e-05s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2843332290649414s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.0208284854888916s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-tha took 2.928040027618408s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 7.152557373046875e-05s
Availability | VoID file availability check for OntoBeef Domain took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.25886058807373047s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020993709564208984s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.744529724121094e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.3589859008789062e-05s
INFO | --- Analysis for ontobeef-domain took 2.838608503341675s
Availability | SPARQL endpoint availability check for Ontos News Portal took 7.796287536621094e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0003147125244140625s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.2563920021057129s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.021235227584838867s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 0.0001087188720703125s
Believability | Calculation of trust value for Ontos News Portal took 9.059906005859375e-06s
INFO | --- Analysis for ontos-news-portal took 2.860417366027832s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 4.2438507080078125e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.00038886070251464844s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.2665133476257324s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.075599670410156e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 7.3909759521484375e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.8330440521240234s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 7.295608520507812e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.23647284507751465s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.020963430404663086s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0009725093841552734s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 4.38690185546875e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 7.867813110351562e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 2.7955405712127686s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.2796943187713623s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.02141261100769043s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 4.291534423828125e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 8.58306884765625e-06s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 2.8763492107391357s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.291534423828125e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.2725410461425781s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.021109580993652344s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 5.2928924560546875e-05s
Believability | Calculation of trust value for Open Data Euskadi took 7.62939453125e-06s
INFO | --- Analysis for open-data-euskadi took 2.8556289672851562s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 4.673004150390625e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.2584352493286133s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.021096467971801758s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010967254638671875s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 8.821487426757812e-06s
INFO | --- Analysis for open-data-risp took 2.875195026397705s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for Open Data Thesaurus took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.26927971839904785s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.02103447914123535s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.058547973632812e-05s
Believability | Calculation of trust value for Open Data Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for open-data-thesaurus took 2.872443199157715s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.291534423828125e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.2535574436187744s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.021185636520385742s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 3.3855438232421875e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 7.152557373046875e-06s
INFO | --- Analysis for open-data-tor-vergata took 2.86545729637146s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.8160552978515625e-05s
Availability | VoID file availability check for Open Election Data Project took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.28754115104675293s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.723403930664062e-05s
Believability | Calculation of trust value for Open Election Data Project took 7.867813110351562e-06s
INFO | --- Analysis for open-election-data-project took 2.8428549766540527s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 4.220008850097656e-05s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.00031113624572753906s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.26291561126708984s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02151656150817871s
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.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 9.72747802734375e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 7.62939453125e-06s
INFO | --- Analysis for open-energy-info-wiki took 2.8774383068084717s
Availability | SPARQL endpoint availability check for Open Library took 4.410743713378906e-05s
Availability | VoID file availability check for Open Library took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for Open Library took 0.24772238731384277s
Reputation | Calculation of the PageRank for Open Library took 0.020928621292114258s
Interlinking | Calculation of Degree of Connection for Open Library took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Open Library took 7.033348083496094e-05s
Believability | Calculation of trust value for Open Library took 8.106231689453125e-06s
INFO | --- Analysis for open-library took 2.894137144088745s
Availability | SPARQL endpoint availability check for Open Directory took 4.220008850097656e-05s
Availability | VoID file availability check for Open Directory took 0.0003287792205810547s
Completeness | Calculation of interlinking completeness for Open Directory took 0.24445796012878418s
Reputation | Calculation of the PageRank for Open Directory took 0.020954608917236328s
Interlinking | Calculation of Degree of Connection for Open Directory took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Directory took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Open Directory took 3.1948089599609375e-05s
Believability | Calculation of trust value for Open Directory took 8.821487426757812e-06s
INFO | --- Analysis for open_directory took 2.840538263320923s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 4.220008850097656e-05s
Availability | VoID file availability check for Open Land Use @PSNC took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.2341318130493164s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.02122330665588379s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 3.457069396972656e-05s
Believability | Calculation of trust value for Open Land Use @PSNC took 8.344650268554688e-06s
INFO | --- Analysis for Open_Land_Use took 2.8574883937835693s
Availability | SPARQL endpoint availability check for flyatlas took 4.124641418457031e-05s
Availability | VoID file availability check for flyatlas took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for flyatlas took 0.24240636825561523s
Reputation | Calculation of the PageRank for flyatlas took 0.021012306213378906s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.218650817871094e-05s
Believability | Calculation of trust value for flyatlas took 7.3909759521484375e-06s
INFO | --- Analysis for openbiomed-flyatlas took 2.798034191131592s
Availability | SPARQL endpoint availability check for OpenCalais took 4.1961669921875e-05s
Availability | VoID file availability check for OpenCalais took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.2543916702270508s
Reputation | Calculation of the PageRank for OpenCalais took 0.02100682258605957s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00011014938354492188s
Believability | Calculation of trust value for OpenCalais took 6.67572021484375e-06s
INFO | --- Analysis for opencalais took 2.8896515369415283s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 4.291534423828125e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.2516322135925293s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.02117300033569336s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.915496826171875e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 7.867813110351562e-06s
INFO | --- Analysis for opencorporates took 2.858020782470703s
Availability | SPARQL endpoint availability check for OpenCyc took 4.267692565917969e-05s
Availability | VoID file availability check for OpenCyc took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.26206374168395996s
Reputation | Calculation of the PageRank for OpenCyc took 0.021169185638427734s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00011038780212402344s
Believability | Calculation of trust value for OpenCyc took 6.67572021484375e-06s
INFO | --- Analysis for opencyc took 2.9191818237304688s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.266765832901001s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.0209500789642334s
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.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 2.8353781700134277s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 6.008148193359375e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.2778480052947998s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.020862817764282227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 3.051835536956787s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.26120758056640625s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.02084946632385254s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 2.860862970352173s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.2568957805633545s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.021536588668823242s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.8681719303131104s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.255157470703125s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020945072174072266s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 2.8567631244659424s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 8.606910705566406e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.2665834426879883s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020953655242919922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.842484712600708s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.2504875659942627s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.02100539207458496s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 2.8440072536468506s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.26326513290405273s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020868539810180664s
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.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.409385681152344e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.809584379196167s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.2563657760620117s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.02083277702331543s
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.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.267692565917969e-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.8282015323638916s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.029273986816406e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0003077983856201172s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.2483057975769043s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.02103281021118164s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 9.298324584960938e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 2.8366174697875977s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.2778174877166748s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.02071833610534668s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 2.8556764125823975s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 5.698204040527344e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.28145790100097656s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.02083134651184082s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0008330345153808594s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.887580871582031e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 2.8237571716308594s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 7.534027099609375e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.00033664703369140625s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.2716505527496338s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.02076864242553711s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0008046627044677734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 5.054473876953125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 2.885784387588501s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.25509190559387207s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.021190166473388672s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.649162292480469e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.8225674629211426s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.839897155761719e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.25597047805786133s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.02092123031616211s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.76837158203125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.80501651763916s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.000244140625s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.23896527290344238s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020895957946777344s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.8275461196899414s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.00035834312438964844s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.2545652389526367s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.02090311050415039s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 2.787687063217163s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.25329136848449707s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 2.914445638656616s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 5.888938903808594e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0003101825714111328s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.2776186466217041s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.02089715003967285s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 7.891654968261719e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.873161792755127s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.24793505668640137s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 2.8067166805267334s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.25722241401672363s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 4.744529724121094e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 2.870468854904175s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.00030040740966796875s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.26188015937805176s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020928621292114258s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-service-expenditure took 2.8592207431793213s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.00032711029052734375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.2621598243713379s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0008714199066162109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 5.245208740234375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.3828277587890625e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.7824180126190186s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 7.915496826171875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.23750686645507812s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 2.7604572772979736s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.2667527198791504s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.021081209182739258s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.649162292480469e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 2.809939384460449s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.27963924407958984s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.020678043365478516s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.673004150390625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 2.7833914756774902s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.887580871582031e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.27277302742004395s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.57763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 2.820450782775879s
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.00026917457580566406s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.2680799961090088s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 2.894697904586792s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.25031590461730957s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0207369327545166s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 5.030632019042969e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 2.8335702419281006s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.25235986709594727s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.021166324615478516s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 2.806722640991211s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2900674343109131s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020728349685668945s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 2.8735837936401367s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2575044631958008s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020728349685668945s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 2.815626859664917s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.2743039131164551s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.02088165283203125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 5.0067901611328125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 9.5367431640625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 2.821836233139038s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.2935910224914551s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.021300077438354492s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.53131103515625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 9.059906005859375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.902008295059204s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 6.008148193359375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.27154040336608887s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.57763671875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.827317953109741s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.2666778564453125s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.02076435089111328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0008077621459960938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 5.3882598876953125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 2.8943943977355957s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 5.435943603515625e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.24709820747375488s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.02072310447692871s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.57763671875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 2.890878677368164s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 6.651878356933594e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.2623004913330078s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 2.8388373851776123s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.2805135250091553s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.020614147186279297s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 9.298324584960938e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.779203176498413s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.2562596797943115s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020752906799316406s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.792213439941406e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 2.7643046379089355s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.2626321315765381s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020739078521728516s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007157325744628906s
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 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 2.838078022003174s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.7206878662109375e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.2684004306793213s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 2.865004062652588s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.00030112266540527344s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.24440383911132812s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.021120309829711914s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0008552074432373047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 4.673004150390625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 9.298324584960938e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 2.7628579139709473s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 5.698204040527344e-05s
Availability | VoID file availability check for Open Data of Ecuador took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.27776098251342773s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.511543273925781e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 8.106231689453125e-06s
INFO | --- Analysis for opendataec took 2.895448684692383s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 7.534027099609375e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.24639225006103516s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020746469497680664s
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.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 8.106231689453125e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 2.8659143447875977s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.315376281738281e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0003497600555419922s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.2809114456176758s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 2.9170756340026855s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.792213439941406e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.24612879753112793s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 2.872215509414673s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.982948303222656e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.22830462455749512s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.02069258689880371s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 8.106231689453125e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 2.7522547245025635s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.267692565917969e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.24420762062072754s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.02093029022216797s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 8.106231689453125e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 2.798171043395996s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 4.363059997558594e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.2401721477508545s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.02074885368347168s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 2.7970383167266846s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.38690185546875e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.00034809112548828125s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.24214935302734375s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02104043960571289s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 2.819586753845215s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.6253204345703125e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.2423262596130371s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020764589309692383s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 2.739912271499634s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 5.2928924560546875e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.25551891326904297s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.02091526985168457s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 9.775161743164062e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.7712783813476562s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 4.2438507080078125e-05s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.2698099613189697s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020689010620117188s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.1948089599609375e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.4781951904296875e-05s
INFO | --- Analysis for openlink-lod-cache took 2.7896440029144287s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 4.220008850097656e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.27695465087890625s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.02072763442993164s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 0.00011229515075683594s
Believability | Calculation of trust value for openlinksw dataspaces took 7.152557373046875e-06s
INFO | --- Analysis for openlinksw-dataspaces took 2.808828592300415s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.220008850097656e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.25023627281188965s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020717382431030273s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.489059448242188e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 7.3909759521484375e-06s
INFO | --- Analysis for openlylocal took 2.891080617904663s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 4.220008850097656e-05s
Availability | VoID file availability check for OpenMobileNetwork took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.26932692527770996s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.020658493041992188s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.867813110351562e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 7.867813110351562e-06s
INFO | --- Analysis for openmobilenetwork took 2.7814366817474365s
Availability | SPARQL endpoint availability check for OpenTox took 4.553794860839844e-05s
Availability | VoID file availability check for OpenTox took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for OpenTox took 0.2478809356689453s
Reputation | Calculation of the PageRank for OpenTox took 0.02210855484008789s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for OpenTox took 4.029273986816406e-05s
Believability | Calculation of trust value for OpenTox took 8.106231689453125e-06s
INFO | --- Analysis for opentox took 2.7677128314971924s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 5.650520324707031e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.26824164390563965s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 3.886222839355469e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 8.106231689453125e-06s
INFO | --- Analysis for openuplabs took 2.8041834831237793s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 4.1484832763671875e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.24139142036437988s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.02108287811279297s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 3.361701965332031e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 7.62939453125e-06s
INFO | --- Analysis for opus took 2.7715694904327393s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 6.651878356933594e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.2724723815917969s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.02086496353149414s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.981590270996094e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 7.62939453125e-06s
INFO | --- Analysis for orcid took 2.7843008041381836s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 4.38690185546875e-05s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.2641940116882324s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.02075338363647461s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.775161743164062e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 2.8242976665496826s
Availability | SPARQL endpoint availability check for oreilly took 4.291534423828125e-05s
Availability | VoID file availability check for oreilly took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for oreilly took 0.2383127212524414s
Reputation | Calculation of the PageRank for oreilly took 0.02089667320251465s
Interlinking | Calculation of Degree of Connection for oreilly took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for oreilly took 5.14984130859375e-05s
Believability | Calculation of trust value for oreilly took 7.62939453125e-06s
INFO | --- Analysis for oreilly took 2.7190380096435547s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 4.1961669921875e-05s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.2554750442504883s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.0208740234375s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.600120544433594e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 8.344650268554688e-06s
INFO | --- Analysis for Organchem-Data took 2.7643983364105225s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 4.220008850097656e-05s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.2513446807861328s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.02084064483642578s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 7.176399230957031e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for organic-edunet took 2.7036118507385254s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 4.124641418457031e-05s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.26686692237854004s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.3113021850585938e-05s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 9.775161743164062e-06s
INFO | --- Analysis for orkg took 2.7396626472473145s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.9999325275421143s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.25838732719421387s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020728111267089844s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 0.00010943412780761719s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 8.821487426757812e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 8.307442426681519s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 4.220008850097656e-05s
Availability | VoID file availability check for OSM Semantic Network took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.2575063705444336s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020932435989379883s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.933906555175781e-05s
Believability | Calculation of trust value for OSM Semantic Network took 7.62939453125e-06s
INFO | --- Analysis for osm-semantic-network took 2.8596243858337402s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 4.315376281738281e-05s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.2523064613342285s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.020812511444091797s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.266334533691406e-05s
Believability | Calculation of trust value for Open Transport Map @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for OTM took 2.8495452404022217s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.410743713378906e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.2736334800720215s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.02084207534790039s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 3.337860107421875e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 7.3909759521484375e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 3.0432991981506348s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.1961669921875e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.26487302780151367s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.02090167999267578s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.409385681152344e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 8.106231689453125e-06s
INFO | --- Analysis for ox-ac-uk-catalogue took 2.9100708961486816s
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.00032806396484375s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.25115180015563965s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.02088022232055664s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.361701965332031e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 8.58306884765625e-06s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 2.9048871994018555s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 4.458427429199219e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.2740473747253418s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.020869731903076172s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 3.409385681152344e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 1.0013580322265625e-05s
INFO | --- Analysis for ox-ac-uk-openmeters took 2.825749397277832s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 4.696846008300781e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.2673213481903076s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020755290985107422s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 3.504753112792969e-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.9294681549072266s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.839897155761719e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.246323823928833s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.020937681198120117s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 3.314018249511719e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 8.58306884765625e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 2.9258618354797363s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 4.363059997558594e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.00030303001403808594s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.2534599304199219s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.021213054656982422s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 3.361701965332031e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 8.821487426757812e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 2.875873327255249s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 4.57763671875e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.25090765953063965s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.02118396759033203s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 3.314018249511719e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 9.298324584960938e-06s
INFO | --- Analysis for oxpoints took 2.854942798614502s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 4.291332483291626s
Availability | VoID file availability check for Pali English Lexicon took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.27755284309387207s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.02103900909423828s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0009350776672363281s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 4.7206878662109375e-05s
Believability | Calculation of trust value for Pali English Lexicon took 7.867813110351562e-06s
INFO | --- Analysis for pali-english-lexicon took 9.915785789489746s
Availability | SPARQL endpoint availability check for PanLex took 7.748603820800781e-05s
Availability | VoID file availability check for PanLex took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for PanLex took 0.25356340408325195s
Reputation | Calculation of the PageRank for PanLex took 0.021162748336791992s
Interlinking | Calculation of Degree of Connection for PanLex took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0010693073272705078s
Interlinking | Calculation of Clustering coefficient for PanLex took 0.00010633468627929688s
Believability | Calculation of trust value for PanLex took 8.821487426757812e-06s
INFO | --- Analysis for panlex took 2.87469220161438s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 8.082389831542969e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.26181936264038086s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020867586135864258s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 4.3392181396484375e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.3589859008789062e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 2.8167543411254883s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 4.315376281738281e-05s
Availability | VoID file availability check for patents.data.gov.uk took 0.0003368854522705078s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.24321508407592773s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.021082162857055664s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 5.412101745605469e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 1.3113021850585938e-05s
INFO | --- Analysis for patents-data-gov-uk took 2.8168563842773438s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.267692565917969e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.00036406517028808594s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.27483606338500977s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.020609617233276367s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 4.291534423828125e-05s
Believability | Calculation of trust value for PDEV-Lemon took 7.867813110351562e-06s
INFO | --- Analysis for pdev-lemon took 2.9259049892425537s
Availability | SPARQL endpoint availability check for pdevlemon took 4.1961669921875e-05s
Availability | VoID file availability check for pdevlemon took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.2495131492614746s
Reputation | Calculation of the PageRank for pdevlemon took 0.0207369327545166s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.123283386230469e-05s
Believability | Calculation of trust value for pdevlemon took 1.1682510375976562e-05s
INFO | --- Analysis for pdevlemon took 2.8628456592559814s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.553794860839844e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.2746620178222656s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.630752563476562e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 8.106231689453125e-06s
INFO | --- Analysis for periodo took 2.9137964248657227s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.220008850097656e-05s
Availability | VoID file availability check for Personal_Homepages took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.24871373176574707s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.021044254302978516s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0008378028869628906s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.0004284381866455078s
Believability | Calculation of trust value for Personal_Homepages took 9.059906005859375e-06s
INFO | --- Analysis for personal-homepages took 2.9631412029266357s
Availability | SPARQL endpoint availability check for Ontology of University People took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology of University People took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.2528839111328125s
Reputation | Calculation of the PageRank for Ontology of University People took 0.020571231842041016s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 3.314018249511719e-05s
Believability | Calculation of trust value for Ontology of University People took 9.298324584960938e-06s
INFO | --- Analysis for PersonOnto took 2.8437089920043945s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 5.316734313964844e-05s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2651643753051758s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.021042823791503906s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3828277587890625e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.239776611328125e-05s
INFO | --- Analysis for PFKHS took 2.8978891372680664s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 4.267692565917969e-05s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.24032902717590332s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007293224334716797s
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 8.58306884765625e-06s
INFO | --- Analysis for PFRPPH took 2.8198070526123047s
Availability | SPARQL endpoint availability check for PGxLOD took 4.2438507080078125e-05s
Availability | VoID file availability check for PGxLOD took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.24954485893249512s
Reputation | Calculation of the PageRank for PGxLOD took 0.020954132080078125s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 4.7206878662109375e-05s
Believability | Calculation of trust value for PGxLOD took 7.62939453125e-06s
INFO | --- Analysis for PGxLOD took 2.8602375984191895s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 4.029273986816406e-05s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.2575647830963135s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.02087998390197754s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 7.867813110351562e-06s
INFO | --- Analysis for phoible took 2.8498613834381104s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 4.100799560546875e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.25449681282043457s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.020986080169677734s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.314018249511719e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 7.3909759521484375e-06s
INFO | --- Analysis for PISM took 2.952897071838379s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 5.745887756347656e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.00029850006103515625s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.25281476974487305s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.02082991600036621s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.702278137207031e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 7.62939453125e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.8559954166412354s
Availability | SPARQL endpoint availability check for digitized plant specimen took 4.220008850097656e-05s
Availability | VoID file availability check for digitized plant specimen took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.25847768783569336s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.02080512046813965s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 7.295608520507812e-05s
Believability | Calculation of trust value for digitized plant specimen took 1.1682510375976562e-05s
INFO | --- Analysis for plant-specimen took 2.84474778175354s
Availability | SPARQL endpoint availability check for Pleiades took 4.315376281738281e-05s
Availability | VoID file availability check for Pleiades took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for Pleiades took 0.2670564651489258s
Reputation | Calculation of the PageRank for Pleiades took 0.020784854888916016s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.606910705566406e-05s
Believability | Calculation of trust value for Pleiades took 7.152557373046875e-06s
INFO | --- Analysis for pleiades took 2.9671263694763184s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 4.363059997558594e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.25998592376708984s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020934581756591797s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.409385681152344e-05s
Believability | Calculation of trust value for podorozhnyk.com took 7.3909759521484375e-06s
INFO | --- Analysis for podorozhnyk took 2.8966176509857178s
Availability | SPARQL endpoint availability check for Poképédia took 4.673004150390625e-05s
Availability | VoID file availability check for Poképédia took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2458653450012207s
Reputation | Calculation of the PageRank for Poképédia took 0.020822525024414062s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.724761962890625e-05s
Believability | Calculation of trust value for Poképédia took 9.298324584960938e-06s
INFO | --- Analysis for pokepedia-fr took 2.7749545574188232s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.506111145019531e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.26514458656311035s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.020814180374145508s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 8.153915405273438e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 8.344650268554688e-06s
INFO | --- Analysis for polymath-virtual-library took 2.8956735134124756s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 4.363059997558594e-05s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2659626007080078s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.02099442481994629s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.430511474609375e-05s
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 2.8382961750030518s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.291534423828125e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.2545473575592041s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 3.314018249511719e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 7.867813110351562e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.8891594409942627s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.291534423828125e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.2476210594177246s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.020986557006835938s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 3.409385681152344e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 8.344650268554688e-06s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 2.8628363609313965s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 4.124641418457031e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.27885866165161133s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.02090001106262207s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 3.337860107421875e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 1.2874603271484375e-05s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.877243995666504s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 4.220008850097656e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.0003364086151123047s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.24999618530273438s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.02082037925720215s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 3.337860107421875e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 7.62939453125e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.7939631938934326s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 4.315376281738281e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.2633981704711914s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.020924091339111328s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 3.504753112792969e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 2.8002941608428955s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 4.363059997558594e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.2949516773223877s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.020978212356567383s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 3.552436828613281e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.9112517833709717s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.27910614013671875s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.021087646484375s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 3.457069396972656e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 1.2636184692382812e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.8829405307769775s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.2581019401550293s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.02097344398498535s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 3.504753112792969e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 8.58306884765625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.877124547958374s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.25344157218933105s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.020950794219970703s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 3.409385681152344e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 2.7961928844451904s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.0008933544158935547s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.2689647674560547s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.020831823348999023s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 3.409385681152344e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 8.58306884765625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.8868041038513184s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 4.3392181396484375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.25893211364746094s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.02102947235107422s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 3.6716461181640625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.802896499633789s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 4.291534423828125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.2991604804992676s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.020809173583984375s
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.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 3.504753112792969e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.950106382369995s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.2563447952270508s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.020801544189453125s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 3.4332275390625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.8812527656555176s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.1961669921875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.2603907585144043s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.020848512649536133s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 3.314018249511719e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 1.3589859008789062e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.8844268321990967s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 4.291534423828125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.2646329402923584s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.0209500789642334s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 3.337860107421875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.8281264305114746s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 8.749961853027344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.00030803680419921875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2549245357513428s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.02088165283203125s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 3.9577484130859375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 8.821487426757812e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.8339321613311768s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.2559020519256592s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 3.2901763916015625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 8.344650268554688e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.8502883911132812s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.2675454616546631s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.020940303802490234s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 3.4332275390625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 6.67572021484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.8230955600738525s
Availability | SPARQL endpoint availability check for prefix.cc took 4.553794860839844e-05s
Availability | VoID file availability check for prefix.cc took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.2579770088195801s
Reputation | Calculation of the PageRank for prefix.cc took 0.020858287811279297s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 4.5299530029296875e-05s
Believability | Calculation of trust value for prefix.cc took 1.3828277587890625e-05s
INFO | --- Analysis for prefix-cc took 2.797149658203125s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 4.363059997558594e-05s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.23807120323181152s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.021673202514648438s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0013163089752197266s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 7.295608520507812e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 8.106231689453125e-06s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 2.8441059589385986s
Availability | SPARQL endpoint availability check for PreLex took 4.291534423828125e-05s
Availability | VoID file availability check for PreLex took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for PreLex took 0.2780747413635254s
Reputation | Calculation of the PageRank for PreLex took 0.02092719078063965s
Interlinking | Calculation of Degree of Connection for PreLex took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.700920104980469e-05s
Believability | Calculation of trust value for PreLex took 8.106231689453125e-06s
INFO | --- Analysis for prelex took 2.866792917251587s
Availability | SPARQL endpoint availability check for Prelinger Archives took 4.706339359283447s
Availability | VoID file availability check for Prelinger Archives took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.25646018981933594s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.021043062210083008s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.4332275390625e-05s
Believability | Calculation of trust value for Prelinger Archives took 7.867813110351562e-06s
INFO | --- Analysis for prelinger_archives took 9.959929466247559s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 6.818771362304688e-05s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.2488691806793213s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.021022319793701172s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 5.602836608886719e-05s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 8.344650268554688e-06s
INFO | --- Analysis for premon took 2.8431923389434814s
Availability | SPARQL endpoint availability check for Previsible took 4.315376281738281e-05s
Availability | VoID file availability check for Previsible took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Previsible took 0.25646233558654785s
Reputation | Calculation of the PageRank for Previsible took 0.02079010009765625s
Interlinking | Calculation of Degree of Connection for Previsible took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.4066696166992188e-05s
Believability | Calculation of trust value for Previsible took 8.344650268554688e-06s
INFO | --- Analysis for Previsible took 2.907927989959717s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 4.363059997558594e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.2785978317260742s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.745887756347656e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 8.106231689453125e-06s
INFO | --- Analysis for princeton-library-findingaids took 2.8905937671661377s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 4.3392181396484375e-05s
Availability | VoID file availability check for PrinParLat in LiLa took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.27084970474243164s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020976781845092773s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 4.363059997558594e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 1.3589859008789062e-05s
INFO | --- Analysis for PrinParLat took 2.824753999710083s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.3404521942138672s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.256420373916626s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.726119995117188e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.867813110351562e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.2653708457946777s
Availability | SPARQL endpoint availability check for Prior Panel took 8.487701416015625e-05s
Availability | VoID file availability check for Prior Panel took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.27060937881469727s
Reputation | Calculation of the PageRank for Prior Panel took 0.020901203155517578s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.790855407714844e-05s
Believability | Calculation of trust value for Prior Panel took 8.106231689453125e-06s
INFO | --- Analysis for Prior_Panel took 2.8648667335510254s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 4.315376281738281e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.27150988578796387s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 3.790855407714844e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 8.58306884765625e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 2.748119354248047s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 4.363059997558594e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.24057316780090332s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.020896196365356445s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.24249267578125e-05s
Believability | Calculation of trust value for Procomún SPARQL took 1.2159347534179688e-05s
INFO | --- Analysis for procomun-sparql took 2.792680263519287s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.649162292480469e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.2580130100250244s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.023192167282104492s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0008335113525390625s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 3.981590270996094e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.78037691116333s
Availability | SPARQL endpoint availability check for ProductDB took 4.3392181396484375e-05s
Availability | VoID file availability check for ProductDB took 0.00031566619873046875s
Completeness | Calculation of interlinking completeness for ProductDB took 0.2621798515319824s
Reputation | Calculation of the PageRank for ProductDB took 0.02132248878479004s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for ProductDB took 8.58306884765625e-05s
Believability | Calculation of trust value for ProductDB took 8.344650268554688e-06s
INFO | --- Analysis for productdb took 2.8656368255615234s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Product Types Ontology took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.2441418170928955s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.02110004425048828s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 8.249282836914062e-05s
Believability | Calculation of trust value for Product Types Ontology took 8.58306884765625e-06s
INFO | --- Analysis for productontology took 2.926095962524414s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.124641418457031e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.2645728588104248s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.020776033401489258s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.0001068115234375s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 2.897719383239746s
Availability | SPARQL endpoint availability check for provenanceweb took 4.220008850097656e-05s
Availability | VoID file availability check for provenanceweb took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.24117016792297363s
Reputation | Calculation of the PageRank for provenanceweb took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 7.963180541992188e-05s
Believability | Calculation of trust value for provenanceweb took 7.152557373046875e-06s
INFO | --- Analysis for provenanceweb took 2.7890729904174805s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 7.224082946777344e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.256267786026001s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.021097660064697266s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00011181831359863281s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 7.152557373046875e-06s
INFO | --- Analysis for proyectoapadrina took 2.8665411472320557s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 6.771087646484375e-05s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.2501044273376465s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.021008014678955078s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.981590270996094e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 1.33514404296875e-05s
INFO | --- Analysis for pscs-catalogue took 2.988551378250122s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.124641418457031e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.26020288467407227s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.02076578140258789s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.677078247070312e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 8.106231689453125e-06s
INFO | --- Analysis for psh-subject-headings took 2.88923978805542s
Availability | SPARQL endpoint availability check for Depression took 4.38690185546875e-05s
Availability | VoID file availability check for Depression took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Depression took 0.28981924057006836s
Reputation | Calculation of the PageRank for Depression took 0.020709753036499023s
Interlinking | Calculation of Degree of Connection for Depression took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Depression took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Depression took 3.409385681152344e-05s
Believability | Calculation of trust value for Depression took 1.3828277587890625e-05s
INFO | --- Analysis for Psychology took 2.8955888748168945s
Availability | SPARQL endpoint availability check for PubChem RDF took 4.124641418457031e-05s
Availability | VoID file availability check for PubChem RDF took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.268735408782959s
Reputation | Calculation of the PageRank for PubChem RDF took 0.02093982696533203s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.553794860839844e-05s
Believability | Calculation of trust value for PubChem RDF took 7.867813110351562e-06s
INFO | --- Analysis for PubChem_RDF took 2.901366949081421s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 4.315376281738281e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.2514040470123291s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.020730018615722656s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 3.4809112548828125e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 9.059906005859375e-06s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 2.9173314571380615s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 4.267692565917969e-05s
Availability | VoID file availability check for Public Spending in Greece took 0.00035643577575683594s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.2683072090148926s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.0214693546295166s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 9.72747802734375e-05s
Believability | Calculation of trust value for Public Spending in Greece took 9.059906005859375e-06s
INFO | --- Analysis for public-spending-in-greece took 2.968900680541992s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 4.1484832763671875e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.23905348777770996s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 3.218650817871094e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 6.67572021484375e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 2.8522541522979736s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 4.315376281738281e-05s
Availability | VoID file availability check for Publications Office Authority tables took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 0.2537221908569336s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.021431684494018555s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.1961669921875e-05s
Believability | Calculation of trust value for Publications Office Authority tables took 8.344650268554688e-06s
INFO | --- Analysis for publications_office_authority_tables took 2.839050769805908s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 4.315376281738281e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.26749706268310547s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.02087712287902832s
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.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.528594970703125e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 7.867813110351562e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 2.8507962226867676s
Availability | SPARQL endpoint availability check for QBOAirbase took 4.1484832763671875e-05s
Availability | VoID file availability check for QBOAirbase took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.26755499839782715s
Reputation | Calculation of the PageRank for QBOAirbase took 0.021306991577148438s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.796287536621094e-05s
Believability | Calculation of trust value for QBOAirbase took 8.821487426757812e-06s
INFO | --- Analysis for qboairbase took 2.918401002883911s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 4.363059997558594e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.24965596199035645s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.02130866050720215s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 4.029273986816406e-05s
Believability | Calculation of trust value for qualitywebdata.org took 8.106231689453125e-06s
INFO | --- Analysis for qualitywebdata-org took 2.839181661605835s
Availability | SPARQL endpoint availability check for Qualité de l'air took 4.38690185546875e-05s
Availability | VoID file availability check for Qualité de l'air took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.24273991584777832s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.021187782287597656s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 3.5762786865234375e-05s
Believability | Calculation of trust value for Qualité de l'air took 7.152557373046875e-06s
INFO | --- Analysis for Qualité_de_l'air took 2.9204061031341553s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 4.2438507080078125e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.278700590133667s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.020963430404663086s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.3855438232421875e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 7.3909759521484375e-06s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 3.0070884227752686s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.6006870269775391s
Availability | VoID file availability check for Querolus in LiLa took 0.0004150867462158203s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.2910435199737549s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.03314709663391113s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0014760494232177734s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 6.651878356933594e-05s
Believability | Calculation of trust value for Querolus in LiLa took 8.106231689453125e-06s
INFO | --- Analysis for Querolus took 3.943176507949829s
Availability | SPARQL endpoint availability check for Quotations Book took 6.818771362304688e-05s
Availability | VoID file availability check for Quotations Book took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.27397990226745605s
Reputation | Calculation of the PageRank for Quotations Book took 0.02126789093017578s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 3.528594970703125e-05s
Believability | Calculation of trust value for Quotations Book took 7.867813110351562e-06s
INFO | --- Analysis for quotations_book took 2.910374879837036s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 7.05718994140625e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.2724800109863281s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.02107524871826172s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.4809112548828125e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.152557373046875e-06s
INFO | --- Analysis for r4r took 2.8378803730010986s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.2438507080078125e-05s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.000244140625s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.25933051109313965s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.021581411361694336s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0008094310760498047s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.91278076171875e-05s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.62939453125e-06s
INFO | --- Analysis for racai-legalnero took 2.8109920024871826s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 4.291534423828125e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.2737083435058594s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.02150416374206543s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 4.0531158447265625e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 8.106231689453125e-06s
INFO | --- Analysis for racai-llod-corola-we took 2.8777353763580322s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 5.602836608886719e-05s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.2645077705383301s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.021219491958618164s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.409385681152344e-05s
Believability | Calculation of trust value for PARSEME-Ro corpus took 7.867813110351562e-06s
INFO | --- Analysis for racai-llod-parseme-ro took 2.8157994747161865s
Availability | SPARQL endpoint availability check for RoLEX took 5.2928924560546875e-05s
Availability | VoID file availability check for RoLEX took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for RoLEX took 0.23585796356201172s
Reputation | Calculation of the PageRank for RoLEX took 0.02117300033569336s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.504753112792969e-05s
Believability | Calculation of trust value for RoLEX took 9.059906005859375e-06s
INFO | --- Analysis for racai-llod-rolex took 2.857635736465454s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.24532699584960938s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.021185874938964844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 3.457069396972656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.867813110351562e-06s
INFO | --- Analysis for racai-llod-romanian-treebank took 2.7773828506469727s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.2438507080078125e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.24530339241027832s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.021221160888671875s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 3.3855438232421875e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 2.851372241973877s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.172325134277344e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.2923002243041992s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.02124643325805664s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.814697265625e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 9.059906005859375e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.9593889713287354s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 4.3392181396484375e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.2534666061401367s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.021336078643798828s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 3.4332275390625e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.2159347534179688e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.8082852363586426s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 4.220008850097656e-05s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.2903938293457031s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.020875215530395508s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 3.266334533691406e-05s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 7.867813110351562e-06s
INFO | --- Analysis for racai-llod-rtasc took 2.9189717769622803s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 4.3392181396484375e-05s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.28283095359802246s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.02089381217956543s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 3.409385681152344e-05s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 1.430511474609375e-05s
INFO | --- Analysis for racai-llod-simonero took 2.907517433166504s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.21704483032226562s
Availability | VoID file availability check for Rådata nå! took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.28154683113098145s
Reputation | Calculation of the PageRank for Rådata nå! took 0.022396087646484375s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 9.322166442871094e-05s
Believability | Calculation of trust value for Rådata nå! took 1.0013580322265625e-05s
INFO | --- Analysis for radatana took 3.176730155944824s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 4.410743713378906e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.00036263465881347656s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.2449634075164795s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.02195906639099121s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0010259151458740234s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 5.125999450683594e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 7.62939453125e-06s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 2.9332523345947266s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.315376281738281e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.28484249114990234s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.021130800247192383s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 3.2901763916015625e-05s
Believability | Calculation of trust value for Raphael Research Resource took 9.059906005859375e-06s
INFO | --- Analysis for raphaelresearchresource took 2.974517345428467s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 4.482269287109375e-05s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0003447532653808594s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.2515857219696045s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.020801782608032227s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.2901763916015625e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 7.867813110351562e-06s
INFO | --- Analysis for ravensburg-local-shopping-graph took 2.784275770187378s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 4.2438507080078125e-05s
Availability | VoID file availability check for Polish LGU financial statements took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.2493894100189209s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.021173477172851562s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 3.552436828613281e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 1.0013580322265625e-05s
INFO | --- Analysis for Rb_PL_LGU took 2.8663275241851807s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 4.3392181396484375e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.0003132820129394531s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.2671852111816406s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.021004438400268555s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 3.314018249511719e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 1.2874603271484375e-05s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 2.8421313762664795s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.25351715087890625s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.02176213264465332s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0008697509765625s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 3.8623809814453125e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 9.298324584960938e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 2.848477602005005s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.27477526664733887s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.020837783813476562s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 3.337860107421875e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 2.850426435470581s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 4.267692565917969e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.264723539352417s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.020682096481323242s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 3.743171691894531e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 2.8538358211517334s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 4.1484832763671875e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.26326727867126465s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.020946025848388672s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 3.409385681152344e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 9.059906005859375e-06s
INFO | --- Analysis for rcahmw-periods-list took 2.846388816833496s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.792213439941406e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.25447535514831543s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.024088144302368164s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 2.9087066650390625e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0012540817260742188s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 0.00011992454528808594s
Believability | Calculation of trust value for RDF Book Mashup took 8.106231689453125e-06s
INFO | --- Analysis for rdf-book-mashup took 2.8766984939575195s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.458427429199219e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.26053476333618164s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020926713943481445s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00010538101196289062s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 6.67572021484375e-06s
INFO | --- Analysis for rdfize-lastfm took 2.7949976921081543s
Availability | SPARQL endpoint availability check for RDFLicense took 4.00543212890625e-05s
Availability | VoID file availability check for RDFLicense took 0.0003654956817626953s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.2806417942047119s
Reputation | Calculation of the PageRank for RDFLicense took 0.021027088165283203s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0008771419525146484s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 4.482269287109375e-05s
Believability | Calculation of trust value for RDFLicense took 8.344650268554688e-06s
INFO | --- Analysis for rdflicense took 2.903055191040039s
Availability | SPARQL endpoint availability check for RDFohloh took 4.2438507080078125e-05s
Availability | VoID file availability check for RDFohloh took 0.00030541419982910156s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.2713446617126465s
Reputation | Calculation of the PageRank for RDFohloh took 0.020999670028686523s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 9.751319885253906e-05s
Believability | Calculation of trust value for RDFohloh took 1.2636184692382812e-05s
INFO | --- Analysis for rdfohloh took 2.915276527404785s
Availability | SPARQL endpoint availability check for Reactome RDF took 6.699562072753906e-05s
Availability | VoID file availability check for Reactome RDF took 0.0003643035888671875s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.2593693733215332s
Reputation | Calculation of the PageRank for Reactome RDF took 0.0208890438079834s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 4.38690185546875e-05s
Believability | Calculation of trust value for Reactome RDF took 1.33514404296875e-05s
INFO | --- Analysis for reactome-rdf took 2.795991897583008s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 4.410743713378906e-05s
Availability | VoID file availability check for Rechtspraak.nl took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.269866943359375s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.021203041076660156s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 0.00011372566223144531s
Believability | Calculation of trust value for Rechtspraak.nl took 7.152557373046875e-06s
INFO | --- Analysis for rechtspraak took 2.879490852355957s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.267692565917969e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.26900506019592285s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.020826101303100586s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 9.417533874511719e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 7.3909759521484375e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 2.9166839122772217s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 6.508827209472656e-05s
Availability | VoID file availability check for reference.data.gov.uk took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.24961161613464355s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020958423614501953s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.0001590251922607422s
Believability | Calculation of trust value for reference.data.gov.uk took 1.1205673217773438e-05s
INFO | --- Analysis for reference-data-gov-uk took 2.8202743530273438s
Availability | SPARQL endpoint availability check for Regiony took 4.172325134277344e-05s
Availability | VoID file availability check for Regiony took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Regiony took 0.23524212837219238s
Reputation | Calculation of the PageRank for Regiony took 0.0211026668548584s
Interlinking | Calculation of Degree of Connection for Regiony took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Regiony took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Regiony took 3.337860107421875e-05s
Believability | Calculation of trust value for Regiony took 7.867813110351562e-06s
INFO | --- Analysis for regiony took 2.874246120452881s
Availability | SPARQL endpoint availability check for RELD took 4.291534423828125e-05s
Availability | VoID file availability check for RELD took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for RELD took 0.2403881549835205s
Reputation | Calculation of the PageRank for RELD took 0.021225690841674805s
Interlinking | Calculation of Degree of Connection for RELD took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for RELD took 3.528594970703125e-05s
Believability | Calculation of trust value for RELD took 1.7642974853515625e-05s
INFO | --- Analysis for RELD took 2.881004810333252s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 6.198883056640625e-05s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.26644420623779297s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.020717382431030273s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 3.933906555175781e-05s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 8.58306884765625e-06s
INFO | --- Analysis for reload took 2.892557382583618s
Availability | SPARQL endpoint availability check for Land use merced dataset took 5.626678466796875e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0003490447998046875s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.2636075019836426s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.02141880989074707s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.743171691894531e-05s
Believability | Calculation of trust value for Land use merced dataset took 1.2159347534179688e-05s
INFO | --- Analysis for remote_Sensing took 2.8916990756988525s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 4.1961669921875e-05s
Availability | VoID file availability check for Renewable Energy Generators took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.2524099349975586s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.02230668067932129s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 5.2928924560546875e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 8.106231689453125e-06s
INFO | --- Analysis for renewable_energy_generators took 2.8909504413604736s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 4.1961669921875e-05s
Availability | VoID file availability check for research.data.gov.uk took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.26195287704467773s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 0.00010371208190917969s
Believability | Calculation of trust value for research.data.gov.uk took 1.2636184692382812e-05s
INFO | --- Analysis for research-data-gov-uk took 2.915360450744629s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 4.410743713378906e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.2555561065673828s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.020617246627807617s
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.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 3.409385681152344e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 6.4373016357421875e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 2.8843834400177s
Availability | SPARQL endpoint availability check for Restaurantes took 4.1961669921875e-05s
Availability | VoID file availability check for Restaurantes took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.25640153884887695s
Reputation | Calculation of the PageRank for Restaurantes took 0.02092909812927246s
Interlinking | Calculation of Degree of Connection for Restaurantes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Restaurantes took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 3.4809112548828125e-05s
Believability | Calculation of trust value for Restaurantes took 9.059906005859375e-06s
INFO | --- Analysis for restaurantes-zaragoza took 2.8367161750793457s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.38690185546875e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.27558064460754395s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.020900249481201172s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 7.62939453125e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 7.3909759521484375e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 2.8842175006866455s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 7.605552673339844e-05s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0003151893615722656s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.26795315742492676s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.020778179168701172s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.337860107421875e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 8.106231689453125e-06s
INFO | --- Analysis for revistas_turismo took 2.9266719818115234s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 4.506111145019531e-05s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0003612041473388672s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.2676970958709717s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.021030426025390625s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.0001289844512939453s
Believability | Calculation of trust value for Revyu.com - Review Anything took 9.298324584960938e-06s
INFO | --- Analysis for revyu took 2.837610960006714s
Availability | SPARQL endpoint availability check for sdafsadf took 4.172325134277344e-05s
Availability | VoID file availability check for sdafsadf took 0.0003108978271484375s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.26741909980773926s
Reputation | Calculation of the PageRank for sdafsadf took 0.020850181579589844s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.528594970703125e-05s
Believability | Calculation of trust value for sdafsadf took 7.62939453125e-06s
INFO | --- Analysis for rgsdfg took 2.89546275138855s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.601478576660156e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.277254581451416s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.020772933959960938s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 5.316734313964844e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 7.867813110351562e-06s
INFO | --- Analysis for riese took 2.862358808517456s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 4.1961669921875e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.2623441219329834s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.02077770233154297s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 3.2901763916015625e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 7.3909759521484375e-06s
INFO | --- Analysis for rijksmuseum took 2.8031270503997803s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 30.36265754699707s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.2584547996520996s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.020981311798095703s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0008113384246826172s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 5.173683166503906e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 8.106231689453125e-06s
INFO | --- Analysis for rism took 63.143800497055054s
Availability | SPARQL endpoint availability check for RISM Authority data took 20.02693819999695s
Availability | VoID file availability check for RISM Authority data took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.24544405937194824s
Reputation | Calculation of the PageRank for RISM Authority data took 0.021013736724853516s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0008087158203125s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 5.269050598144531e-05s
Believability | Calculation of trust value for RISM Authority data took 9.059906005859375e-06s
INFO | --- Analysis for rism-authorities took 53.31849551200867s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.363059997558594e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.26433229446411133s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.021078109741210938s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.361701965332031e-05s
Believability | Calculation of trust value for engineering equipment ontology took 7.62939453125e-06s
INFO | --- Analysis for rk took 2.8628768920898438s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 6.723403930664062e-05s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00037097930908203125s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.23281002044677734s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.03397417068481445s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0018668174743652344s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0005397796630859375s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.8779633045196533s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 4.363059997558594e-05s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0003085136413574219s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.27841663360595703s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.02075982093811035s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00014710426330566406s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-budapest took 2.8933379650115967s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0003676414489746094s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.2640848159790039s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.022533178329467773s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0011451244354248047s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00024628639221191406s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.8682162761688232s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0003161430358886719s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.2751905918121338s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.02078080177307129s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00020241737365722656s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.8507447242736816s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.2817881107330322s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.0002040863037109375s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.841926097869873s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 4.363059997558594e-05s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.2615175247192383s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020622968673706055s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 4.482269287109375e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.8461854457855225s
Availability | SPARQL endpoint availability check for crm took 5.412101745605469e-05s
Availability | VoID file availability check for crm took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for crm took 0.2583487033843994s
Reputation | Calculation of the PageRank for crm took 0.020688772201538086s
Interlinking | Calculation of Degree of Connection for crm took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for crm took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for crm took 3.361701965332031e-05s
Believability | Calculation of trust value for crm took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-crm took 2.84283709526062s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 4.291534423828125e-05s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.2669486999511719s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00011730194091796875s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-curriculum took 2.8557794094085693s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 4.673004150390625e-05s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.2492971420288086s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.021052122116088867s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.507469177246094e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.8305470943450928s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 4.38690185546875e-05s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.25664424896240234s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.02096271514892578s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.00023436546325683594s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 1.3589859008789062e-05s
INFO | --- Analysis for rkb-explorer-dblp took 2.822981119155884s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 4.410743713378906e-05s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.2569108009338379s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.891654968261719e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.8927605152130127s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 4.291534423828125e-05s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.24239826202392578s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.02087569236755371s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.870529174804688e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-deploy took 2.792262554168701s
Availability | SPARQL endpoint availability check for digitaleconomy took 4.3392181396484375e-05s
Availability | VoID file availability check for digitaleconomy took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.275498628616333s
Reputation | Calculation of the PageRank for digitaleconomy took 0.021257877349853516s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0008311271667480469s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.814697265625e-05s
Believability | Calculation of trust value for digitaleconomy took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.9550395011901855s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 4.291534423828125e-05s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2680814266204834s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.02076864242553711s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00014734268188476562s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-dotac took 2.843366861343384s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.863739013671875e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.26660776138305664s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020897388458251953s
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.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.340576171875e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-ecs took 2.7976901531219482s
Availability | SPARQL endpoint availability check for enaktingpsi took 5.4836273193359375e-05s
Availability | VoID file availability check for enaktingpsi took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.2732253074645996s
Reputation | Calculation of the PageRank for enaktingpsi took 0.020848751068115234s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 3.266334533691406e-05s
Believability | Calculation of trust value for enaktingpsi took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.815099000930786s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 6.604194641113281e-05s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.2604026794433594s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.022352218627929688s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0001785755157470703s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-eprints took 2.842362880706787s
Availability | SPARQL endpoint availability check for epsrc took 4.172325134277344e-05s
Availability | VoID file availability check for epsrc took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for epsrc took 0.2806386947631836s
Reputation | Calculation of the PageRank for epsrc took 0.020792245864868164s
Interlinking | Calculation of Degree of Connection for epsrc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for epsrc took 6.008148193359375e-05s
Believability | Calculation of trust value for epsrc took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 2.896864652633667s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 4.2438507080078125e-05s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.2754073143005371s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.02093505859375s
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.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.845329284667969e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-era took 2.897469997406006s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 7.081031799316406e-05s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.2587714195251465s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020709514617919922s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010395050048828125s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.846759080886841s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 4.172325134277344e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.2729454040527344s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.021114826202392578s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 3.504753112792969e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-foreign took 2.843116521835327s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 4.553794860839844e-05s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.00030112266540527344s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.25972867012023926s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020757198333740234s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.1552734375e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-ft took 2.885240077972412s
Availability | SPARQL endpoint availability check for fun took 4.410743713378906e-05s
Availability | VoID file availability check for fun took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for fun took 0.2720768451690674s
Reputation | Calculation of the PageRank for fun took 0.02117300033569336s
Interlinking | Calculation of Degree of Connection for fun took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for fun took 0.0008471012115478516s
Interlinking | Calculation of Clustering coefficient for fun took 8.869171142578125e-05s
Believability | Calculation of trust value for fun took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.8497097492218018s
Availability | SPARQL endpoint availability check for gdlc took 4.291534423828125e-05s
Availability | VoID file availability check for gdlc took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for gdlc took 0.2543962001800537s
Reputation | Calculation of the PageRank for gdlc took 0.02299332618713379s
Interlinking | Calculation of Degree of Connection for gdlc took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for gdlc took 0.001132965087890625s
Interlinking | Calculation of Clustering coefficient for gdlc took 9.250640869140625e-05s
Believability | Calculation of trust value for gdlc took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.8647618293762207s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 4.220008850097656e-05s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.2489018440246582s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.0209352970123291s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0008184909820556641s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00013971328735351562s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-ibm took 2.799858331680298s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 4.3392181396484375e-05s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.2706718444824219s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020914554595947266s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0008225440979003906s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.00014448165893554688s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-ieee took 2.8484950065612793s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 4.315376281738281e-05s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.2350156307220459s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.020885944366455078s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.000148773193359375s
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.74275803565979s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 4.410743713378906e-05s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.2675771713256836s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.02089858055114746s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.4849853515625e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.8829352855682373s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 4.3392181396484375e-05s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.2859933376312256s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.02071237564086914s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.700920104980469e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.983421802520752s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 6.937980651855469e-05s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.26252293586730957s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.76837158203125e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.8641884326934814s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 5.269050598144531e-05s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.26261234283447266s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020806550979614258s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00016069412231445312s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.818648099899292s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 4.3392181396484375e-05s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.2567324638366699s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00014591217041015625s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.9273297786712646s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 4.506111145019531e-05s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.23996210098266602s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.020869970321655273s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.628036499023438e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-lisbon took 2.913808822631836s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 4.267692565917969e-05s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.2547318935394287s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020697832107543945s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00016069412231445312s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.8591277599334717s
Availability | SPARQL endpoint availability check for notube took 8.106231689453125e-05s
Availability | VoID file availability check for notube took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for notube took 0.2503540515899658s
Reputation | Calculation of the PageRank for notube took 0.020752429962158203s
Interlinking | Calculation of Degree of Connection for notube took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for notube took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for notube took 4.5299530029296875e-05s
Believability | Calculation of trust value for notube took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-notube took 2.86570143699646s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 4.220008850097656e-05s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.000274658203125s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.26630401611328125s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.02081441879272461s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.0001347064971923828s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.9021544456481934s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0003197193145751953s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.2920804023742676s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020862579345703125s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0001506805419921875s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.918285846710205s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.1961669921875e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.24940180778503418s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.021094083786010742s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 5.173683166503906e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-opencyc took 2.9660611152648926s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 4.3392181396484375e-05s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.2625725269317627s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.020874500274658203s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.843971252441406e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-os took 2.8681821823120117s
Availability | SPARQL endpoint availability check for photos took 5.316734313964844e-05s
Availability | VoID file availability check for photos took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for photos took 0.24812602996826172s
Reputation | Calculation of the PageRank for photos took 0.022022247314453125s
Interlinking | Calculation of Degree of Connection for photos took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for photos took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for photos took 8.344650268554688e-05s
Believability | Calculation of trust value for photos took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.8177571296691895s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 6.079673767089844e-05s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.26503539085388184s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.02071523666381836s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011324882507324219s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.865506172180176s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 4.2438507080078125e-05s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0002930164337158203s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.273944616317749s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.020839691162109375s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019311904907226562s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.8283567428588867s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 4.315376281738281e-05s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.25897932052612305s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.02098679542541504s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00014281272888183594s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.8359549045562744s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 4.267692565917969e-05s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.23854613304138184s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020928621292114258s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.1552734375e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-risks took 2.7805323600769043s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 4.3392181396484375e-05s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.29560351371765137s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012373924255371094s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.889432191848755s
Availability | SPARQL endpoint availability check for roni took 4.458427429199219e-05s
Availability | VoID file availability check for roni took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for roni took 0.23914599418640137s
Reputation | Calculation of the PageRank for roni took 0.021124839782714844s
Interlinking | Calculation of Degree of Connection for roni took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for roni took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for roni took 3.147125244140625e-05s
Believability | Calculation of trust value for roni took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-roni took 2.788694381713867s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 4.363059997558594e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0003590583801269531s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.26127123832702637s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.02093505859375s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00022292137145996094s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.4066696166992188e-05s
INFO | --- Analysis for rkb-explorer-southampton took 2.914355993270874s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 4.506111145019531e-05s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.2794005870819092s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.000110626220703125s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-ulm took 2.7839980125427246s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 4.2438507080078125e-05s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.26586389541625977s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 0.00010561943054199219s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.789254665374756s
Availability | SPARQL endpoint availability check for webconf took 4.267692565917969e-05s
Availability | VoID file availability check for webconf took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for webconf took 0.26361513137817383s
Reputation | Calculation of the PageRank for webconf took 0.020727872848510742s
Interlinking | Calculation of Degree of Connection for webconf took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00011444091796875s
Believability | Calculation of trust value for webconf took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-webconf took 2.8839802742004395s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.2654592990875244s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.02124333381652832s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0008573532104492188s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 8.416175842285156e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-webscience took 2.8246397972106934s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 5.4836273193359375e-05s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.00029349327087402344s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.24115371704101562s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.020921945571899414s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00021219253540039062s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-wiki took 2.847506046295166s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 4.291534423828125e-05s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.2674140930175781s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.020981550216674805s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 0.00010466575622558594s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.8929808139801025s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 4.2438507080078125e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.2798442840576172s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.020845413208007812s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 3.337860107421875e-05s
Believability | Calculation of trust value for RKB Explorer Data took 8.344650268554688e-06s
INFO | --- Analysis for rkb_explorer_data took 2.874387502670288s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.22825217247009277s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0006814002990722656s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 28.63159680366516s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.43297433853149414s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 1.7623372077941895s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.663278341293335s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 5.0942487716674805s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.248884916305542s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.07926273345947266s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.08766055107116699s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.08553528785705566s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.08000922203063965s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.08649539947509766s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.09239435195922852s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.08040189743041992s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.17029690742492676s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.07888340950012207s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.09335827827453613s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.08569192886352539s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.35063648223877s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 0.00010919570922851562s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.0865926742553711s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.08642435073852539s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.0859830379486084s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.09317874908447266s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.07921147346496582s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.16579794883728027s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.16992807388305664s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 34.55542063713074s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.11011791229248047s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.07903838157653809s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.08482789993286133s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 4.0757362842559814s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.09652519226074219s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 3.0475716590881348s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 6.602123498916626s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.4788291454315186s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.3733580112457275s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 3.0796713829040527s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.08627700805664062s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 496.92918133735657s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.9921655654907227s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.022587060928344727s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0011684894561767578s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 0.00011277198791503906s
Interoperability | Check the re-using of existing vocabs for ROCEEH Out of Africa Database (ROAD) took 2.6226043701171875e-06s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 1.2636184692382812e-05s
INFO | --- Analysis for roceeh-road took 627.0348155498505s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.3392181396484375e-05s
Availability | VoID file availability check for The Rosetta Project took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.6889595985412598s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.020769834518432617s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 3.1948089599609375e-05s
Believability | Calculation of trust value for The Rosetta Project took 6.9141387939453125e-06s
INFO | --- Analysis for rosetta-project took 3.3247764110565186s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 4.2438507080078125e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.27031946182250977s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.02073502540588379s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 3.218650817871094e-05s
Believability | Calculation of trust value for ontology terrorist attack took 8.344650268554688e-06s
INFO | --- Analysis for ROSHANI took 3.699086904525757s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.1961669921875e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0011010169982910156s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.28128528594970703s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.600120544433594e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 8.344650268554688e-06s
INFO | --- Analysis for ROSHANI_SAHU took 2.8738393783569336s
Availability | SPARQL endpoint availability check for x took 4.76837158203125e-05s
Availability | VoID file availability check for x took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for x took 0.26318907737731934s
Reputation | Calculation of the PageRank for x took 0.02107977867126465s
Interlinking | Calculation of Degree of Connection for x took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for x took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for x took 3.3855438232421875e-05s
Believability | Calculation of trust value for x took 8.821487426757812e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 3.318295955657959s
Availability | SPARQL endpoint availability check for Rpm Find took 4.220008850097656e-05s
Availability | VoID file availability check for Rpm Find took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.24364495277404785s
Reputation | Calculation of the PageRank for Rpm Find took 0.020735740661621094s
Interlinking | Calculation of Degree of Connection for Rpm Find took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Rpm Find took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 3.170967102050781e-05s
Believability | Calculation of trust value for Rpm Find took 8.58306884765625e-06s
INFO | --- Analysis for rpm_find took 3.24886417388916s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.2438507080078125e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.26645970344543457s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.020834922790527344s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.961822509765625e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 7.3909759521484375e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 2.839400053024292s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.25383567810058594s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.486343383789062e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 7.62939453125e-06s
INFO | --- Analysis for rubentaelman took 2.8326449394226074s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.2438507080078125e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.26642847061157227s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.020720243453979492s
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.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.821487426757812e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 8.344650268554688e-06s
INFO | --- Analysis for rubenverborgh took 2.8929178714752197s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 4.315376281738281e-05s
Availability | VoID file availability check for Russian Universities Specialities took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.24942302703857422s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.021106719970703125s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 3.814697265625e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 8.106231689453125e-06s
INFO | --- Analysis for russian-universities-specialities took 2.7994844913482666s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.2438507080078125e-05s
Availability | VoID file availability check for RuThes Cloud took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.27687668800354004s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.02153468132019043s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 3.600120544433594e-05s
Believability | Calculation of trust value for RuThes Cloud took 8.58306884765625e-06s
INFO | --- Analysis for ruthes took 2.862902879714966s
Availability | SPARQL endpoint availability check for RxNorm took 4.124641418457031e-05s
Availability | VoID file availability check for RxNorm took 0.000274658203125s
Completeness | Calculation of interlinking completeness for RxNorm took 0.2512688636779785s
Reputation | Calculation of the PageRank for RxNorm took 0.021686553955078125s
Interlinking | Calculation of Degree of Connection for RxNorm took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RxNorm took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.814697265625e-05s
Believability | Calculation of trust value for RxNorm took 8.344650268554688e-06s
INFO | --- Analysis for rxnorm took 2.8948400020599365s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 4.291534423828125e-05s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0003058910369873047s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.23328042030334473s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.021037817001342773s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.409385681152344e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 9.059906005859375e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 2.8355040550231934s
Availability | SPARQL endpoint availability check for SALDO took 4.267692565917969e-05s
Availability | VoID file availability check for SALDO took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for SALDO took 0.24314022064208984s
Reputation | Calculation of the PageRank for SALDO took 0.02138686180114746s
Interlinking | Calculation of Degree of Connection for SALDO took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for SALDO took 0.0012454986572265625s
Interlinking | Calculation of Clustering coefficient for SALDO took 4.744529724121094e-05s
Believability | Calculation of trust value for SALDO took 7.867813110351562e-06s
INFO | --- Analysis for saldo took 2.785796642303467s
Availability | SPARQL endpoint availability check for SALDO-RDF took 4.220008850097656e-05s
Availability | VoID file availability check for SALDO-RDF took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.2655322551727295s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.020888566970825195s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.814697265625e-05s
Believability | Calculation of trust value for SALDO-RDF took 8.58306884765625e-06s
INFO | --- Analysis for saldo-rdf took 2.8935155868530273s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 4.38690185546875e-05s
Availability | VoID file availability check for SALDOM-RDF took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.24871420860290527s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020981788635253906s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 4.0531158447265625e-05s
Believability | Calculation of trust value for SALDOM-RDF took 8.58306884765625e-06s
INFO | --- Analysis for saldom-rdf took 2.886662006378174s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 0.00010538101196289062s
Availability | VoID file availability check for Salzburgerland DE took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.25153160095214844s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.02082967758178711s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010895729064941406s
Believability | Calculation of trust value for Salzburgerland DE took 1.2636184692382812e-05s
INFO | --- Analysis for salzburgerland-com-de took 2.986922264099121s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.6253204345703125e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.2911667823791504s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.023915529251098633s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0008816719055175781s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.0001277923583984375s
Believability | Calculation of trust value for Salzburgerland EN took 8.344650268554688e-06s
INFO | --- Analysis for salzburgerland-com-en took 2.9303674697875977s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.3392181396484375e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.252331018447876s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.020850658416748047s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.000942230224609375s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00012826919555664062s
Believability | Calculation of trust value for Salzburgerland IT took 6.9141387939453125e-06s
INFO | --- Analysis for salzburgerland-com-it took 2.8803932666778564s
Availability | SPARQL endpoint availability check for sameAs.org took 6.413459777832031e-05s
Availability | VoID file availability check for sameAs.org took 0.0003342628479003906s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.27648043632507324s
Reputation | Calculation of the PageRank for sameAs.org took 0.0211184024810791s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 3.409385681152344e-05s
Believability | Calculation of trust value for sameAs.org took 8.344650268554688e-06s
INFO | --- Analysis for sameas-org took 2.925856828689575s
Availability | SPARQL endpoint availability check for sandrart.net took 4.4345855712890625e-05s
Availability | VoID file availability check for sandrart.net took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.2702927589416504s
Reputation | Calculation of the PageRank for sandrart.net took 0.020853042602539062s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 8.058547973632812e-05s
Believability | Calculation of trust value for sandrart.net took 7.3909759521484375e-06s
INFO | --- Analysis for sandrart-net took 2.883124589920044s
Availability | SPARQL endpoint availability check for Taxons  took 4.124641418457031e-05s
Availability | VoID file availability check for Taxons  took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Taxons  took 0.27470993995666504s
Reputation | Calculation of the PageRank for Taxons  took 0.020769119262695312s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Taxons  took 7.2479248046875e-05s
Believability | Calculation of trust value for Taxons  took 8.344650268554688e-06s
INFO | --- Analysis for sandre took 2.921818494796753s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 4.1484832763671875e-05s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.2765614986419678s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.021152496337890625s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.504753112792969e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 1.1205673217773438e-05s
INFO | --- Analysis for sanskrit-english-lexicon took 2.8727223873138428s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.25849223136901855s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.020766019821166992s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 3.123283386230469e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 8.106231689453125e-06s
INFO | --- Analysis for santillana_guide_dataset took 2.802401304244995s
Availability | SPARQL endpoint availability check for SATAR test  took 4.1484832763671875e-05s
Availability | VoID file availability check for SATAR test  took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.2498152256011963s
Reputation | Calculation of the PageRank for SATAR test  took 0.0208740234375s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 3.3855438232421875e-05s
Believability | Calculation of trust value for SATAR test  took 1.6927719116210938e-05s
INFO | --- Analysis for SATAR_test took 2.8651719093322754s
Availability | SPARQL endpoint availability check for SCBG Data took 4.124641418457031e-05s
Availability | VoID file availability check for SCBG Data took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.27825021743774414s
Reputation | Calculation of the PageRank for SCBG Data took 0.020843505859375s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.344650268554688e-05s
Believability | Calculation of trust value for SCBG Data took 9.059906005859375e-06s
INFO | --- Analysis for SCBG-Data took 2.8735952377319336s
Availability | SPARQL endpoint availability check for schema.org took 4.1961669921875e-05s
Availability | VoID file availability check for schema.org took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for schema.org took 0.25243115425109863s
Reputation | Calculation of the PageRank for schema.org took 0.020838499069213867s
Interlinking | Calculation of Degree of Connection for schema.org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for schema.org took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.838539123535156e-05s
Believability | Calculation of trust value for schema.org took 1.2874603271484375e-05s
INFO | --- Analysis for schema-org took 2.8230209350585938s
Availability | SPARQL endpoint availability check for Schemantra took 4.291534423828125e-05s
Availability | VoID file availability check for Schemantra took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for Schemantra took 0.30196595191955566s
Reputation | Calculation of the PageRank for Schemantra took 0.02078080177307129s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Schemantra took 3.337860107421875e-05s
Believability | Calculation of trust value for Schemantra took 7.867813110351562e-06s
INFO | --- Analysis for Schemantra took 2.9717493057250977s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 4.291534423828125e-05s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.2710230350494385s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020989656448364258s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.9577484130859375e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 1.239776611328125e-05s
INFO | --- Analysis for schemapedia took 2.964996099472046s
Availability | SPARQL endpoint availability check for scholarlydata took 4.172325134277344e-05s
Availability | VoID file availability check for scholarlydata took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.24905109405517578s
Reputation | Calculation of the PageRank for scholarlydata took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for scholarlydata took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 3.2901763916015625e-05s
Believability | Calculation of trust value for scholarlydata took 9.298324584960938e-06s
INFO | --- Analysis for scholarlydata took 2.7955026626586914s
Availability | SPARQL endpoint availability check for Scholarometer took 4.00543212890625e-05s
Availability | VoID file availability check for Scholarometer took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.25017642974853516s
Reputation | Calculation of the PageRank for Scholarometer took 0.02094578742980957s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 9.059906005859375e-05s
Believability | Calculation of trust value for Scholarometer took 8.58306884765625e-06s
INFO | --- Analysis for scholarometer took 2.83890962600708s
Availability | SPARQL endpoint availability check for Science Commons took 4.2438507080078125e-05s
Availability | VoID file availability check for Science Commons took 0.0003330707550048828s
Completeness | Calculation of interlinking completeness for Science Commons took 0.25705552101135254s
Reputation | Calculation of the PageRank for Science Commons took 0.02196192741394043s
Interlinking | Calculation of Degree of Connection for Science Commons took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Science Commons took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Science Commons took 3.62396240234375e-05s
Believability | Calculation of trust value for Science Commons took 7.62939453125e-06s
INFO | --- Analysis for science_commons took 2.8429412841796875s
Availability | SPARQL endpoint availability check for ScienceWise took 4.267692565917969e-05s
Availability | VoID file availability check for ScienceWise took 0.00035953521728515625s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.2553894519805908s
Reputation | Calculation of the PageRank for ScienceWise took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for ScienceWise took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ScienceWise took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 3.24249267578125e-05s
Believability | Calculation of trust value for ScienceWise took 8.344650268554688e-06s
INFO | --- Analysis for sciencewise took 2.830843687057495s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 7.367134094238281e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.2482750415802002s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.022516250610351562s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 3.7670135498046875e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 8.58306884765625e-06s
INFO | --- Analysis for scoreboard took 2.7859046459198s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 7.343292236328125e-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.0002505779266357422s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.28975439071655273s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.021152257919311523s
Interlinking | Calculation of Degree of Connection for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.100799560546875e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 7.867813110351562e-06s
INFO | --- Analysis for SDDEC took 2.7807865142822266s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 8.511543273925781e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.2617506980895996s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.02115488052368164s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 3.4332275390625e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 7.867813110351562e-06s
INFO | --- Analysis for SDG took 2.797516107559204s
Availability | SPARQL endpoint availability check for sears.com took 4.291534423828125e-05s
Availability | VoID file availability check for sears.com took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for sears.com took 0.29153990745544434s
Reputation | Calculation of the PageRank for sears.com took 0.02090930938720703s
Interlinking | Calculation of Degree of Connection for sears.com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.914138793945312e-05s
Believability | Calculation of trust value for sears.com took 7.152557373046875e-06s
INFO | --- Analysis for sears took 2.8756861686706543s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 4.291534423828125e-05s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0003056526184082031s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.2616276741027832s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.021033525466918945s
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.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.274482727050781e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.775161743164062e-06s
INFO | --- Analysis for sec-rdfabout took 2.8853585720062256s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 5.602836608886719e-05s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.23892664909362793s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.02095627784729004s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.273124694824219e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for secold took 2.731588363647461s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.291534423828125e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.28237175941467285s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 3.457069396972656e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 7.3909759521484375e-06s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 2.8386268615722656s
Availability | SPARQL endpoint availability check for semanlink took 4.124641418457031e-05s
Availability | VoID file availability check for semanlink took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for semanlink took 0.26317930221557617s
Reputation | Calculation of the PageRank for semanlink took 0.022712230682373047s
Interlinking | Calculation of Degree of Connection for semanlink took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.0001544952392578125s
Believability | Calculation of trust value for semanlink took 8.821487426757812e-06s
INFO | --- Analysis for semanlink took 2.885157823562622s
Availability | SPARQL endpoint availability check for Semantic Library took 4.267692565917969e-05s
Availability | VoID file availability check for Semantic Library took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.2769792079925537s
Reputation | Calculation of the PageRank for Semantic Library took 0.021007776260375977s
Interlinking | Calculation of Degree of Connection for Semantic Library took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic Library took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 3.266334533691406e-05s
Believability | Calculation of trust value for Semantic Library took 8.58306884765625e-06s
INFO | --- Analysis for semantic-library took 2.8842835426330566s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 4.2438507080078125e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.25240325927734375s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 3.2901763916015625e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 8.106231689453125e-06s
INFO | --- Analysis for semantic-profiling-network took 2.8720333576202393s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 4.291534423828125e-05s
Availability | VoID file availability check for Semantic Universe Data took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.2736046314239502s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.020972251892089844s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.218650817871094e-05s
Believability | Calculation of trust value for Semantic Universe Data took 8.821487426757812e-06s
INFO | --- Analysis for semantic-universe took 2.9333982467651367s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 4.315376281738281e-05s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.2728309631347656s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020772933959960938s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00014448165893554688s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 8.58306884765625e-06s
INFO | --- Analysis for semantic-web-dog-food took 2.899851083755493s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 4.0531158447265625e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.2531266212463379s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.982948303222656e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 7.867813110351562e-06s
INFO | --- Analysis for semantic-web-grundlagen took 2.812725782394409s
Availability | SPARQL endpoint availability check for semantic-web-journal took 4.506111145019531e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.2644321918487549s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.02134561538696289s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 3.5762786865234375e-05s
Believability | Calculation of trust value for semantic-web-journal took 8.58306884765625e-06s
INFO | --- Analysis for semantic-web-journal took 2.834773540496826s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 7.2479248046875e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.25494980812072754s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020766735076904297s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.749961853027344e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 7.3909759521484375e-06s
INFO | --- Analysis for semantic-xbrl took 2.9597041606903076s
Availability | SPARQL endpoint availability check for Semantic Bible took 4.220008850097656e-05s
Availability | VoID file availability check for Semantic Bible took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.26242613792419434s
Reputation | Calculation of the PageRank for Semantic Bible took 0.02069544792175293s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 3.337860107421875e-05s
Believability | Calculation of trust value for Semantic Bible took 8.58306884765625e-06s
INFO | --- Analysis for semantic_bible took 2.8565523624420166s
Availability | SPARQL endpoint availability check for SemanticQuran took 4.100799560546875e-05s
Availability | VoID file availability check for SemanticQuran took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.27400827407836914s
Reputation | Calculation of the PageRank for SemanticQuran took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 9.322166442871094e-05s
Believability | Calculation of trust value for SemanticQuran took 1.3589859008789062e-05s
INFO | --- Analysis for semanticquran took 2.90533709526062s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.291534423828125e-05s
Availability | VoID file availability check for SemanticTweet took 0.00021910667419433594s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.26470446586608887s
Reputation | Calculation of the PageRank for SemanticTweet took 0.021059036254882812s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.841255187988281e-05s
Believability | Calculation of trust value for SemanticTweet took 9.059906005859375e-06s
INFO | --- Analysis for semantictweet took 2.9209089279174805s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.1961669921875e-05s
Availability | VoID file availability check for semanticweb.org took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.2506139278411865s
Reputation | Calculation of the PageRank for semanticweb.org took 0.021320104598999023s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 8.130073547363281e-05s
Believability | Calculation of trust value for semanticweb.org took 8.344650268554688e-06s
INFO | --- Analysis for semanticweb-org took 2.862837553024292s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 8.463859558105469e-05s
Availability | VoID file availability check for Semantic CrunchBase took 0.00022220611572265625s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.2621915340423584s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020770788192749023s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.985664367675781e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 8.821487426757812e-06s
INFO | --- Analysis for semsol-crunchbase took 2.89741849899292s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 0.00010323524475097656s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.00031757354736328125s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.2543764114379883s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.021183252334594727s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0008437633514404297s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 4.5299530029296875e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 8.344650268554688e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.7752394676208496s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 5.364418029785156e-05s
Availability | VoID file availability check for SentimentWortschatz took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.2579915523529053s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.02095508575439453s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.649162292480469e-05s
Believability | Calculation of trust value for SentimentWortschatz took 8.106231689453125e-06s
INFO | --- Analysis for sentiws took 2.7960288524627686s
Availability | SPARQL endpoint availability check for seoul-bike-data took 4.2438507080078125e-05s
Availability | VoID file availability check for seoul-bike-data took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.27956080436706543s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.02117443084716797s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0008554458618164062s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 3.457069396972656e-05s
Believability | Calculation of trust value for seoul-bike-data took 8.58306884765625e-06s
INFO | --- Analysis for seoul-bike-data took 2.841055154800415s
Availability | SPARQL endpoint availability check for Serendipity took 4.1961669921875e-05s
Availability | VoID file availability check for Serendipity took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Serendipity took 0.27057433128356934s
Reputation | Calculation of the PageRank for Serendipity took 0.02219367027282715s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Serendipity took 8.058547973632812e-05s
Believability | Calculation of trust value for Serendipity took 9.298324584960938e-06s
INFO | --- Analysis for serendipity took 2.8531296253204346s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 4.363059997558594e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.2509782314300537s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.02108025550842285s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.4332275390625e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 8.106231689453125e-06s
INFO | --- Analysis for Sherry_Wine took 2.9304392337799072s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.363059997558594e-05s
Availability | VoID file availability check for Sherry Wine took 0.0003304481506347656s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.2499701976776123s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020943164825439453s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0008118152618408203s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.409385681152344e-05s
Believability | Calculation of trust value for Sherry Wine took 7.62939453125e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.8270316123962402s
Availability | SPARQL endpoint availability check for Shoah victims? names took 4.3392181396484375e-05s
Availability | VoID file availability check for Shoah victims? names took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.254133939743042s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.020856857299804688s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.57763671875e-05s
Believability | Calculation of trust value for Shoah victims? names took 1.2874603271484375e-05s
INFO | --- Analysis for shoah-victims-names took 2.8488802909851074s
Availability | SPARQL endpoint availability check for Person took 4.315376281738281e-05s
Availability | VoID file availability check for Person took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Person took 0.2552475929260254s
Reputation | Calculation of the PageRank for Person took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for Person took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Person took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Person took 3.62396240234375e-05s
Believability | Calculation of trust value for Person took 7.867813110351562e-06s
INFO | --- Analysis for Shripriya_Dubey took 2.891868829727173s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 5.9604644775390625e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.28000831604003906s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.021109342575073242s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 3.361701965332031e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 8.58306884765625e-06s
INFO | --- Analysis for Shutterstock took 2.858494997024536s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.267692565917969e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.2620410919189453s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.020949840545654297s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 3.4809112548828125e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 7.867813110351562e-06s
INFO | --- Analysis for simile_data_collection took 2.829272985458374s
Availability | SPARQL endpoint availability check for SIMPLE took 4.315376281738281e-05s
Availability | VoID file availability check for SIMPLE took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.2766256332397461s
Reputation | Calculation of the PageRank for SIMPLE took 0.020938634872436523s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.410743713378906e-05s
Believability | Calculation of trust value for SIMPLE took 7.867813110351562e-06s
INFO | --- Analysis for simple took 2.888400077819824s
Availability | SPARQL endpoint availability check for SITC-V4 took 4.267692565917969e-05s
Availability | VoID file availability check for SITC-V4 took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.27100467681884766s
Reputation | Calculation of the PageRank for SITC-V4 took 0.020945310592651367s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.029273986816406e-05s
Believability | Calculation of trust value for SITC-V4 took 7.867813110351562e-06s
INFO | --- Analysis for sitc-v4 took 2.909284830093384s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.458427429199219e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.25485777854919434s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020981788635253906s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.863739013671875e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 7.867813110351562e-06s
INFO | --- Analysis for sli_galnet_rdf took 2.9214518070220947s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.315376281738281e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.23969197273254395s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.02084803581237793s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.5762786865234375e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 8.106231689453125e-06s
INFO | --- Analysis for slideshare2rdf took 2.8002161979675293s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 4.2438507080078125e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.2761199474334717s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.020953893661499023s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 3.4332275390625e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 1.7881393432617188e-05s
INFO | --- Analysis for slidewiki-rdf-sparql took 2.896822452545166s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.4362447261810303s
Availability | VoID file availability check for Linked Stage Graph took 0.00028705596923828125s
Extra | Recovery of all triples for Linked Stage Graph took 2.106212854385376s
Performance | Total latancy measurement for Linked Stage Graph took 0.9764811992645264s
Amount of data | Number of triples check for Linked Stage Graph took 0.196366548538208s
Interoperability | New terms check for Linked Stage Graph took 1.5657565593719482s
Versatility | Languages check for Linked Stage Graph took 0.6814486980438232s
Interpretability | Number of blank nodes check for Linked Stage Graph took 0.217576265335083s
Security | Check HTTPS for Linked Stage Graph took 0.13263630867004395s
Interpretability | RDF structures check for Linked Stage Graph took 0.24644875526428223s
Versatility | Serialization formats check for Linked Stage Graph took 0.20995497703552246s
Availability | RDF dump link check for Linked Stage Graph took 0.20171403884887695s
License | MR license check for Linked Stage Graph took 0.199904203414917s
License | HR license check for Linked Stage Graph took 1.809709072113037s
Amount of data | Number of property check for Linked Stage Graph took 0.1852130889892578s
Understandability | Number of label check for Linked Stage Graph took 0.22177696228027344s
Understandability | URI regex check for Linked Stage Graph took 0.409942626953125s
Understandability | Vocabs check for Linked Stage Graph took 0.24268293380737305s
Verifiability | Authors check for Linked Stage Graph took 0.21371746063232422s
Verifiability | Publishers check for Linked Stage Graph took 0.21755409240722656s
Performance | Throughput check for Linked Stage Graph took 10.733619451522827s
Amount of data | Check the number of entities for Linked Stage Graph took 7.319450378417969e-05s
Verifiability | Contribs. check for Linked Stage Graph took 0.20673489570617676s
Interlinking | sameAs chians check for Linked Stage Graph took 0.20427560806274414s
Interlinking | skos check for Linked Stage Graph took 0.21077728271484375s
Interlinking | skos check for Linked Stage Graph took 0.22205591201782227s
Timeliness | dataset update frequency check for Linked Stage Graph took 0.24606943130493164s
Currency | Creation date check for Linked Stage Graph took 0.41159486770629883s
Currency | Modification date check for Linked Stage Graph took 0.4036860466003418s
Rep.Conc. | URIs length for Linked Stage Graph took 1.4513072967529297s
Interoperability | New vocabularies check for Linked Stage Graph took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Linked Stage Graph took 0.20237946510314941s
Accuracy | Check Functional Property for Linked Stage Graph took 0.19187045097351074s
Accuracy | Check Inverse Functional Property for Linked Stage Graph took 0.1898798942565918s
Accuracy | Check Empty annotation labels for Linked Stage Graph took 0.8334121704101562s
Accuracy | Check White space in annotation for Linked Stage Graph took 0.023900747299194336s
Accuracy | Check Datatype consistency for Linked Stage Graph took 0.0279541015625s
Consistency | Disjoint class check for Linked Stage Graph took 0.20922398567199707s
Consistency | Check Misplaced properties for Linked Stage Graph took 0.9341087341308594s
Consistency | Misplaced classes for Linked Stage Graph took 0.5545437335968018s
Consistency | Check Ontology hijacking for Linked Stage Graph took 2.0591230392456055s
Consistency | Check Invalid usage of undefined classes for Linked Stage Graph took 1.3134307861328125s
Consistency | Check Invalid usage of undefined properties for Linked Stage Graph took 1.8118741512298584s
Conciseness | Check Extensional conciseness for Linked Stage Graph took 0.02754378318786621s
Conciseness | Check Intensional conciseness for Linked Stage Graph took 0.545468807220459s
Security | Sign check for Linked Stage Graph took 0.2116537094116211s
Availability | Check URIs Dereferenciability for Linked Stage Graph took 1182.4739563465118s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 1.281017780303955s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.02174997329711914s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 6.628036499023438e-05s
Interoperability | Check the re-using of existing vocabs for Linked Stage Graph took 2.6226043701171875e-06s
Believability | Calculation of trust value for Linked Stage Graph took 1.2874603271484375e-05s
INFO | --- Analysis for slod took 1253.2640821933746s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 4.506111145019531e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.25449538230895996s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.021351099014282227s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 3.5762786865234375e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 7.3909759521484375e-06s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 2.9039833545684814s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 4.3392181396484375e-05s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.7059164047241211s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.02207779884338379s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00010418891906738281s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for Smart_POI_dataset took 3.3905272483825684s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 4.1961669921875e-05s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0003452301025390625s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.2693905830383301s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.021045684814453125s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.000911712646484375s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 4.506111145019531e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 8.821487426757812e-06s
INFO | --- Analysis for smartlink took 2.812157154083252s
Availability | SPARQL endpoint availability check for SNIK took 4.315376281738281e-05s
Availability | VoID file availability check for SNIK took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for SNIK took 0.25615930557250977s
Reputation | Calculation of the PageRank for SNIK took 0.02080845832824707s
Interlinking | Calculation of Degree of Connection for SNIK took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for SNIK took 7.343292236328125e-05s
Believability | Calculation of trust value for SNIK took 7.3909759521484375e-06s
INFO | --- Analysis for snik took 2.808957576751709s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 5.7220458984375e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.2476940155029297s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 3.24249267578125e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 7.867813110351562e-06s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 2.905972719192505s
Availability | SPARQL endpoint availability check for SocialLink took 4.220008850097656e-05s
Availability | VoID file availability check for SocialLink took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for SocialLink took 0.2578263282775879s
Reputation | Calculation of the PageRank for SocialLink took 0.02085709571838379s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.557868957519531e-05s
Believability | Calculation of trust value for SocialLink took 7.867813110351562e-06s
INFO | --- Analysis for SocialLink took 2.8912436962127686s
Availability | SPARQL endpoint availability check for SocialLink took 4.220008850097656e-05s
Availability | VoID file availability check for SocialLink took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for SocialLink took 0.25415730476379395s
Reputation | Calculation of the PageRank for SocialLink took 0.020771026611328125s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for SocialLink took 3.457069396972656e-05s
Believability | Calculation of trust value for SocialLink took 7.867813110351562e-06s
INFO | --- Analysis for sociallink took 2.882389545440674s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 4.220008850097656e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.2621495723724365s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.021323204040527344s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.6716461181640625e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 6.9141387939453125e-06s
INFO | --- Analysis for SocialRoles took 2.8950483798980713s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.25390028953552246s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020800352096557617s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 0.00011849403381347656s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for socialsemweb-thesaurus took 3.2295572757720947s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.225440979003906e-05s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2573235034942627s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.021145105361938477s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.910064697265625e-05s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.5367431640625e-06s
INFO | --- Analysis for Soil_maps took 2.8221442699432373s
Availability | SPARQL endpoint availability check for terrorrist ontology took 4.172325134277344e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.23958206176757812s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.021330595016479492s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.457069396972656e-05s
Believability | Calculation of trust value for terrorrist ontology took 8.106231689453125e-06s
INFO | --- Analysis for somya_omer took 2.8475310802459717s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.172325134277344e-05s
Availability | VoID file availability check for Sonclubcx took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.2538285255432129s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020804882049560547s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.52587890625e-05s
Believability | Calculation of trust value for Sonclubcx took 8.58306884765625e-06s
INFO | --- Analysis for sonclubcx took 2.8521339893341064s
Availability | SPARQL endpoint availability check for SORS took 4.3392181396484375e-05s
Availability | VoID file availability check for SORS took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for SORS took 0.25572681427001953s
Reputation | Calculation of the PageRank for SORS took 0.021004438400268555s
Interlinking | Calculation of Degree of Connection for SORS took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for SORS took 6.008148193359375e-05s
Believability | Calculation of trust value for SORS took 1.1444091796875e-05s
INFO | --- Analysis for sors took 2.8878393173217773s
Availability | SPARQL endpoint availability check for Soudy České republiky took 4.267692565917969e-05s
Availability | VoID file availability check for Soudy České republiky took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.2623624801635742s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.021099567413330078s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 3.552436828613281e-05s
Believability | Calculation of trust value for Soudy České republiky took 9.059906005859375e-06s
INFO | --- Analysis for soudy--esk--republiky took 2.8867878913879395s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.267692565917969e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.2709183692932129s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.894371032714844e-05s
Believability | Calculation of trust value for southampton-ac-uk took 1.4066696166992188e-05s
INFO | --- Analysis for southampton-ac-uk took 2.8945391178131104s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 4.2438507080078125e-05s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.2811298370361328s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.02085566520690918s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.4332275390625e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 7.3909759521484375e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 2.805433988571167s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 5.173683166503906e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.24260663986206055s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.021074771881103516s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.822845458984375e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 8.821487426757812e-06s
INFO | --- Analysis for southampton-ecs-eprints took 2.78960919380188s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 4.172325134277344e-05s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0002930164337158203s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.2467358112335205s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.021019697189331055s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.3855438232421875e-05s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 8.58306884765625e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 2.8294472694396973s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 4.291534423828125e-05s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.2597200870513916s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.021340370178222656s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.9591064453125e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 9.775161743164062e-06s
INFO | --- Analysis for sparql-endpoint-status took 2.7754383087158203s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 5.9604644775390625e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.000301361083984375s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.25554466247558594s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.020885229110717773s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 3.170967102050781e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 6.4373016357421875e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 2.8724923133850098s
Availability | SPARQL endpoint availability check for SPQR took 4.57763671875e-05s
Availability | VoID file availability check for SPQR took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for SPQR took 0.2618446350097656s
Reputation | Calculation of the PageRank for SPQR took 0.0209658145904541s
Interlinking | Calculation of Degree of Connection for SPQR took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SPQR took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for SPQR took 3.504753112792969e-05s
Believability | Calculation of trust value for SPQR took 8.58306884765625e-06s
INFO | --- Analysis for spqr took 2.8596601486206055s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.220008850097656e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.24477481842041016s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.02097630500793457s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.96453857421875e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 7.3909759521484375e-06s
INFO | --- Analysis for springernaturescigraph took 2.8119046688079834s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.553794860839844e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.26215267181396484s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.021233081817626953s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.552436828613281e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 6.67572021484375e-06s
INFO | --- Analysis for srcmf took 2.7921226024627686s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 4.267692565917969e-05s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.2650892734527588s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.020879030227661133s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 4.863739013671875e-05s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 8.344650268554688e-06s
INFO | --- Analysis for ssf took 2.8818254470825195s
Availability | SPARQL endpoint availability check for SSF took 5.0067901611328125e-05s
Availability | VoID file availability check for SSF took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for SSF took 0.24659061431884766s
Reputation | Calculation of the PageRank for SSF took 0.021161556243896484s
Interlinking | Calculation of Degree of Connection for SSF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SSF took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for SSF took 3.24249267578125e-05s
Believability | Calculation of trust value for SSF took 8.821487426757812e-06s
INFO | --- Analysis for ssf-lexicon took 2.695615768432617s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.76837158203125e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.26645827293395996s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.02075982093811035s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.886222839355469e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 6.9141387939453125e-06s
INFO | --- Analysis for st-andrews-resource-lists took 2.7345540523529053s
Availability | SPARQL endpoint availability check for STAC took 4.363059997558594e-05s
Availability | VoID file availability check for STAC took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for STAC took 0.27427196502685547s
Reputation | Calculation of the PageRank for STAC took 0.021245479583740234s
Interlinking | Calculation of Degree of Connection for STAC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for STAC took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for STAC took 3.5762786865234375e-05s
Believability | Calculation of trust value for STAC took 9.298324584960938e-06s
INFO | --- Analysis for stac took 2.843982219696045s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 4.172325134277344e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.00031280517578125s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.2633850574493408s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.021086454391479492s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 3.552436828613281e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 8.106231689453125e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 2.8411800861358643s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.363059997558594e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.253002405166626s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020906925201416016s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.719329833984375e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 8.344650268554688e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 2.839698314666748s
Availability | SPARQL endpoint availability check for Stammbuch took 4.291534423828125e-05s
Availability | VoID file availability check for Stammbuch took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.24037480354309082s
Reputation | Calculation of the PageRank for Stammbuch took 0.021004676818847656s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 3.337860107421875e-05s
Believability | Calculation of trust value for Stammbuch took 1.3828277587890625e-05s
INFO | --- Analysis for Stammbuch took 2.872438669204712s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 4.172325134277344e-05s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.2599174976348877s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.021116971969604492s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010967254638671875s
Believability | Calculation of trust value for statistics.data.gov.uk took 9.5367431640625e-06s
INFO | --- Analysis for statistics-data-gov-uk took 2.8336055278778076s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 7.200241088867188e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.2620546817779541s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.021461963653564453s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 3.528594970703125e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 8.58306884765625e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.855144739151001s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.259474515914917s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.0208895206451416s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00010967254638671875s
Believability | Calculation of trust value for statusnet-1w6-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-1w6-org took 2.816190004348755s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0003719329833984375s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.2813839912414551s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.021329402923583984s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 0.0001785755157470703s
Believability | Calculation of trust value for statusnet-20100-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-20100-org took 2.957571268081665s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.2788827419281006s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.02102804183959961s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 7.963180541992188e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.928114891052246s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.57763671875e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.2553684711456299s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.020853757858276367s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 8.726119995117188e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.8310720920562744s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.2791252136230469s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.989738464355469e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-belfalas-org took 2.9185736179351807s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.2607433795928955s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.021416425704956055s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0009543895721435547s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00013375282287597656s
Believability | Calculation of trust value for statusnet-bka-li took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-bka-li took 2.860211133956909s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.24647259712219238s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.021260499954223633s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 4.4345855712890625e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-bonifaz-ec took 2.895153284072876s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 5.745887756347656e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.2618536949157715s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.021283864974975586s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 5.14984130859375e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-ced117-net took 2.8534207344055176s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.24525976181030273s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.459785461425781e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.8539745807647705s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0003707408905029297s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.24760913848876953s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.02086043357849121s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011658668518066406s
Believability | Calculation of trust value for statusnet-chromic-org took 5.4836273193359375e-06s
INFO | --- Analysis for statusnet-chromic-org took 2.762432098388672s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 9.608268737792969e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.25423645973205566s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020817995071411133s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 8.606910705566406e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 2.8598806858062744s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.25650572776794434s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.021204710006713867s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 6.103515625e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.8696627616882324s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.00038313865661621094s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.26036596298217773s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.020842313766479492s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 7.581710815429688e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 2.8886165618896484s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.252108097076416s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.021045684814453125s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00011610984802246094s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 7.62939453125e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.814814567565918s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.26232218742370605s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.020945310592651367s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.794929504394531e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.8715298175811768s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.2601754665374756s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.021181583404541016s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.793571472167969e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-doomicile-de took 2.9070003032684326s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.00030875205993652344s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.26621413230895996s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.000804901123046875s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 0.00018739700317382812s
Believability | Calculation of trust value for statusnet-dtdns-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-dtdns-net took 2.856793165206909s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0003612041473388672s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.24971270561218262s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.021336078643798828s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 4.553794860839844e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-equestriarp-net took 2.8478519916534424s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.25694799423217773s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.021371126174926758s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 8.296966552734375e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-exdc-net took 2.9159319400787354s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.2393636703491211s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.021106719970703125s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.965896606445312e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-fcac-com took 2.86708664894104s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.25897932052612305s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.021754741668701172s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0010335445404052734s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 7.390975952148438e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 2.843994140625s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.2573356628417969s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.02112436294555664s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00018668174743652344s
Believability | Calculation of trust value for statusnet-fragdev-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-fragdev-com took 2.922546863555908s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.25028109550476074s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.02136993408203125s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 8.0108642578125e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.8671658039093018s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.27992939949035645s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.021143436431884766s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00011801719665527344s
Believability | Calculation of trust value for statusnet-gegeweb-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.819263219833374s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.26049184799194336s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.020856142044067383s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 7.653236389160156e-05s
Believability | Calculation of trust value for statusnet-glou-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-glou-org took 2.7837717533111572s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0003662109375s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.27967095375061035s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.022240400314331055s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00013327598571777344s
Believability | Calculation of trust value for statusnet-gomertronic-com took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.9098830223083496s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.2540280818939209s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.021084070205688477s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00011205673217773438s
Believability | Calculation of trust value for statusnet-hackerposse-com took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.83843731880188s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.00029659271240234375s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.2565724849700928s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.021332263946533203s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0011262893676757812s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 7.152557373046875e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-hii-co-il took 2.9138996601104736s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.26705074310302734s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.021097421646118164s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.34600830078125e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 2.881988763809204s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.2653632164001465s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.02109813690185547s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.508827209472656e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.8850016593933105s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2543184757232666s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.021021366119384766s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.57763671875e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.8976192474365234s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.24359130859375s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.020879507064819336s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 6.461143493652344e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 1.5735626220703125e-05s
INFO | --- Analysis for statusnet-johndrinkwater-name took 2.815833330154419s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 8.20159912109375e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0003476142883300781s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.29125046730041504s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011682510375976562s
Believability | Calculation of trust value for statusnet-jonkman-ca took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-jonkman-ca took 2.9578680992126465s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.2767753601074219s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.021258115768432617s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 0.00010514259338378906s
Believability | Calculation of trust value for statusnet-kaimi-cc took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-kaimi-cc took 2.7971813678741455s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0002989768981933594s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.25557923316955566s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.021253108978271484s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 5.817413330078125e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.8244240283966064s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 5.698204040527344e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.2545762062072754s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.02079939842224121s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 4.553794860839844e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 2.867231607437134s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.26812314987182617s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.021936655044555664s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.653236389160156e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.920954465866089s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0008931159973144531s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.25438690185546875s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.02074146270751953s
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.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 5.793571472167969e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.8634636402130127s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.2599802017211914s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.02084517478942871s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0008673667907714844s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 7.367134094238281e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.8313963413238525s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.25638771057128906s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.021332740783691406s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 0.00010085105895996094s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.8989498615264893s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.26239871978759766s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.021088361740112305s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00012731552124023438s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.8738882541656494s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.2683908939361572s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.020980119705200195s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.7697296142578125e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-ludost-net took 2.8656773567199707s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.2570493221282959s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.021079540252685547s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 0.00011014938354492188s
Believability | Calculation of trust value for statusnet-lydiastench-com took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.9389753341674805s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.25484776496887207s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.020937681198120117s
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.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.698204040527344e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-m-kuttner-com took 2.854738473892212s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.744529724121094e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.25365281105041504s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.021366596221923828s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00016307830810546875s
Believability | Calculation of trust value for statusnet-macno-org took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-macno-org took 3.015000820159912s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 7.271766662597656e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.243333101272583s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.020754575729370117s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.890296936035156e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.836357593536377s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.57763671875e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.2792172431945801s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 0.00010347366333007812s
Believability | Calculation of trust value for statusnet-maymay-net took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-maymay-net took 2.8360297679901123s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.2792470455169678s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.021257638931274414s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.0001780986785888672s
Believability | Calculation of trust value for statusnet-morphtown-de took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.8850057125091553s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.23766350746154785s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.02088022232055664s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 0.0001163482666015625s
Believability | Calculation of trust value for statusnet-mrblog-nl took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.792088508605957s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.00031948089599609375s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.26361083984375s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.02272176742553711s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 6.818771362304688e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.881232500076294s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.255476713180542s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.02134537696838379s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 6.175041198730469e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-my-status-tk took 2.8222103118896484s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0003230571746826172s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.2678372859954834s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.02079010009765625s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00010943412780761719s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.8505401611328125s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.294849157333374s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.650520324707031e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.8946754932403564s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 7.43865966796875e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.2529776096343994s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.020722627639770508s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.4849853515625e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.8237557411193848s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 8.0108642578125e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0004138946533203125s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.2686011791229248s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.0208742618560791s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.654594421386719e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.8612046241760254s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.23776459693908691s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.020951271057128906s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0008242130279541016s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 6.103515625e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-panda-id-au took 2.836000919342041s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.3219602108001709s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.020803213119506836s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.799003601074219e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-piana-eu took 3.097630262374878s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.2618217468261719s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.020772218704223633s
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.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.939338684082031e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.852630615234375s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.2734208106994629s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.021047592163085938s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.0002734661102294922s
Believability | Calculation of trust value for statusnet-postblue-info took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.91459059715271s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 6.437301635742188e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.2794778347015381s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.02104043960571289s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 9.250640869140625e-05s
Believability | Calculation of trust value for statusnet-progval-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-progval-net took 2.8473875522613525s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 7.510185241699219e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.26433825492858887s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.021157503128051758s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00012087821960449219s
Believability | Calculation of trust value for statusnet-qdnx-org took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-qdnx-org took 2.9201223850250244s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.26442861557006836s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.628036499023438e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-qth-fr took 2.8936755657196045s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.2745027542114258s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020925283432006836s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.0002281665802001953s
Believability | Calculation of trust value for statusnet-quitter-se took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-quitter-se took 2.8067657947540283s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.26734447479248047s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020885705947875977s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010704994201660156s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.927180528640747s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.2555258274078369s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.02111506462097168s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 6.508827209472656e-05s
Believability | Calculation of trust value for statusnet-recit-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-recit-org took 2.881383180618286s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.2708773612976074s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.02132415771484375s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00016689300537109375s
Believability | Calculation of trust value for statusnet-russwurm-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-russwurm-org took 2.9362261295318604s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.26555848121643066s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020931720733642578s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.749961853027344e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-samnoble-org took 2.8693621158599854s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.00030732154846191406s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.26656413078308105s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.02083587646484375s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.869171142578125e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.8942270278930664s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.2880549430847168s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.020896196365356445s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 0.00012254714965820312s
Believability | Calculation of trust value for statusnet-scoffoni-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.8673386573791504s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.25656819343566895s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.02085733413696289s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.67572021484375e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.8993077278137207s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.26493382453918457s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020867586135864258s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.796287536621094e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 2.852933645248413s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0003235340118408203s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.27583813667297363s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.020936965942382812s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.0002200603485107422s
Believability | Calculation of trust value for statusnet-skilledtests-com took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-skilledtests-com took 2.873621702194214s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.23810482025146484s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.020830154418945312s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010776519775390625s
Believability | Calculation of trust value for statusnet-somsants-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.811836004257202s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.25508975982666016s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.020651817321777344s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00014662742614746094s
Believability | Calculation of trust value for statusnet-soucy-cc took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-soucy-cc took 2.8459713459014893s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.26561903953552246s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.020802021026611328s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.341934204101562e-05s
Believability | Calculation of trust value for statusnet-spip-org took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-spip-org took 2.9918079376220703s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 5.626678466796875e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.2540163993835449s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020954608917236328s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.723403930664062e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-spraci-org took 2.8008806705474854s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.28016161918640137s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.020758867263793945s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00011396408081054688s
Believability | Calculation of trust value for statusnet-ssweeny-net took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 2.802476644515991s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.26923060417175293s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020766735076904297s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00022935867309570312s
Believability | Calculation of trust value for statusnet-status-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-status-net took 2.8485267162323s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0003211498260498047s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2594306468963623s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.020761728286743164s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.745887756347656e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.7794559001922607s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 5.3882598876953125e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.25008559226989746s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.021005868911743164s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.679794311523438e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.8057303428649902s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.24928712844848633s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.020906686782836914s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0008563995361328125s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00014019012451171875s
Believability | Calculation of trust value for statusnet-thelovebug-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.8315327167510986s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0003905296325683594s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.24225783348083496s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.02125072479248047s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0022296905517578125s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 0.00010228157043457031s
Believability | Calculation of trust value for statusnet-thornton2-com took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-thornton2-com took 2.849174737930298s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.26574063301086426s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.021233797073364258s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00011539459228515625s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.9180667400360107s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.2635350227355957s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.02100968360900879s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 4.124641418457031e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-tl1n-com took 2.8267316818237305s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 5.459785461425781e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2745945453643799s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.021009206771850586s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.818771362304688e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.909395694732666s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.2587876319885254s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020775318145751953s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 4.1484832763671875e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.875291585922241s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.220008850097656e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.00041675567626953125s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.2590663433074951s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020914554595947266s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 3.647804260253906e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for steak took 2.9034476280212402s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 8.821487426757812e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0003132820129394531s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.26142454147338867s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.021483182907104492s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0012860298156738281s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 7.510185241699219e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 8.106231689453125e-06s
INFO | --- Analysis for stitch-rameau took 2.907982587814331s
Availability | SPARQL endpoint availability check for Stone Tech Square took 4.1484832763671875e-05s
Availability | VoID file availability check for Stone Tech Square took 0.00032067298889160156s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.25951457023620605s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.02080559730529785s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.430511474609375e-05s
Believability | Calculation of trust value for Stone Tech Square took 8.821487426757812e-06s
INFO | --- Analysis for stone-tech-square-data took 2.8615000247955322s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 4.3392181396484375e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.2951357364654541s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.020846843719482422s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 3.147125244140625e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 8.58306884765625e-06s
INFO | --- Analysis for strukturovan--popisy-z-fda took 2.8418335914611816s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 6.103515625e-05s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.2479391098022461s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.02118062973022461s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00011610984802246094s
Believability | Calculation of trust value for STW Thesaurus for Economics took 8.344650268554688e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 2.8603603839874268s
Availability | SPARQL endpoint availability check for SudershanTech took 4.267692565917969e-05s
Availability | VoID file availability check for SudershanTech took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.2539999485015869s
Reputation | Calculation of the PageRank for SudershanTech took 0.02095174789428711s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.5762786865234375e-05s
Believability | Calculation of trust value for SudershanTech took 7.152557373046875e-06s
INFO | --- Analysis for SudershanTech took 2.9109883308410645s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 4.7206878662109375e-05s
Availability | VoID file availability check for Sudoc bibliographic data took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.2494792938232422s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.02108907699584961s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.982948303222656e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 8.821487426757812e-06s
INFO | --- Analysis for sudocfr took 2.875697135925293s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 4.267692565917969e-05s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.2805049419403076s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.02122950553894043s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 7.796287536621094e-05s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 1.4066696166992188e-05s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 2.9245760440826416s
Availability | SPARQL endpoint availability check for Surge Radio took 6.771087646484375e-05s
Availability | VoID file availability check for Surge Radio took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.2638282775878906s
Reputation | Calculation of the PageRank for Surge Radio took 0.021100759506225586s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 9.655952453613281e-05s
Believability | Calculation of trust value for Surge Radio took 8.344650268554688e-06s
INFO | --- Analysis for surge-radio took 2.927307605743408s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 4.3392181396484375e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.27724719047546387s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.021070241928100586s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.886222839355469e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 1.2159347534179688e-05s
INFO | --- Analysis for SWAT took 2.860445261001587s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 5.0067901611328125e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.0003399848937988281s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.2749927043914795s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.02170085906982422s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 7.843971252441406e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 8.106231689453125e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 2.989725112915039s
Availability | SPARQL endpoint availability check for SweFN-RDF took 4.410743713378906e-05s
Availability | VoID file availability check for SweFN-RDF took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.26274847984313965s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.021164417266845703s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.933906555175781e-05s
Believability | Calculation of trust value for SweFN-RDF took 9.059906005859375e-06s
INFO | --- Analysis for swefn-rdf took 2.8254363536834717s
Availability | SPARQL endpoint availability check for SwetoDblp took 7.200241088867188e-05s
Availability | VoID file availability check for SwetoDblp took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.25155067443847656s
Reputation | Calculation of the PageRank for SwetoDblp took 0.021108150482177734s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.981590270996094e-05s
Believability | Calculation of trust value for SwetoDblp took 8.106231689453125e-06s
INFO | --- Analysis for sweto-dblp took 2.8638789653778076s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 4.220008850097656e-05s
Availability | VoID file availability check for Swift Vocabulary took 0.0007159709930419922s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.26175522804260254s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.02091217041015625s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 7.128715515136719e-05s
Believability | Calculation of trust value for Swift Vocabulary took 8.58306884765625e-06s
INFO | --- Analysis for Swift took 2.890888214111328s
Availability | SPARQL endpoint availability check for SymbolicData took 7.319450378417969e-05s
Availability | VoID file availability check for SymbolicData took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.26652097702026367s
Reputation | Calculation of the PageRank for SymbolicData took 0.020839452743530273s
Interlinking | Calculation of Degree of Connection for SymbolicData took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 4.3392181396484375e-05s
Believability | Calculation of trust value for SymbolicData took 8.821487426757812e-06s
INFO | --- Analysis for symbolicdata took 2.847283363342285s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 4.291534423828125e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.25566554069519043s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.021277666091918945s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.24249267578125e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 8.58306884765625e-06s
INFO | --- Analysis for symptoms-in-chinese took 2.8576719760894775s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.5570259094238281s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0004150867462158203s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.4841454029083252s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.8508021831512451s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 50.37043762207031s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 19.763855695724487s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.21185779571533203s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 9.732364892959595s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.09899687767028809s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.5465364456176758s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.23971271514892578s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.19395136833190918s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.3164098262786865s
License | HR license check for National Digital Data Archive of Hungary (partial) took 55.292439699172974s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.5875809192657471s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 37.856240034103394s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.33751869201660156s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.21547579765319824s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.18539738655090332s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.17034339904785156s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.44480299949646s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 7.009506225585938e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.81272554397583s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.8271725177764893s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.6057422161102295s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5863432884216309s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.530078411102295s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 2.962275981903076s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 2.862649917602539s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 62.69298338890076s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.1675722599029541s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.25139331817626953s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0026123523712158203s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.001476287841796875s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.17582321166992188s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 45.711010217666626s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.250734806060791s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.6154913902282715s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.3299901485443115s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 46.524723052978516s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002172231674194336s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.3421328067779541s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.18909358978271484s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 15.828703165054321s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.7946996688842773s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.0300595760345459s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0008692741394042969s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 0.00011467933654785156s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 2.1457672119140625e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 8.58306884765625e-06s
INFO | --- Analysis for sztaki-lod took 615.241486787796s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.315376281738281e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.2939293384552002s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.020984649658203125s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.4836273193359375e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 8.106231689453125e-06s
INFO | --- Analysis for t4gm-info took 3.881230115890503s
Availability | SPARQL endpoint availability check for tags2con delicious took 5.1021575927734375e-05s
Availability | VoID file availability check for tags2con delicious took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.2785661220550537s
Reputation | Calculation of the PageRank for tags2con delicious took 0.020928382873535156s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.3392181396484375e-05s
Believability | Calculation of trust value for tags2con delicious took 9.059906005859375e-06s
INFO | --- Analysis for tags2con-delicious took 3.721806764602661s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 4.291534423828125e-05s
Availability | VoID file availability check for Taiwan geographic names took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.2427845001220703s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.020915508270263672s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 5.5789947509765625e-05s
Believability | Calculation of trust value for Taiwan geographic names took 1.3589859008789062e-05s
INFO | --- Analysis for taiwan-geographic-names took 2.8790974617004395s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 4.410743713378906e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0007305145263671875s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.2609596252441406s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.02107524871826172s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.822845458984375e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 7.867813110351562e-06s
INFO | --- Analysis for talis-openlibrary took 4.244447708129883s
Availability | SPARQL endpoint availability check for TalkBank took 4.5299530029296875e-05s
Availability | VoID file availability check for TalkBank took 0.0003161430358886719s
Completeness | Calculation of interlinking completeness for TalkBank took 0.2705264091491699s
Reputation | Calculation of the PageRank for TalkBank took 0.02100539207458496s
Interlinking | Calculation of Degree of Connection for TalkBank took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for TalkBank took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for TalkBank took 3.981590270996094e-05s
Believability | Calculation of trust value for TalkBank took 8.821487426757812e-06s
INFO | --- Analysis for talkbank took 2.8420798778533936s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 4.363059997558594e-05s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.00029349327087402344s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.2458970546722412s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020934343338012695s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00013756752014160156s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 8.106231689453125e-06s
INFO | --- Analysis for taxonconcept took 2.910555601119995s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 6.103515625e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.26586008071899414s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.02119278907775879s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 9.5367431640625e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.0013580322265625e-05s
INFO | --- Analysis for taxonconcept-assets took 2.751065731048584s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 7.867813110351562e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.25037527084350586s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.021433591842651367s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.6743621826171875e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 8.58306884765625e-06s
INFO | --- Analysis for taxonconcept-occurences took 2.781451463699341s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 7.200241088867188e-05s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.24830317497253418s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.020653724670410156s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 5.173683166503906e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 1.0251998901367188e-05s
INFO | --- Analysis for taxref-ld took 2.891676902770996s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 8.249282836914062e-05s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.25969886779785156s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.021109342575073242s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 3.361701965332031e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 8.106231689453125e-06s
INFO | --- Analysis for tcga took 2.845334053039551s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 4.553794860839844e-05s
Availability | VoID file availability check for TCGA Roadmap took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.2598147392272949s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.021349191665649414s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.939338684082031e-05s
Believability | Calculation of trust value for TCGA Roadmap took 1.2636184692382812e-05s
INFO | --- Analysis for tcga-roadmap took 2.8394203186035156s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 4.267692565917969e-05s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.2790238857269287s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.021156787872314453s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00011491775512695312s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 8.58306884765625e-06s
INFO | --- Analysis for tcmgenedit_dataset took 2.8282344341278076s
Availability | SPARQL endpoint availability check for TDS took 4.2438507080078125e-05s
Availability | VoID file availability check for TDS took 0.00030112266540527344s
Completeness | Calculation of interlinking completeness for TDS took 0.25155186653137207s
Reputation | Calculation of the PageRank for TDS took 0.0211794376373291s
Interlinking | Calculation of Degree of Connection for TDS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for TDS took 4.5299530029296875e-05s
Believability | Calculation of trust value for TDS took 8.344650268554688e-06s
INFO | --- Analysis for tds took 2.8267734050750732s
Availability | SPARQL endpoint availability check for TED Talks took 4.291534423828125e-05s
Availability | VoID file availability check for TED Talks took 0.00031757354736328125s
Completeness | Calculation of interlinking completeness for TED Talks took 0.23860454559326172s
Reputation | Calculation of the PageRank for TED Talks took 0.021204233169555664s
Interlinking | Calculation of Degree of Connection for TED Talks took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TED Talks took 0.0008509159088134766s
Interlinking | Calculation of Clustering coefficient for TED Talks took 3.719329833984375e-05s
Believability | Calculation of trust value for TED Talks took 8.344650268554688e-06s
INFO | --- Analysis for ted-talks took 2.7981247901916504s
Availability | SPARQL endpoint availability check for TEKORD took 4.458427429199219e-05s
Availability | VoID file availability check for TEKORD took 0.0003235340118408203s
Completeness | Calculation of interlinking completeness for TEKORD took 0.2574119567871094s
Reputation | Calculation of the PageRank for TEKORD took 0.02229928970336914s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0011897087097167969s
Interlinking | Calculation of Clustering coefficient for TEKORD took 6.842613220214844e-05s
Believability | Calculation of trust value for TEKORD took 9.775161743164062e-06s
INFO | --- Analysis for tekord took 2.9030039310455322s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 4.315376281738281e-05s
Availability | VoID file availability check for Telegraphis Linked Data took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.2622659206390381s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.021048545837402344s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00011992454528808594s
Believability | Calculation of trust value for Telegraphis Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for telegraphis took 2.8272643089294434s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.267692565917969e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.2732508182525635s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.020799636840820312s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.772445678710938e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 1.0013580322265625e-05s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 2.855052947998047s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.220008850097656e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.26688551902770996s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.0227200984954834s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.001271963119506836s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 5.2928924560546875e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.8689255714416504s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 4.267692565917969e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.2562685012817383s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.020846843719482422s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0008394718170166016s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 3.62396240234375e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for terminesp took 2.789285182952881s
Availability | SPARQL endpoint availability check for Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Ontology took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Ontology took 0.2608480453491211s
Reputation | Calculation of the PageRank for Ontology took 0.02137613296508789s
Interlinking | Calculation of Degree of Connection for Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.600120544433594e-05s
Believability | Calculation of trust value for Ontology took 8.344650268554688e-06s
INFO | --- Analysis for Terrorist_attack took 2.8732645511627197s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 0.00010323524475097656s
Availability | VoID file availability check for Terrorist Attack1 took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.2554597854614258s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.021136760711669922s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.3855438232421875e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 1.5020370483398438e-05s
INFO | --- Analysis for Terrorist_Attack_1 took 2.751150608062744s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 4.482269287109375e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.0003371238708496094s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.2552633285522461s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.02433490753173828s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0010631084442138672s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 4.9591064453125e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 7.62939453125e-06s
INFO | --- Analysis for tesauro-materias-bupm took 2.835026979446411s
Availability | SPARQL endpoint availability check for Teseo took 4.315376281738281e-05s
Availability | VoID file availability check for Teseo took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Teseo took 0.24397039413452148s
Reputation | Calculation of the PageRank for Teseo took 0.021406173706054688s
Interlinking | Calculation of Degree of Connection for Teseo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Teseo took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Teseo took 3.361701965332031e-05s
Believability | Calculation of trust value for Teseo took 8.106231689453125e-06s
INFO | --- Analysis for teseo took 2.8348548412323s
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.0002751350402832031s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.26183629035949707s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.02143406867980957s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.600120544433594e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 8.344650268554688e-06s
INFO | --- Analysis for Tesla_Deaths took 2.905463695526123s
Availability | SPARQL endpoint availability check for test took 4.291534423828125e-05s
Availability | VoID file availability check for test took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for test took 0.2518637180328369s
Reputation | Calculation of the PageRank for test took 0.021749496459960938s
Interlinking | Calculation of Degree of Connection for test took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for test took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for test took 3.552436828613281e-05s
Believability | Calculation of trust value for test took 1.2874603271484375e-05s
INFO | --- Analysis for test took 2.882112741470337s
Availability | SPARQL endpoint availability check for Test took 4.220008850097656e-05s
Availability | VoID file availability check for Test took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Test took 0.27599358558654785s
Reputation | Calculation of the PageRank for Test took 0.020969390869140625s
Interlinking | Calculation of Degree of Connection for Test took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Test took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Test took 3.2901763916015625e-05s
Believability | Calculation of trust value for Test took 1.1205673217773438e-05s
INFO | --- Analysis for Test took 2.8344545364379883s
Availability | SPARQL endpoint availability check for test-svu took 4.220008850097656e-05s
Availability | VoID file availability check for test-svu took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for test-svu took 0.28760457038879395s
Reputation | Calculation of the PageRank for test-svu took 0.020865917205810547s
Interlinking | Calculation of Degree of Connection for test-svu took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.337860107421875e-05s
Believability | Calculation of trust value for test-svu took 9.059906005859375e-06s
INFO | --- Analysis for test-svu took 2.922788619995117s
Availability | SPARQL endpoint availability check for Test took 4.1484832763671875e-05s
Availability | VoID file availability check for Test took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Test took 0.270477294921875s
Reputation | Calculation of the PageRank for Test took 0.021125316619873047s
Interlinking | Calculation of Degree of Connection for Test took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Test took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Test took 3.6716461181640625e-05s
Believability | Calculation of trust value for Test took 8.106231689453125e-06s
INFO | --- Analysis for Test_ took 2.9142086505889893s
Availability | SPARQL endpoint availability check for xxxxx took 4.124641418457031e-05s
Availability | VoID file availability check for xxxxx took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for xxxxx took 0.2566699981689453s
Reputation | Calculation of the PageRank for xxxxx took 0.02072739601135254s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for xxxxx took 4.839897155761719e-05s
Believability | Calculation of trust value for xxxxx took 1.2636184692382812e-05s
INFO | --- Analysis for testee took 2.8528506755828857s
Availability | SPARQL endpoint availability check for Texai Lexicon took 8.368492126464844e-05s
Availability | VoID file availability check for Texai Lexicon took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.2634999752044678s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.020884275436401367s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 3.528594970703125e-05s
Believability | Calculation of trust value for Texai Lexicon took 8.106231689453125e-06s
INFO | --- Analysis for texai_lexicon took 2.911714792251587s
Availability | SPARQL endpoint availability check for tharawat magazine took 4.1961669921875e-05s
Availability | VoID file availability check for tharawat magazine took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.25389885902404785s
Reputation | Calculation of the PageRank for tharawat magazine took 0.021050691604614258s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00011205673217773438s
Believability | Calculation of trust value for tharawat magazine took 7.867813110351562e-06s
INFO | --- Analysis for tharawat-magazine-com took 2.7358648777008057s
Availability | SPARQL endpoint availability check for The CIARD RING took 4.220008850097656e-05s
Availability | VoID file availability check for The CIARD RING took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.2431328296661377s
Reputation | Calculation of the PageRank for The CIARD RING took 0.02079153060913086s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 3.4809112548828125e-05s
Believability | Calculation of trust value for The CIARD RING took 8.344650268554688e-06s
INFO | --- Analysis for the-ciard-ring took 2.8126537799835205s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 7.748603820800781e-05s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.00036215782165527344s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.2524380683898926s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.03198051452636719s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0014007091522216797s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 4.482269287109375e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 9.298324584960938e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 2.918849468231201s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.7863273620605469s
Availability | VoID file availability check for The European Library Open Dataset took 0.0005259513854980469s
Extra | Recovery of all triples for The European Library Open Dataset took 1.115168571472168s
Performance | Total latancy measurement for The European Library Open Dataset took 1.2312958240509033s
Amount of data | Number of triples check for The European Library Open Dataset took 30.221692085266113s
Versatility | Languages check for The European Library Open Dataset took 0.2865118980407715s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.224039793014526s
Interpretability | RDF structures check for The European Library Open Dataset took 0.25631070137023926s
Versatility | Serialization formats check for The European Library Open Dataset took 0.242354154586792s
Availability | RDF dump link check for The European Library Open Dataset took 0.25748109817504883s
License | MR license check for The European Library Open Dataset took 0.2849748134613037s
License | HR license check for The European Library Open Dataset took 0.25200629234313965s
Amount of data | Number of property check for The European Library Open Dataset took 0.2446892261505127s
Understandability | Number of label check for The European Library Open Dataset took 0.5363857746124268s
Understandability | URI regex check for The European Library Open Dataset took 0.49473023414611816s
Understandability | Vocabs check for The European Library Open Dataset took 0.2310476303100586s
Verifiability | Authors check for The European Library Open Dataset took 0.2534034252166748s
Verifiability | Publishers check for The European Library Open Dataset took 0.24834132194519043s
Performance | Throughput check for The European Library Open Dataset took 11.881428956985474s
Amount of data | Check the number of entities for The European Library Open Dataset took 6.818771362304688e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.23730707168579102s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.3080027103424072s
Interlinking | skos check for The European Library Open Dataset took 0.2617185115814209s
Interlinking | skos check for The European Library Open Dataset took 0.2873384952545166s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.25244665145874023s
Currency | Creation date check for The European Library Open Dataset took 0.5000207424163818s
Currency | Modification date check for The European Library Open Dataset took 0.5053806304931641s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.584782123565674s
Interoperability | New vocabularies check for The European Library Open Dataset took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.23000741004943848s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 0.47380876541137695s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.028105497360229492s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.029950857162475586s
Consistency | Disjoint class check for The European Library Open Dataset took 0.2599067687988281s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.493776559829712s
Consistency | Misplaced classes for The European Library Open Dataset took 0.3687748908996582s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.8157942295074463s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.3665282726287842s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.555198431015015s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03398275375366211s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.24546027183532715s
Security | Sign check for The European Library Open Dataset took 0.23169159889221191s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 13.000011682510376s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.2825052738189697s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.02120494842529297s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 2.384185791015625e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 8.58306884765625e-06s
INFO | --- Analysis for the-european-library-open-dataset took 388.07265758514404s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 4.3392181396484375e-05s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.28005242347717285s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.02103281021118164s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00010514259338378906s
Believability | Calculation of trust value for The Eurostat Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for the-eurostat-linked-data took 2.832578182220459s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 4.1961669921875e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.25266075134277344s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.020725250244140625s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 3.361701965332031e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.1682510375976562e-05s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 2.8624675273895264s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.220008850097656e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.26748228073120117s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.605552673339844e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 1.3113021850585938e-05s
INFO | --- Analysis for the-living-lod-cloud took 2.8392436504364014s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 4.506111145019531e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.00032901763916015625s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.2837979793548584s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.021294593811035156s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0008597373962402344s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 3.838539123535156e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 7.867813110351562e-06s
INFO | --- Analysis for the-midi-linked-data-cloud took 2.859797716140747s
Availability | SPARQL endpoint availability check for The View From took 0.09395051002502441s
Availability | VoID file availability check for The View From took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for The View From took 0.26935553550720215s
Reputation | Calculation of the PageRank for The View From took 0.020805835723876953s
Interlinking | Calculation of Degree of Connection for The View From took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for The View From took 0.00011157989501953125s
Believability | Calculation of trust value for The View From took 7.62939453125e-06s
INFO | --- Analysis for the-view-from took 2.9835028648376465s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 4.2438507080078125e-05s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.2919034957885742s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020816802978515625s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.981590270996094e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.0967254638671875e-05s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 2.930894374847412s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 4.076957702636719e-05s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.26202988624572754s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.314018249511719e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 7.152557373046875e-06s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 2.8606488704681396s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.38690185546875e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.28609347343444824s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.020966529846191406s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00013208389282226562s
Believability | Calculation of trust value for The Content Wrangler took 7.3909759521484375e-06s
INFO | --- Analysis for thecontentwrangler-com took 2.851264715194702s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 5.650520324707031e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.2460470199584961s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 3.361701965332031e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 7.3909759521484375e-06s
INFO | --- Analysis for thesaurus-bncf took 2.8353431224823s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.267692565917969e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.2551424503326416s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.02050471305847168s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.314018249511719e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 9.059906005859375e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.7535996437072754s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 4.33734655380249s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0003066062927246094s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.2535572052001953s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.677078247070312e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 8.106231689453125e-06s
INFO | --- Analysis for thesaurus-w took 8.753737449645996s
Availability | SPARQL endpoint availability check for theses.fr took 4.2438507080078125e-05s
Availability | VoID file availability check for theses.fr took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for theses.fr took 0.2576429843902588s
Reputation | Calculation of the PageRank for theses.fr took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for theses.fr took 5.125999450683594e-05s
Believability | Calculation of trust value for theses.fr took 7.62939453125e-06s
INFO | --- Analysis for thesesfr took 2.846652030944824s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.6253204345703125e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.2283647060394287s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.020935535430908203s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.315376281738281e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 8.106231689453125e-06s
INFO | --- Analysis for Thinkphile took 2.7236111164093018s
Availability | SPARQL endpoint availability check for ThIST took 5.078315734863281e-05s
Availability | VoID file availability check for ThIST took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for ThIST took 0.25172877311706543s
Reputation | Calculation of the PageRank for ThIST took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for ThIST took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ThIST took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for ThIST took 8.487701416015625e-05s
Believability | Calculation of trust value for ThIST took 7.62939453125e-06s
INFO | --- Analysis for thist took 2.743591070175171s
Availability | SPARQL endpoint availability check for TIP took 40.03844928741455s
Availability | VoID file availability check for TIP took 0.0003192424774169922s
Completeness | Calculation of interlinking completeness for TIP took 0.26690030097961426s
Reputation | Calculation of the PageRank for TIP took 0.021023988723754883s
Interlinking | Calculation of Degree of Connection for TIP took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for TIP took 0.000125885009765625s
Believability | Calculation of trust value for TIP took 7.62939453125e-06s
INFO | --- Analysis for tip took 102.9096941947937s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 4.1961669921875e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.27024102210998535s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.020855188369750977s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.337860107421875e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 1.239776611328125e-05s
INFO | --- Analysis for TOPMODEL took 2.8822147846221924s
Availability | SPARQL endpoint availability check for Tourpedia took 4.220008850097656e-05s
Availability | VoID file availability check for Tourpedia took 0.0007607936859130859s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.2589290142059326s
Reputation | Calculation of the PageRank for Tourpedia took 0.02065420150756836s
Interlinking | Calculation of Degree of Connection for Tourpedia took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Tourpedia took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 3.409385681152344e-05s
Believability | Calculation of trust value for Tourpedia took 8.58306884765625e-06s
INFO | --- Analysis for tourpedia took 3.3688247203826904s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 4.3392181396484375e-05s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.26394009590148926s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.021315574645996094s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0008108615875244141s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.910064697265625e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 8.58306884765625e-06s
INFO | --- Analysis for TP-data took 3.2786526679992676s
Availability | SPARQL endpoint availability check for Trackloaded Linked Open Data took 4.220008850097656e-05s
Availability | VoID file availability check for Trackloaded Linked Open Data took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for Trackloaded Linked Open Data took 0.2536618709564209s
Reputation | Calculation of the PageRank for Trackloaded Linked Open Data took 0.021110057830810547s
Interlinking | Calculation of Degree of Connection for Trackloaded Linked Open Data took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Trackloaded Linked Open Data took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Trackloaded Linked Open Data took 1.4781951904296875e-05s
Believability | Calculation of trust value for Trackloaded Linked Open Data took 8.58306884765625e-06s
INFO | --- Analysis for trackloaded took 3.324315309524536s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.27584195137023926s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.02074742317199707s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.673004150390625e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for traditional-korean-medicine took 2.8469507694244385s
Availability | SPARQL endpoint availability check for Traffic Scotland took 4.267692565917969e-05s
Availability | VoID file availability check for Traffic Scotland took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.2797236442565918s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.020672321319580078s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.8623809814453125e-05s
Believability | Calculation of trust value for Traffic Scotland took 7.867813110351562e-06s
INFO | --- Analysis for traffic-scotland took 2.9494781494140625s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 4.601478576660156e-05s
Availability | VoID file availability check for Transparency International Linked Data took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.24616479873657227s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.020804882049560547s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00011992454528808594s
Believability | Calculation of trust value for Transparency International Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for transparency-linked-data took 2.8759825229644775s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 5.340576171875e-05s
Availability | VoID file availability check for transport.data.gov.uk took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.24052214622497559s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.02080512046813965s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.870529174804688e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 8.106231689453125e-06s
INFO | --- Analysis for transport-data-gov-uk took 2.900221347808838s
Availability | SPARQL endpoint availability check for OpenUpLabs Transport took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenUpLabs Transport took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for OpenUpLabs Transport took 0.25401902198791504s
Reputation | Calculation of the PageRank for OpenUpLabs Transport took 0.020787477493286133s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Transport took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Transport took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Transport took 3.1948089599609375e-05s
Believability | Calculation of trust value for OpenUpLabs Transport took 8.106231689453125e-06s
INFO | --- Analysis for transport-openuplabs took 2.80071759223938s
Availability | SPARQL endpoint availability check for Trelios took 6.985664367675781e-05s
Availability | VoID file availability check for Trelios took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Trelios took 0.25710034370422363s
Reputation | Calculation of the PageRank for Trelios took 0.020810604095458984s
Interlinking | Calculation of Degree of Connection for Trelios took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.4543533325195312e-05s
Believability | Calculation of trust value for Trelios took 8.58306884765625e-06s
INFO | --- Analysis for Trelios took 2.7692041397094727s
Availability | SPARQL endpoint availability check for Twarql took 4.1961669921875e-05s
Availability | VoID file availability check for Twarql took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Twarql took 0.25481534004211426s
Reputation | Calculation of the PageRank for Twarql took 0.021002531051635742s
Interlinking | Calculation of Degree of Connection for Twarql took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Twarql took 7.939338684082031e-05s
Believability | Calculation of trust value for Twarql took 8.106231689453125e-06s
INFO | --- Analysis for twarql took 2.8422021865844727s
Availability | SPARQL endpoint availability check for TWC Data-gov took 4.3392181396484375e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.26451873779296875s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.024347782135009766s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.933906555175781e-05s
Believability | Calculation of trust value for TWC Data-gov took 8.106231689453125e-06s
INFO | --- Analysis for twc-data-gov took 2.8793528079986572s
Availability | SPARQL endpoint availability check for Tetherless World Constellation Demonstrations took 4.220008850097656e-05s
Availability | VoID file availability check for Tetherless World Constellation Demonstrations took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for Tetherless World Constellation Demonstrations took 0.27299070358276367s
Reputation | Calculation of the PageRank for Tetherless World Constellation Demonstrations took 0.02257704734802246s
Interlinking | Calculation of Degree of Connection for Tetherless World Constellation Demonstrations took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Tetherless World Constellation Demonstrations took 0.0011594295501708984s
Interlinking | Calculation of Clustering coefficient for Tetherless World Constellation Demonstrations took 4.553794860839844e-05s
Believability | Calculation of trust value for Tetherless World Constellation Demonstrations took 8.344650268554688e-06s
INFO | --- Analysis for twc-demos took 2.794391393661499s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 4.553794860839844e-05s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.2453916072845459s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.02075481414794922s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 3.361701965332031e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 7.867813110351562e-06s
INFO | --- Analysis for twc-healthdata took 2.8075270652770996s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.1484832763671875e-05s
Availability | VoID file availability check for Instance Hub (all) took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.24825000762939453s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.020903348922729492s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 7.2479248046875e-05s
Believability | Calculation of trust value for Instance Hub (all) took 7.867813110351562e-06s
INFO | --- Analysis for twc-hub took 2.759660482406616s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 4.458427429199219e-05s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.25406718254089355s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.021164655685424805s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00010967254638671875s
Believability | Calculation of trust value for IEEE VIS Source Data took 8.106231689453125e-06s
INFO | --- Analysis for twc-ieeevis took 2.8026928901672363s
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.00029277801513671875s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.27883052825927734s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.021050691604614258s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 9.417533874511719e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 7.152557373046875e-06s
INFO | --- Analysis for twc-logd took 2.9047114849090576s
Availability | SPARQL endpoint availability check for twc-opendap took 4.267692565917969e-05s
Availability | VoID file availability check for twc-opendap took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.27707910537719727s
Reputation | Calculation of the PageRank for twc-opendap took 0.021151304244995117s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 7.867813110351562e-05s
Believability | Calculation of trust value for twc-opendap took 7.3909759521484375e-06s
INFO | --- Analysis for twc-opendap took 2.8875820636749268s
Availability | SPARQL endpoint availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 4.0531158447265625e-05s
Availability | VoID file availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.2658865451812744s
Reputation | Calculation of the PageRank for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.020753145217895508s
Interlinking | Calculation of Degree of Connection for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 3.1948089599609375e-05s
Believability | Calculation of trust value for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 1.2636184692382812e-05s
INFO | --- Analysis for tweetskb took 2.8785650730133057s
Availability | SPARQL endpoint availability check for Twitter Linked Data Service took 4.1961669921875e-05s
Availability | VoID file availability check for Twitter Linked Data Service took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Twitter Linked Data Service took 0.23832011222839355s
Reputation | Calculation of the PageRank for Twitter Linked Data Service took 0.020771265029907227s
Interlinking | Calculation of Degree of Connection for Twitter Linked Data Service took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Twitter Linked Data Service took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Twitter Linked Data Service took 3.266334533691406e-05s
Believability | Calculation of trust value for Twitter Linked Data Service took 7.3909759521484375e-06s
INFO | --- Analysis for twitter-lids took 2.8009755611419678s
Availability | SPARQL endpoint availability check for typepad took 4.100799560546875e-05s
Availability | VoID file availability check for typepad took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for typepad took 0.24025630950927734s
Reputation | Calculation of the PageRank for typepad took 0.020746707916259766s
Interlinking | Calculation of Degree of Connection for typepad took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for typepad took 5.507469177246094e-05s
Believability | Calculation of trust value for typepad took 7.62939453125e-06s
INFO | --- Analysis for typepad took 2.823655366897583s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.9028935432434082s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.2742774486541748s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.02073049545288086s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.5299530029296875e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 7.152557373046875e-06s
INFO | --- Analysis for ub-mannheim-linked-data took 4.438791751861572s
Availability | SPARQL endpoint availability check for Uberblic.org took 4.2438507080078125e-05s
Availability | VoID file availability check for Uberblic.org took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.25481557846069336s
Reputation | Calculation of the PageRank for Uberblic.org took 0.02083897590637207s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00010848045349121094s
Believability | Calculation of trust value for Uberblic.org took 8.821487426757812e-06s
INFO | --- Analysis for uberblic took 2.803234815597534s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.6560914516448975s
Availability | VoID file availability check for UDante in LiLa took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.25562238693237305s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 4.363059997558594e-05s
Believability | Calculation of trust value for UDante in LiLa took 6.4373016357421875e-06s
INFO | --- Analysis for UDante took 4.002139091491699s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.23952102661132812s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.020965099334716797s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 3.337860107421875e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for ufo took 2.8393149375915527s
Availability | SPARQL endpoint availability check for Uganda Disasters took 7.700920104980469e-05s
Availability | VoID file availability check for Uganda Disasters took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.2446269989013672s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.02101421356201172s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 5.6743621826171875e-05s
Believability | Calculation of trust value for Uganda Disasters took 9.298324584960938e-06s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.7927958965301514s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 4.410743713378906e-05s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.25363945960998535s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.021035194396972656s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.00010609626770019531s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for uis-linked-data took 2.783625841140747s
Availability | SPARQL endpoint availability check for UK Legislation took 4.1961669921875e-05s
Availability | VoID file availability check for UK Legislation took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.2521555423736572s
Reputation | Calculation of the PageRank for UK Legislation took 0.020880937576293945s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 9.036064147949219e-05s
Believability | Calculation of trust value for UK Legislation took 7.62939453125e-06s
INFO | --- Analysis for uk-legislation-api took 2.847022533416748s
Availability | SPARQL endpoint availability check for UK Postcodes took 5.364418029785156e-05s
Availability | VoID file availability check for UK Postcodes took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.2770235538482666s
Reputation | Calculation of the PageRank for UK Postcodes took 0.02075505256652832s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.9604644775390625e-05s
Believability | Calculation of trust value for UK Postcodes took 7.62939453125e-06s
INFO | --- Analysis for uk-postcodes took 2.932612180709839s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 4.291534423828125e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.2512037754058838s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.020862579345703125s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0001347064971923828s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 8.106231689453125e-06s
INFO | --- Analysis for umbel took 2.824151039123535s
Availability | SPARQL endpoint availability check for UMTHES took 4.2438507080078125e-05s
Availability | VoID file availability check for UMTHES took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for UMTHES took 0.27313232421875s
Reputation | Calculation of the PageRank for UMTHES took 0.020847558975219727s
Interlinking | Calculation of Degree of Connection for UMTHES took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UMTHES took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for UMTHES took 4.673004150390625e-05s
Believability | Calculation of trust value for UMTHES took 8.58306884765625e-06s
INFO | --- Analysis for umthes took 2.828547477722168s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 5.936622619628906e-05s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0003249645233154297s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.25572991371154785s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.023265600204467773s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.790855407714844e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 8.58306884765625e-06s
INFO | --- Analysis for un-hazardous-numbers took 2.847393035888672s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.863739013671875e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.27445292472839355s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.0208280086517334s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.62396240234375e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for unesco-thesaurus took 2.893902540206909s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.2641713619232178s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020859718322753906s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.4809112548828125e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for unescothes took 2.8700215816497803s
Availability | SPARQL endpoint availability check for UniProt took 5.340576171875e-05s
Availability | VoID file availability check for UniProt took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for UniProt took 0.2962617874145508s
Reputation | Calculation of the PageRank for UniProt took 0.021099567413330078s
Interlinking | Calculation of Degree of Connection for UniProt took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for UniProt took 4.38690185546875e-05s
Believability | Calculation of trust value for UniProt took 8.58306884765625e-06s
INFO | --- Analysis for UniProt took 2.9775938987731934s
Availability | SPARQL endpoint availability check for UniProt took 4.076957702636719e-05s
Availability | VoID file availability check for UniProt took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for UniProt took 0.26917481422424316s
Reputation | Calculation of the PageRank for UniProt took 0.03220772743225098s
Interlinking | Calculation of Degree of Connection for UniProt took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0013988018035888672s
Interlinking | Calculation of Clustering coefficient for UniProt took 8.249282836914062e-05s
Believability | Calculation of trust value for UniProt took 7.867813110351562e-06s
INFO | --- Analysis for uniprot took 2.816821813583374s
Availability | SPARQL endpoint availability check for UniProt citations took 4.2438507080078125e-05s
Availability | VoID file availability check for UniProt citations took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for UniProt citations took 0.26389360427856445s
Reputation | Calculation of the PageRank for UniProt citations took 0.020869016647338867s
Interlinking | Calculation of Degree of Connection for UniProt citations took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UniProt citations took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for UniProt citations took 3.5762786865234375e-05s
Believability | Calculation of trust value for UniProt citations took 7.62939453125e-06s
INFO | --- Analysis for uniprot-citations took 2.8280746936798096s
Availability | SPARQL endpoint availability check for UniProt databases took 7.486343383789062e-05s
Availability | VoID file availability check for UniProt databases took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for UniProt databases took 0.2553586959838867s
Reputation | Calculation of the PageRank for UniProt databases took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for UniProt databases took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UniProt databases took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for UniProt databases took 3.3855438232421875e-05s
Believability | Calculation of trust value for UniProt databases took 8.344650268554688e-06s
INFO | --- Analysis for uniprot-databases took 2.8611984252929688s
Availability | SPARQL endpoint availability check for uniprot-metadata took 4.482269287109375e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.2792680263519287s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.021153926849365234s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.341934204101562e-05s
Believability | Calculation of trust value for uniprot-metadata took 9.059906005859375e-06s
INFO | --- Analysis for uniprot-metadata took 2.8814525604248047s
Availability | SPARQL endpoint availability check for UniProtKB Taxonomy took 4.2438507080078125e-05s
Availability | VoID file availability check for UniProtKB Taxonomy took 0.0002884864807128906s
Completeness | Calculation of interlinking completeness for UniProtKB Taxonomy took 0.2536149024963379s
Reputation | Calculation of the PageRank for UniProtKB Taxonomy took 0.02116680145263672s
Interlinking | Calculation of Degree of Connection for UniProtKB Taxonomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UniProtKB Taxonomy took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for UniProtKB Taxonomy took 3.504753112792969e-05s
Believability | Calculation of trust value for UniProtKB Taxonomy took 8.58306884765625e-06s
INFO | --- Analysis for uniprot-taxonomy took 2.914149045944214s
Availability | SPARQL endpoint availability check for UniProt UniParc took 4.315376281738281e-05s
Availability | VoID file availability check for UniProt UniParc took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for UniProt UniParc took 0.2662076950073242s
Reputation | Calculation of the PageRank for UniProt UniParc took 0.020907878875732422s
Interlinking | Calculation of Degree of Connection for UniProt UniParc took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for UniProt UniParc took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for UniProt UniParc took 3.5762786865234375e-05s
Believability | Calculation of trust value for UniProt UniParc took 9.059906005859375e-06s
INFO | --- Analysis for uniprot-uniparc took 2.862333059310913s
Availability | SPARQL endpoint availability check for UniProt UniPathway took 4.2438507080078125e-05s
Availability | VoID file availability check for UniProt UniPathway took 0.0007300376892089844s
Completeness | Calculation of interlinking completeness for UniProt UniPathway took 0.26479458808898926s
Reputation | Calculation of the PageRank for UniProt UniPathway took 0.0210268497467041s
Interlinking | Calculation of Degree of Connection for UniProt UniPathway took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UniProt UniPathway took 0.0008080005645751953s
Interlinking | Calculation of Clustering coefficient for UniProt UniPathway took 3.409385681152344e-05s
Believability | Calculation of trust value for UniProt UniPathway took 7.867813110351562e-06s
INFO | --- Analysis for uniprot-unipathway took 2.845562219619751s
Availability | SPARQL endpoint availability check for UniProtKB took 4.267692565917969e-05s
Availability | VoID file availability check for UniProtKB took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.2780015468597412s
Reputation | Calculation of the PageRank for UniProtKB took 0.020938873291015625s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0008089542388916016s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 6.008148193359375e-05s
Believability | Calculation of trust value for UniProtKB took 6.9141387939453125e-06s
INFO | --- Analysis for uniprotkb took 2.8761398792266846s
Availability | SPARQL endpoint availability check for UniProt UniRef took 4.267692565917969e-05s
Availability | VoID file availability check for UniProt UniRef took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for UniProt UniRef took 0.25302791595458984s
Reputation | Calculation of the PageRank for UniProt UniRef took 0.0209958553314209s
Interlinking | Calculation of Degree of Connection for UniProt UniRef took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UniProt UniRef took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for UniProt UniRef took 3.2901763916015625e-05s
Believability | Calculation of trust value for UniProt UniRef took 8.344650268554688e-06s
INFO | --- Analysis for uniref took 2.8144421577453613s
Availability | SPARQL endpoint availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 4.1961669921875e-05s
Availability | VoID file availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.2530345916748047s
Reputation | Calculation of the PageRank for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.020905256271362305s
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.0007171630859375s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 3.147125244140625e-05s
Believability | Calculation of trust value for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 7.62939453125e-06s
INFO | --- Analysis for unistat-kis-2011-2012-in-rdf-key-information-set-uk-universities took 2.8576552867889404s
Availability | SPARQL endpoint availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 4.1484832763671875e-05s
Availability | VoID file availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.27244114875793457s
Reputation | Calculation of the PageRank for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.021023035049438477s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 3.337860107421875e-05s
Believability | Calculation of trust value for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 7.867813110351562e-06s
INFO | --- Analysis for unistat-kis-in-rdf-key-information-set-uk-universities took 2.7964272499084473s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.2780337333679199s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.021012306213378906s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 4.3392181396484375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 2.833951234817505s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.2520310878753662s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0206754207611084s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 5.054473876953125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 2.8305914402008057s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.26480841636657715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.021327495574951172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 4.482269287109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 2.832332134246826s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.23203086853027344s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.020952701568603516s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 4.839897155761719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-basque took 2.8105087280273438s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 5.030632019042969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.26421499252319336s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.02085137367248535s
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.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 1.1205673217773438e-05s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 2.8452577590942383s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.00037169456481933594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.2696685791015625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.021023273468017578s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 2.925976514816284s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.25261640548706055s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.02086925506591797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 2.8354761600494385s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.264636754989624s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.020847082138061523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 9.298324584960938e-06s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 2.864976644515991s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.24907827377319336s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.021200180053710938s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 2.8318653106689453s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 7.724761962890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.25141215324401855s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.02227306365966797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0009000301361083984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 5.14984130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech took 2.851088285446167s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.00030517578125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.25736355781555176s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.020810604095458984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 2.8642189502716064s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 7.200241088867188e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.2562568187713623s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.02086925506591797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 2.8024492263793945s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0003027915954589844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.2678241729736328s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.02083563804626465s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 4.57763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-danish took 2.9242641925811768s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.2670478820800781s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.02096104621887207s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 4.7206878662109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 2.8531830310821533s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 5.507469177246094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.26736974716186523s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.02100205421447754s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 2.848151922225952s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 7.557868957519531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.2788076400756836s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.021000146865844727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-english took 2.870891571044922s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.26496100425720215s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.02081751823425293s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 2.841283082962036s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 7.343292236328125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0003190040588378906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.2640995979309082s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.02071094512939453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.673004150390625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 2.8260891437530518s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.000293731689453125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.2435140609741211s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.021132469177246094s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0009567737579345703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.982948303222656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 2.8281311988830566s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.2608203887939453s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.021245479583740234s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0009775161743164062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 5.0067901611328125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 2.8772270679473877s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.2638828754425049s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.020763635635375977s
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.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 4.601478576660156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 2.893995761871338s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.00029969215393066406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.248915433883667s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.020847082138061523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-french took 2.821798086166382s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.26826047897338867s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.020830869674682617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician took 2.796721935272217s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 5.650520324707031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.25592947006225586s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.021191835403442383s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0008480548858642578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 4.649162292480469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 2.8931665420532227s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.24358081817626953s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.021020174026489258s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-german took 2.7833478450775146s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.00029969215393066406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.2425365447998047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.021407604217529297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.744529724121094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 2.797382354736328s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.00036835670471191406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.2600412368774414s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.021163463592529297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0008416175842285156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 5.340576171875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-greek took 2.854025363922119s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.2619664669036865s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.020881175994873047s
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.0008187294006347656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 4.696846008300781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 2.7767515182495117s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 0.0001316070556640625s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.2575812339782715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.021093130111694336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 2.834968090057373s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.25730037689208984s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.021155118942260742s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 4.696846008300781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 2.8842146396636963s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.2562119960784912s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0008213520050048828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 4.6253204345703125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 2.870490550994873s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 5.793571472167969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.29500246047973633s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.020874738693237305s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-irish took 2.8904871940612793s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.2526724338531494s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.021023988723754883s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-italian took 2.8603456020355225s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.2556726932525635s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 2.8306989669799805s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.00032258033752441406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.25039243698120117s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.021066904067993164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 2.903366804122925s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 5.5789947509765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.25823330879211426s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.021115779876708984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.6253204345703125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 2.820831775665283s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.28981947898864746s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin took 2.7954320907592773s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 5.3882598876953125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.3072662353515625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.02064657211303711s
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.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 2.908895254135132s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.2634754180908203s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.020914554595947266s
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.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 9.059906005859375e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 2.7960855960845947s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.2654910087585449s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.02078557014465332s
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.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 2.786160945892334s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.26043009757995605s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 2.8689069747924805s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.260514497756958s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.020869016647338867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 4.3392181396484375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 2.8661580085754395s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.076957702636719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.2529306411743164s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.02093362808227539s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.482269287109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-persian took 2.874337673187256s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.27786731719970703s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-polish took 2.8721320629119873s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.29110264778137207s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.020788908004760742s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 2.926187753677368s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.2796745300292969s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020952463150024414s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 2.9172861576080322s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.24900245666503906s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.020979642868041992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 4.649162292480469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 2.8750381469726562s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.00029969215393066406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.24967074394226074s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020914554595947266s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 2.8660507202148438s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.2756533622741699s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.020792007446289062s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian took 2.909679651260376s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.23636126518249512s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.020769596099853516s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 2.7995190620422363s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.24799275398254395s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.020803451538085938s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 4.315376281738281e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 2.7243051528930664s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.2588980197906494s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 2.1219253540039062e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 2.829125165939331s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.649162292480469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.24332213401794434s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.020990371704101562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 4.601478576660156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 2.8255085945129395s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.00033164024353027344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.25513458251953125s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.020686864852905273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 2.7749671936035156s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 4.673004150390625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.26706361770629883s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.020975589752197266s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 2.8073058128356934s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.25801825523376465s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.021184206008911133s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 5.14984130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 2.9037506580352783s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.6253204345703125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.25457763671875s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.020990371704101562s
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.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 2.8549485206604004s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 6.389617919921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0003688335418701172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.24747657775878906s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.03205513954162598s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0012836456298828125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 5.555152893066406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 9.775161743164062e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 2.793090343475342s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0003566741943359375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.2539191246032715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.020823001861572266s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 2.830333709716797s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.28838467597961426s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.02083134651184082s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 4.410743713378906e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 2.9374921321868896s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.26369667053222656s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 2.8643717765808105s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.28937625885009766s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.020609617233276367s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 4.649162292480469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 2.844290256500244s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.23128962516784668s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.0208280086517334s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0008254051208496094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 2.794520378112793s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.267230749130249s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0008246898651123047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 2.917445659637451s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 4.4345855712890625e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.26294803619384766s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.02085256576538086s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 7.557868957519531e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 7.867813110351562e-06s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 2.893958568572998s
Availability | SPARQL endpoint availability check for Universitat Pompeu Fabra - linked data took 4.172325134277344e-05s
Availability | VoID file availability check for Universitat Pompeu Fabra - linked data took 0.0003352165222167969s
Completeness | Calculation of interlinking completeness for Universitat Pompeu Fabra - linked data took 0.27281689643859863s
Reputation | Calculation of the PageRank for Universitat Pompeu Fabra - linked data took 0.021261215209960938s
Interlinking | Calculation of Degree of Connection for Universitat Pompeu Fabra - linked data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universitat Pompeu Fabra - linked data took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Universitat Pompeu Fabra - linked data took 3.695487976074219e-05s
Believability | Calculation of trust value for Universitat Pompeu Fabra - linked data took 7.867813110351562e-06s
INFO | --- Analysis for universitat-pompeu-fabra-linked-data took 2.919442892074585s
Availability | SPARQL endpoint availability check for University of Bristol took 4.100799560546875e-05s
Availability | VoID file availability check for University of Bristol took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for University of Bristol took 0.2639806270599365s
Reputation | Calculation of the PageRank for University of Bristol took 0.021256446838378906s
Interlinking | Calculation of Degree of Connection for University of Bristol took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for University of Bristol took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for University of Bristol took 3.457069396972656e-05s
Believability | Calculation of trust value for University of Bristol took 1.33514404296875e-05s
INFO | --- Analysis for university-of-bristol took 2.83431339263916s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 4.2438507080078125e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.000274658203125s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.27613329887390137s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.02077960968017578s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007154941558837891s
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 7.62939453125e-06s
INFO | --- Analysis for university-plymouth-reading-lists took 2.849884033203125s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 7.772445678710938e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.00036787986755371094s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.2505638599395752s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.020746707916259766s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 4.7206878662109375e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 1.1444091796875e-05s
INFO | --- Analysis for university-sussex-reading-lists took 2.8530654907226562s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 4.3392181396484375e-05s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.27735209465026855s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.02112865447998047s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0011200904846191406s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 9.274482727050781e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 7.62939453125e-06s
INFO | --- Analysis for unodc took 2.8734164237976074s
Availability | SPARQL endpoint availability check for Super Ontology took 7.390975952148438e-05s
Availability | VoID file availability check for Super Ontology took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.24919486045837402s
Reputation | Calculation of the PageRank for Super Ontology took 0.020565032958984375s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 8.749961853027344e-05s
Believability | Calculation of trust value for Super Ontology took 1.5974044799804688e-05s
INFO | --- Analysis for upper-ontology took 3.1005735397338867s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.00029850006103515625s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.27730584144592285s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.021344423294067383s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0008161067962646484s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.933906555175781e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 8.344650268554688e-06s
INFO | --- Analysis for Upper_Ontology took 2.8641631603240967s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 4.363059997558594e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.000293731689453125s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.2778773307800293s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.021097421646118164s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 3.4332275390625e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 7.152557373046875e-06s
INFO | --- Analysis for Urban_Atlas_ took 2.8561031818389893s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 4.172325134277344e-05s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.24757885932922363s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.02075982093811035s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 3.457069396972656e-05s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 8.106231689453125e-06s
INFO | --- Analysis for Urban_Atlas_Dataset took 2.8649797439575195s
Availability | SPARQL endpoint availability check for URIBurner took 4.1484832763671875e-05s
Availability | VoID file availability check for URIBurner took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for URIBurner took 0.2886044979095459s
Reputation | Calculation of the PageRank for URIBurner took 0.02086329460144043s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for URIBurner took 0.00010657310485839844s
Believability | Calculation of trust value for URIBurner took 8.344650268554688e-06s
INFO | --- Analysis for uriburner took 2.8631997108459473s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.363059997558594e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00031065940856933594s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.24820446968078613s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.266334533691406e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 7.867813110351562e-06s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 2.7934823036193848s
Availability | SPARQL endpoint availability check for Legija Stranaca took 5.030632019042969e-05s
Availability | VoID file availability check for Legija Stranaca took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.26910877227783203s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.021167278289794922s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 3.528594970703125e-05s
Believability | Calculation of trust value for Legija Stranaca took 7.867813110351562e-06s
INFO | --- Analysis for Uros_Legija_Susa took 2.816343307495117s
Availability | SPARQL endpoint availability check for Legija took 6.4849853515625e-05s
Availability | VoID file availability check for Legija took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Legija took 0.2742421627044678s
Reputation | Calculation of the PageRank for Legija took 0.021764278411865234s
Interlinking | Calculation of Degree of Connection for Legija took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Legija took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Legija took 3.719329833984375e-05s
Believability | Calculation of trust value for Legija took 7.867813110351562e-06s
INFO | --- Analysis for Uros_Susa took 2.902517080307007s
Availability | SPARQL endpoint availability check for US Political Violence took 4.315376281738281e-05s
Availability | VoID file availability check for US Political Violence took 0.0002930164337158203s
Completeness | Calculation of interlinking completeness for US Political Violence took 0.25504040718078613s
Reputation | Calculation of the PageRank for US Political Violence took 0.02081918716430664s
Interlinking | Calculation of Degree of Connection for US Political Violence took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for US Political Violence took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for US Political Violence took 3.314018249511719e-05s
Believability | Calculation of trust value for US Political Violence took 9.775161743164062e-06s
INFO | --- Analysis for us-political-violence took 2.8484654426574707s
Availability | SPARQL endpoint availability check for USAGE review corpus took 4.2438507080078125e-05s
Availability | VoID file availability check for USAGE review corpus took 0.0003104209899902344s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.24569296836853027s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.020601987838745117s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.361701965332031e-05s
Believability | Calculation of trust value for USAGE review corpus took 1.2874603271484375e-05s
INFO | --- Analysis for usage-review-corpus took 2.8175647258758545s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 4.291534423828125e-05s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.24915456771850586s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.020838260650634766s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 8.106231689453125e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for utpl-lod took 2.8032877445220947s
Availability | SPARQL endpoint availability check for Výkazy zisku a ztrát obcí ČR took 7.62939453125e-05s
Availability | VoID file availability check for Výkazy zisku a ztrát obcí ČR took 0.00034332275390625s
Completeness | Calculation of interlinking completeness for Výkazy zisku a ztrát obcí ČR took 0.2583451271057129s
Reputation | Calculation of the PageRank for Výkazy zisku a ztrát obcí ČR took 0.02132725715637207s
Interlinking | Calculation of Degree of Connection for Výkazy zisku a ztrát obcí ČR took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Výkazy zisku a ztrát obcí ČR took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Výkazy zisku a ztrát obcí ČR took 3.600120544433594e-05s
Believability | Calculation of trust value for Výkazy zisku a ztrát obcí ČR took 8.344650268554688e-06s
INFO | --- Analysis for v-kazy-zisku-a-ztr-t-obc---r took 2.8013694286346436s
Availability | SPARQL endpoint availability check for terrorist attack took 4.315376281738281e-05s
Availability | VoID file availability check for terrorist attack took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.23949146270751953s
Reputation | Calculation of the PageRank for terrorist attack took 0.021360158920288086s
Interlinking | Calculation of Degree of Connection for terrorist attack took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 4.673004150390625e-05s
Believability | Calculation of trust value for terrorist attack took 8.344650268554688e-06s
INFO | --- Analysis for varsha took 2.7577507495880127s
Availability | SPARQL endpoint availability check for VA took 5.555152893066406e-05s
Availability | VoID file availability check for VA took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for VA took 0.2612426280975342s
Reputation | Calculation of the PageRank for VA took 0.02078557014465332s
Interlinking | Calculation of Degree of Connection for VA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for VA took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for VA took 3.504753112792969e-05s
Believability | Calculation of trust value for VA took 1.0251998901367188e-05s
INFO | --- Analysis for Vehicule_Autonome took 2.8308844566345215s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 4.4345855712890625e-05s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.26895666122436523s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.021199703216552734s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 4.00543212890625e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 8.58306884765625e-06s
INFO | --- Analysis for VelezIndexTotiusArtis took 2.871267795562744s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 4.172325134277344e-05s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.2514946460723877s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.02100205421447754s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0008370876312255859s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 0.0001049041748046875s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 9.5367431640625e-06s
INFO | --- Analysis for verrijktkoninkrijk took 2.825380325317383s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 5.53131103515625e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.2521679401397705s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.02171778678894043s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00019431114196777344s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 7.62939453125e-06s
INFO | --- Analysis for viaf took 2.7976346015930176s
Availability | SPARQL endpoint availability check for Vías Públicas de Zaragoza (Localización) took 4.2438507080078125e-05s
Availability | VoID file availability check for Vías Públicas de Zaragoza (Localización) took 0.00041747093200683594s
Completeness | Calculation of interlinking completeness for Vías Públicas de Zaragoza (Localización) took 0.24998736381530762s
Reputation | Calculation of the PageRank for Vías Públicas de Zaragoza (Localización) took 0.02232217788696289s
Interlinking | Calculation of Degree of Connection for Vías Públicas de Zaragoza (Localización) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Vías Públicas de Zaragoza (Localización) took 0.0009942054748535156s
Interlinking | Calculation of Clustering coefficient for Vías Públicas de Zaragoza (Localización) took 4.029273986816406e-05s
Believability | Calculation of trust value for Vías Públicas de Zaragoza (Localización) took 8.344650268554688e-06s
INFO | --- Analysis for vias-publicas-zaragoza took 2.8452861309051514s
Availability | SPARQL endpoint availability check for Vihar Exports took 4.3392181396484375e-05s
Availability | VoID file availability check for Vihar Exports took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.27008938789367676s
Reputation | Calculation of the PageRank for Vihar Exports took 0.020804882049560547s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 3.6716461181640625e-05s
Believability | Calculation of trust value for Vihar Exports took 8.106231689453125e-06s
INFO | --- Analysis for Vihar_Exports took 2.8192520141601562s
Availability | SPARQL endpoint availability check for vimeo.videoobject took 4.315376281738281e-05s
Availability | VoID file availability check for vimeo.videoobject took 0.00041222572326660156s
Completeness | Calculation of interlinking completeness for vimeo.videoobject took 0.27741074562072754s
Reputation | Calculation of the PageRank for vimeo.videoobject took 0.020688295364379883s
Interlinking | Calculation of Degree of Connection for vimeo.videoobject took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for vimeo.videoobject took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for vimeo.videoobject took 3.600120544433594e-05s
Believability | Calculation of trust value for vimeo.videoobject took 6.9141387939453125e-06s
INFO | --- Analysis for vimeo_videoobject took 2.825977325439453s
Availability | SPARQL endpoint availability check for VIVO took 4.3392181396484375e-05s
Availability | VoID file availability check for VIVO took 0.0003275871276855469s
Completeness | Calculation of interlinking completeness for VIVO took 0.22899723052978516s
Reputation | Calculation of the PageRank for VIVO took 0.020639419555664062s
Interlinking | Calculation of Degree of Connection for VIVO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for VIVO took 7.843971252441406e-05s
Believability | Calculation of trust value for VIVO took 8.58306884765625e-06s
INFO | --- Analysis for vivo took 2.803680658340454s
Availability | SPARQL endpoint availability check for VIVO Cornell took 4.267692565917969e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0003371238708496094s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.2738914489746094s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.02092742919921875s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 3.218650817871094e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.273124694824219e-05s
Believability | Calculation of trust value for VIVO Cornell took 1.33514404296875e-05s
INFO | --- Analysis for vivo-cornell-university took 2.833758592605591s
Availability | SPARQL endpoint availability check for VIVO CU-Boulder took 5.3882598876953125e-05s
Availability | VoID file availability check for VIVO CU-Boulder took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for VIVO CU-Boulder took 0.2542839050292969s
Reputation | Calculation of the PageRank for VIVO CU-Boulder took 0.020934581756591797s
Interlinking | Calculation of Degree of Connection for VIVO CU-Boulder took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for VIVO CU-Boulder took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for VIVO CU-Boulder took 3.5762786865234375e-05s
Believability | Calculation of trust value for VIVO CU-Boulder took 9.5367431640625e-06s
INFO | --- Analysis for vivo-cu-boulder took 2.885941505432129s
Availability | SPARQL endpoint availability check for VIVO Indiana took 6.532669067382812e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.2784299850463867s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.02111077308654785s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 8.535385131835938e-05s
Believability | Calculation of trust value for VIVO Indiana took 9.059906005859375e-06s
INFO | --- Analysis for vivo-indiana-university took 2.8749277591705322s
Availability | SPARQL endpoint availability check for VIVO Ponce took 9.1552734375e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0003769397735595703s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.26762962341308594s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.02116084098815918s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.719329833984375e-05s
Believability | Calculation of trust value for VIVO Ponce took 8.58306884765625e-06s
INFO | --- Analysis for vivo-ponce took 2.787046432495117s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 4.363059997558594e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0003101825714111328s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.2711353302001953s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.02138805389404297s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 4.124641418457031e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 8.58306884765625e-06s
INFO | --- Analysis for vivo-scripps-research-institute took 2.973684787750244s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 4.291534423828125e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.2556886672973633s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.020746946334838867s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 0.00010538101196289062s
Believability | Calculation of trust value for VIVO University of Florida took 8.344650268554688e-06s
INFO | --- Analysis for vivo-university-of-florida took 2.7919304370880127s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 4.3392181396484375e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.2520570755004883s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.02335381507873535s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0009667873382568359s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 5.2928924560546875e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 8.344650268554688e-06s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 2.785391092300415s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 4.267692565917969e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.25003838539123535s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.0208284854888916s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 4.029273986816406e-05s
Believability | Calculation of trust value for VIVO WUSTL took 1.1682510375976562e-05s
INFO | --- Analysis for vivo-wustl took 2.917056083679199s
Availability | SPARQL endpoint availability check for vivo2doi took 7.176399230957031e-05s
Availability | VoID file availability check for vivo2doi took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.2752833366394043s
Reputation | Calculation of the PageRank for vivo2doi took 0.020853757858276367s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.673004150390625e-05s
Believability | Calculation of trust value for vivo2doi took 8.58306884765625e-06s
INFO | --- Analysis for vivo2doi took 2.7784507274627686s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 4.220008850097656e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.00030517578125s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.2542731761932373s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.02211785316467285s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 0.00010561943054199219s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 8.58306884765625e-06s
INFO | --- Analysis for vu-wordnet took 2.851928472518921s
Availability | SPARQL endpoint availability check for vulnerapedia took 8.392333984375e-05s
Availability | VoID file availability check for vulnerapedia took 0.00030303001403808594s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.24363470077514648s
Reputation | Calculation of the PageRank for vulnerapedia took 0.020769596099853516s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 6.794929504394531e-05s
Believability | Calculation of trust value for vulnerapedia took 8.58306884765625e-06s
INFO | --- Analysis for vulnerapedia took 2.8277807235717773s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 4.220008850097656e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.24148917198181152s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0207672119140625s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.430511474609375e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 9.298324584960938e-06s
INFO | --- Analysis for VVASIAK took 2.8657212257385254s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 4.267692565917969e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.0003161430358886719s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.37935733795166016s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.0211026668548584s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0008757114410400391s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.933906555175781e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 8.821487426757812e-06s
INFO | --- Analysis for Vyvasta took 2.9287898540496826s
Availability | SPARQL endpoint availability check for W3C took 4.172325134277344e-05s
Availability | VoID file availability check for W3C took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for W3C took 0.24843096733093262s
Reputation | Calculation of the PageRank for W3C took 0.020734310150146484s
Interlinking | Calculation of Degree of Connection for W3C took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for W3C took 0.00016260147094726562s
Believability | Calculation of trust value for W3C took 3.24249267578125e-05s
INFO | --- Analysis for w3c took 2.906374216079712s
Availability | SPARQL endpoint availability check for W3C Provenance Incubator Group Vocabulary Mappings took 9.036064147949219e-05s
Availability | VoID file availability check for W3C Provenance Incubator Group Vocabulary Mappings took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for W3C Provenance Incubator Group Vocabulary Mappings took 0.2518608570098877s
Reputation | Calculation of the PageRank for W3C Provenance Incubator Group Vocabulary Mappings took 0.020821094512939453s
Interlinking | Calculation of Degree of Connection for W3C Provenance Incubator Group Vocabulary Mappings took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for W3C Provenance Incubator Group Vocabulary Mappings took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for W3C Provenance Incubator Group Vocabulary Mappings took 3.552436828613281e-05s
Believability | Calculation of trust value for W3C Provenance Incubator Group Vocabulary Mappings took 7.62939453125e-06s
INFO | --- Analysis for w3c-provenance-incubator-group-vocabulary-mappings took 2.8216958045959473s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 4.172325134277344e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0003082752227783203s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.2549738883972168s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.0210421085357666s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0008573532104492188s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00012731552124023438s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 7.867813110351562e-06s
INFO | --- Analysis for w3c-wordnet took 2.848243474960327s
Availability | SPARQL endpoint availability check for WarSampo took 0.3378031253814697s
Availability | VoID file availability check for WarSampo took 0.0002770423889160156s
Extra | Recovery of all triples for WarSampo took 25.552304983139038s
Performance | Total latancy measurement for WarSampo took 0.8456306457519531s
Amount of data | Number of triples check for WarSampo took 18.91392946243286s
Interoperability | New terms check for WarSampo took 3.8255395889282227s
Versatility | Languages check for WarSampo took 54.09262442588806s
Interpretability | Number of blank nodes check for WarSampo took 18.26586127281189s
Security | Check HTTPS for WarSampo took 0.419431209564209s
Interpretability | RDF structures check for WarSampo took 0.18190479278564453s
Versatility | Serialization formats check for WarSampo took 0.20862436294555664s
Availability | RDF dump link check for WarSampo took 3.4323203563690186s
License | MR license check for WarSampo took 0.17627930641174316s
License | HR license check for WarSampo took 47.22369718551636s
Amount of data | Number of property check for WarSampo took 0.18062186241149902s
Understandability | Number of label check for WarSampo took 10.67223834991455s
Understandability | URI regex check for WarSampo took 0.34302592277526855s
Understandability | Vocabs check for WarSampo took 0.18140721321105957s
Verifiability | Authors check for WarSampo took 0.16562652587890625s
Verifiability | Publishers check for WarSampo took 0.1685938835144043s
Performance | Throughput check for WarSampo took 10.989916801452637s
Amount of data | Check the number of entities for WarSampo took 17.475048542022705s
Verifiability | Contribs. check for WarSampo took 0.1806485652923584s
Interlinking | sameAs chians check for WarSampo took 0.19100499153137207s
Interlinking | skos check for WarSampo took 0.18008804321289062s
Interlinking | skos check for WarSampo took 0.16163969039916992s
Timeliness | dataset update frequency check for WarSampo took 0.17551326751708984s
Currency | Creation date check for WarSampo took 0.3419370651245117s
Currency | Modification date check for WarSampo took 0.35428595542907715s
Rep.Conc. | URIs length for WarSampo took 50.03650379180908s
Interoperability | New vocabularies check for WarSampo took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.16613388061523438s
Accuracy | Check Functional Property for WarSampo took 0.17163968086242676s
Accuracy | Check Inverse Functional Property for WarSampo took 0.16836071014404297s
Accuracy | Check Empty annotation labels for WarSampo took 11.8330819606781s
Accuracy | Check White space in annotation for WarSampo took 2.3523504734039307s
Accuracy | Check Datatype consistency for WarSampo took 5.643298149108887s
Consistency | Disjoint class check for WarSampo took 0.17271685600280762s
Consistency | Check Misplaced properties for WarSampo took 20.00338625907898s
Consistency | Check Ontology hijacking for WarSampo took 21.021989345550537s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.4527106285095215s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.6967737674713135s
Conciseness | Check Extensional conciseness for WarSampo took 2.8402140140533447s
Conciseness | Check Intensional conciseness for WarSampo took 0.2576146125793457s
Security | Sign check for WarSampo took 0.16699481010437012s
Availability | Check URIs Dereferenciability for WarSampo took 2.7567503452301025s
Completeness | Calculation of interlinking completeness for WarSampo took 0.9519107341766357s
Reputation | Calculation of the PageRank for WarSampo took 0.02146005630493164s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for WarSampo took 9.918212890625e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 2.1457672119140625e-06s
Believability | Calculation of trust value for WarSampo took 1.0251998901367188e-05s
INFO | --- Analysis for warsampo took 996.3615741729736s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 0.29852890968322754s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0002624988555908203s
Extra | Recovery of all triples for WASABI RDF Knowledge Graph took 2.5426485538482666s
Performance | Total latancy measurement for WASABI RDF Knowledge Graph took 0.38341236114501953s
Amount of data | Number of triples check for WASABI RDF Knowledge Graph took 105.44192147254944s
Interoperability | New terms check for WASABI RDF Knowledge Graph took 2.4785375595092773s
Versatility | Languages check for WASABI RDF Knowledge Graph took 300.1037721633911s
Interpretability | Number of blank nodes check for WASABI RDF Knowledge Graph took 95.13950943946838s
Interpretability | RDF structures check for WASABI RDF Knowledge Graph took 0.11142873764038086s
Versatility | Serialization formats check for WASABI RDF Knowledge Graph took 0.14512133598327637s
Availability | RDF dump link check for WASABI RDF Knowledge Graph took 12.920418739318848s
License | MR license check for WASABI RDF Knowledge Graph took 0.18513226509094238s
License | HR license check for WASABI RDF Knowledge Graph took 300.03171157836914s
Amount of data | Number of property check for WASABI RDF Knowledge Graph took 0.11282515525817871s
Understandability | Number of label check for WASABI RDF Knowledge Graph took 3.8037474155426025s
Understandability | URI regex check for WASABI RDF Knowledge Graph took 0.2242131233215332s
Understandability | Vocabs check for WASABI RDF Knowledge Graph took 0.07920050621032715s
Verifiability | Authors check for WASABI RDF Knowledge Graph took 0.08063316345214844s
Verifiability | Publishers check for WASABI RDF Knowledge Graph took 0.0700690746307373s
Performance | Throughput check for WASABI RDF Knowledge Graph took 10.463892936706543s
Amount of data | Check the number of entities for WASABI RDF Knowledge Graph took 0.11301922798156738s
Verifiability | Contribs. check for WASABI RDF Knowledge Graph took 0.11851739883422852s
Interlinking | sameAs chians check for WASABI RDF Knowledge Graph took 0.08976912498474121s
Interlinking | skos check for WASABI RDF Knowledge Graph took 0.07178378105163574s
Interlinking | skos check for WASABI RDF Knowledge Graph took 0.07742905616760254s
Timeliness | dataset update frequency check for WASABI RDF Knowledge Graph took 0.29511547088623047s
Currency | Creation date check for WASABI RDF Knowledge Graph took 0.15125012397766113s
Currency | Modification date check for WASABI RDF Knowledge Graph took 0.15935444831848145s
Rep.Conc. | URIs length for WASABI RDF Knowledge Graph took 61.266812562942505s
Interoperability | New vocabularies check for WASABI RDF Knowledge Graph took 11.332453727722168s
Consistency | Deprecated classes/propertiers check for WASABI RDF Knowledge Graph took 0.07088351249694824s
Accuracy | Check Functional Property for WASABI RDF Knowledge Graph took 0.22371411323547363s
Accuracy | Check Inverse Functional Property for WASABI RDF Knowledge Graph took 0.22282648086547852s
Accuracy | Check Empty annotation labels for WASABI RDF Knowledge Graph took 1.1025416851043701s
Accuracy | Check White space in annotation for WASABI RDF Knowledge Graph took 0.0841379165649414s
Accuracy | Check Datatype consistency for WASABI RDF Knowledge Graph took 0.08789300918579102s
Consistency | Disjoint class check for WASABI RDF Knowledge Graph took 0.07649683952331543s
Consistency | Check Misplaced properties for WASABI RDF Knowledge Graph took 54.372193813323975s
Consistency | Misplaced classes for WASABI RDF Knowledge Graph took 1.4174020290374756s
Consistency | Check Ontology hijacking for WASABI RDF Knowledge Graph took 2.937592029571533s
Consistency | Check Invalid usage of undefined classes for WASABI RDF Knowledge Graph took 1.9749350547790527s
Consistency | Check Invalid usage of undefined properties for WASABI RDF Knowledge Graph took 33.221014976501465s
Conciseness | Check Extensional conciseness for WASABI RDF Knowledge Graph took 0.09669351577758789s
Conciseness | Check Intensional conciseness for WASABI RDF Knowledge Graph took 1.314901351928711s
Security | Sign check for WASABI RDF Knowledge Graph took 0.3461112976074219s
Availability | Check URIs Dereferenciability for WASABI RDF Knowledge Graph took 20.68097686767578s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 1.654059648513794s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.021733999252319336s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0008187294006347656s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 0.00010991096496582031s
Interoperability | Check the re-using of existing vocabs for WASABI RDF Knowledge Graph took 10.419552326202393s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 7.62939453125e-06s
INFO | --- Analysis for wasabi took 16455.484847307205s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 4.363059997558594e-05s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.2692575454711914s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.021275758743286133s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0008525848388671875s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 3.528594970703125e-05s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for Water_Areas_Classification took 4.209027528762817s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 4.2438507080078125e-05s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.7099406719207764s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.020795345306396484s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0008008480072021484s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 3.457069396972656e-05s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 7.62939453125e-06s
INFO | --- Analysis for Water_Buffer took 3.7640209197998047s
Availability | SPARQL endpoint availability check for WebIsALOD took 4.2438507080078125e-05s
Availability | VoID file availability check for WebIsALOD took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.2662079334259033s
Reputation | Calculation of the PageRank for WebIsALOD took 0.021073102951049805s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 8.487701416015625e-05s
Believability | Calculation of trust value for WebIsALOD took 7.62939453125e-06s
INFO | --- Analysis for webisalod took 3.3217175006866455s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 0.0003974437713623047s
Availability | VoID file availability check for webnmasunotraveler took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.25786900520324707s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.020906925201416016s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 3.9577484130859375e-05s
Believability | Calculation of trust value for webnmasunotraveler took 8.106231689453125e-06s
INFO | --- Analysis for webnmasunotraveler took 2.8054866790771484s
Availability | SPARQL endpoint availability check for Whisky Circle took 4.220008850097656e-05s
Availability | VoID file availability check for Whisky Circle took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.2487938404083252s
Reputation | Calculation of the PageRank for Whisky Circle took 0.020997047424316406s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00014448165893554688s
Believability | Calculation of trust value for Whisky Circle took 7.152557373046875e-06s
INFO | --- Analysis for whisky-circle-info took 2.811702251434326s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.0002884864807128906s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.23744678497314453s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.02069091796875s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0008323192596435547s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 4.076957702636719e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 7.867813110351562e-06s
INFO | --- Analysis for WHOnto took 2.843499183654785s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.26862072944641113s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.020766735076904297s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 3.4332275390625e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for whonto took 2.895451307296753s
Availability | SPARQL endpoint availability check for Wikidata took 4.506111145019531e-05s
Availability | VoID file availability check for Wikidata took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for Wikidata took 0.27303457260131836s
Reputation | Calculation of the PageRank for Wikidata took 0.020832061767578125s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0008571147918701172s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.0003459453582763672s
Believability | Calculation of trust value for Wikidata took 1.1920928955078125e-05s
INFO | --- Analysis for wikidata took 2.887389659881592s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 7.510185241699219e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.2506601810455322s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.020868539810180664s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 7.343292236328125e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 8.344650268554688e-06s
INFO | --- Analysis for wikilinks-rdf-nif took 2.8359599113464355s
Availability | SPARQL endpoint availability check for WikiPathways took 4.100799560546875e-05s
Availability | VoID file availability check for WikiPathways took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.2597010135650635s
Reputation | Calculation of the PageRank for WikiPathways took 0.020660400390625s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 5.2928924560546875e-05s
Believability | Calculation of trust value for WikiPathways took 8.106231689453125e-06s
INFO | --- Analysis for wikipathways took 2.836503505706787s
Availability | SPARQL endpoint availability check for WikiWord Thesaurus Data took 4.315376281738281e-05s
Availability | VoID file availability check for WikiWord Thesaurus Data took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for WikiWord Thesaurus Data took 0.2613072395324707s
Reputation | Calculation of the PageRank for WikiWord Thesaurus Data took 0.020749807357788086s
Interlinking | Calculation of Degree of Connection for WikiWord Thesaurus Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WikiWord Thesaurus Data took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for WikiWord Thesaurus Data took 3.0994415283203125e-05s
Believability | Calculation of trust value for WikiWord Thesaurus Data took 1.2636184692382812e-05s
INFO | --- Analysis for wikiword_thesaurus took 2.871060848236084s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 4.220008850097656e-05s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.24690818786621094s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.02091217041015625s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 9.298324584960938e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 1.2159347534179688e-05s
INFO | --- Analysis for wiktionary-dbpedia-org took 2.7812860012054443s
Availability | SPARQL endpoint availability check for Wings workflow provenance dataset took 4.172325134277344e-05s
Availability | VoID file availability check for Wings workflow provenance dataset took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Wings workflow provenance dataset took 0.23177123069763184s
Reputation | Calculation of the PageRank for Wings workflow provenance dataset took 0.020775556564331055s
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.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Wings workflow provenance dataset took 3.24249267578125e-05s
Believability | Calculation of trust value for Wings workflow provenance dataset took 1.2159347534179688e-05s
INFO | --- Analysis for wings-workflow-provenance-dataset took 2.7497143745422363s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2557544708251953s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.24133658409118652s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.020758628845214844s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.814697265625e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 9.298324584960938e-06s
INFO | --- Analysis for wl-kg took 4.389986753463745s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 7.534027099609375e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.24849605560302734s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.020939111709594727s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 7.414817810058594e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 7.152557373046875e-06s
INFO | --- Analysis for wn-wiki-instances took 2.7834768295288086s
Availability | SPARQL endpoint availability check for World Loanword Database took 6.079673767089844e-05s
Availability | VoID file availability check for World Loanword Database took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.27371644973754883s
Reputation | Calculation of the PageRank for World Loanword Database took 0.020925521850585938s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 7.295608520507812e-05s
Believability | Calculation of trust value for World Loanword Database took 6.67572021484375e-06s
INFO | --- Analysis for wold took 2.774559259414673s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 4.2438507080078125e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.2537059783935547s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.020967960357666016s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 3.314018249511719e-05s
Believability | Calculation of trust value for Wood Trick LLC took 6.4373016357421875e-06s
INFO | --- Analysis for woodtrick took 2.874945640563965s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 4.076957702636719e-05s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.26224589347839355s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for WordFormationLatin took 2.835129737854004s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 4.2438507080078125e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.2827885150909424s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.020823955535888672s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.00010800361633300781s
Believability | Calculation of trust value for WordLift Blog EN took 1.33514404296875e-05s
INFO | --- Analysis for wordlift-io-blog-en took 2.8268320560455322s
Availability | SPARQL endpoint availability check for WordLift IT took 4.2438507080078125e-05s
Availability | VoID file availability check for WordLift IT took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.2548098564147949s
Reputation | Calculation of the PageRank for WordLift IT took 0.020794391632080078s
Interlinking | Calculation of Degree of Connection for WordLift IT took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WordLift IT took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00011658668518066406s
Believability | Calculation of trust value for WordLift IT took 7.152557373046875e-06s
INFO | --- Analysis for wordlift-io-blog-it took 2.8627941608428955s
Availability | SPARQL endpoint availability check for Wordnet took 4.172325134277344e-05s
Availability | VoID file availability check for Wordnet took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Wordnet took 0.23782992362976074s
Reputation | Calculation of the PageRank for Wordnet took 0.0207827091217041s
Interlinking | Calculation of Degree of Connection for Wordnet took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Wordnet took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Wordnet took 4.458427429199219e-05s
Believability | Calculation of trust value for Wordnet took 6.9141387939453125e-06s
INFO | --- Analysis for wordnet took 2.75795316696167s
Availability | SPARQL endpoint availability check for WordNet-RDF took 4.100799560546875e-05s
Availability | VoID file availability check for WordNet-RDF took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.26819443702697754s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.020903587341308594s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.965896606445312e-05s
Believability | Calculation of trust value for WordNet-RDF took 7.3909759521484375e-06s
INFO | --- Analysis for wordnet-rdf took 2.812490224838257s
Availability | SPARQL endpoint availability check for wordpress took 4.4345855712890625e-05s
Availability | VoID file availability check for wordpress took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for wordpress took 0.23548245429992676s
Reputation | Calculation of the PageRank for wordpress took 0.020877599716186523s
Interlinking | Calculation of Degree of Connection for wordpress took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for wordpress took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.869171142578125e-05s
Believability | Calculation of trust value for wordpress took 7.3909759521484375e-06s
INFO | --- Analysis for wordpress took 2.8542168140411377s
Availability | SPARQL endpoint availability check for wordpress.post took 4.100799560546875e-05s
Availability | VoID file availability check for wordpress.post took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for wordpress.post took 0.2523655891418457s
Reputation | Calculation of the PageRank for wordpress.post took 0.020730257034301758s
Interlinking | Calculation of Degree of Connection for wordpress.post took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for wordpress.post took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for wordpress.post took 3.218650817871094e-05s
Believability | Calculation of trust value for wordpress.post took 7.62939453125e-06s
INFO | --- Analysis for wordpress_post took 2.8111753463745117s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 8.988380432128906e-05s
Availability | VoID file availability check for World Bank Linked Data took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.25641632080078125s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.02073049545288086s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.0001277923583984375s
Believability | Calculation of trust value for World Bank Linked Data took 1.2159347534179688e-05s
INFO | --- Analysis for world-bank-linked-data took 2.8180408477783203s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 4.267692565917969e-05s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.24848604202270508s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.020672321319580078s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 9.059906005859375e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 6.67572021484375e-06s
INFO | --- Analysis for world-factbook-fu-berlin took 2.79407000541687s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 4.1484832763671875e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.24860048294067383s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.020819902420043945s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 9.036064147949219e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 1.1682510375976562e-05s
INFO | --- Analysis for world-wide-web-foundation took 2.925391674041748s
Availability | SPARQL endpoint availability check for WikiPathways took 6.508827209472656e-05s
Availability | VoID file availability check for WikiPathways took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.2540171146392822s
Reputation | Calculation of the PageRank for WikiPathways took 0.02091836929321289s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 3.266334533691406e-05s
Believability | Calculation of trust value for WikiPathways took 6.9141387939453125e-06s
INFO | --- Analysis for wp took 2.821751117706299s
Availability | SPARQL endpoint availability check for wunderground.weatherreport took 4.4345855712890625e-05s
Availability | VoID file availability check for wunderground.weatherreport took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for wunderground.weatherreport took 0.25063061714172363s
Reputation | Calculation of the PageRank for wunderground.weatherreport took 0.021436691284179688s
Interlinking | Calculation of Degree of Connection for wunderground.weatherreport took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for wunderground.weatherreport took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for wunderground.weatherreport took 3.647804260253906e-05s
Believability | Calculation of trust value for wunderground.weatherreport took 7.152557373046875e-06s
INFO | --- Analysis for wunderground_weatherreport took 2.7474923133850098s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.3213956356048584s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0002772808074951172s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 2.6003472805023193s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.833345890045166s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.22458124160766602s
Interoperability | New terms check for World War 1 as Linked Open Data took 2.476613759994507s
Versatility | Languages check for World War 1 as Linked Open Data took 0.4411444664001465s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.21500802040100098s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.42947840690612793s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.43724989891052246s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.3201735019683838s
Availability | RDF dump link check for World War 1 as Linked Open Data took 4.953898668289185s
License | MR license check for World War 1 as Linked Open Data took 0.1702744960784912s
License | HR license check for World War 1 as Linked Open Data took 1.6047160625457764s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.15690946578979492s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.732701301574707s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.3722066879272461s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.21155953407287598s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.17225241661071777s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.18100953102111816s
Performance | Throughput check for World War 1 as Linked Open Data took 10.892901182174683s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.07938337326049805s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.18250679969787598s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.2155132293701172s
Interlinking | skos check for World War 1 as Linked Open Data took 0.17281842231750488s
Interlinking | skos check for World War 1 as Linked Open Data took 0.16892623901367188s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.26534056663513184s
Currency | Creation date check for World War 1 as Linked Open Data took 0.32771754264831543s
Currency | Modification date check for World War 1 as Linked Open Data took 0.16769766807556152s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 1.9494330883026123s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 6.770794868469238s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.21240878105163574s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.1714017391204834s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.16605067253112793s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.1666259765625s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.05144143104553223s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.31792521476745605s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.16538166999816895s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.6275858879089355s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.067653179168701s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.348602056503296s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.6718881130218506s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.20038223266601562s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.7761931419372559s
Security | Sign check for World War 1 as Linked Open Data took 0.18334412574768066s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 7.086106300354004s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.2640209197998047s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.020979642868041992s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 8.988380432128906e-05s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 6.848368883132935s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 1.3113021850585938e-05s
INFO | --- Analysis for ww1lod took 97.13306522369385s
Availability | SPARQL endpoint availability check for XlendiAmphorae took 4.38690185546875e-05s
Availability | VoID file availability check for XlendiAmphorae took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for XlendiAmphorae took 0.27576518058776855s
Reputation | Calculation of the PageRank for XlendiAmphorae took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for XlendiAmphorae took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for XlendiAmphorae took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for XlendiAmphorae took 3.337860107421875e-05s
Believability | Calculation of trust value for XlendiAmphorae took 7.867813110351562e-06s
INFO | --- Analysis for xlendiamphorae took 2.882469654083252s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 4.291534423828125e-05s
Availability | VoID file availability check for xLiD-Lexica took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.2772970199584961s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.02080559730529785s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 7.581710815429688e-05s
Believability | Calculation of trust value for xLiD-Lexica took 7.3909759521484375e-06s
INFO | --- Analysis for xlid-lexica took 2.8434929847717285s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 4.267692565917969e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.26245641708374023s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.020808696746826172s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 4.100799560546875e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 8.106231689453125e-06s
INFO | --- Analysis for xwn took 2.90324330329895s
Availability | SPARQL endpoint availability check for xxx took 4.291534423828125e-05s
Availability | VoID file availability check for xxx took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for xxx took 0.23700308799743652s
Reputation | Calculation of the PageRank for xxx took 0.020877838134765625s
Interlinking | Calculation of Degree of Connection for xxx took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for xxx took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for xxx took 3.409385681152344e-05s
Believability | Calculation of trust value for xxx took 8.106231689453125e-06s
INFO | --- Analysis for xx took 2.7744970321655273s
Availability | SPARQL endpoint availability check for YAGO took 4.363059997558594e-05s
Availability | VoID file availability check for YAGO took 0.0003159046173095703s
Completeness | Calculation of interlinking completeness for YAGO took 0.27372312545776367s
Reputation | Calculation of the PageRank for YAGO took 0.020800113677978516s
Interlinking | Calculation of Degree of Connection for YAGO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.0001590251922607422s
Believability | Calculation of trust value for YAGO took 8.344650268554688e-06s
INFO | --- Analysis for yago took 2.866229772567749s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 4.2438507080078125e-05s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.26972484588623047s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.02354145050048828s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.001104593276977539s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 0.0001049041748046875s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 7.867813110351562e-06s
INFO | --- Analysis for yahoo_geoplanet took 2.911776065826416s
Availability | SPARQL endpoint availability check for Yale Senselab took 4.1484832763671875e-05s
Availability | VoID file availability check for Yale Senselab took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.25610780715942383s
Reputation | Calculation of the PageRank for Yale Senselab took 0.02090740203857422s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 3.3855438232421875e-05s
Believability | Calculation of trust value for Yale Senselab took 7.62939453125e-06s
INFO | --- Analysis for yale_senselab took 2.840985059738159s
Availability | SPARQL endpoint availability check for test-dapp-2 took 4.291534423828125e-05s
Availability | VoID file availability check for test-dapp-2 took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.24335622787475586s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 3.147125244140625e-05s
Believability | Calculation of trust value for test-dapp-2 took 8.106231689453125e-06s
INFO | --- Analysis for yordhis took 2.8185513019561768s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 4.8160552978515625e-05s
Availability | VoID file availability check for Yovisto - academic video search took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.2586047649383545s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.020658254623413086s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 7.462501525878906e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 8.344650268554688e-06s
INFO | --- Analysis for yovisto took 2.824443817138672s
Availability | SPARQL endpoint availability check for Yleinen suomalainen asiasanasto - YSA took 4.553794860839844e-05s
Availability | VoID file availability check for Yleinen suomalainen asiasanasto - YSA took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Yleinen suomalainen asiasanasto - YSA took 0.24570083618164062s
Reputation | Calculation of the PageRank for Yleinen suomalainen asiasanasto - YSA took 0.020769357681274414s
Interlinking | Calculation of Degree of Connection for Yleinen suomalainen asiasanasto - YSA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Yleinen suomalainen asiasanasto - YSA took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Yleinen suomalainen asiasanasto - YSA took 3.695487976074219e-05s
Believability | Calculation of trust value for Yleinen suomalainen asiasanasto - YSA took 7.62939453125e-06s
INFO | --- Analysis for ysa took 2.767850875854492s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.00036334991455078125s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.2323765754699707s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 6.151199340820312e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for yso took 2.798175573348999s
Availability | SPARQL endpoint availability check for yso-fi-allars took 4.315376281738281e-05s
Availability | VoID file availability check for yso-fi-allars took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.2637059688568115s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.020933866500854492s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.719329833984375e-05s
Believability | Calculation of trust value for yso-fi-allars took 7.867813110351562e-06s
INFO | --- Analysis for yso-fi-allars took 2.7841742038726807s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 4.458427429199219e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.2743566036224365s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.020725727081298828s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.695487976074219e-05s
Believability | Calculation of trust value for yso-fi-ysa took 7.62939453125e-06s
INFO | --- Analysis for yso-fi-ysa took 2.8725392818450928s
Availability | SPARQL endpoint availability check for YSO places took 4.315376281738281e-05s
Availability | VoID file availability check for YSO places took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for YSO places took 0.2781059741973877s
Reputation | Calculation of the PageRank for YSO places took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for YSO places took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for YSO places took 0.0008132457733154297s
Interlinking | Calculation of Clustering coefficient for YSO places took 3.409385681152344e-05s
Believability | Calculation of trust value for YSO places took 1.2159347534179688e-05s
INFO | --- Analysis for yso-paikat took 2.8404033184051514s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 4.363059997558594e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.00029468536376953125s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.26811981201171875s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.790855407714844e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 1.2159347534179688e-05s
INFO | --- Analysis for zaragoza-datosabiertos took 2.869340181350708s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 4.410743713378906e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.2721095085144043s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.02150440216064453s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 4.220008850097656e-05s
Believability | Calculation of trust value for zaragoza_turruta took 1.4543533325195312e-05s
INFO | --- Analysis for zaragoza_turruta took 2.8609437942504883s
Availability | SPARQL endpoint availability check for ZBW Labs took 4.3392181396484375e-05s
Availability | VoID file availability check for ZBW Labs took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.2522578239440918s
Reputation | Calculation of the PageRank for ZBW Labs took 0.020978927612304688s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 7.128715515136719e-05s
Believability | Calculation of trust value for ZBW Labs took 8.58306884765625e-06s
INFO | --- Analysis for zbw-labs took 2.903701066970825s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.2877311706542969s
Availability | VoID file availability check for 20th Century Press Archives took 0.00028967857360839844s
Extra | Recovery of all triples for 20th Century Press Archives took 26.907286643981934s
Performance | Total latancy measurement for 20th Century Press Archives took 0.7931222915649414s
Amount of data | Number of triples check for 20th Century Press Archives took 2.1719672679901123s
Interoperability | New terms check for 20th Century Press Archives took 2.0150020122528076s
Versatility | Languages check for 20th Century Press Archives took 5.88241982460022s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.8458316326141357s
Interpretability | RDF structures check for 20th Century Press Archives took 0.18398308753967285s
Versatility | Serialization formats check for 20th Century Press Archives took 0.17173242568969727s
Availability | RDF dump link check for 20th Century Press Archives took 0.13347077369689941s
License | MR license check for 20th Century Press Archives took 0.1575334072113037s
License | HR license check for 20th Century Press Archives took 5.6865222454071045s
Amount of data | Number of property check for 20th Century Press Archives took 0.1718614101409912s
Understandability | Number of label check for 20th Century Press Archives took 0.5593023300170898s
Understandability | URI regex check for 20th Century Press Archives took 0.29637885093688965s
Understandability | Vocabs check for 20th Century Press Archives took 0.15494346618652344s
Verifiability | Authors check for 20th Century Press Archives took 0.17218589782714844s
Verifiability | Publishers check for 20th Century Press Archives took 0.14879059791564941s
Performance | Throughput check for 20th Century Press Archives took 10.688787698745728s
Amount of data | Check the number of entities for 20th Century Press Archives took 7.343292236328125e-05s
Verifiability | Contribs. check for 20th Century Press Archives took 0.15073633193969727s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.13539719581604004s
Interlinking | skos check for 20th Century Press Archives took 0.21959280967712402s
Interlinking | skos check for 20th Century Press Archives took 0.19310617446899414s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.14168596267700195s
Currency | Creation date check for 20th Century Press Archives took 0.30858540534973145s
Currency | Modification date check for 20th Century Press Archives took 0.29575061798095703s
Rep.Conc. | URIs length for 20th Century Press Archives took 15.96991753578186s
Interoperability | New vocabularies check for 20th Century Press Archives took 1.239776611328125e-05s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.14120221138000488s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.18112778663635254s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.1505284309387207s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 4.59557032585144s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8709001541137695s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.323541164398193s
Consistency | Disjoint class check for 20th Century Press Archives took 0.1750185489654541s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.2611567974090576s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.433992385864258s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 7.779726266860962s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.620488405227661s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.8116939067840576s
Security | Sign check for 20th Century Press Archives took 0.15885233879089355s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 950.9625217914581s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 1.3632149696350098s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.021467924118041992s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 3.170967102050781e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00011539459228515625s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 2.6226043701171875e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 7.62939453125e-06s
INFO | --- Analysis for zbw-pressemappe20 took 1075.2667298316956s
Availability | SPARQL endpoint availability check for zhishi.lemon took 7.152557373046875e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.25861668586730957s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.020965099334716797s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 4.9591064453125e-05s
Believability | Calculation of trust value for zhishi.lemon took 5.9604644775390625e-06s
INFO | --- Analysis for zhishi-lemon took 3.2871458530426025s
Availability | SPARQL endpoint availability check for Zhishi.me took 4.267692565917969e-05s
Availability | VoID file availability check for Zhishi.me took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.24823713302612305s
Reputation | Calculation of the PageRank for Zhishi.me took 0.0210416316986084s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 7.319450378417969e-05s
Believability | Calculation of trust value for Zhishi.me took 7.152557373046875e-06s
INFO | --- Analysis for zhishi-me took 3.359358310699463s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.482269287109375e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.2620360851287842s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.021209239959716797s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 6.842613220214844e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 7.3909759521484375e-06s
INFO | --- Analysis for zitgist-musicbrainz took 2.8314576148986816s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 4.363059997558594e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.2672724723815918s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.02083420753479004s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 3.266334533691406e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 8.821487426757812e-06s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 2.89245867729187s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.33658409118652344s
Availability | VoID file availability check for performing-arts.ch took 0.0005431175231933594s
Extra | Recovery of all triples for performing-arts.ch took 19.921709537506104s
Performance | Total latancy measurement for performing-arts.ch took 0.7577545642852783s
Amount of data | Number of triples check for performing-arts.ch took 54.192652463912964s
Interoperability | New terms check for performing-arts.ch took 1.7269444465637207s
Versatility | Languages check for performing-arts.ch took 60.12615728378296s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.14889144897461s
Interpretability | RDF structures check for performing-arts.ch took 0.19864845275878906s
Versatility | Serialization formats check for performing-arts.ch took 0.19488525390625s
Availability | RDF dump link check for performing-arts.ch took 0.15311074256896973s
License | MR license check for performing-arts.ch took 0.7807855606079102s
License | HR license check for performing-arts.ch took 41.87793016433716s
Amount of data | Number of property check for performing-arts.ch took 0.16237163543701172s
Understandability | Number of label check for performing-arts.ch took 6.266831159591675s
Understandability | URI regex check for performing-arts.ch took 0.2909255027770996s
Understandability | Vocabs check for performing-arts.ch took 0.17356657981872559s
Verifiability | Authors check for performing-arts.ch took 0.17111945152282715s
Verifiability | Publishers check for performing-arts.ch took 0.1683962345123291s
Performance | Throughput check for performing-arts.ch took 10.851784229278564s
Amount of data | Check the number of entities for performing-arts.ch took 7.772445678710938e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.14847278594970703s
Interlinking | sameAs chians check for performing-arts.ch took 0.6728215217590332s
Interlinking | skos check for performing-arts.ch took 0.1771376132965088s
Interlinking | skos check for performing-arts.ch took 0.16806530952453613s
Timeliness | dataset update frequency check for performing-arts.ch took 0.16091609001159668s
Currency | Creation date check for performing-arts.ch took 0.33916354179382324s
Currency | Modification date check for performing-arts.ch took 0.319415807723999s
Rep.Conc. | URIs length for performing-arts.ch took 26.41346311569214s
Interoperability | New vocabularies check for performing-arts.ch took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.17218756675720215s
Accuracy | Check Functional Property for performing-arts.ch took 0.17024731636047363s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.15698790550231934s
Accuracy | Check Empty annotation labels for performing-arts.ch took 11.802209615707397s
Accuracy | Check White space in annotation for performing-arts.ch took 2.5331532955169678s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.879494667053223s
Consistency | Disjoint class check for performing-arts.ch took 0.189422607421875s
Consistency | Check Misplaced properties for performing-arts.ch took 0.34166932106018066s
Consistency | Misplaced classes for performing-arts.ch took 8.534969806671143s
Consistency | Check Ontology hijacking for performing-arts.ch took 50.354912519454956s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 19092.278293848038s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.9828252792358398s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.933175802230835s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.36055731773376465s
Security | Sign check for performing-arts.ch took 0.14659619331359863s
Availability | Check URIs Dereferenciability for performing-arts.ch took 5.085811614990234s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 1.5667974948883057s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.02132701873779297s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 2.4318695068359375e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 2.384185791015625e-06s
Believability | Calculation of trust value for performing-arts.ch took 1.2159347534179688e-05s
INFO | --- Analysis for performing-arts.ch took 19831.599078178406s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.5397918224334717s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.33678197860717773s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.4066696166992188e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for The-AA-Thesaurus took 10.39048147201538s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.459435224533081s
Availability | VoID file availability check for MiMoTextBase took 0.0004169940948486328s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.2588634490966797s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.4543533325195312e-05s
Believability | Calculation of trust value for MiMoTextBase took 7.867813110351562e-06s
INFO | --- Analysis for MiMoTextBase took 8.031753778457642s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.48737359046936035s
Availability | VoID file availability check for National Library of Sweden took 0.0004203319549560547s
Extra | Recovery of all triples for National Library of Sweden took 5.539072275161743s
Performance | Total latancy measurement for National Library of Sweden took 1.073035717010498s
Amount of data | Number of triples check for National Library of Sweden took 25.087146282196045s
Interoperability | New terms check for National Library of Sweden took 15.253932476043701s
Versatility | Languages check for National Library of Sweden took 0.22171354293823242s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.1916582584381s
Interpretability | RDF structures check for National Library of Sweden took 0.22470831871032715s
Versatility | Serialization formats check for National Library of Sweden took 0.22546076774597168s
Availability | RDF dump link check for National Library of Sweden took 0.22338652610778809s
License | MR license check for National Library of Sweden took 0.22312617301940918s
License | HR license check for National Library of Sweden took 0.2128129005432129s
Amount of data | Number of property check for National Library of Sweden took 0.21406245231628418s
Understandability | Number of label check for National Library of Sweden took 0.2137436866760254s
Understandability | URI regex check for National Library of Sweden took 0.4352083206176758s
Understandability | Vocabs check for National Library of Sweden took 0.21138906478881836s
Verifiability | Authors check for National Library of Sweden took 0.202409029006958s
Verifiability | Publishers check for National Library of Sweden took 0.21306777000427246s
Performance | Throughput check for National Library of Sweden took 10.713730096817017s
Amount of data | Check the number of entities for National Library of Sweden took 7.200241088867188e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.21261096000671387s
Interlinking | sameAs chians check for National Library of Sweden took 0.21303582191467285s
Interlinking | skos check for National Library of Sweden took 0.20194673538208008s
Interlinking | skos check for National Library of Sweden took 0.19997525215148926s
Timeliness | dataset update frequency check for National Library of Sweden took 0.21338891983032227s
Currency | Creation date check for National Library of Sweden took 0.451153039932251s
Currency | Modification date check for National Library of Sweden took 0.42759037017822266s
Rep.Conc. | URIs length for National Library of Sweden took 81.10079097747803s
Interoperability | New vocabularies check for National Library of Sweden took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.22461247444152832s
Accuracy | Check Functional Property for National Library of Sweden took 0.21195697784423828s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.22347760200500488s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.27609753608703613s
Consistency | Disjoint class check for National Library of Sweden took 0.20107626914978027s
Consistency | Check Misplaced properties for National Library of Sweden took 62.05568051338196s
Consistency | Misplaced classes for National Library of Sweden took 1.178255319595337s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.343534231185913s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.3723623752593994s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 63.37923979759216s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.2951018810272217s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.38443589210510254s
Security | Sign check for National Library of Sweden took 0.210341215133667s
Availability | Check URIs Dereferenciability for National Library of Sweden took 14.796634435653687s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 1.6230642795562744s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.000675201416015625s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.8358230590820312e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.3113021850585938e-05s
INFO | --- Analysis for NLS took 1382.7979984283447s
Availability | SPARQL endpoint availability check for Japan Search took 1.6732456684112549s
Availability | VoID file availability check for Japan Search took 0.0002815723419189453s
Extra | Recovery of all triples for Japan Search took 3.7417666912078857s
Performance | Total latancy measurement for Japan Search took 2.165550470352173s
Amount of data | Number of triples check for Japan Search took 5.74377703666687s
Interoperability | New terms check for Japan Search took 3.8039116859436035s
Versatility | Languages check for Japan Search took 0.7274346351623535s
Interpretability | Number of blank nodes check for Japan Search took 10.290647029876709s
Interpretability | RDF structures check for Japan Search took 0.49681591987609863s
Versatility | Serialization formats check for Japan Search took 0.44585156440734863s
Availability | RDF dump link check for Japan Search took 0.3148198127746582s
License | MR license check for Japan Search took 1.0643670558929443s
License | HR license check for Japan Search took 10.271449565887451s
Amount of data | Number of property check for Japan Search took 0.8072075843811035s
Understandability | Number of label check for Japan Search took 2.734065294265747s
Understandability | URI regex check for Japan Search took 0.5775527954101562s
Understandability | Vocabs check for Japan Search took 0.309600830078125s
Verifiability | Authors check for Japan Search took 0.30878210067749023s
Verifiability | Publishers check for Japan Search took 0.7422740459442139s
Performance | Throughput check for Japan Search took 11.457525491714478s
Amount of data | Check the number of entities for Japan Search took 0.00010561943054199219s
Verifiability | Contribs. check for Japan Search took 0.2824826240539551s
Interlinking | sameAs chians check for Japan Search took 0.28479862213134766s
Interlinking | skos check for Japan Search took 0.2961583137512207s
Interlinking | skos check for Japan Search took 0.2831296920776367s
Timeliness | dataset update frequency check for Japan Search took 0.348679780960083s
Currency | Creation date check for Japan Search took 0.5222084522247314s
Currency | Modification date check for Japan Search took 0.5886073112487793s
Rep.Conc. | URIs length for Japan Search took 13.693042278289795s
Interoperability | New vocabularies check for Japan Search took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.2844524383544922s
Accuracy | Check Empty annotation labels for Japan Search took 2.1834092140197754s
Accuracy | Check White space in annotation for Japan Search took 0.029332637786865234s
Accuracy | Check Datatype consistency for Japan Search took 0.029929399490356445s
Consistency | Disjoint class check for Japan Search took 0.25888514518737793s
Consistency | Check Misplaced properties for Japan Search took 10.58483338356018s
Consistency | Misplaced classes for Japan Search took 1.0734703540802002s
Consistency | Check Ontology hijacking for Japan Search took 1.7143220901489258s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.3120713233947754s
Consistency | Check Invalid usage of undefined properties for Japan Search took 12.721766471862793s
Conciseness | Check Extensional conciseness for Japan Search took 0.03771710395812988s
Conciseness | Check Intensional conciseness for Japan Search took 0.9955432415008545s
Security | Sign check for Japan Search took 0.28667187690734863s
Availability | Check URIs Dereferenciability for Japan Search took 13.172425031661987s
Completeness | Calculation of interlinking completeness for Japan Search took 0.8484976291656494s
Reputation | Calculation of the PageRank for Japan Search took 0.021294116973876953s
Interlinking | Calculation of Degree of Connection for Japan Search took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Japan Search took 1.4781951904296875e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 2.1457672119140625e-06s
Believability | Calculation of trust value for Japan Search took 8.106231689453125e-06s
INFO | --- Analysis for Japan-Search took 401.10798168182373s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.3082613945007324s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0002987384796142578s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.25139927864074707s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.021225690841674805s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0008366107940673828s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.5020370483398438e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 7.867813110351562e-06s
INFO | --- Analysis for Rijksmuseum took 5.440024375915527s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.5439503192901611s
Availability | VoID file availability check for Finnish Public Libraries took 0.0006847381591796875s
Extra | Recovery of all triples for Finnish Public Libraries took 16.90146517753601s
Performance | Total latancy measurement for Finnish Public Libraries took 1.9095325469970703s
Amount of data | Number of triples check for Finnish Public Libraries took 60.25485610961914s
Interoperability | New terms check for Finnish Public Libraries took 16.657039165496826s
Versatility | Languages check for Finnish Public Libraries took 60.23457670211792s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 60.33942532539368s
Interpretability | RDF structures check for Finnish Public Libraries took 0.24589300155639648s
Versatility | Serialization formats check for Finnish Public Libraries took 0.26117396354675293s
Availability | RDF dump link check for Finnish Public Libraries took 0.30779123306274414s
License | MR license check for Finnish Public Libraries took 0.24058151245117188s
License | HR license check for Finnish Public Libraries took 55.87690496444702s
Amount of data | Number of property check for Finnish Public Libraries took 0.37316107749938965s
Understandability | Number of label check for Finnish Public Libraries took 14.98980164527893s
Understandability | URI regex check for Finnish Public Libraries took 0.4560270309448242s
Understandability | Vocabs check for Finnish Public Libraries took 0.31572532653808594s
Verifiability | Authors check for Finnish Public Libraries took 0.34833240509033203s
Verifiability | Publishers check for Finnish Public Libraries took 0.23813796043395996s
Performance | Throughput check for Finnish Public Libraries took 11.058476448059082s
Amount of data | Check the number of entities for Finnish Public Libraries took 7.009506225585938e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.13388657569885254s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.3160524368286133s
Interlinking | skos check for Finnish Public Libraries took 0.23903822898864746s
Interlinking | skos check for Finnish Public Libraries took 0.1215507984161377s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.2609982490539551s
Currency | Creation date check for Finnish Public Libraries took 0.3744087219238281s
Currency | Modification date check for Finnish Public Libraries took 0.22880220413208008s
Rep.Conc. | URIs length for Finnish Public Libraries took 84.12224555015564s
Interoperability | New vocabularies check for Finnish Public Libraries took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.23997259140014648s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 9.305236339569092s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.175835371017456s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.306697845458984s
Consistency | Disjoint class check for Finnish Public Libraries took 0.10814142227172852s
Consistency | Check Misplaced properties for Finnish Public Libraries took 60.645349740982056s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 17.607563257217407s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.6099450588226318s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 61.754581928253174s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.7661898136138916s
Security | Sign check for Finnish Public Libraries took 0.3620929718017578s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 1.194657564163208s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 1.3956232070922852s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.021596908569335938s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.4781951904296875e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 1.9073486328125e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 8.344650268554688e-06s
INFO | --- Analysis for FI-Library took 690.218501329422s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 3.904653549194336s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.25817346572875977s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.021439790725708008s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.9550323486328125e-05s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 7.62939453125e-06s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 8.87713623046875s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.844008445739746s
Availability | VoID file availability check for National Library Netherlands took 0.0005824565887451172s
Extra | Recovery of all triples for National Library Netherlands took 0.6614012718200684s
Performance | Total latancy measurement for National Library Netherlands took 0.8585367202758789s
Amount of data | Number of triples check for National Library Netherlands took 0.1503145694732666s
Interoperability | New terms check for National Library Netherlands took 1.458136796951294s
Versatility | Languages check for National Library Netherlands took 58.14384865760803s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.16739130020141602s
Interpretability | RDF structures check for National Library Netherlands took 0.16801142692565918s
Versatility | Serialization formats check for National Library Netherlands took 0.16660356521606445s
Availability | RDF dump link check for National Library Netherlands took 0.2310945987701416s
License | MR license check for National Library Netherlands took 0.15000319480895996s
License | HR license check for National Library Netherlands took 0.19067120552062988s
Amount of data | Number of property check for National Library Netherlands took 0.16986823081970215s
Understandability | Number of label check for National Library Netherlands took 0.16826534271240234s
Understandability | URI regex check for National Library Netherlands took 0.32150816917419434s
Understandability | Vocabs check for National Library Netherlands took 0.15047907829284668s
Verifiability | Authors check for National Library Netherlands took 0.2135601043701172s
Verifiability | Publishers check for National Library Netherlands took 0.14821076393127441s
Performance | Throughput check for National Library Netherlands took 10.999639749526978s
Amount of data | Check the number of entities for National Library Netherlands took 3.600120544433594e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.17153382301330566s
Interlinking | sameAs chians check for National Library Netherlands took 0.14821529388427734s
Interlinking | skos check for National Library Netherlands took 0.1646735668182373s
Interlinking | skos check for National Library Netherlands took 0.15828299522399902s
Timeliness | dataset update frequency check for National Library Netherlands took 0.1589205265045166s
Currency | Creation date check for National Library Netherlands took 0.3148314952850342s
Currency | Modification date check for National Library Netherlands took 0.3140120506286621s
Rep.Conc. | URIs length for National Library Netherlands took 0.6454463005065918s
Interoperability | New vocabularies check for National Library Netherlands took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.16770315170288086s
Accuracy | Check Functional Property for National Library Netherlands took 0.13612866401672363s
Accuracy | Check Inverse Functional Property for National Library Netherlands took 0.17074990272521973s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.41109657287597656s
Accuracy | Check White space in annotation for National Library Netherlands took 0.026602506637573242s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.02989649772644043s
Consistency | Disjoint class check for National Library Netherlands took 0.16491246223449707s
Consistency | Check Misplaced properties for National Library Netherlands took 0.3201601505279541s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.8152475357055664s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 2.3071343898773193s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.5275096893310547s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.03677797317504883s
Security | Sign check for National Library Netherlands took 0.1468183994293213s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1874.8718461990356s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.8830881118774414s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 2.8848648071289062e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 3.123283386230469e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Library Netherlands took 7.3909759521484375e-06s
INFO | --- Analysis for National-Library-Netherlands took 1986.8229973316193s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 3.2151834964752197s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.001272439956665039s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.2536582946777344s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.02106475830078125s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.3828277587890625e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 9.298324584960938e-06s
INFO | --- Analysis for Antique-Renaissance took 8.000399351119995s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 5.334194660186768s
Availability | VoID file availability check for ARTSDATA.CA took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.26531410217285156s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.33514404296875e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 8.106231689453125e-06s
INFO | --- Analysis for ARTSDATA-CA took 10.8826425075531s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.17631745338439941s
Availability | VoID file availability check for Architecture of Knowledge took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.2641158103942871s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.021382570266723633s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.2636184692382812e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 7.3909759521484375e-06s
INFO | --- Analysis for ArCo took 4.771606206893921s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.818103551864624s
Availability | VoID file availability check for ConfermentSampo took 0.00027108192443847656s
Extra | Recovery of all triples for ConfermentSampo took 27.483391761779785s
Performance | Total latancy measurement for ConfermentSampo took 0.8644301891326904s
Amount of data | Number of triples check for ConfermentSampo took 15.542810440063477s
Interoperability | New terms check for ConfermentSampo took 4.5092949867248535s
Versatility | Languages check for ConfermentSampo took 25.212578058242798s
Interpretability | Number of blank nodes check for ConfermentSampo took 7.696412086486816s
Security | Check HTTPS for ConfermentSampo took 0.4357895851135254s
Interpretability | RDF structures check for ConfermentSampo took 0.21236181259155273s
Versatility | Serialization formats check for ConfermentSampo took 0.1830136775970459s
Availability | RDF dump link check for ConfermentSampo took 3.2095141410827637s
License | MR license check for ConfermentSampo took 0.17830348014831543s
License | HR license check for ConfermentSampo took 0.265408992767334s
Amount of data | Number of property check for ConfermentSampo took 0.1611936092376709s
Understandability | Number of label check for ConfermentSampo took 5.828097343444824s
Understandability | URI regex check for ConfermentSampo took 0.3535337448120117s
Understandability | Vocabs check for ConfermentSampo took 0.1706075668334961s
Verifiability | Authors check for ConfermentSampo took 0.18176817893981934s
Verifiability | Publishers check for ConfermentSampo took 0.16453886032104492s
Performance | Throughput check for ConfermentSampo took 10.322716474533081s
Amount of data | Check the number of entities for ConfermentSampo took 4.164079904556274s
Verifiability | Contribs. check for ConfermentSampo took 0.18317747116088867s
Interlinking | sameAs chians check for ConfermentSampo took 1.0111145973205566s
Interlinking | skos check for ConfermentSampo took 0.16928434371948242s
Interlinking | skos check for ConfermentSampo took 0.16826772689819336s
Timeliness | dataset update frequency check for ConfermentSampo took 0.17971444129943848s
Currency | Creation date check for ConfermentSampo took 0.3599672317504883s
Currency | Modification date check for ConfermentSampo took 0.36563587188720703s
Rep.Conc. | URIs length for ConfermentSampo took 34.01859736442566s
Interoperability | New vocabularies check for ConfermentSampo took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.6277484893798828s
Accuracy | Check Functional Property for ConfermentSampo took 0.6340579986572266s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.17522263526916504s
Accuracy | Check Empty annotation labels for ConfermentSampo took 15.422667980194092s
Accuracy | Check White space in annotation for ConfermentSampo took 2.964226722717285s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.417290925979614s
Consistency | Disjoint class check for ConfermentSampo took 0.18005847930908203s
Consistency | Check Misplaced properties for ConfermentSampo took 6.306239128112793s
Consistency | Check Ontology hijacking for ConfermentSampo took 14.524554252624512s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.490544080734253s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.6180081367492676s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.9452531337738037s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.1795792579650879s
Security | Sign check for ConfermentSampo took 0.16774606704711914s
Availability | Check URIs Dereferenciability for ConfermentSampo took 1338.8793532848358s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 1.1788654327392578s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.02094292640686035s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.5974044799804688e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 5.0067901611328125e-06s
Believability | Calculation of trust value for ConfermentSampo took 8.821487426757812e-06s
INFO | --- Analysis for ConfermentSampo took 1665.94473195076s
Availability | SPARQL endpoint availability check for Museum Finland took 0.2596607208251953s
Availability | VoID file availability check for Museum Finland took 0.0002720355987548828s
Extra | Recovery of all triples for Museum Finland took 6.284078359603882s
Performance | Total latancy measurement for Museum Finland took 0.8422961235046387s
Amount of data | Number of triples check for Museum Finland took 0.4683353900909424s
Interoperability | New terms check for Museum Finland took 2.6925134658813477s
Versatility | Languages check for Museum Finland took 0.6630637645721436s
Interpretability | Number of blank nodes check for Museum Finland took 0.39154529571533203s
Security | Check HTTPS for Museum Finland took 0.2638561725616455s
Interpretability | RDF structures check for Museum Finland took 0.7687981128692627s
Versatility | Serialization formats check for Museum Finland took 0.19956088066101074s
Availability | RDF dump link check for Museum Finland took 0.19115090370178223s
License | MR license check for Museum Finland took 0.23059964179992676s
License | HR license check for Museum Finland took 0.528095006942749s
Amount of data | Number of property check for Museum Finland took 0.18157029151916504s
Understandability | Number of label check for Museum Finland took 0.34076356887817383s
Understandability | URI regex check for Museum Finland took 0.3635897636413574s
Understandability | Vocabs check for Museum Finland took 0.1781601905822754s
Verifiability | Authors check for Museum Finland took 0.18070125579833984s
Verifiability | Publishers check for Museum Finland took 0.15816259384155273s
Performance | Throughput check for Museum Finland took 11.243986129760742s
Amount of data | Check the number of entities for Museum Finland took 0.00011396408081054688s
Verifiability | Contribs. check for Museum Finland took 0.18791937828063965s
Interlinking | sameAs chians check for Museum Finland took 0.16530823707580566s
Interlinking | skos check for Museum Finland took 0.17516660690307617s
Interlinking | skos check for Museum Finland took 0.16884827613830566s
Timeliness | dataset update frequency check for Museum Finland took 0.17864489555358887s
Currency | Creation date check for Museum Finland took 0.3488428592681885s
Currency | Modification date check for Museum Finland took 0.42610740661621094s
Rep.Conc. | URIs length for Museum Finland took 3.7302358150482178s
Interoperability | New vocabularies check for Museum Finland took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.16979146003723145s
Accuracy | Check Functional Property for Museum Finland took 0.1795792579650879s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.1572856903076172s
Accuracy | Check Empty annotation labels for Museum Finland took 0.9957683086395264s
Accuracy | Check White space in annotation for Museum Finland took 0.060660600662231445s
Accuracy | Check Datatype consistency for Museum Finland took 0.9995763301849365s
Consistency | Disjoint class check for Museum Finland took 0.17796730995178223s
Consistency | Check Misplaced properties for Museum Finland took 0.6553249359130859s
Consistency | Check Ontology hijacking for Museum Finland took 2.5235466957092285s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.840813398361206s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 2.122178077697754s
Conciseness | Check Extensional conciseness for Museum Finland took 0.7108182907104492s
Conciseness | Check Intensional conciseness for Museum Finland took 0.22362947463989258s
Security | Sign check for Museum Finland took 0.16748428344726562s
Availability | Check URIs Dereferenciability for Museum Finland took 2966.9481978416443s
Completeness | Calculation of interlinking completeness for Museum Finland took 1.1831812858581543s
Reputation | Calculation of the PageRank for Museum Finland took 0.021401166915893555s
Interlinking | Calculation of Degree of Connection for Museum Finland took 2.765655517578125e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 6.508827209472656e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 1.9073486328125e-06s
Believability | Calculation of trust value for Museum Finland took 9.5367431640625e-06s
INFO | --- Analysis for FI-Museum took 3027.1855738162994s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.17584633827209473s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0006992816925048828s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 15.61514925956726s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.9879062175750732s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 32.18103384971619s
Interoperability | New terms check for Mapping Manuscript Migrations took 48.65449786186218s
Versatility | Languages check for Mapping Manuscript Migrations took 74.89435696601868s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 29.944249629974365s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.40226316452026367s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.17331337928771973s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.16833877563476562s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.17811846733093262s
License | MR license check for Mapping Manuscript Migrations took 0.17944741249084473s
License | HR license check for Mapping Manuscript Migrations took 1.7581043243408203s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.1645362377166748s
Understandability | Number of label check for Mapping Manuscript Migrations took 9.179269075393677s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.3460109233856201s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.15827584266662598s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.18294525146484375s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.17871451377868652s
Performance | Throughput check for Mapping Manuscript Migrations took 11.186527967453003s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.0665028095245361s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.17278265953063965s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.5024640560150146s
Interlinking | skos check for Mapping Manuscript Migrations took 0.17724156379699707s
Interlinking | skos check for Mapping Manuscript Migrations took 0.15941882133483887s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.17128944396972656s
Currency | Creation date check for Mapping Manuscript Migrations took 0.3430044651031494s
Currency | Modification date check for Mapping Manuscript Migrations took 0.16637921333312988s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 49.1052188873291s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.1631450653076172s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.1569371223449707s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.16992640495300293s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 10.955218076705933s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.4462335109710693s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.928009510040283s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.16324090957641602s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 23.697819471359253s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 16.107236862182617s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.640007495880127s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.6500401496887207s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.869943857192993s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.17465710639953613s
Security | Sign check for Mapping Manuscript Migrations took 0.17652249336242676s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1609.537559747696s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 1.1580076217651367s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.02139115333557129s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 3.0994415283203125e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 2.5510787963867188e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 1.9073486328125e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 8.821487426757812e-06s
INFO | --- Analysis for MMM took 2065.593579053879s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.22626948356628418s
Availability | VoID file availability check for Semantic Kalevala took 0.0002918243408203125s
Extra | Recovery of all triples for Semantic Kalevala took 8.963248014450073s
Performance | Total latancy measurement for Semantic Kalevala took 0.81685471534729s
Amount of data | Number of triples check for Semantic Kalevala took 0.48641204833984375s
Interoperability | New terms check for Semantic Kalevala took 2.1769120693206787s
Versatility | Languages check for Semantic Kalevala took 0.9229328632354736s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.3733859062194824s
Security | Check HTTPS for Semantic Kalevala took 0.4270920753479004s
Interpretability | RDF structures check for Semantic Kalevala took 0.4557170867919922s
Versatility | Serialization formats check for Semantic Kalevala took 0.18711137771606445s
Availability | RDF dump link check for Semantic Kalevala took 0.20656490325927734s
License | MR license check for Semantic Kalevala took 0.2032322883605957s
License | HR license check for Semantic Kalevala took 1.032994270324707s
Amount of data | Number of property check for Semantic Kalevala took 0.16916823387145996s
Understandability | Number of label check for Semantic Kalevala took 0.5284957885742188s
Understandability | URI regex check for Semantic Kalevala took 0.3443644046783447s
Understandability | Vocabs check for Semantic Kalevala took 0.18609237670898438s
Verifiability | Authors check for Semantic Kalevala took 0.172868013381958s
Verifiability | Publishers check for Semantic Kalevala took 0.2760148048400879s
Performance | Throughput check for Semantic Kalevala took 11.092741250991821s
Amount of data | Check the number of entities for Semantic Kalevala took 7.2479248046875e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.18615365028381348s
Interlinking | sameAs chians check for Semantic Kalevala took 0.1639270782470703s
Interlinking | skos check for Semantic Kalevala took 0.28986597061157227s
Interlinking | skos check for Semantic Kalevala took 0.16680049896240234s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.1826937198638916s
Currency | Creation date check for Semantic Kalevala took 0.354717493057251s
Currency | Modification date check for Semantic Kalevala took 0.33287715911865234s
Rep.Conc. | URIs length for Semantic Kalevala took 4.8028810024261475s
Interoperability | New vocabularies check for Semantic Kalevala took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.22284889221191406s
Accuracy | Check Functional Property for Semantic Kalevala took 0.15771079063415527s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.1650526523590088s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.891998052597046s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.29169154167175293s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.3907575607299805s
Consistency | Disjoint class check for Semantic Kalevala took 0.16896486282348633s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.7419216632843018s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.4069623947143555s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.4743103981018066s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.673734188079834s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.9038820266723633s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.21692776679992676s
Security | Sign check for Semantic Kalevala took 0.17300057411193848s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 2692.873520374298s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 1.1314494609832764s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.021364688873291016s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.430511474609375e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 2.1457672119140625e-06s
Believability | Calculation of trust value for Semantic Kalevala took 8.58306884765625e-06s
INFO | --- Analysis for Semantic-Kalevala took 2759.7192900180817s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.8897292613983154s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0006537437438964844s
Extra | Recovery of all triples for Smithsonian American Art Museum took 279.5411422252655s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.175271987915039s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5743184089660645s
Interoperability | New terms check for Smithsonian American Art Museum took 3.396611452102661s
Versatility | Languages check for Smithsonian American Art Museum took 28.913658380508423s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.6059753894805908s
Security | Check HTTPS for Smithsonian American Art Museum took 0.3764646053314209s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.6437575817108154s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.624394416809082s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.6528518199920654s
License | MR license check for Smithsonian American Art Museum took 0.6120481491088867s
License | HR license check for Smithsonian American Art Museum took 17.91279625892639s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5663504600524902s
Understandability | Number of label check for Smithsonian American Art Museum took 0.591240644454956s
Understandability | URI regex check for Smithsonian American Art Museum took 1.246264934539795s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.6087055206298828s
Verifiability | Authors check for Smithsonian American Art Museum took 0.6314349174499512s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.5938973426818848s
Performance | Throughput check for Smithsonian American Art Museum took 12.605480432510376s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 8.082389831542969e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.5995702743530273s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.584352970123291s
Interlinking | skos check for Smithsonian American Art Museum took 0.5925898551940918s
Interlinking | skos check for Smithsonian American Art Museum took 0.5678555965423584s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.5936784744262695s
Currency | Creation date check for Smithsonian American Art Museum took 1.210392951965332s
Currency | Modification date check for Smithsonian American Art Museum took 1.2949535846710205s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 105.00797414779663s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.5872316360473633s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 19.872727394104004s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.4982295036315918s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.298429727554321s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5766754150390625s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 4.175716400146484s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 101.86017417907715s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 2.6795616149902344s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 5.3648130893707275s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.9673092365264893s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.7160890102386475s
Security | Sign check for Smithsonian American Art Museum took 0.6180391311645508s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.6663782596588135s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.9776735305786133s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.021395444869995117s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.5735626220703125e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 2.1457672119140625e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 9.775161743164062e-06s
INFO | --- Analysis for Smithsonian took 709.1937699317932s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.30733752250671387s
Availability | VoID file availability check for Zeri Photo Archive took 0.0012593269348144531s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.29427170753479004s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.3828277587890625e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 1.1682510375976562e-05s
INFO | --- Analysis for Zeri-Photo-Archive took 6.405284643173218s
Availability | SPARQL endpoint availability check for Archives Hub took 20.50433087348938s
Availability | VoID file availability check for Archives Hub took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.25513577461242676s
Reputation | Calculation of the PageRank for Archives Hub took 0.021384000778198242s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.33514404296875e-05s
Believability | Calculation of trust value for Archives Hub took 8.106231689453125e-06s
INFO | --- Analysis for Archives-Hub took 54.74817395210266s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.4074151515960693s
Availability | VoID file availability check for Yale centre of British Art took 0.00040531158447265625s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.2762267589569092s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.020991802215576172s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.2874603271484375e-05s
Believability | Calculation of trust value for Yale centre of British Art took 7.3909759521484375e-06s
INFO | --- Analysis for Yale took 4.463870525360107s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 261.6955530643463s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.25523877143859863s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.021166563034057617s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.5735626220703125e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 8.106231689453125e-06s
INFO | --- Analysis for ADL took 536.6500482559204s
Availability | SPARQL endpoint availability check for MusicKG took 0.8314945697784424s
Availability | VoID file availability check for MusicKG took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for MusicKG took 0.6941866874694824s
Reputation | Calculation of the PageRank for MusicKG took 0.021187543869018555s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.3589859008789062e-05s
Believability | Calculation of trust value for MusicKG took 8.344650268554688e-06s
INFO | --- Analysis for MusicKG took 5.562557697296143s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.853844404220581s
Availability | VoID file availability check for CIDOC-CRM took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.26656532287597656s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.021360158920288086s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.4066696166992188e-05s
Believability | Calculation of trust value for CIDOC-CRM took 7.62939453125e-06s
INFO | --- Analysis for CIDOC-CRM took 3.928571939468384s
Availability | SPARQL endpoint availability check for Mondis took 0.3687105178833008s
Availability | VoID file availability check for Mondis took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for Mondis took 0.26039719581604004s
Reputation | Calculation of the PageRank for Mondis took 0.02111029624938965s
Interlinking | Calculation of Degree of Connection for Mondis took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.3828277587890625e-05s
Believability | Calculation of trust value for Mondis took 8.344650268554688e-06s
INFO | --- Analysis for Mondis took 3.2390787601470947s
Availability | SPARQL endpoint availability check for DigitalNZ took 2.863032341003418s
Availability | VoID file availability check for DigitalNZ took 0.0009634494781494141s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.3026115894317627s
Reputation | Calculation of the PageRank for DigitalNZ took 0.02080368995666504s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.3828277587890625e-05s
Believability | Calculation of trust value for DigitalNZ took 1.1682510375976562e-05s
INFO | --- Analysis for DigitalNZ took 6.732693195343018s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.21312832832336426s
Availability | VoID file availability check for Fondazione Zeri took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.7377655506134033s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.021113157272338867s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.3828277587890625e-05s
Believability | Calculation of trust value for Fondazione Zeri took 7.62939453125e-06s
INFO | --- Analysis for Fondazione-Zeri took 3.7600553035736084s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.4546833038330078s
Availability | VoID file availability check for Digital Public Library of America took 0.00043773651123046875s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.49865245819091797s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.02116227149963379s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.4066696166992188e-05s
Believability | Calculation of trust value for Digital Public Library of America took 7.3909759521484375e-06s
INFO | --- Analysis for Library-of-America took 4.430662631988525s
Availability | SPARQL endpoint availability check for Auckland Museum took 1.8016462326049805s
Availability | VoID file availability check for Auckland Museum took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.23952388763427734s
Reputation | Calculation of the PageRank for Auckland Museum took 0.021025896072387695s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.3828277587890625e-05s
Believability | Calculation of trust value for Auckland Museum took 7.152557373046875e-06s
INFO | --- Analysis for Auckland-Museum took 6.5685014724731445s
Availability | SPARQL endpoint availability check for National Library of Spain took 3.7672340869903564s
Availability | VoID file availability check for National Library of Spain took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.2586860656738281s
Reputation | Calculation of the PageRank for National Library of Spain took 0.021556854248046875s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.3828277587890625e-05s
Believability | Calculation of trust value for National Library of Spain took 1.2636184692382812e-05s
INFO | --- Analysis for BNE took 6.782820701599121s
Availability | SPARQL endpoint availability check for National Library of Korea took 1.8726637363433838s
Availability | VoID file availability check for National Library of Korea took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.2640562057495117s
Reputation | Calculation of the PageRank for National Library of Korea took 0.021101713180541992s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0008733272552490234s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.5735626220703125e-05s
Believability | Calculation of trust value for National Library of Korea took 6.67572021484375e-06s
INFO | --- Analysis for Korea-Library took 4.735372304916382s
Availability | SPARQL endpoint availability check for The State Russian Museum took 2.465426445007324s
Availability | VoID file availability check for The State Russian Museum took 0.000274658203125s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.2737433910369873s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.02090287208557129s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.430511474609375e-05s
Believability | Calculation of trust value for The State Russian Museum took 8.344650268554688e-06s
INFO | --- Analysis for Russian-Museum took 5.441957235336304s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.7484805583953857s
Availability | VoID file availability check for National Library of Scotland took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.28072357177734375s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.021094799041748047s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0008492469787597656s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 2.0742416381835938e-05s
Believability | Calculation of trust value for National Library of Scotland took 9.059906005859375e-06s
INFO | --- Analysis for National-Library-of-Scotland took 6.946058988571167s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.33807945251464844s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.2560865879058838s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.020729780197143555s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.3589859008789062e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 1.1920928955078125e-05s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 3.2908332347869873s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.20640325546264648s
Availability | VoID file availability check for OntoComedySources took 0.0007071495056152344s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.26462531089782715s
Reputation | Calculation of the PageRank for OntoComedySources took 0.02132558822631836s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 4.291534423828125e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.4066696166992188e-05s
Believability | Calculation of trust value for OntoComedySources took 7.867813110351562e-06s
INFO | --- Analysis for OntoComedySources took 3.8162596225738525s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.22133803367614746s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.2766869068145752s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.021089792251586914s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.3589859008789062e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 7.152557373046875e-06s
INFO | --- Analysis for OntoCeramic-2.0 took 4.33787202835083s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.18082499504089355s
Availability | VoID file availability check for SaintGall Ontology took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.25484561920166016s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.0211946964263916s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.4066696166992188e-05s
Believability | Calculation of trust value for SaintGall Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for SaintGall-Ontology took 3.095794200897217s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.8441815376281738s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.4080510139465332s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.020718812942504883s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.5020370483398438e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 8.106231689453125e-06s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 4.026247262954712s
Availability | SPARQL endpoint availability check for ICON took 0.27394890785217285s
Availability | VoID file availability check for ICON took 0.0004017353057861328s
Completeness | Calculation of interlinking completeness for ICON took 0.2793893814086914s
Reputation | Calculation of the PageRank for ICON took 0.02091073989868164s
Interlinking | Calculation of Degree of Connection for ICON took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for ICON took 1.239776611328125e-05s
Believability | Calculation of trust value for ICON took 1.2159347534179688e-05s
INFO | --- Analysis for ICON took 4.011754274368286s
Availability | SPARQL endpoint availability check for Polifonia took 0.3484170436859131s
Availability | VoID file availability check for Polifonia took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for Polifonia took 0.25860118865966797s
Reputation | Calculation of the PageRank for Polifonia took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.3113021850585938e-05s
Believability | Calculation of trust value for Polifonia took 7.867813110351562e-06s
INFO | --- Analysis for Polifonia took 4.355068922042847s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.2935187816619873s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0008258819580078125s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.29081082344055176s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.020980119705200195s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.4066696166992188e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 7.867813110351562e-06s
INFO | --- Analysis for Atlas-of-Paths took 3.9777557849884033s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.22013640403747559s
Availability | VoID file availability check for Music Note Ontology took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.26639485359191895s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.021283388137817383s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.52587890625e-05s
Believability | Calculation of trust value for Music Note Ontology took 8.821487426757812e-06s
INFO | --- Analysis for Music-Note-Ontology took 9.758897542953491s
Availability | SPARQL endpoint availability check for HaMSE took 0.2073376178741455s
Availability | VoID file availability check for HaMSE took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for HaMSE took 0.2789428234100342s
Reputation | Calculation of the PageRank for HaMSE took 0.021123170852661133s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.52587890625e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.430511474609375e-05s
Believability | Calculation of trust value for HaMSE took 8.106231689453125e-06s
INFO | --- Analysis for HaMSE took 6.813865423202515s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.08638930320739746s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.26282811164855957s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.021367311477661133s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.33514404296875e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 8.344650268554688e-06s
INFO | --- Analysis for FOod took 3.3551409244537354s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.7186000347137451s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0007627010345458984s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.29209446907043457s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.021538972854614258s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.52587890625e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 9.775161743164062e-06s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 5.115345239639282s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.565568208694458s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0005967617034912109s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.2561614513397217s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.2636184692382812e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 8.106231689453125e-06s
INFO | --- Analysis for ARIADNE took 5.746462106704712s
Availability | SPARQL endpoint availability check for MappingChange took 0.5496499538421631s
Availability | VoID file availability check for MappingChange took 0.0002646446228027344s
Extra | Recovery of all triples for MappingChange took 62.97007942199707s
Performance | Total latancy measurement for MappingChange took 1.6443395614624023s
Amount of data | Number of triples check for MappingChange took 31.870485067367554s
Interoperability | New terms check for MappingChange took 7.8021299839019775s
Versatility | Languages check for MappingChange took 37.94745349884033s
Interpretability | Number of blank nodes check for MappingChange took 16.144543170928955s
Interpretability | RDF structures check for MappingChange took 0.3147892951965332s
Versatility | Serialization formats check for MappingChange took 0.2904355525970459s
Availability | RDF dump link check for MappingChange took 0.2966189384460449s
License | MR license check for MappingChange took 0.29401183128356934s
License | HR license check for MappingChange took 5.2614850997924805s
Amount of data | Number of property check for MappingChange took 0.3075706958770752s
Understandability | Number of label check for MappingChange took 2.4082298278808594s
Understandability | URI regex check for MappingChange took 0.5756118297576904s
Understandability | Vocabs check for MappingChange took 0.29222679138183594s
Verifiability | Authors check for MappingChange took 0.3059196472167969s
Verifiability | Publishers check for MappingChange took 0.2952854633331299s
Performance | Throughput check for MappingChange took 11.652902126312256s
Amount of data | Check the number of entities for MappingChange took 7.367134094238281e-05s
Verifiability | Contribs. check for MappingChange took 0.2948460578918457s
Interlinking | sameAs chians check for MappingChange took 0.28609228134155273s
Interlinking | skos check for MappingChange took 0.295027494430542s
Interlinking | skos check for MappingChange took 0.2946655750274658s
Timeliness | dataset update frequency check for MappingChange took 0.2967402935028076s
Currency | Creation date check for MappingChange took 0.573868989944458s
Currency | Modification date check for MappingChange took 0.586554765701294s
Rep.Conc. | URIs length for MappingChange took 62.146448373794556s
Interoperability | New vocabularies check for MappingChange took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for MappingChange took 0.28957152366638184s
Accuracy | Check Functional Property for MappingChange took 0.2931528091430664s
Accuracy | Check Inverse Functional Property for MappingChange took 0.2902193069458008s
Accuracy | Check Empty annotation labels for MappingChange took 5.089674234390259s
Accuracy | Check White space in annotation for MappingChange took 0.4657466411590576s
Accuracy | Check Datatype consistency for MappingChange took 5.254043817520142s
Consistency | Disjoint class check for MappingChange took 0.28405237197875977s
Consistency | Check Misplaced properties for MappingChange took 9.846083879470825s
Consistency | Check Ontology hijacking for MappingChange took 30.690118312835693s
Consistency | Check Invalid usage of undefined classes for MappingChange took 1.3874120712280273s
Consistency | Check Invalid usage of undefined properties for MappingChange took 11.246456623077393s
Conciseness | Check Extensional conciseness for MappingChange took 3.113049030303955s
Conciseness | Check Intensional conciseness for MappingChange took 0.3049123287200928s
Security | Sign check for MappingChange took 0.29230213165283203s
Availability | Check URIs Dereferenciability for MappingChange took 2100.8526945114136s
Completeness | Calculation of interlinking completeness for MappingChange took 1.6148626804351807s
Reputation | Calculation of the PageRank for MappingChange took 0.021538734436035156s
Interlinking | Calculation of Degree of Connection for MappingChange took 3.552436828613281e-05s
Interlinking | Calculation of Centrality for MappingChange took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for MappingChange took 7.367134094238281e-05s
Interoperability | Check the re-using of existing vocabs for MappingChange took 1.9073486328125e-06s
Believability | Calculation of trust value for MappingChange took 1.1920928955078125e-05s
INFO | --- Analysis for mappingch took 2501.6184890270233s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.32512354850769043s
Availability | VoID file availability check for Odeuropa Ontology took 0.0003132820129394531s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.7243742942810059s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.021023988723754883s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.2874603271484375e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 1.239776611328125e-05s
INFO | --- Analysis for Odeuropa took 5.067422151565552s

--- Total time for analysis:375762.4375708103s ---
--- Total time for analysis:104.37845488078064 hours ---